Yaplet.io Emails
Set up instant email addresses with the @yaplet.io domain — no DNS or verification required.
What Are Yaplet.io Emails?
Yaplet.io emails are ready-to-use email addresses in the format [email protected] (for example, [email protected] or [email protected]). They let your team receive and reply to emails directly from the Yaplet inbox without any domain configuration.
What You Can Do With Yaplet.io Emails
- Receive emails from customers directly in your Yaplet inbox
- Let Yaplet answer automatically — when the widget you assign has an active AI agent, incoming emails from verified senders get an AI reply by email
- Reply to conversations from within the inbox — replies are sent from your yaplet.io address
- Automatic email threading — customer replies route back to the same conversation
- Assign to widgets so incoming emails route to the correct inbox
- Use in email automations for automated email responses
- Related email chats — see all conversations with the same email address from the chat sidebar
Creating a Yaplet.io Email
Open the Emailing settings
Go to Settings → Connections → Emailing. The Yaplet Emails view is open by default (the bar at the top of the page also has Custom Domains).
Find the "Create an address" card
At the top of the page, the Create an address card has an email field that ends in @yaplet.io, a widget dropdown and a Create button. There is no dialog to open: you type right there.
Enter your email prefix
Type the prefix for your email address in the field. For example, entering hello creates [email protected].
Prefix rules:
- Must be between 3 and 30 characters
- Lowercase letters and numbers only
- Must start and end with a letter or number
- Dots (
.), hyphens (-), and underscores (_) are allowed in the middle - Example valid prefixes:
hello,contact,sales.team,help-desk
Select a widget
Choose which widget this email should be associated with in the dropdown (Select a widget). Incoming emails sent to this address will appear in that widget's inbox. A widget is required.
Save
Click Create. The address appears under Your addresses and becomes active immediately — no verification step needed.
Blocked Prefixes
yaplet.io is a single address pool shared by every Yaplet customer, so a wider than usual set of prefixes is reserved on it — partly to keep the mail system working, partly so nobody can register an address that looks like it comes from Yaplet itself. Reserved prefixes are refused when you try to save:
| Blocked prefix | Reason |
|---|---|
no-reply | Reserved for system emails |
noreply | Reserved for system emails |
postmaster | Email infrastructure standard |
abuse | Email infrastructure standard |
mailer-daemon | Email infrastructure standard |
bounce | Email infrastructure standard |
admin | Reserved for administration |
About fifty more common words are reserved as well — among them support, help, news, api, docs, mail, status, www and yaplet — as is anything starting with reply-. Matching is exact, so combining words still works: support-acme is accepted even though support on its own is not.
@yaplet.io. On a custom domain you own there is nothing to collide with, so support@, news@, admin@ and the rest are all allowed — only the handful of mail-system prefixes (no-reply, noreply, postmaster, abuse, mailer-daemon, bounce) stay reserved there.Managing Your Emails
Your yaplet.io emails are listed under Your addresses, with their count in brackets. Each one is a row showing:
- The full email address, with a Copy address button beside it
- Active or No widget, with the date it was added
- A Widget dropdown showing where its mail is routed
You can change the widget assignment at any time by picking a different widget in that dropdown — the change saves straight away. To delete an email, open the More actions menu (the three dots) at the end of its row, choose Delete address, then confirm.
How Incoming Emails Work
When someone sends an email to your yaplet.io address, Yaplet automatically:
- Creates a visitor in your system using the sender's email address — or adds the email to the visitor that an earlier email from that address created. Someone who chatted on your website and later emails you appears as a separate email visitor, not on their website visitor. A reply to an existing conversation still lands in that conversation
- Creates a new chat in the inbox with the "Email" source badge, assigned to the widget linked to that email address
- Displays the email content as the first message in the conversation, with the email's attached pictures, PDFs and videos shown like files sent in the chat
- Stores the email subject and shows it as the conversation title in the inbox list and above the chat
These email-source chats behave differently from regular widget chats:
- Messages you send in an email-source chat are automatically delivered as email to the visitor, shown as a single message bubble with an email marker. In a website chat, by contrast, a reply is emailed only when you switch on Also send by email next to the send button
- The visitor does not need to have the chat widget installed. All communication happens over email
- The chat header shows an Email badge so you can identify email-source conversations at a glance
- Emailing a reply is free with a paid plan or during the free 14 days. Without either, each reply costs 1 credit of bought credit. With no credit it is not emailed: the reply still shows in the chat, and the person answering sees the warning "Not emailed — your plan doesn't include email replies."
- A workspace with no sending address of its own sends website-chat replies, chat transcripts and ticket emails from the shared address
[email protected], with the brand's name (or, failing that, the workspace's name) as the sender, for exampleAcme <[email protected]>
Email Attachments
Yaplet checks every file attached to an email by its content, not its name. It shows JPEG, PNG, WebP and GIF pictures, PDFs, and MP4 and WebM videos, within these limits:
- The whole email, attachments included, up to 25 MB — a bigger email does not arrive
- At most 10 files per email
- PDFs up to 10 MB
- Pictures up to 25 megapixels, shrunk to 4096 pixels on the longest side
- Tiny pictures, such as signature logos and spacer images, are left out silently
Any other file — a ZIP, a Word or Excel file, or one past the limits — is not shown. A private line, visible only to your team, names it instead, for example "Attachments not shown: invoice.zip, contract.docx", so you know to ask the customer for a PDF or a picture. The line is written in your brand's language, and the visitor never sees it.
AI Answers on Email
If the brand behind your email address has an active AI agent whose Answers on → Email switch is on (Brand → AI agent → General — on unless you switch it off), Yaplet answers incoming emails automatically — the same way it answers widget chats, drawing on that brand's knowledge: its knowledge bases, documentation, uploaded files, website pages and Q&A entries.
- The customer gets Yaplet's reply by email, and can simply reply to keep the conversation going with the AI
- Every AI email is clearly marked with a small footer noting it was written by the AI assistant
- Each AI email includes a "Talk to a human" button — one click plus a confirmation, and the conversation moves to your team's queue for a human reply
- Yaplet steps back permanently on a conversation as soon as an agent replies, and stays silent whenever a human has been requested
- Auto-generated mail is never answered — out-of-office replies, newsletters, and mailer-daemon messages are detected and skipped, and daily reply caps prevent email loops
- An AI reply is paid like other AI work — from your free AI credits during the free 14 days, then from the credit you bought, then from your paid plan's usage billing. If nothing can pay, Yaplet does not answer and the email waits for your team
Only Verified Senders Get an Automatic Answer
Yaplet answers an email only when our mail system, which receives your incoming mail, could prove who sent it: the email passed the DMARC check of the domain in its From address. DMARC is a rule a domain publishes so that receiving mail servers can confirm that a message claiming to come from that domain really did. Workflow emails and automatic notices follow the same rule.
An email whose sender can't be proven may have been sent in someone else's name, so it never triggers mail on its own. Any such email that reaches your inbox — from a domain that publishes no DMARC rule, or one that didn't pass it — becomes a normal conversation for your team:
- Nothing goes out automatically: no AI reply, no workflow email, no automatic notice
- The conversation shows a Sender not verified badge in its subject bar, with the tooltip "We could not prove that this email came from this visitor's address. The AI did not answer it." It also shows when the newest email came from a different address than the visitor's
- If the visitor's colleague replies from another address, automatic mail stops and the badge shows until the visitor writes again
- A human agent can reply as usual. Those replies count toward your organization's email sending limits
- The rule applies to every organization, and there is no setting to turn it off
Filtering Incoming Email
Two per-brand settings decide which incoming emails deserve attention at all. Both live on the Email tab of Brand settings, and both apply to every address routed to that brand's widget — yaplet.io and custom-domain addresses alike.
Spam filter (on by default)
Every incoming email is scanned before Yaplet processes it. If the scan flags it as spam — or the sender's address is provably forged — the email is discarded before a conversation is created: nothing appears in the inbox and nobody is notified. Emails carrying a virus are always discarded, whether the spam filter is on or off.
Turn the filter off for a brand if you want everything to arrive — for example, if you review pitches or bulk mail by hand. Only definite spam verdicts are filtered; borderline or uncertain emails always get through.
AI answer filter (off by default)
Yaplet normally replies to every email from a verified sender that reaches the inbox (as long as its Answers on → Email switch is on). With the AI answer filter enabled, a quick AI check reads each email first and decides whether it warrants a reply — customer questions, complaints and sales inquiries do; newsletters, receipts, automated notifications and cold vendor pitches don't.
- An email judged "no reply needed" stays visible in the inbox — it is not deleted — but Yaplet stays silent and your team gets no notification for it
- You can steer the decision with your own rules, written in plain language in the Filter instructions field — for example: "Never reply to job applications. Always reply to guest post offers."
- If the check itself ever fails, Yaplet answers normally — a broken filter never silences your support email
Email Threading
Yaplet automatically threads email conversations. Every outgoing email includes a unique Reply-To address tied to the specific chat. When the customer replies from their email client:
- The reply is routed back to the same conversation in your inbox
- The full email thread is preserved in the chat history
- This works regardless of which email client the customer uses (Gmail, Outlook, Apple Mail, etc.)
- Your replies arrive as "Re: {the customer's subject}" inside their original email thread — grouped with their own message in their mailbox, not as a separate conversation
Related Email Chats
When viewing a chat where the visitor has an email address, you can click the Related email chats button in the sidebar Actions section. This shows all other conversations in the same widget involving the same email address, letting you quickly navigate between related conversations.
Yaplet.io vs. Custom Domain Emails
Yaplet.io emails are ideal for getting started quickly, but they share the yaplet.io domain reputation with all other Yaplet users. For better deliverability, branding, and access to newsletters, consider setting up a custom domain.
| Feature | Yaplet.io | Custom Domain |
|---|---|---|
| Setup effort | None | DNS configuration required |
| Email branding | @yaplet.io | @yourdomain.com |
| Newsletter campaigns | Not available | Available (after verification) |
| Sender reputation | Shared | Your own |
| Warmup needed | No | Automatic, per provider |