Skip to content

Notifications

Workspace → Notifications. Each topic is subscribed separately, with its own recipients and its own cadence.

TopicWhat it sends
LeadsNew leads, with the interest and notes extracted from the conversation.
ConversationsA digest of what visitors asked and how it went.
Content gapsQuestions your website could not answer, ranked by how often they were asked.
InsightsWhat changed since the last one: volume, sentiment, topics moving.
SecurityRejections — rate limits, blocked origins, failed bot checks.
AnomaliesSomething is wrong: turns failing, or retrieval returning nothing.

Cadence is daily, weekly or monthly per topic. Recipients are a list of addresses, not tied to workspace membership, so a digest can go to someone who never signs in.

For most workspaces:

  • Leads → immediate, to whoever answers them. A lead that sits for a day is usually a lead that went elsewhere.
  • Content gaps → weekly, to whoever owns the website. This is the one that changes your site over time.
  • Anomalies → on. It is not a digest, it is an alarm.

Conversations and insights are worth reading for the first month while you are learning what the assistant is being asked, and worth turning off once you have stopped reading them.

The health check runs on its own and mails when something is actually broken: chat turns failing repeatedly, or retrieval coming back empty when it should not.

There is a cooldown between alerts on the same problem, so a bad hour produces one email rather than a hundred. It also means the absence of a second email is not evidence the first one resolved itself.

Rejections are logged whenever a request is refused: per-IP rate limits, per-conversation caps, over-long messages, a failed bot check, a blocked origin, or the daily budget being reached.

A slow trickle is normal on any public site. A spike is worth a look — see abuse limits for what each rejection type means and which dial changes it.