MuninMunin
Sign inStart free
Channel · Email

The address you already publish.

Mail arrives at your own domain, gets authenticated, joins the thread it belongs to, and is answered from what your business actually knows. Nothing is migrated. Nothing is re-typed.

Start freeSet up the channel
  • Your own address
  • SPF · DKIM · DMARC on arrival
  • Threads stay threaded
  • Received and stored in the EU
How it goes

Three steps.
One of them is yours.

Mail in, answer out. Everything in between is the part nobody wanted to do anyway — and the one moment that needs judgement is still yours.

01

It arrives where it always did.

Your own address, on your own domain. Authenticated before anything reads it, and matched to the conversation it belongs to — so this is a reply, not a new ticket.

AJRuth Calderruth.calder@harbourgate-lettings.co.ukto support@yourcompany.com09:14
Custom SLA on the Pro plan?

Hi — we’re moving our support desk over in February, and legal has questions before they sign.

Does the Pro plan cover a custom SLA, or is that enterprise only?

SPFDKIMDMARCMatched to your conversation from November
02

It reads what you already know.

Your knowledge base, not the open internet. Every sentence it drafts traces back to something you published — and where you have published nothing, it says so instead of inventing an answer.

Munin agentworking
Searching your knowledge base
  • Service levels and uptime0.91
  • What’s included in Pro0.84
  • Contract exceptions0.77
Drafting a reply

Hi Anna — custom SLAs sit outside the Pro plan,but the uptime commitment applies to every plan.

Contract exception — this one goes to a human
03

You say yes. It replies as you.

Or it simply sends, on the topics you said could go unattended. Either way the answer leaves from your address, inside her thread. She sees your company — never a ticket number, never a queue.

Waiting for you2 min
Re: Custom SLA on the Pro plan?

Hi Anna — custom SLAs sit outside the Pro plan, but the uptime commitment applies to every plan, and an exception is worth a conversation before February. Shall I put you in front of someone on Thursday?

Cites: Service levels and uptime · Contract exceptions
Sent in-thread from support@yourcompany.com · 09:21
And then, without being asked
  • The activity is on Anna’s record
  • The conversation is filed under pricing
  • The fourth SLA question this month is drafted as a help article
What it takes

Three records and an afternoon.

The address your customers already know keeps working. You are changing where it lands, not what it is.

No migration, no dual-running, no export. If you turn it off, the mail goes back to where it went before.

  1. 01Point the mail somewhereOne MX record on a subdomain — or forward the address you already publish. Both arrive at the same place.
  2. 02Prove you're youDKIM and a return path on your own domain, so replies leave as your company and land in the inbox rather than the spam folder.
  3. 03Say who answersA paragraph of instruction and the knowledge it may quote. That is the whole configuration.
The honest part

What it won't do.

  • 01

    Send from a domain you haven't verified. Unauthenticated mail is held, never guessed at.

  • 02

    Answer from outside the knowledge you gave it. If the answer isn't there, it says so and asks you.

  • 03

    Act on a topic you marked supervised — those wait in the queue however long you take.

And it isn't alone

Email is one lane.

The same thread carries the chat widget, SMS and voice. Anna can write on Thursday, call on Friday, and never repeat herself — because it was never four systems.

See all four channels
  • Email
  • Widget
  • SMS
  • Voice
One customer record

Open source. Open protocol.
One stack, your terms.

Start free on CloudStar on GitHubRead the docs