Chatbot pushes
This page is the channel-level reference for chatbot pushes. The cross-cutting “why this matters” view lives at Chatbot-activity push.
Channel: Customer requested human
The headline channel for chatbot operators. Critical-priority by default.
What triggers
- Customer explicitly asks to talk to a human.
- Bot escalates because it can’t answer (configurable threshold per bot).
- Customer is detected as escalating in tone (frustration, anger, repeated dissatisfaction).
Banner format
🆘 Customer escalation: Bot X
"I want to talk to a human about my refund."
Tap to claim and respond.Configurations
- Per-bot subscription — agents subscribe to specific bots.
- First-claim wins — push includes a “Claim” action; first agent to tap takes the conversation.
- Override quiet hours — opt-in (defaults to yes for this channel because timing matters).
- Roles — only members with
chatbot.respondpermission see the push.
Tap action
Opens the conversation in real-time-agent-chat mode (also coming soon — see Real-time agent chat).
Channel: Agent auto-update
When an AI agent makes an automated change, push notification gives you visibility before the change has unintended downstream effects.
What triggers
- Bot re-trained itself on new content (e.g., picked up new pages from a watched website).
- Bot added auto-imported KB chunks (e.g., from a stakeholder-shared doc).
- Bot’s prompt was auto-tuned because of low CSAT or high deflection.
- Bot added a new linked tool / integration.
Banner format
🤖 Bot X auto-updated
12 KB chunks added from "supplier-spec-2026.pdf".
Tap to review.Configurations
- Per-event-type toggle — quiet on minor (KB chunk additions); loud on big (tool additions).
- Per-bot toggle — quiet bots that update frequently if you trust them; loud on bots you’re testing.
Tap action
Opens the bot’s auto-update audit log.
Channel: Workflow status
For chatbot platforms with workflow-based automation, every workflow run can push status events.
Sub-channels
| Sub-channel | What it pushes | Default |
|---|---|---|
| Started | Workflow begins | On |
| Step transitions | Each step completes | Off (verbose) |
| Finished | Success or failure | On |
| Stuck | Step taking longer than expected | On |
Banner format
Started:
⚙️ Workflow started: Lead enrichment
For new contact "Jane Doe (Acme)".Finished:
✅ Workflow finished: Lead enrichment
Status: success. Duration 4m 12s.
Tap for details.Stuck:
⚠️ Workflow stuck: Daily KPI digest
Step 3 has been running for 15 min (avg: 2 min).
Tap to investigate.Configurations
- Per-workflow subscription — subscribe only to the workflows that matter to you.
- Sub-channel toggles — fine-grained on/off.
Tap action
Opens the workflow run’s detail view.
Status
| Channel | Source events | Push bridge | Mobile UI | Notes |
|---|---|---|---|---|
| Customer escalation | ✅ Already produced | In dev | In dev | First to ship |
| Agent auto-update | ✅ Already produced (audit log) | In dev | In dev | Depends on per-event-type filtering |
| Workflow status | ✅ Already produced (workflow events) | In dev | In dev | Sub-channel granularity is the work |
The chatbot platform already produces every event listed here. The work is on the push bridge — the service that turns “event happened” into “deliver to specific devices that subscribed to this channel.”