Every team keeps a few facts that no inbox knows about: which order a question is about, which plan a customer is on, when their contract renews. Attributes give those facts a place. Open Desk settings → Attributes to add them. Only the owner or an administrator of the workspace can change the list; everyone who works in the Desk can fill them in.
Two kinds
- On each conversation - every conversation has its own value, like an order number or a region.
- On the customer - one value per customer, shown on every conversation with that customer. Change it in one conversation and it changes in all of them. This needs the customer's email address, so a chat visitor who never gave one cannot have customer details.
Types
| Type | Holds |
|---|---|
| Text | Up to 500 characters. |
| Number | A whole or decimal number. |
| Link | A web address starting with http:// or https://. |
| Date | A day, such as 2026-11-30. |
| List of choices | One of the choices you wrote down, one per line. |
| Yes or no | A checkbox. |
An attribute's name, kind and type are chosen when you add it; the name, help text and choices can change later. A workspace can have up to 30. Deleting one removes its values from every conversation and customer in the background.
Fill them in
Open a conversation. Custom details sits in the right column under the customer. Change what you need and choose Save details; an emptied field clears the value. Each change leaves a line in the conversation, such as "Anna set Order number to A-100".
Use them
- In rules. Automation and routing rules can look at an attribute: choose it in the list of things to check. Text and links can be compared with is, contains and is set; numbers with is greater than and is less than; dates with is before and is after; lists with is and is not; yes or no with is. For example: "when the customer's plan is Pro, set the priority to high".
- In the list. Under Filters, pick a custom detail and its value to see only matching conversations. Save the result as a view to keep it one click away.
- In the API and the MCP tools. Set values with
attributeswhen you update a conversation, filter the list withattribute=plan:Pro, and read the definitions from/desk/attributes. In rules the field is writtenattribute:<key>.
