Keep useful context together
A customer profile helps the team understand the relationship across purchases. Review identity, contact information and account access alongside the relevant order history.
RECOGNISE THE RELATIONSHIP
Bring customer profiles, order history and retention tools into the same commerce operation. Give your team context for the next conversation and a thoughtful reason for the next purchase.

BUILT AROUND THE WORK
A customer profile helps the team understand the relationship across purchases. Review identity, contact information and account access alongside the relevant order history.
The segment workspace supports defining audiences and criteria. Choose a business purpose first, then check membership rules and the quality of the information used.
Explore tiers, referrals and the customer balance workflow. Decide what earns a reward, how it is redeemed and what happens after cancellation or return.

THE BUSINESS BEHIND THE CAPABILITY
Customer context becomes useful when the team can connect the latest question to orders, service and relevant commercial permissions.
A matching segment does not automatically authorise a marketing message.
Define earning, redemption and correction rules alongside cancellations, returns and customer support.
INSIDE CUSTOMERS & LOYALTY
The customer record becomes useful when it supports the next interaction. Profiles, purchase history, account context and retention tools give staff a better starting point. Relevant segments and understandable reward rules make that context useful without turning every customer into a mailing-list entry.
Maintain relevant identity and contact details in the customer workspace.
Inspect the relationship through orders and the information relevant to service.
Define audiences with explicit criteria and review the resulting membership.
Configure an appropriate reward model and inspect its earning and redemption journey.
Define eligibility and the outcome of a referral within the configured programme.
Keep communication consent and provider configuration part of campaign execution.
FOLLOW THE BUSINESS JOURNEY
A returning customer asks about a previous purchase. Staff use the profile and relevant order history to understand the request. The marketing team defines a segment for a new collection, checks its membership and reviews communication permissions before preparing outreach. Rewards need a clear rule when an order is cancelled or returned.
| What happens | What the team needs to resolve |
|---|---|
| Records appear duplicated | Review identity and source information before merging or changing account relationships. |
| A customer should not receive marketing | Respect consent and channel preferences even when the customer belongs to an audience. |
| A reward needs reversal | Trace the qualifying purchase and apply the configured programme rule. |
CLOSER TO THE PRODUCT
Actual views supplied from Agora. Open each capture to inspect the controls and context. These views are separate from the interactive examples and their illustrative data.
SEGMENT RULES
Inspect audience identity, dynamic membership and matching rules in the supplied segment-creation interface.
FOLLOW THE PROCESS
Check identity, contact preferences and the relevant purchase history.
Build a segment or loyalty rule around a clear customer need.
Inspect eligibility, channel permissions and the customer-facing experience before launching a retention activity.
Operating walkthrough · Review the exact configuration for your business.
A CLEARER PICTURE
The product includes segment criteria and dynamic audience controls. Review the rule and resulting membership for your use case.
Plan inclusion and configuration differ. Confirm the available loyalty and referral functions.
Use appropriate consent, preferences and communication-provider settings. A customer record is not automatic permission for marketing.
BUILD WITH AGORA
Bring your business, your ambition and the questions that matter. Let’s explore what you can build with Agora.