E-commerce
July 1, 2026
"Delete this chat now." The bot confirms the deletion even though a dispute is open. Or it redirects to the FAQ without distinguishing between account and conversation.
An e-commerce conversation deletion AI chatbot detects the sensitive request, explains the scope (one exchange vs history), collects identity, informs about dispute exceptions, and routes to agent #903 without executing the delete from the widget.
This guide #904 covers intents bot_convdel_*, flow CONVDELbot CDB-1 to CDB-8, and guardrails CONVDEL-VERIFY-GATE. Bot pair from the CONVDEL playbook (#903). Use case: informed conversational deletion on the widget side.
Summary
Why must the bot inform before routing?
Deletion = irreversible action and often blocked by litigation. CONVDEL-VERIFY-GATE and NO-DELETE-WITHOUT-AGENT-BOT prevent false promises and misrouted convdel_ tickets #903.
What the deletion bot solves
Detected request: erase support chat history
Scope explained: single vs full vs account #823
Identity slots: order email before escalate
Anticipated litigation: copy retention if case is open
No widget delete: agent handoff CD-5 #903
DTC retail example
DTC, scope copy + verify gate. convdel_bot_scope_informed_rate 91%, convdel_bot_deflect +29% in 5 weeks.
CONVDELbot #904 vs CONVDEL #903, ACCTDELbot #824, HISTACCbot #902 and CONVRECBOT #900
Six privacy erasure contents, six distinct roles.
Quick Matrix
#904 CONVDELbot: bot detect explain scope collect identity route delete agent
CONVDEL #903: agents verify dispute execute confirm CD-5
ACCTDEL #823: entire account deletion distinct conversation
ACCTDELbot #824: bot account delete distinct convdel
HISTACCbot #902: access copy distinct deletion
CONVRECBOT #900: retention delete_route directs
CONVREC #899: recording policy distinct delete execution
Pipeline: widget deletion request → #904 scope + verify → handoff #903 execute.
Which bot_convdel_* intents should be configured?
Eight deletion intents mapped CONVDEL-MAP #903.
Eight bot_convdel intents
bot_convdel_detect_request: erase conversation map intent
bot_convdel_scope_explain: single full what remains map
bot_convdel_slot_email: verification email map
bot_convdel_slot_order: verification order map
bot_convdel_litige_notice: retention if open dispute map
bot_convdel_escalate_agent: handoff delete agent map
bot_convdel_dpo_handoff: contested GDPR erasure map
bot_convdel_feed_loop: consume LOG #903 scope copy map
Each request logs scope_informed identity_slots escalate_reason convdel_* tag.
How should I use CONVDEL-MAP #903?
The bot reads CONVDEL-MAP #903 + delete fields: scope_copy_single, scope_copy_full, litige_notice_copy, verify_fields, delete_sla_hours, convdel_feed_priority, acctdel_reroute_phrases.
Conversation deletion guardrails
CONVDEL-VERIFY-GATE: identity slots before agent escalation
NO-DELETE-WITHOUT-AGENT-BOT: never delete helpdesk from widget
SCOPE-FIRST-BOT: scope_explain before identity collection
LITIGE-NOTICE-BOT: litige_notice if case is detected
ACCTDEL-REROUTE-BOT: entire account → #824 ACCTDELbot
HISTACC-REROUTE-BOT: copy requested → #902
DPO-HANDOFF-BOT: immediate formal dispute
CONVDEL-FEED-LOOP-BOT: LOG #903 enriches scope_copy
CONVDELBOT-SUP policy in six rules
Six rules for responsible conversation deletion.
SCOPE-FIRST-BOT: explain scope before promising deletion
CONVDEL-VERIFY-GATE: full identity verification before handoff
NO-DELETE-WITHOUT-AGENT-BOT: execution by agent #903 only
LITIGE-NOTICE-BOT: inform about legal retention if applicable
ACCTDEL-REROUTE-BOT: strict separation between account and conversation deletion
CONVDEL-FEED-LOOP-BOT: review copy of each LOG #903 within 48 hours
Flow CONVDELbot CDB-1 to CDB-8
Eight-step flow: detect scope verify notice escalate log handoff.
CDB-1 Ingest: message erase delete chat history
CDB-2 Detect: bot_convdel_detect_request vs acctdel #824
CDB-3 Scope explain: single full SCOPE-INFO what remains
CDB-4 Slot collect: email order CONVDEL-VERIFY-GATE
CDB-5 Litige notice: litige_notice if case flagged
CDB-6 Escalate: escalate_agent context #155 to #903
CDB-7 Feed loop: LOG #903 adjusts scope_copy dispute
CDB-8 Log: scope_informed deflect verify_complete
Example TPL-CONVDELbot-SCOPE
“We can delete this conversation or your support history. Your account and orders remain active unless requested separately. An open dispute may delay deletion.”
TPL-CONVDELbot and touchpoints templates
Four short deletion embed templates.
TPL-CONVDELbot-SCOPE
[scope_copy map.] Single vs full. SCOPE-FIRST-BOT.
TPL-CONVDELbot-VERIFY
[verify_copy map.] Order email. CONVDEL-VERIFY-GATE.
TPL-CONVDELbot-LITIGE
[litige_copy map.] Retention until closure. LITIGE-NOTICE-BOT.
TPL-CONVDELbot-ESCALATE
[escalate_copy map.] Team handoff within {{delete_sla_hours}}. NO-DELETE-WITHOUT-AGENT.
Touchpoints
"Delete the chat": detect + scope_explain
"Delete my account": ACCTDEL-REROUTE #824
Chargeback mentioned: litige_notice before escalate
LOG CONVDEL #903: feed_loop scope_copy
Edge cases and reroutes
Five cases outside the standard flow.
Copy before deletion: #902 HISTACCbot then convdel
Retention question only: #900 CONVRECBOT
Account + conversations: clarify two processes #824 and #904
Client demands immediate action: SCOPE + litige_notice not delete widget
Convdel_ ticket despite bot: feed_loop review missing scope
Essential convdel_bot KPIs
Five CONVDELbot steering metrics and correlation #903.
convdel_bot_scope_informed_rate: % of requests with scope_explain before handoff
convdel_bot_deflect: well-routed requests without incomplete ticket
convdel_bot_verify_before_escalate_rate: handoffs after VERIFY-GATE
convdel_bot_acctdel_misroute_rate: poorly routed account convdel target 0
convdel_bot_widget_delete_attempts: executed delete widget target 0
Target: widget_delete_attempts at zero and scope_informed close to 100%.
CONVDELbot anti-patterns
Five common bot deletion errors.
Confirm delete widget: NO-DELETE-WITHOUT-AGENT strict
Ignore scope: SCOPE-FIRST before verify
Confuse account: ACCTDEL-REROUTE #824
Forget dispute: LITIGE-NOTICE if chargeback reported
Escalate without identity: VERIFY-GATE slots mandatory
CONVDELbot with Qstomy
Qstomy on Shopify: CONVDEL-MAP sync #903, scope templates widget, verify slots, dispute notice, escalate handoff #155, KPI convdel_bot dashboard.
Scenario: retail DTC, 3 misrouted convdel tickets/month. Scope + verify + escalate. convdel_bot_scope_informed_rate 91%, convdel_deletion_resolution_rate #903 +11 pts in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
CONVDELbot Checklist (8 steps)
CONVDEL-MAP Sync #903: scope_copy dispute verify delete_sla
CONVDELBOT-SUP Policy: 6 SCOPE VERIFY NO-DELETE rules
8 bot_convdel_* intents: flow CDB-1 to CDB-8
4 TPL-CONVDELbot-* templates: SCOPE VERIFY DISPUTE ESCALATE
acctdel_reroute: account phrases to #824
escalate_agent handoff: context slots #155 to #903
Red team delete chat: scope no direct delete test
KPI Dashboard: convdel_bot_* section 9 + delta convdel_
FAQ
Difference with #903?
#903 = agents execute delete confirm. #904 = bot inform router.
Does the bot delete the chat?
No. NO-DELETE-WITHOUT-AGENT. Agent #903 CD-5.
Difference with #824?
#824 = account deletion. #904 = support conversation deletion.
Open dispute?
DISPUTE-NOTICE then handoff. Agent DISPUTE-BLOCKED #903 if blocked.
Going further
This week: activate detect_request, scope verify dispute templates, escalate handoff, measure convdel_bot_scope_informed_rate.
Enzo
July 1, 2026
