Connect an email channel by forwarding a mailbox to its ingest address, reply from the inbox, and understand why email stays human-first.
Email is the one channel that is human-first by design. An inbound email lands in the Inbox flagged needs_human and waits for a person. There is no AI-replies toggle on email: a misfired automatic reply costs more in an async medium than a slower human one.
What you need
A mailbox you can set auto-forwarding on, and a chatbot to attach the channel to.
Connect
Add an Email channel on the chatbot's Channels tab. You are shown a forwarding address of the form:
ch-<channelId>@<your platform's ingest domain>Point your mailbox at it. With Gmail:
- 1Settings → Forwarding and POP/IMAP → Add a forwarding address, and paste
the channel's ingest address.
- 2Gmail sends a confirmation email to that address. It arrives **as a
conversation in your evoriqa inbox** — open it and click the confirmation link, or copy the code back into Gmail.
- 3Turn forwarding on.
A mailbox can only forward to an email address, never to a URL. That is exactly what the ingest address is for. A raw per-channel webhook also exists for setups that already run their own mail parser: POST to the channel's webhook URL with an x-channel-secret header and a body of { "from": "...", "text": "...", "name": "...", "id": "..." }.
Inbound mail is deduplicated on the provider's message id, so a retried delivery does not create two conversations.
Verify it works
Send an email to the mailbox you forwarded. Within a moment it should appear in the inbox as a waiting conversation, tagged as email, with the sender's address.
Replying
Agents reply from the inbox and the reply goes out through your workspace's configured sender. The channel's from name overrides the display name, so mail can appear to come from your brand rather than the platform's.
Attachments are supported on email replies — up to five files per message. See Claim and reply.
Troubleshooting
| Symptom | Check |
|---|---|
| No messages yet on the health chip | Forwarding is not on, or the confirmation step was never completed |
| Confirmation email never seen | It arrives as a conversation in your evoriqa inbox, not in your mailbox |
| Mail arrives twice | Two forwards point at the same channel |
| Replies not arriving to the customer | The workspace's outbound sender is not configured |
Inbound ingest depends on operator-side configuration of the ingest domain. If your deployment shows no ingest address at connect time, that is the piece that is missing — ask your operator, or your provider if you are a resold client.
Where to go next
Last updated