Email & calling
Send from your domain without handing over the inbox.
If connecting a mailbox is more access than you want to grant, engagement can send through a delivery provider authenticated for your domain instead. The platform gains the ability to send and no ability to read.
What connects
A transactional or bulk email provider, authenticated against your sending domain.
What crosses the boundary
- Into the platform: delivery, bounce and complaint status for what it sent.
- Out of the platform: the messages it sent.
- Never: your inbox. This connection cannot read mail at all.
What this makes possible
- Sends newsletters and sequences at volume from your own domain
- Reports delivery, bounces and complaints so suppression stays accurate
Setting it up
- 1Verify your sending domain.
- 2Nominate the addresses motions may send from.
- 3Confirm the suppression list is shared with the platform.
Permissions
Send-only. There is no read capability on this connection, which is why some customers prefer it — a platform that cannot read your mail cannot leak it.
Where it stops
Send-only means no threading against replies and no reading of responses, so a motion using this alone cannot follow a conversation or stop on a reply. For sequences and agent engagement, connect a mailbox; this is the right choice for newsletters. Message content passes through the provider in the ordinary course of delivery, and the provider is named on the subprocessors page.
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]