Manage customer records
Find customer records and connect each customer with their organization and support history.
On this page
Overview
Customers at #/customers is the directory of people who have tickets, portal logins, or chat/email identities. Each row links to Customer 360. You can filter by status, type, and organization, and bulk-archive if you have delete rights.
When to use this
Tickets need a stable customer record so portal IDOR isolation, organizations, and WooCommerce order context attach to one person instead of duplicate emails.
Where to find the controls
Sidebar Customers → #/customers. Duplicate detection defaults: Settings → System → Customers (#/settings/system/customers).
Who can make these changes
View: elegant_support_view_customer. Manage: elegant_support_manage_customer. Export: elegant_support_export_customer. Delete/archive: elegant_support_delete_customer. Merge and anonymize are separate caps.
Before you begin
Default customer status and duplicate rules live in System → Customers. Portal login behaviour is System → Portal plus Feature Manager customer_portal.
Follow these steps
- Search name or email.
- Filter organization or type.
- Open a row for 360.
- Use row menu Create ticket when you have create_ticket.
- Export or archive from the toolbar if permitted.
Settings reference
Name, email, organization, status, type, location, tags, ticket counts. Create form includes organization picker (search existing or create an org).
Example workflow
Two tickets arrive from the same email via form and chat. Duplicate detection suggests one customer; the agent merges nothing because they already share an id.
Good practices
Search organization first when you support B2B accounts. Export before anonymize or uninstall.
Important considerations
Verify portal access with separate test customers and the configured organization policy. Report access outside the intended scope to support.
If something does not work
Customer not found: they may exist only as a guest chat session until email is collected. Create/search 403: missing view_customer or manage_customer. Empty org filter: no organizations created yet.