Communication
Approvals where your team already is.
Connect your chat tool and agents can post notices and approval requests into the channels you nominate, and take a decision from a reply. It is a delivery route for approvals rather than a place agents read from.
What connects
Your team chat platform, through its API.
What crosses the boundary
- Into the agent: an approval decision, and who made it.
- Out of the agent: notices and approval requests in the channels you nominate.
- Never: your message history. This connection does not read channels.
The capabilities this exposes
- Post a notice
- Request an approval
Setting it up
- 1Authorise the connection and choose the channels.
- 2Decide which agents may post, and which notices go where.
- 3Confirm who may decide an approval from chat.
Permissions
Post to nominated channels, and read the decision on a request the platform posted. We do not request history access, do not read other messages and cannot post outside the channels you chose.
Jobs an agent can own once this is connected
- Send an approval request to the finance channel
- Post a notice when an agent hits a budget limit
- Tell a channel an agent paused and why
Where it stops
A decision taken in chat is recorded against the person who made it, and only people you authorised can decide. Chat is a convenience route, not the system of record — the approval itself lives in the platform, and an approval cannot be granted by anybody the platform does not recognise. Agents do not read your conversations here.
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]