Set up the email channel

Route support email into conversations, set sending addresses, verify your sending domain with DKIM and return path records, configure spam filtering, and learn how inbound email is matched to contacts.

JM
James Morton
Written By James MortonLast updated 15 days ago

The email channel turns support email into conversations in your inbox, so a reply from the inbox and a reply from the customer's mailbox land in the same thread. This article covers inbound routing, sending addresses, domain verification, spam filtering, and how Quackback decides which contact an email belongs to.

Configure email in Settings > Support > Channels > Email.

Inbound route

Your workspace has its own inbound address. The Inbound route card shows it ("Email to ... becomes a conversation").

  1. In Forwarding address, enter the address customers write to, for example [email protected], and click Set route.
  2. In your email provider, forward that mailbox to the inbound address shown on the card.

Each message that arrives becomes a new conversation, or threads into an existing one, and a contact is created if the sender is new.

Note: Self-hosted installs that cannot receive inbound webhooks can poll a mailbox instead. See Receive email over IMAP.

The Transport card shows how conversation email is sent and received. On a self-hosted install it reflects the server's environment variables, including whether Custom sending domains are available.

Sending addresses

Set the From address outbound replies use for each area: Support, Feedback, and Changelog. A support reply and a changelog announcement can then come from different addresses.

  1. Under Sending addresses, enter an address such as [email protected].
  2. Choose its area and click Add.

Each address's menu has Send test email, DNS records, SMTP override (send through your own mail server) and Remove.

Verify your sending domain

The first address you add on a domain also sets up that domain. Before mail can be sent as @yourcompany.com, publish the DNS records Quackback lists for it, so inboxes trust the mail instead of sending it to spam. Open DNS records on the address to see them.

On Quackback Cloud there are two records:

Record

Type

Name

What it does

DKIM

TXT

qb…._domainkey

Signs your mail and proves you own the domain

Return path

CNAME

qb-bounce

Handles bounces and aligns SPF with your domain

On a self-hosted install the return path may be an MX and a TXT record instead of one CNAME, depending on how the server is set up.

  1. Add each record at your DNS provider. Enter each name exactly as shown; most DNS hosts add .yourcompany.com themselves.
  2. Quackback checks automatically for 72 hours. While it waits, the domain shows Pending and the address shows "Waiting for yourcompany.com".
  3. When the records are found, the badge goes away and the address sends as itself. Keep the records published.

If the records aren't found after 72 hours, fix them and click Verify. Copy instructions copies the records as plain text, for whoever manages your DNS.

Tip: The DKIM value is longer than 255 characters. Most DNS hosts accept it as is. If yours cuts it short, use Copy as parts and paste the value it gives you.

Once a domain is verified, your workspace can use it elsewhere without another record: custom domains on it need only their routing record, and single sign-on can verify it with one click.

When a domain needs attention

If a record is later removed or changed, the domain shows Needs attention, the address says which record is wrong, and admins get an email. Replies keep working from your default address, or from this address with a risk of landing in spam, until the record is fixed.

If the email provider pauses sending from your workspace because of too many bounces or complaints, a notice on this page says so.

Spam filter and trusted senders

Inbound mail passes sender checks that do not need AI. Any address or domain on your Trusted senders list skips spam checks entirely.

When an AI model is configured, the AI spam filter switch also checks new email and Messenger conversations and moves obvious spam to Spam in the inbox. Filed spam is deleted after 30 days.

  • New workspaces start with the AI spam filter on.
  • Workspaces upgraded from 0.13 start with it off. Turn it on here if you want it.

Turning it off stops the model call. Trusted senders and the other sender checks keep working.

Auto-acknowledgement

Turn on Acknowledge new inbound mail to send a short confirmation when a new inbound email opens a conversation. It is never sent in reply to automated mail, mailing lists, or your own addresses.

The Email activity card lists recent sent and received mail, which helps when you are checking whether a message arrived.

How contacts are matched

A contact is keyed by email address. Anyone can forge the From address on an email, so before Quackback attaches a new inbound message to an existing contact, it checks whether the sending domain authenticated the message with DMARC:

  • DMARC pass: the message is trusted. If the address matches an existing contact, the conversation attaches to that contact. A new address creates a new contact.
  • Anything weaker than a pass (no DMARC record, a policy of quarantine or none, or an unreadable result): a new contact is created and marked unverified. Even if the address matches an existing contact, Quackback does not attach the message to that identity.
  • A hard DMARC failure under a reject policy: the message is held in Spam instead of reaching the inbox, so a teammate can review and release it.

This means two messages from the same address can end up on different contacts when the sender's domain does not pass DMARC. If a customer's mail keeps arriving as unverified, ask them to check their domain's DMARC setup.

Note: These checks apply only to new inbound mail. Replies inside an existing conversation are matched by that conversation's own reply address.

Mail from a sender your workspace has blocked is dropped.

Was this helpful?

Your feedback shapes what we write next.