Chatbot management

A dedicated mobile section for managing your chatbots. Today, you can use the AI tools (chat, notes, prompts) but you can’t directly edit a bot’s settings or view its activity feed from the phone — that’s all on the web. This page lays out the full plan.

What this will let you do

• Bot switcher — when you have multiple bots, pick the active context for AI features (already partially in place via Pick your chatbot).
• Bot detail page — open a bot to see:
  • Its current settings (name, description, type, status).
  • Live activity feed (conversations in the last 24 hours, ratings, escalations).
  • Performance metrics (volume, response quality, CSAT).
  • Linked knowledge sources.
  • Linked integrations.
• Quick edits — toggle the bot on/off; edit description; change tone; enable/disable specific channels.
• Activity drill-down — tap any conversation in the activity feed to read the thread.
• Cross-link to web for deep edits — when you need to retrain on a new website, you’ll get deep-linked to the web flow.

How it’ll work (preview)

A new top-level section in the drawer (visible only to Chatbot subscribers): My Chatbots.

My Chatbots
├── Bot 1 (Active)
│   ├── Settings
│   ├── Activity feed
│   ├── Knowledge sources
│   ├── Conversations
│   └── Performance
├── Bot 2
│   └── ...
└── + Create a new bot (deep links to web)

Each bot’s home page is read-mostly; quick toggles for the most-used settings are inline.

What’s intentionally NOT in scope (for now)

The mobile app won’t try to be the full web product. Specifically excluded for the foreseeable future:

• Building a new chatbot from scratch — too many fields, too many choices, too small a screen.
• Deep training on a website / Notion / Google Drive — same.
• Custom AI Action authoring — code-adjacent and best done on a real keyboard.

These deep-edit flows continue to live on the web; mobile deep-links into them.

Status

• Bot switcher: ✅ partially in place. Active context selection works for AI features.
• Bot detail page: UI design in progress.
• Activity feed: depends on a small backend addition (paginated activity endpoint).
• Quick edits: the relevant API endpoints exist; the mobile UI is what’s missing.
• Beta: planned mid-roadmap, after the Notes → KB feature ships.

Related articles