Notification Center
In-app alerts for platform users — callbacks, ops events, and retention
Notification Center delivers operational events to platform users (owners, admins, and teammates you assign). It is separate from Agent conversation Channels (voice, chat, widget, SIP), which connect end customers to an Agent.
What it is (and is not)
| Surface | Audience | Purpose |
|---|---|---|
| Notification Center | Dashboard users | Callbacks, assignments, ops alerts, deep links into Taliiq |
| Channels | End customers | Live conversations with an Agent |
Delivery uses transports (in_app, browser while the dashboard is open, optional customer SMTP). Transports never attach to an Agent and never own conversation routing.
Inbox behavior
- The bell shows an unseen count (capped at
99+). Opening the drawer marks loaded items seen — it does not mark them all read. - Use Unread filter, mark read/unread, or mark all read.
- Clicking an item marks it read and opens its relative deep link (for example
/contacts/...). - The dashboard polls every ~30–60 seconds. Browser notifications work only while the tab is open (no service worker / mobile push).
Callback requests
When Collect Contact saves a person and the visitor explicitly asked for a call, Taliiq publishes operate.contacts.callback_requested to owners/admins. Payload is minimal (display label + short summary) — never transcripts, recordings, or credentials.
Email (SMTP) transport
Connect Email (SMTP) under Manage → Integrations (capability notification_delivery). Taliiq uses your SMTP credentials for operational alerts — never Taliiq’s mail for customer org notifications.
Urgent/high events (such as callback requests) may send immediately. Routine events may batch for a few minutes.
Retention
Notification history follows the same organization log retention as Observe / Logs.
Changing retention changes notification history, interaction history, and recordings together. Expired data cannot be restored. Zero Data Retention / retention 0 stores no notification rows.
Contact provenance (ContactSource) stays in Postgres under Contacts compliance rules and is not the same as notification history.