How email works in Yaplet
Every email sent to a Yaplet-connected address creates a conversation in your inbox. Agents reply from inside Yaplet, and their replies go out as email to the original sender. Threading is automatic — the visitor's next reply comes back into the same conversation.
You have two kinds of address:
- A yaplet.io address — ready immediately, no DNS setup. Emails arrive at
[email protected]. Good for testing, or for internal use. - An address on your own domain — email arrives at and is sent from your own domain (for example
[email protected]). It needs DNS verification, but it looks entirely like you.
Files a customer attaches come along, for an email of up to 25 MB in total (a bigger one does not arrive, so ask for very large files by link). Pictures (JPEG, PNG, WebP or GIF), PDFs and videos (MP4 or WebM) show in the conversation like files sent in the chat — up to 10 files per email, PDFs up to 10 MB and pictures up to 25 megapixels. Tiny pictures such as signature logos are left out without a mention. Any other file (a ZIP, a Word or Excel file, or one past those limits) is not shown; instead a private line that only your team sees names it, for example Attachments not shown: invoice.zip, contract.docx, so you know to ask the customer for a PDF or a picture.
Option 1 — create a yaplet.io email address
- Go to Settings → Connections → Emailing. The Yaplet Emails view opens by default (the bar at the top also has Custom Domains).
- In the Create an address card at the top, type the part that comes before
@yaplet.io— for examplesupport-mycompanymakes[email protected]. There is no window to open: you type right there. - Next to it, pick the widget in the Select a widget dropdown. Incoming emails to the address are routed to that chat widget's inbox.
- Click Create. The address appears under Your addresses and works right away.
That's it. Share the new address with customers, or use it as the forwarding target for an address you already have (see below).
Option 2 — use your own domain
To send and receive as [email protected], verify your domain first.
- Go to Settings → Connections → Emailing → Custom Domains.
- Click Add domain (the first time, Add your first domain). In the Sending domain field, enter just the domain name — for example
yourcompany.com, with nohttps://orwww.— and click Next. - On the Add DNS records step, add the records Yaplet shows you to your domain's DNS provider. Copy all and Download zone file save you typing. The list is generated for your domain and marks which records are optional — only the three DKIM records are required. One of the optional ones is an MX record on the domain itself, and you only need that one if you want to receive email at that domain inside Yaplet. Then only the addresses you add in Yaplet get their mail there — mail to any other address on that domain is dropped, and its sender gets no bounce.
- Click I've added them. Yaplet then keeps checking your DNS by itself, so there is nothing to press while the records propagate. That is usually one to two hours, occasionally up to 48. When it says the domain is verified, click Done. You can close the window at any time: the domain's card keeps checking, and its Verify domain button brings the setup back.
- Once the domain is verified, open its card with Manage, go to the Emails tab and click Add email. Enter the part before the
@(for examplesupportfor[email protected]), choose the widget it delivers into and click Add.
Option 3 — forward an address you already have
If customers already write to [email protected], you can keep that address and route it through Yaplet without anyone noticing:
- Create a yaplet.io address (option 1 above).
- Verify your own domain and create a sender address on it (option 2 above).
- In your email provider (Gmail, Outlook, Zoho, cPanel and so on), forward
[email protected]to your yaplet.io address.
Forwarded email reaches Yaplet, and agents reply from [email protected] through your verified domain. Customers see no difference.
Yaplet answers email conversations
An email address belongs to a chat widget, and that widget belongs to a brand. If that brand has an active AI agent, and its Answers on → Email switch is on (Brand → AI agent → General — on unless you switch it off), Yaplet answers incoming email by itself, using everything on the brand's Knowledge screen — knowledge bases, documentation, uploaded files, website pages Yaplet has read and question-and-answer entries. Nothing has to be attached to the widget. The customer gets the reply by email within moments and can simply reply to carry on.
- Clearly marked as AI — every AI email carries a small footer saying the AI assistant wrote it.
- A "Talk to a human" button — the button sits in the email. One click opens a page where the customer confirms, and the confirmation moves the conversation to your team's queue for a human reply.
- Yaplet steps back for humans — once an agent replies, or a human has been asked for, Yaplet stays silent on that conversation.
- No robot loops — out-of-office replies, mailing lists and other machine-generated mail are recognized and never answered, and daily caps stop two systems replying to each other forever.
- Only proven senders get an automatic answer — Yaplet answers an email only when it could prove that it really came from the address in its From line: the email passed the DMARC check (the anti-forgery rule) of that address's domain. The same goes for workflow emails and other automatic notices. Email from a domain that publishes no DMARC rule counts as not proven. Any other email still becomes a normal conversation that your team can answer as usual. It shows a Sender not verified badge in its subject bar. The badge also shows when the newest email came from a different address than the visitor's, for example when a colleague of the visitor replies; automatic mail then stops until the visitor writes again. Hovering the badge says: "We could not prove that this email came from this visitor's address. The AI did not answer it." Emails Yaplet sends to an address that has not been proven this way also go through extra safety checks and have a daily limit.
When Yaplet offers a human is set on Brand → AI agent → Human hand-off — see Control when Yaplet hands off to a human.
Filter what gets in — and what Yaplet answers
Two settings on Brand → Brand settings → Email keep junk out of your inbox. Both apply to every address of that brand — yaplet.io and your own domain alike.
- Spam filter — on by default. Email flagged as spam, or coming from a provably forged sender, is discarded before it ever becomes a conversation: nothing appears in the inbox and nobody is notified. Emails carrying a virus are always discarded, whether this filter is on or off. Only definite spam verdicts are filtered — borderline emails always get through. Turn it off if you want everything to arrive.
- AI answer filter — off by default. When on, a quick AI check reads each incoming email before Yaplet replies and decides whether it deserves an answer at all — customer questions do; newsletters, receipts and cold sales pitches don't. A filtered email stays visible in your inbox, but Yaplet stays silent and your team gets no notification about it. In the Filter instructions field you can add your own rules in plain language — for example "Never reply to invoices. Always reply to guest post offers." If Yaplet does not answer email for this brand at all, the tab says so and this filter has nothing to filter.
A discarded spam email leaves no trace, so if a customer says their message never arrived, ask them to resend it — or switch the spam filter off while you investigate.
Email threading and the Email badge
Every outgoing email carries a unique reply-to address, so replies come back to the same conversation, and they go out as "Re: {the customer's subject}" so they thread into the customer's own mailbox. In your inbox the email subject becomes the conversation title, conversations that started from email carry an Email badge, and emailed replies appear as a single bubble with an email marker. Other conversations from the same email address are reachable from the sidebar. A new email joins an existing visitor only when that visitor was itself created by an earlier email, so someone who chatted on your website and later emails you shows up as a separate visitor created from the email. A reply to an existing email conversation still lands in that conversation.
What emailing replies costs
Emailing a reply to a customer is free with a paid plan and during the free 14 days. Without either, each emailed reply uses 1 credit of bought credit. If there is no credit, the reply is not emailed — it still shows in the conversation, with a warning to the person answering. An AI answer by email is paid like other AI work: from your free AI credits first, then bought credit, then your paid plan's usage billing. If nothing can pay, Yaplet does not answer and the email waits for your team in the inbox.
What's next
Ready to connect social channels? See Connect Instagram DMs or Connect Facebook Messenger.