Email & calling
Replies land where your team already works.
Connect your existing mailbox and engagement happens in real threads from your own address. This is not a separate outbound tool with its own inbox nobody checks — the conversation continues where the customer expects it to.
What connects
Your business email, through its provider's API.
What crosses the boundary
- Into the platform: the conversations assigned to a motion or an agent, with their history.
- Out of the platform: replies and drafts, in thread, attributed to the agent or person who sent them.
- Never: the whole mailbox, other people's mail, or folders outside the assignment.
What this makes possible
- Knows whether somebody replied, and what they said
- Keeps the whole conversation in one thread the customer recognises
- Stops automation the moment a human replies
Setting it up
- 1Authorise the mailbox as an administrator.
- 2Nominate the addresses agents may send from.
- 3Start with draft-only if you would rather read them first.
- 4Grant send as a separate decision when you are satisfied.
Permissions
Read access to assigned conversations and send access from the addresses you nominate. We never request permission to delete mail, alter a mailbox or change mail rules.
Where it stops
Draft and send are separate permissions, and most teams run on drafts for a fortnight first. Suppression and opt-outs are enforced by the platform rather than by an agent remembering to check. An agent cannot email anybody who is not already a contact of yours, and content arriving in a mailbox is treated as data — an instruction inside a customer's email is text the agent read, never a rule it follows.
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]