Connect your real mailbox by authorizing Sonta to use it — no new address, no password shared. Once connected, incoming mail becomes conversations on your contacts and outgoing mail is sent from your own address. Set the sending name, decide who on the team can send from it, and check its sending health before running campaigns.

Requirements: a role that can manage email connections, and access to the mailbox you are connecting. Gmail is supported today, with more providers on the way.

Steps

Start the connection for your provider and sign in to the mailbox when prompted. You are authorizing Sonta to use that mailbox — your password is never entered into Sonta or stored by it.
Grant access at the provider's consent screen. Approving returns you to Sonta with the mailbox connected.
Set the sending name. This is what recipients see as the sender — usually a person's name or the business name, not an internal label.
Decide who can use it. A mailbox can be kept to yourself or made available to the team for sending. Sharing grants the ability to send and manage from it — it does not open other people's conversations to everyone.
Send a test message to yourself or a colleague, and confirm it arrives from the right address with the right sender name.

What connecting changes

Two things start working at once. Incoming mail becomes conversations linked to the contacts it comes from, so correspondence sits on the record rather than in a private inbox. And outgoing mail — whether you write it or an automation sends it — goes out through this mailbox, so what customers receive comes from your address, not a generic system one. The messages you send repeatedly are best kept as templates.

Sending health

Sonta keeps a running picture of how your sending is performing — how much is going out, and how much is bouncing or being marked as spam — and turns that into a health rating for the mailbox. This matters more than it sounds: if the rating drops to unhealthy, automated sending from that mailbox is held back automatically rather than pushed through, and resumes once the picture improves. It is a protection, not a punishment — continuing to send from a mailbox with a bad reputation is what gets an address blocked.

A new or lightly used mailbox will show as having too little data to rate, which is normal. Check the rating before starting anything high-volume.

Before you disconnect

Automations that send mail are tied to the mailbox they send from. Check which automations use this mailbox before disconnecting it — disconnecting revokes the authorization, and anything relying on it stops sending. Reconnecting is a fresh authorization, not an undo.

Notes and limitations

Gmail is supported today; other providers are planned. Check what is available rather than assuming.
Sharing a mailbox grants sending, not reading. Who sees which conversation still follows who owns the contact.
Poor sending health pauses automated sends from that mailbox until it recovers.
The health rating counts automated sending — messages you send by hand are not fully reflected in it.
Disconnecting revokes access and stops any automation that sends through it.
Connect a mailbox you control on a domain you own; consumer addresses are fine for testing but poor for business sending.

How inbound mail becomes conversations, and who can see them, is in email and the inbox. Writing the messages you send often is covered in create an email template, sending from an automation in create and activate an automation, and the wider set of connected services in integrations overview.

Connect a mailbox