E-commerce
July 1, 2026
"Is this a human?" "Who controls your bot?" The widget replies "virtual assistant" without specifying supervision or agent routing. The customer opens a humanbot_ ticket.
A supervised e-commerce AI chatbot explains the role of human agents, quality review, brand responsibility, and routes to an agent when requested, complementing the technical handoff (#12).
This guide #916 covers bot_supbot_* intents, flow SUPBOT SAB-1 to SAB-8, and HUMANBOT-REGISTRY-GATE guardrails. Bot pair of the HUMANBOT playbook (#915). Usecase: supervision transparency widget-side.
Summary
Why explain bot-side monitoring?
Trust questions arise in the middle of the chat. Without the team registry copy, the bot denies the agents or blocks the handoff. HUMANBOT-REGISTRY-GATE reduces humanbot_ tickets #915 and strengthens trust.
What tier 1 bot supervision solves
Honest disclosure: bot vs human session
Supervision explained: QA view escalation map
Brand responsibility: bot not solely responsible
Reach human: advisor path button keyword
Agent hours: live map slots
DTC retail example
DTC, registry gate widget. supbot_bot_trust_deflect +40%, supbot_bot_deny_team 0 in 5 weeks.
SUPBOT #916 vs HUMANBOT #915, HANDOFF #12, AITRAN #860 and Governance #142
Seven trust handoff contents, seven distinct roles.
Quick Matrix
#916 SUPBOT: bot explaining agent supervision to reach human tier 1
HUMANBOT #915: agents processing humanbot HB-4 tickets
HANDOFF #12: technical transfer rules SLA intents
AITRAN #860: disclosure of AI status distinct team response
Governance #142: internal RACI validation rules
CONVQMON #911: client quality review distinct from supervision
OFFAIRESP #913: offensive response incident
#12 = how to transfer. #916 = why humans supervise and how to reach them.
Which bot_supbot_* intents should be configured?
Eight supervision intents mapped HUMANBOT-MAP #915.
Eight bot_supbot intents
bot_supbot_disclosure_answer: bot or human now
bot_supbot_supervision_answer: supervision_copy process map
bot_supbot_team_answer: team_copy team map
bot_supbot_responsibility_answer: responsibility_copy brand
bot_supbot_reach_human_route: handoff live button keyword
bot_supbot_hours_answer: hours_copy agent slots
bot_supbot_reassure_trust: always_bot_fear trust_concern
bot_supbot_feed_loop: consume LOG #915 supervision_copy
Each response logs registry_version intent humanbot_* deflect_or_handoff.
How to consume HUMANBOT-MAP #915?
The bot reads HUMANBOT-MAP #915 + bot fields: disclosure_copy, supervision_copy, team_copy, responsibility_copy, reach_human_path, hours_copy, handoff_sla, agent_handoff_url, policy_link.
Bot supervision guardrails
HUMANBOT-REGISTRY-GATE: replies only from sync registry
HONEST-DISCLOSURE-BOT: honest bot vs human session
NO-DENY-TEAM-BOT: do not deny existing agents
REACH-HUMAN-ROUTE-BOT: explicit agent path
HANDOFF-EXECUTE-BOT: reach_human triggers handoff #12
AITRAN-REROUTE-BOT: AI-only status → #860
AGENT-HANDOFF-BOT: complex ticket → #915 agent
SUPBOT-FEED-LOOP-BOT: LOG #915 enriches supervision_copy
SUPBOT-SUP policy in six rules
Six responsible supervision rules widget-side.
HUMANBOT-REGISTRY-GATE: tier 1 from registry #915
HONEST-DISCLOSURE-BOT: disclosure before AI jargon
SUPERVISION-GROUNDED-BOT: supervision_copy registry only
REACH-HUMAN-ROUTE-BOT: reach_human executes handoff
HOURS-HONEST-BOT: agent hours without over-promising
SUPBOT-FEED-LOOP-BOT: LOG #915 review widget within 48 hours
Flow SUPBOT SAB-1 to SAB-8
Flow eight steps: question incoming classify registry answer route handoff log.
SAB-1 Ingest: human message robot supervise advisor
SAB-2 Classify: humanbot_* vs handoff #12 vs aitran #860
SAB-3 Registry gate: HUMANBOT-REGISTRY-GATE lookup
SAB-4 Tier 1 answer: disclosure supervision team responsibility
SAB-5 Route: reach_human_route hours reassure
SAB-6 Handoff execute: HANDOFF-EXECUTE if reach_human live
SAB-7 Feed loop: LOG #915 adjusts supervision_copy
SAB-8 Log: trust_deflect handoff_success deny_team
Example TPL-SUPBOT-SUPERVISION
“Our chatbot is supervised by {{supervision_copy}}. Human advisor: {{reach_human_path}}. Agent hours: {{hours_copy}}.”
TPL-SUPBOT templates and touchpoints
Four short templates supervision embed.
TPL-SUPBOT-DISCLOSURE
[disclosure_copy map.] HONEST-DISCLOSURE session.
TPL-SUPBOT-SUPERVISION
[supervision_copy map.] [team_copy map.] SUPERVISION-GROUNDED.
TPL-SUPBOT-REACH
[reach_human_path map.] [handoff_sla map.] REACH-HUMAN-ROUTE.
TPL-SUPBOT-RESPONSIBILITY
[responsibility_copy map.] Responsible brand bot errors.
Touchpoints
"Is it a robot?": disclosure + supervision
"I want a human": reach_human_route handoff
"Who is supervising?": supervision_answer tier 1
LOG HUMANBOT #915: feed_loop supervision_copy
Edge cases: out-of-hours handoff, live agent mid-chat, BPO
Five cases out of the standard flow.
Human reach out-of-hours: HOURS-HONEST + email callback
Agent takes over mid-chat: session update disclosure
BPO outsourced support: partner honest team_copy
Technical handoff only: #12 HANDOFF
Humanbot_ ticket despite bot: feed_loop review registry gaps
Essential subbot_bot KPIs
Five SUPBOT steering metrics and correlation #915.
supbot_bot_trust_deflect: resolved trust without humanbot_ ticket
supbot_bot_registry_compliance: % of registry-aligned responses
supbot_bot_handoff_success: % reach_human with successful handoff
supbot_bot_deny_team: target 0 agent denial
supbot_bot_supervision_cited: % supervision with registry copy
Target: deny_team at zero and handoff_success above 90% during live hours.
SUPBOT anti-patterns
Five common bot supervision mistakes.
Denying agents: NO-DENY-TEAM mandatory
Promising 24/7 human: HOURS-HONEST register
Blocking reach human: REACH-HUMAN-ROUTE explicit
Confusing AI disclosure: AITRAN-REROUTE #860
Improvised supervision: REGISTRY-GATE only
SUPBOT with Qstomy
Qstomy on Shopify: HUMANBOT-MAP sync #915, templates disclosure supervision reach, handoff live, KPI supbot_bot dashboard.
Scenario: DTC, 6 tickets/month humanbot. Registry gate tier 1. supbot_bot_trust_deflect +40%, humanbot_ tickets -37% in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
SUPBOT Checklist (8 steps)
Sync HUMANBOT-MAP #915: disclosure supervision reach hours
Policy SUPBOT-SUP: 6 rules REGISTRY-GATE HONEST-DISCLOSURE
8 intents bot_supbot_*: flow SAB-1 to SAB-8
4 templates TPL-SUPBOT-*: DISCLOSURE SUPERVISION REACH RESPONSIBILITY
policy_link: public supervision team page
handoff_execute: route #12 reach_human configured
Red team supervision: deny team test reach handoff
KPI Dashboard: supbot_bot_* section 9 + delta humanbot_
FAQ
Difference #915?
#915 = complex tickets agents. #916 = bot tier 1 disclosure supervision reach.
Difference #12?
#12 = technical handoff rules. #916 = human transparency + reach execution.
Difference #860?
#860 = AI response status. #916 = supervision team behind the bot.
Can the bot lie about being
Enzo
July 1, 2026
