E-commerce
July 1, 2026
"The bot disconnected my iPhone without guiding me." "The AI displays the suspect device's full IP address." "Chatbot confuses account sessions and push notifications." Three failures where a miscalibrated devices bot overreacts or leaks data.
An e-commerce connected devices AI chatbot does not replace CONNDEV agents (#847). It reads CONNDEV-MAP, guides through the Active Sessions menu, explains the device list, and hands off the revoke action to humans without revoking the API session or exposing detailed IPs.
This guide #848 covers intents bot_conndev_*, the CONNDEVbot flow, and conndev_bot KPIs. Companion bot of the CONNDEV playbook (#847). AI use case: explaining tier 1 sessions and guiding safety support.
Summary
Why automate session explanation by bot?
"Unknown device", "disconnect old phone", "where to view sessions" arrive on the account page and widget. A calibrated bot reads CONNDEV-MAP, guides self-service, without NO-REVOKE-BOT violation.
What the bot resolves in tier 1 sessions
Guide menu: settings_copy path sessions map
Explain list: list_explain_copy devices map
Unknown device: unknown_ok_copy self-service map
Privacy: privacy_copy who sees map
Support Handoff: #847 payload conndev_* revoke agent
CONNDEVbot vs CONNDEV #847, SUSLOGINbot #844, PUSHNOTIFbot #836 and anti-hallucination #123
Seven contents, seven distinct session paths.
Quick matrix
#848 CONNDEVbot: tier 1 bot explain sessions self-service guide handoff
#847 CONNDEV: agents revoke device CD-5 document
SUSLOGINbot #844: distinct connection alert session management
ACCHACKbot #842: confirmed hack LOCK distinct unknown device
PUSHNOTIFbot #836: distinct push tokens login sessions
TWOFACTbot #840: 2FA post-revoke distinct device list
Anti-hallucination #123: policy map whitelist do not invent revoke
Pipeline: #848 bot guide tier 1 → #847 agents execute CD-5 revoke if self-service fails.
Which bot_conndev_* intents should be configured?
Eight bot session intents mapped to conndev_* typologies #847.
Eight bot_conndev intents
bot_conndev_settings : settings_copy menu path map
bot_conndev_list : list_explain_copy list reading map
bot_conndev_unknown : unknown_ok_copy disconnection guide map
bot_conndev_logout_guide : logout_remote_copy self-service map
bot_conndev_logout_all_guide : logout_all_copy precaution map
bot_conndev_family : family_copy shared account map
bot_conndev_privacy : privacy_copy privacy map
bot_conndev_handoff : revoke agent → CONNDEV847-HANDOFF-BOT
Revoke admin session → human handoff CD-5 only. Bot guide explain only.
How to consume CONNDEV-MAP #847?
The bot reads CONNDEV-MAP #847: conndev_program_id, settings_copy, list_explain_copy, unknown_ok_copy, logout_remote_copy, logout_all_copy, family_copy, privacy_copy, handoff_copy, escalate_signals_copy.
Sensitive sessions guardrails
CONNDEV-MAP-GROUNDED-BOT: sessions response from map only
SELF-SERVICE-FIRST-BOT: settings_copy before handoff revoke
CONNDEV-NO-REVOKE-BOT: do not revoke bot API session
NO-IP-LEAK-BOT: never full IP nor admin logs in chat
PUSH835-REROUTE-BOT: push notifications → #836 distinct sessions
CONNDEV847-HANDOFF-BOT: revoke execute → #847 CD-5 agents
CONNDEVBOT-SUP policy in six rules
Six rules for responsible bot devices.
CONNDEV-MAP-GROUNDED-BOT: guide sessions from map only
SELF-SERVICE-FIRST-BOT: SETTINGS + LIST before handoff
CONNDEV-NO-REVOKE-BOT: zero revoke session bot API
NO-IP-LEAK-BOT: device name and date only, no IP
UNKNOWN-OK-BOT: unknown_ok before escalating piracy
ACCHACK841-ESCALATE-BOT: suspicious command → #841 do not revoke bot
Flow CONNDEVbot CDB-1 to CDB-8
Flow eight steps bot sessions embed page account security widget.
CDB-1 Classify : bot_conndev_* detect keyword connected device session disconnect
CDB-2 Self-service check : SETTINGS offered before revoke handoff
CDB-3 CONNDEV-MAP : settings list unknown privacy handoff escalate
CDB-4 Explain : TPL-CONNDEVbot-SETTINGS or LIST depending on intent
CDB-5 Guardrail : MAP-GROUNDED SELF-SERVICE-FIRST NO-REVOKE NO-IP-LEAK
CDB-6 Respond : TPL-CONNDEVbot max 3 grounded sentences
CDB-7 Handoff or close : #847 payload #841 escalate or close OK
CDB-8 Log : intent self_service_sent revoke_blocked escalate Y/N
Example TPL-CONNDEVbot-SETTINGS
« [settings_copy map.] [list_explain_copy map.] SELF-SERVICE-FIRST-BOT. If failed : agent handoff. »
TPL-CONNDEVbot and touchpoints templates
Four short templates sessions embed account.
TPL-CONNDEVbot-SETTINGS
[settings_copy map.] CONNDEV-MAP-GROUNDED-BOT.
TPL-CONNDEVbot-LIST
[list_explain_copy map.] NO-IP-LEAK-BOT.
TPL-CONNDEVbot-UNKNOWN
[unknown_ok_copy map.] CONNDEV-NO-REVOKE-BOT. Handoff if needed.
TPL-CONNDEVbot-PRIVACY
[privacy_copy map.] Separate login session push #836.
Touchpoints
Account Security Page: bot_conndev_settings instant
Unknown device keyword: bot_conndev_unknown trigger
Disconnect phone keyword: bot_conndev_logout_guide proactive
Suspicious order keyword + device: ACCHACK841 escalate
Edge cases and reroutes
Five cases outside tier 1 bot standard sessions.
Connection alert received: SUSLOGINbot #844 reroute
Old phone push: PUSH835-REROUTE distinct session
Confirmed hacked account: ACCHACKbot #842 escalate
Customer requests device IP: deny NO-IP-LEAK privacy_copy
Post-revoke 2FA support advice: TWOFACTbot #840 optional
Essential conndev_bot KPIs
Five CONNDEVbot management metrics.
conndev_bot_self_service_deflect: closed via SETTINGS without handoff repeat 7d
conndev_bot_self_service_first_rate: SELF-SERVICE-FIRST before revoke handoff
conndev_bot_revoke_blocked_rate: % of revokes requested without bot execution
conndev_bot_ip_leak_violations: target 0 IP logs chat audit
conndev_bot_handoff_rate: escalate #847 / total bot sessions
Target: conndev_bot_ip_leak_violations 0 and conndev_bot_self_service_first_rate greater than 90%.
CONNDEVbot Anti-patterns
Five common bot connected device errors.
Revoke session via bot: CONNDEV-NO-REVOKE-BOT handoff #847
Display IP or admin logs: NO-IP-LEAK LIST-EXPLAIN only
Skip self-service: SELF-SERVICE-FIRST SETTINGS mandatory
Escalate hack on device alone: UNKNOWN-OK before ACCHACK841
Confuse push and session: PUSH835 reroute notifications
CONNDEVbot with Qstomy
Qstomy on Shopify: detect bot_conndev intent on account page, CONNDEV-MAP RAG grounded, SELF-SERVICE-FIRST guardrail, enriched handoff #847 tier 2.
Pipeline: #848 bot guide tier 1 → #847 agents execute revoke CD-5 if needed.
Explore AI support and request a demo.
Checklist, FAQ and going further
CONNDEVbot Checklist (8 steps)
Sync CONNDEV-MAP #847: RAG bot sessions embed security page
CONNDEVBOT-SUP Policy: 6 rules SELF-SERVICE-FIRST NO-REVOKE NO-IP-LEAK
8 intents bot_conndev_*: flow CDB-1 to CDB-8
4 templates TPL-CONNDEVbot-*: SETTINGS LIST UNKNOWN PRIVACY
Block session revoke API: bot read-only no logout write
Red team 20 prompts: ask for IP, revoke session, confuse push
Proactive security page: bot_conndev_settings trigger embed
KPI Dashboard: conndev_bot_* section 9 ip_leak_violations self_service_first
FAQ
Difference #847?
#847 = agents revoke device CD-5 document. #848 = bot guide self-service tier 1.
Bot disconnects the device?
No. CONNDEV-NO-REVOKE-BOT. CONNDEV847-HANDOFF humans CD-5.
Session = push notification?
No. PUSH835-REROUTE if client talks phone alerts.
Unknown device?
bot_conndev_unknown TPL-CONNDEVbot-UNKNOWN. ACCHACK841 if suspicious command.
Going further
This week: deploy CONNDEV-MAP RAG security page embed, red team ip_leak_violations audit, sync bot_conndev_unknown proactive unknown device scenario self-service test.
Enzo
July 1, 2026
