Skip to content

Email

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.

How a forwarded email reaches Evoriqa, and how an agent's reply is sent
How a forwarded email reaches Evoriqa, and how an agent's reply is sent

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:

  1. 1
    Settings → Forwarding and POP/IMAP → Add a forwarding address, and paste the channel's ingest address.
  2. 2
    Gmail 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.
  3. 3
    Turn forwarding on.
Note:

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.

Connect with the API

`POST /channels` creates the channel and returns the inboundSecret — the x-channel-secret value for the raw webhook above. Email is one of the two types with no required credentials; config is optional and only shapes outbound replies:

{
  "type": "email",
  "chatbotId": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
  "config": {
    "fromName": "Northwind Support",
    "subject": "Re: your message"
  }
}

Omit fromName and replies use the workspace's configured sender name; omit subject and they go out as "Reply from support". You still have to set up forwarding to the ingest address yourself — the API does not do that step.

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.

The email channel's connect form
The email channel's connect form

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

SymptomCheck
No messages yet on the health chipForwarding is not on, or the confirmation step was never completed
Confirmation email never seenIt arrives as a conversation in your Evoriqa inbox, not in your mailbox
Mail arrives twiceTwo forwards point at the same channel
Replies not arriving to the customerThe workspace's outbound sender is not configured

If no ingest address is shown when you connect the channel, inbound email is not configured for your account yet — contact Evoriqa support, or your provider if you are a client of an agency.

Where to go next

Last updated