Limits
The record holds the enquiry, the conversation, the preference, the transaction, and service. The follow-up stays outside it.
Customer Management
Create a unified customer record that connects enquiries, conversations, preferences, transactions, service, and relationship history.
Why the customer record matters
A customer is recorded once, with the enquiry, the conversation, and the preference on that record. Transactions and service stay there, and the relationship history stays with the customer.
Connected view
Keep the enquiry, the conversation, and the preference on one customer record.
Right context
Show the transaction and the service already on the profile before the next conversation.
Workflow data
Read the relationship history to see what the enquiry and the preference still need.
Shared pipelines
Hand the customer into the next conversation with the preference and the transaction still attached.
Relationship history
Keep service on the customer record, so the relationship history can be read back to the enquiry and the preference.
Related Features
Why Amarnex?
Handoffs
A recorded conversation goes on with the preference, and service returns with the transaction still attached.
Confirm first
Confirm the enquiry, the preference, and who may update the record before a customer is imported.
Limits
The record holds the enquiry, the conversation, the preference, the transaction, and service. The follow-up stays outside it.
Handoffs
A recorded conversation goes on with the preference, and service returns with the transaction still attached.
Confirm first
Confirm the enquiry, the preference, and who may update the record before a customer is imported.