Notifications
Review the agent's in-dashboard event feed and mirror it to Telegram with Alerts.
Review the agent's in-dashboard event feed and mirror it to Telegram with Alerts.
What appears here#
The agent's Notifications page is an in-dashboard event feed. It records these owner-facing event types:
| Type | Meaning |
|---|---|
| New customer request (lead) | The agent captured a visitor contact/intention record |
| Visitor asked for a human (handoff) | The conversation requested or triggered human follow-up |
| Visitor wrote while you were replying | A visitor wrote while you had taken the conversation over |
| New booking | A booking outcome was recorded |
| Support ticket | A support ticket was opened or updated |
| Action needs approval | A customer-confirmed change is waiting for your approval |
| Action needs attention | An approved action could not be completed |
| Connector needs attention | A messaging channel needs attention |
| Response SLA due | A sales response deadline is due |
| Concierge request | You asked the platform to connect a channel for you |
| Web page could not be added | A page an AI assistant asked to add could not be read |
Each item can show the event type, creation time, visitor name/email when available, and a short excerpt. An unread item is visually highlighted and contributes to the unread count.
The Alerts card on this page can mirror the feed to Telegram: select Send me alerts in Telegram and every new notification also arrives as a message from your own connected Telegram bot (or the Make Agent Fast alerts bot). Approval alerts carry Approve and Decline buttons. Alerts are off by default; the dashboard feed and owner email keep working either way. Marking an item read does not email a visitor, reply to a connector, change a lead, or unsubscribe anyone from an external provider.
Review and mark events#
- Open Notifications for the intended site.
- Prioritize handoffs and time-sensitive bookings.
- Open the related Conversations or Analytics context when identity and intent need confirmation.
- Select Mark read only after the responsible owner has triaged it.
- Use Mark all as read only when every visible/unread event has been intentionally reviewed.
- Select Load more for older pages.
Read state is an owner workflow aid, not proof that a visitor received follow-up. Track the actual follow-up in the approved system of record.
Protect visitor data#
Names, email addresses, booking context, and excerpts can contain personal data. Limit dashboard access, avoid copying events into broadly accessible chat rooms, and do not treat the excerpt as the complete consent/context record.
Deleting or marking a notification does not automatically remove the related lead, conversation, booking, provider record, or exported copy. Use the privacy/deletion workflow for data-subject requests.
Troubleshooting#
| Symptom | Check |
|---|---|
| Expected event is absent | Correct site, actual lead/handoff/booking completion, event time, and related conversation |
| Unread count seems stale | Refresh after the mark action and verify it reported success |
| Marking read did not contact visitor | Expected; this feed does not send follow-up |
| Older item is missing | Use Load more; the first page is intentionally bounded |
| Need alerts outside the dashboard | Turn on Telegram in the Alerts card; for email/Slack-style routing, use the Public API or signed webhooks |
For automation, consume the supported Public API resources or signed webhook events rather than scraping this dashboard.