1. Settings
  2. Support agent
  3. Context

Context

Choose what details the support agent can see about people while it works a ticket. Tools return only the fields selected here. Changes apply from the next run.

All changes saved
Replies in public channels are visible to everyone in the channel. Responses could include any context the agent uses.
Identity
OktaOkta
Connected
Profile fields from your identity provider about the requester, and anyone a request is about. When a field is toggled off, the support agent can't see it.
Field
Key
Sample value
Visible to agent
NamenameRiley Chen
Emailemailriley.chen@acme.com
Display NamedisplayNameRiley Chen
TitletitleSenior Account Executive
TeamIf in your profileteamEnterprise Sales
DepartmentdepartmentSales
ManagermanagerDana Okafor
Manager IDmanagerId00u1a2b3c4d5e6f7g8h9
Is a People Leader?If in your profilePLfalse
Cost CentercostCenterCC-4120
Office LocationIf in your profileofficelocationChicago HQ
CitycityChicago
StatestateIL
Country CodecountryCodeUS
Start DateIf in your profilestart_date2023-04-17
Each provider returns different fields, so each connected provider has its own table. A field in more than one table has one setting. Access rules and approver routing still read every profile field. This only changes what the agent sees.

Add custom field

Add a key from the user profile in your identity provider. The agent can't see the new field until you turn it on.

In Okta, open Directory → Profile Editor, then the user profile. Use the attribute's variable name.

The name of the field on this page. The agent sees the key and its value.