Splice AI answers your support and sales email from your own documents, sending through Gmail, Microsoft 365 or your own SMTP, without asking to scan your mailbox.
Ways to send, Gmail, Microsoft 365, or your own SMTP server
Mailbox-scanning permissions needed, inbound arrives by forwarding
Languages replied in, matching whatever the sender wrote
Thread, replies land in the existing one rather than starting a new chain
Answer properly from your own material, thread like a human would, and stay out of the mail it has no business reading.
You point a forwarding rule at an address we give you. There is no request to read your whole mailbox, no invasive Google permission screen, and nothing scanning mail you never sent our way. Only what you forward reaches the agent.
Connect Gmail, Microsoft 365, or any SMTP server with presets for the common providers. Replies leave from the address your customer already knows, not a no-reply relay that lands in promotions.
Replies carry proper In-Reply-To and References headers and resolve the real thread, so they appear under the original conversation. The subject is never mangled with an extra Re: prefix, because the thread is what groups a conversation, not the subject line.
Banking and security-category mail is filtered out of the agent's reach by design. Your one-time codes and bank alerts are not material for an AI to be drafting replies from, even by accident.
Email follow-ups are scheduled in days rather than hours, because nobody wants a nudge ninety minutes after an unanswered email. They cancel the moment the person replies or a teammate steps in.
You can leave WhatsApp on autopilot and keep email entirely manual, or the reverse. Email tends to be where teams want a human read first, and that is a switch rather than a compromise.
Answering inbound and sending outbound share one system, so your merge fields, unsubscribes and sending identity are handled the same way in both.
Use the recipient's name and email, or any column from the file you imported, so a campaign reads like it was written for the person receiving it.
Every campaign renders a working unsubscribe URL rather than a placeholder, and anyone who opts out is skipped on future sends automatically.
Links are wrapped for tracking as the email renders, so there is no separate tracked-link control to remember to use on each one.
Before a campaign goes out, a test send requires a value for every merge field it detected, so a blank token cannot reach a real recipient.
Campaign HTML is cleaned on the way in and again before public rendering, and inline data URLs are refused rather than passed through.
Campaigns send through the integration attached to the right workspace and agent, rather than guessing at whichever account was connected first.
Plenty of B2B buying still happens over email, and a slow reply is the most common way to lose one.
Order, delivery and return emails answered in the thread, with refunds routed to a person.
Pricing and spec questions answered fast, so an enquiry does not go cold waiting for a rep.
The same twenty questions answered instantly during the season, with the unusual ones escalated.
Itinerary and availability emails answered while the customer is still comparing options.
Scope and quote follow-ups handled, so proposals do not die in an unopened inbox.
How-to questions answered from your docs, bugs and billing handed to the team that owns them.
Most email automation either wants your whole mailbox or sends from a relay address that lands in promotions. Neither is necessary.
How it reads your mail
Splice AI
Only what you forward to it
Typical email bot
Full mailbox access, usually
Your inbox today
You read it
Where replies come from
Splice AI
Your own address, in the original thread
Typical email bot
A no-reply relay address
Your inbox today
Your address
Threading
Splice AI
Proper headers, subject left untouched
Typical email bot
New chain, subject prefixed Re: Re:
Your inbox today
Correct
Sensitive mail
Splice AI
Banking and security categories filtered out
Typical email bot
Reads everything
Your inbox today
You use judgment
When it is unsure
Splice AI
Drafts it and waits for you
Typical email bot
Sends a canned reply
Your inbox today
Sits unanswered
Follow-ups
Splice AI
Scheduled in days, cancelled when they reply
Typical email bot
None, or badly timed
Your inbox today
Whenever someone remembers
What you pay for
Splice AI
Credits as the agent works, no seats
Typical email bot
Per seat, per month
Your inbox today
Salaries and slow replies
Set one forwarding rule from the address you already publish to the one we give you. Nothing else in your mail setup changes.
Gmail, Microsoft 365 or your own SMTP server, so replies leave from the address your customers recognise.
Start with every email held as a draft, read a few, then raise the trust once you can see how it answers.
No. Inbound works by forwarding: you set a rule that sends copies of the mail you choose to an address we give you, and only that reaches the agent. There is no permission request to scan your entire mailbox, which is deliberate, both for your privacy and because those permissions carry an approval burden we would rather not put you through.
Yes. Connect Gmail, Microsoft 365, or any SMTP server, and replies go out from the address your customer already recognises. Common providers have presets so you are not hunting for host and port settings.
Yes. Replies carry the correct In-Reply-To and References headers and resolve the real thread before sending, so they group under the original conversation in the recipient's client. The subject is left exactly as it was, with no extra Re: prefix bolted on.
Banking and security-category mail is filtered out of the agent's reach entirely. On top of that, refunds, chargebacks, legal threats and data-deletion requests force a human review draft, and anything the agent cannot ground in your documents is capped below the auto-send threshold so it can only ever sit as a draft.
Yes, and it is the setting we would suggest starting with. Auto-send is controlled per channel, so you can leave email fully manual while WhatsApp runs on autopilot, then loosen it once you have read enough drafts to trust the answers.
They are scheduled in days rather than hours, because a nudge ninety minutes after an unanswered email reads as desperate. A follow-up cancels itself as soon as the person replies, when the ticket is marked solved, and when a teammate takes the conversation over.
Yes. Import a CSV, use merge fields from any column in it, and every link is wrapped for click tracking automatically. Unsubscribe links are real working links rather than placeholders, and a test send will refuse to go out until every merge field it detected has a value.
When you send campaigns through a connected Resend account, a spam complaint is received over a signed webhook and that person is unsubscribed automatically, so they are never contacted again. To be straight with you about the limits: bounces are not processed yet, and we do not generate SPF or DKIM records for you, so your sending domain still needs to be set up properly on your side.
It detects the language and script of the incoming email and replies in the same one, covering English plus twelve Indian languages, in native script or romanised.
Yes. Email threads land in the same inbox and against the same lead as WhatsApp, Instagram, phone and website conversations, behind one knowledge base, so a customer switching channel does not have to explain themselves twice.
Bring your documents and the questions your customers ask. We’ll walk through it together.