Send and receive email through a connected inbox, threaded with the customer's other conversations.
kind: "email" is a connected inbox (for example support@yourcompany.com). Mail sent to it
arrives in Gauge as conversations; replies go out from it and thread correctly in the customer's
mail client.
What it can do
| Text | Yes |
| Attachments | Not yet over the API |
| Start a conversation | Yes: address the recipient by email address |
| Campaigns | Yes |
| Delivery | immediate, or queued when your workspace uses the newer email pipeline (see capabilities.delivery) |
Threading
Replies keep the email thread: Gauge sets the standard In-Reply-To and References headers, so
the customer sees one conversation in their mail client, and their answer comes back into the same
Gauge conversation.
Who the mail is from
How a reply is sent depends on how the inbox is connected:
| Connected as | From | Replies come back via | Signed by |
|---|---|---|---|
| A mailbox (IMAP/SMTP, Gmail or Microsoft 365) | The mailbox itself, with the connection's display name. A copy lands in its Sent folder. | The mailbox (Gauge reads it) | Your mail provider, as for any mail you send |
| A forwarding address (no mailbox) | Gauge's shared sending address; your inbox address is the Reply-To | The Reply-To | Gauge's sending domain, not yours |
Gauge does not yet sign mail with your domain's DKIM key. If recipients must see your own domain as the sender, connect the inbox as a mailbox. Either way the threading headers are kept, so the customer sees one conversation.