People & authority
An approval needs a name, and names change.
Roles, responsibilities and approval authority come from your people records, so a discount request routes to whoever currently holds that authority rather than to whoever was named when the motion was built.
What connects
Your people, role and responsibility system, through its API.
What crosses the boundary
- Into the platform: roles, teams, responsibilities and approval authority.
- Out of the platform: nothing.
- Never: salary, performance, assessment or absence data. Not exposed to any agent, on any plan.
What this makes possible
- Routes an approval to whoever currently holds the authority
- Sends a handoff to the person who actually owns the relationship
- Keeps the commercial authority ladder correct as people change role
Setting it up
- 1Authorise a read-only connection.
- 2Confirm the commercial approval authority mapping.
- 3Confirm who owns which accounts.
Permissions
Read-only, and limited to role, responsibility and approval authority. Salary, performance and assessment data is not requested and is not available to any agent under any configuration.
Where it stops
Read-only: nothing here changes a role or an authority. Deriving approvals from your own records keeps them correct as people move, and it also means an out-of-date people record produces misrouted approvals — the platform cannot tell the difference. This is also not a route to monitoring anybody: no view ranks people by activity volume, and using this data that way breaches the acceptable use policy.
People & authority
Others in this category.
Make sure every opportunity gets a next action.
Let AI handle the repetitive engagement, keep follow-up moving, and bring your team in when a customer needs a real conversation.
Agents identify themselves on every call · Nothing commits without you · [email protected]