Review a customer in Customer 360
Use a consolidated customer profile to understand previous tickets, activity and available commerce context.
On this page
Overview
Customer 360 at #/customers/{id} is the single profile: contact fields, organization, tags, ticket history, and optional WooCommerce orders when WooCommerce is active and you have elegant_support_view_commerce.
When to use this
Agents need order and ticket history in one place before they reply. It also prevents opening the wrong person when emails look similar.
Where to find the controls
From #/customers, Inbox customer link, or ticket workspace customer card. Edit uses the same form fields as create.
Who can make these changes
elegant_support_view_customer to open. elegant_support_manage_customer to edit. Merge / anonymize / export / delete require their named caps.
Before you begin
Which fields appear on create/edit follows System → Customers plus tags. Commerce tiles appear only when WooCommerce is available — the helpdesk works without it.
Follow these steps
- Open the profile.
- Confirm email and organization.
- Scan open tickets.
- Create a ticket if needed.
- Edit profile or tags.
- If WooCommerce is present, read recent orders before promising a refund.
Settings reference
Name, email, phone, organization, company, location, status, type, tags, ticket list, activity, optional order table. organization_id is a reference, not free text only.
Example workflow
A billing question: 360 shows the customer, org “Acme”, three tickets, and a WooCommerce order On hold. The agent replies on the existing ticket instead of creating a duplicate.
Good practices
Use 360 before merging. Anonymize is irreversible from the customer’s perspective — export first.
Important considerations
Never grant portal users this screen. Internal notes on related tickets stay off-limits to customers and to Chat AI.
If something does not work
404 customer not found: wrong id or deleted/archived record. Orders missing: WooCommerce inactive, feature off, or missing view_commerce — not an AI problem.