MuninMuninA script tag on your site. It answers out of your own documentation while the question is still in their head — and when it should not answer, it says so and fetches a person by name.
Nobody is waiting on a reply, because the reply is already there. Your attention goes to the question the agent decided it should not settle alone.
No form, no email address, no ticket number. The widget knows which page they are on and, if they are signed in, who they are — so the question arrives with its context already attached.
Is Pro per seat or per organisation? We’re 40 people but only 6 would ever use it.
14:02Your pricing page, your docs, your knowledge base. Every answer traces back to something you published — and the retrieval happens in the second between their question and the reply.
Pro is per seat — you would pay for the six,not the forty. Volume pricing starts at twenty.
A discount it cannot authorise, an account it cannot see, a complaint that needs a person. It says so plainly, gathers what a colleague will need, and puts a name on it — rather than improvising something you would have to retract.
Pro is per seat, so you would be paying for the six people who use it — not all forty.
Plans and what is in them · Seats, users and billingCan you do anything on the price if we commit for two years?
That one is not mine to answer, honestly. I have asked Ida on our side to pick it up — she will email you today.
It goes on the page the way your analytics does. Nothing about your site has to change around it.
It loads after everything else on the page and does nothing at all until it is opened. Remove the tag and it is gone — there is no other trace on your site.
Pretend to be a person. Asked directly, it says what it is.
Answer from outside the knowledge you gave it. Where that runs out, it says so and fetches someone.
Speak about an account it cannot verify. Without a signed identity it stays on the general answer.
The same thread carries email, SMS and voice. Someone can ask here at two, email at four, and never introduce themselves twice — because it was never four systems.
See all four channelsOpen source. Open protocol.
One stack, your terms.