Email in Cove is a mailbox. It is not Gmail OAuth, and it is not “paste a webhook and hope.”
What a founder does
- Open Channels → Email.
- Save the public address customers already write to (
help@yourdomain.com). - Copy the Cove receive address (
{your-slug}@inbound.coveinbox.co). The same address is on Settings → Organization. Save Email so Cove starts ingesting mail to that address. - In Google Workspace or Microsoft 365, forward that public inbox to the Cove address (or add it as an alias).
- Send a test from a mailbox you control. The thread should appear in Inbox within a minute.
Desk replies go out through Resend. Reply-To is the Cove address (plus a conversation tag), so the customer’s next reply lands on the same thread — including after you resolve it.
What this is not
- Not Gmail OAuth. A Google refresh token without a reviewed inbox poll is not a mailbox. That connect stays coming soon.
- Not required: a per-workspace signed webhook. Use that only if you cannot forward mail and you are building your own poster.
If mail does not land
The receive domain needs MX at Resend or the Cove inbound-mail worker. That is a one-time operator step (see docs/INBOUND_EMAIL.md). Founders only forward.
Was this helpful?
If a step is wrong, write help@coveinbox.co.
Related
Shared inbox
Work the shared inbox
Open, pending, resolved, spam, snoozed. Assign a person, leave an internal note, insert a quick reply. ⌘ Enter sends.
Shared inbox
Resolve a conversation and CSAT
Resolve ends the widget thread and can ask for a 1–5 rating. A new message after that is a new conversation.
Shared inbox
Email campaigns
Email a People segment from Broadcasts. Sequential send, cap 200. RFC 8058 one-click unsubscribe.
Put the widget on the site
Fourteen-day trial. Per workspace. Conversations are unlimited.