Get an email the moment a visitor asks for a human, the moment your AI hits a question it can't answer, and a Monday digest that summarises the week — so nothing slow-rots in a dashboard nobody opened.
A visitor on your site clicks "talk to a human." They write out their question, hit submit, and wait.
Hours pass. Maybe a day. Nobody on your team logged into the dashboard, so nobody saw the ticket. By the time someone notices, the visitor is gone — or worse, they've told a friend about the experience.
The same thing happens with unanswered questions. Your AI hits a knowledge gap, declines to answer, and the question goes into a queue. The queue grows. Patterns emerge — fifty people asking variations of the same thing — but nobody sees the pattern because nobody is looking.
This feature solves both problems with the simplest possible mechanism: email.
Three notifications, each with a clear job:
Instant ticket alerts. A visitor submits the human handoff form. Within seconds, an email lands in your team's inbox with their name, their message, and a one-click link to respond. No dashboard required.
Instant unanswered-question alerts. Your AI declines to answer a new question. You get told. Now you can add the missing knowledge base entry before the next ten people hit the same wall.
Weekly digest. Monday morning, a single email summarising the week — tickets received, new gaps in your knowledge base, and the questions visitors asked most often. Thirty seconds to read, week of context.
Every minute of ticket delay compounds. A visitor who escalated to a human did so because the AI wasn't enough. They're already mildly frustrated. The longer they wait, the more frustrated they get — and the more likely they are to never come back. Instant email cuts response time from "whenever someone checks the dashboard" to "right now."
Unanswered questions are your roadmap. When your AI says "I don't know," it's telling you exactly what content is missing. A visitor just did the work of identifying a gap in your knowledge base. If you don't hear about it, you can't fix it. Each question that surfaces this week is a fix that prevents fifty failed conversations next month.
Patterns only emerge if you're looking. One unanswered question is noise. Twenty variations of the same question is a signal — a missing FAQ, a confusing product page, a feature people don't know exists. The weekly digest surfaces the top questions by frequency so the signal is impossible to miss.
You configure recipients once. By default, the organization owner gets every notification. You can add a shared inbox like support@yourcompany.com, a team lead, or as many additional addresses as you need. Each notification type can be turned on or off independently.
When an event happens, the system fires off the email in the background — your visitor never waits on email delivery. The email contains everything your team needs to act:
Right now, staying on top of widget activity means logging into the dashboard. That works when one person does it religiously. It fails the moment that person takes a day off, switches teams, or forgets.
Email is durable. It sits in an inbox until someone reads it. It can be forwarded, archived, searched, replied to. It works with whatever support workflow your team already has — a shared inbox, a ticketing system, a Slack integration that watches for new mail. You don't need to teach your team a new tool. They already know how to handle email.
This feature is planned. When it ships:
The mechanism is plain text email — no fancy HTML templates, no third-party services, no extra integration work for you. Email shows up. Your team responds. That's the whole product.