Customer data
The agent knows who it is dealing with.
Connecting your customer system lets agents read who a customer is, what terms they are on and who owns the relationship — and record what they did about it. It does not give an agent your customer database.
What connects
Your CRM or customer management system, through its own API and its own permission model.
What crosses the boundary
- Into the agent: name, status, terms, assigned owner, account age — for customers inside the agent's assigned scope only.
- Out of the agent: activities it logged, attributed to the agent's identity.
- Never: bulk export of the customer base, or customers outside the agent's scope.
The capabilities this exposes
- Read a customer
- Find a customer
- Record an activity
Setting it up
- 1Authorise the connection as an administrator.
- 2Choose which customers are in scope — all, a team's, or a segment.
- 3Grant individual capabilities to individual agents.
- 4Review what each agent can reach before deploying it.
Permissions
We request read access to customers and write access to activities. We do not request permission to delete a customer, change an account owner or export the database — those are refused at the platform even where your system would allow them.
Jobs an agent can own once this is connected
- Follow up every new lead within ten minutes
- Flag accounts that have gone quiet before renewal
- Attach customer context to an escalated conversation
Where it stops
An agent sees what the connection's scope allows and nothing more. It cannot infer a customer it has no access to, and a search returns only in-scope results — so a search cannot be used to enumerate the customer base. Changing the account owner is not available to any agent.
Give AI a job.
Build an agent, choose what it can access, define what it may do, and deploy it to work safely across your business.
No code required · Full SDKs and API · Stop any agent instantly · [email protected]