Chatbot-activity push notifications

Chatbot operators face a different push challenge from sellers: not “is something selling?”, but “is something running?” The three channels below are the chatbot-side equivalent of the Amazon-activity push roadmap.

What this will let you do

A real-time pipe from your chatbot’s runtime into your phone. The three channels:

1. Customer requested a human

The most actionable push for any chatbot operator. When a customer asks to talk to a human (explicitly or because the bot escalated), the agents subscribed to that bot get pushed.

Configurable:

• Per-bot subscription — agents subscribe to specific bots, not all of them.
• Quiet hours — but escalations override quiet hours by default (this is the channel where seconds matter).
• First-to-claim wins — the push includes a “Claim” action; the first agent to tap takes the conversation.
• Roles — only members with the chatbot.respond permission get the push.

2. Agent auto-update

When an AI agent makes an automated change during creation or runtime, the push fires:

• “Bot X re-trained itself on 5 new website pages.”
• “Bot X added 12 new KB chunks (auto-imported from a spec doc).”
• “Bot X’s prompt was auto-tuned because of low CSAT.”

Why push this? Auto-updates can drift the bot in unexpected ways. Operators want to know as they happen, not at the next weekly review.

Configurable:

• Per-event-type toggle — keep KB additions silent, only push for prompt changes, etc.
• Per-bot toggle — quiet bots that update frequently if you trust them.

3. Live workflow status

When a workflow runs on the chatbot platform, get live status pushes:

• Workflow started — the bot kicked off a multi-step automation (e.g., “Lead enrichment workflow started for new contact”).
• Workflow step transitions — at each major step (verbose; off by default).
• Workflow finished — success or failure, with a summary.
• Workflow stuck — if a step is taking longer than expected, push to alert.

Configurable per-workflow. Most operators turn on Started and Finished; advanced operators add Stuck for the workflows that have a history of getting stuck.

How it’ll work (preview)

The pipeline:

1. Chatbot platform event (escalation, auto-update, workflow event) lands on Hilal’s backend.
2. Channel rules decide who, if anyone, gets pushed.
3. Expo Push delivers to registered devices.
4. Tap the push → deep links into the relevant screen — the conversation, the bot’s auto-update log, or the workflow run.

Mock examples

Customer requested a human:

🆘 Customer escalation: Bot X “I want to talk to a human about my refund.” Tap to claim and respond.

Agent auto-update:

🤖 Bot X auto-updated 12 KB chunks added from “supplier-spec-2026.pdf”. Tap to review.

Workflow status:

⚙️ Workflow finished: “Lead enrichment” Status: success. Duration 4m 12s. Tap for details.

Workflow stuck:

⚠️ Workflow stuck: “Daily KPI digest” Step 3 has been running for 15 min (avg: 2 min). Tap to investigate.

Status

• Push token registration: ✅ in place.
• Escalation events: depend on the chatbot platform’s existing handoff signal — already produced; the push bridge is what’s new.
• Agent auto-update events: depend on the chatbot platform’s auto-update audit log — already produced.
• Workflow events: depend on the chatbot platform’s workflow execution events — already produced.
• Beta: ships with the rest of the push roadmap, in the same major release as live agent conversations.

Related articles