E-commerce
July 1, 2026
"Is this chat being recorded?" The bot replies "I don't know" or makes up "we don't keep anything". The customer opens a convrec_ ticket.
An e-commerce history retention AI chatbot replies from the retention register: duration, customer service purpose, who accesses it, how to request a copy or deletion, without legal improvisation.
This guide #900 covers intents bot_convrec_*, flow CONVRECBOT CHB-1 to CHB-8, and guardrails CONVREC-REGISTRY-GATE. Bot pair of the playbook CONVREC (#899). Usecase: retention transparency on the widget side.
Summary
Why should the bot explain retention?
Privacy questions in the middle of CS chat: without copy registry, the bot shifts or lies. CONVREC-REGISTRY-GATE and NO-FAKE-ZERO-STORAGE-BOT reduce convrec_ tickets #899 and complete session resumption #882 without confusing them with account toggles #850.
What the retention bot solves
Vague recording: client does not know if chat is stored
Opaque duration: how long it is kept
Internal access: who reads the history
Deletion copy: tier 1 routing or agent handoff
Fewer tickets: drop in convrec_is_recorded
DTC Retail Example
DTC mode, widget registry copy. convrec_bot_deflect +38%, convrec_bot_registry_compliance 97% in 5 weeks.
CONVRECBOT #900 vs CONVREC #899, CHATINT #881, RESUME #882 and PRIVPREFbot #850
Six historical privacy contents, six distinct roles.
Quick matrix
#900 CONVRECBOT: bot to explain retention access copy deletion widget
CONVREC #899: agents handling CR-5 recording tickets
CHATINT #881: lost conversation recovery distinct storage policy
RESUME #882: session recovery UX distinct retention
PRIVPREFbot #850: account marketing toggles distinct from conversation
Privacy #154: transversal privacy support
CONSENT bot: data consent distinct from chat history
Pipeline: retention question widget → #900 tier 1 → handoff #899 if access delete DPO.
Which bot_convrec_* intents should be configured?
Eight retention intents mapped CONVREC-MAP #899.
Eight bot_convrec intents
bot_convrec_recording_answer: recording yes no purpose map
bot_convrec_retention_answer: retention period then action map
bot_convrec_access_answer: who can view history map
bot_convrec_consent_answer: prior information banner map
bot_convrec_copy_route: request copy agent handoff map
bot_convrec_delete_route: request erasure handoff map
bot_convrec_dpo_handoff: formal GDPR rights map
bot_convrec_feed_loop: consume LOG #899 registry map
Each privacy response logs registry_version intent convrec_* deflect_or_handoff.
How do I consume CONVREC-MAP #899?
The bot reads CONVREC-MAP #899 + registry fields: retention_days, recording_status, access_roles, consent_banner_copy, copy_request_sla, delete_conditions, convrec_feed_priority.
Historical Retention Guardrails
CONVREC-REGISTRY-GATE: responses only from sync registry
NO-FAKE-ZERO-STORAGE-BOT: do not promise zero if transcript is stored
RETENTION-COPY-BOT: purpose duration from registry, not improvised
COPY-ROUTE-BOT: copy_route handoff agent registry SLA
DELETE-ROUTE-BOT: delete_route if conditions are OK, otherwise agent
DPO-HANDOFF-BOT: formal rights never processed by bot alone
CONVREC-FEED-LOOP-BOT: LOG #899 enriches registry copy
CHATINT-REROUTE-BOT: session lost → #882 RESUME not convrec
CONVRECBOT-SUP policy in six rules
Six rules for historical transparency and accountability.
CONVREC-REGISTRY-GATE : tier 1 from registry #899 only
NO-FAKE-ZERO-STORAGE-BOT : honesty about actual transcript storage
RETENTION-COPY-BOT : duration + purpose + post-retention action
COPY-DELETE-ROUTE-BOT : deletion copy routed to agent if outside tier 1
DPO-HANDOFF-BOT : immediate escalate_dpo for formal GDPR rights
CONVREC-FEED-LOOP-BOT : each LOG #899 review registry within 48 hours
Flow CONVRECBOT CHB-1 to CHB-8
Eight-step flow: incoming question classify registry answer route log handoff.
CHB-1 Ingest: message privacy retention recording
CHB-2 Classify: convrec_* via CONVREC-MAP #899
CHB-3 Registry gate: CONVREC-REGISTRY-GATE lookup copy
CHB-4 Tier 1 answer: recording retention access consent
CHB-5 Route action: copy_route delete_route dpo_handoff
CHB-6 Chatint reroute: session lost → #882 no convrec
CHB-7 Feed loop: LOG #899 adjusts registry widget
CHB-8 Log: deflect registry_compliance handoff_rate
Example TPL-CONVRECBOT-RETENTION
“Our chat conversations are retained for {{retention_days}} days for support and quality. Then {{post_retention_action}}. Access: support team only.”
TPL-CONVRECBOT templates and touchpoints
Four short retention embed templates.
TPL-CONVRECBOT-RECORDING
[recording_copy map.] QA support purpose. CONVREC-REGISTRY-GATE.
TPL-CONVRECBOT-RETENTION
[retention_copy map.] Post-retention action duration. RETENTION-COPY-BOT.
TPL-CONVRECBOT-ACCESS
[access_copy map.] Support roles. No third-party marketing.
TPL-CONVRECBOT-COPY-ROUTE
[copy_route_copy map.] SLA agent handoff {{copy_request_sla}}. COPY-ROUTE-BOT.
Touchpoints
"Do you record?": recording_answer tier 1
"How long do you keep it?": retention_answer
"I want a copy": copy_route handoff #899
LOG CONVREC #899: feed_loop registry copy
Edge cases and reroutes
Five cases out of the standard flow.
Session expired: #881 CHATINT or #882 RESUME
Account marketing toggles: #850 PRIVPREFbot
Complete account deletion: #823 ACCTDEL
Formal GDPR request: immediate dpo_handoff
convrec_ ticket despite bot: feed_loop review registry gaps
Essential convrec_bot KPIs
Five CONVRECBOT steering metrics and correlation #899.
convrec_bot_deflect: retention questions resolved without a convrec_ ticket
convrec_bot_registry_compliance: % of answers aligned with registry
convrec_bot_tier1_resolution_rate: simple info without handoff
convrec_bot_copy_handoff_sla: copy_route delay to agent
convrec_bot_fake_zero_storage: fake zero storage answers target 0
Target: registry_compliance close to 100% and deflect rising after gate active.
CONVRECBOT Anti-patterns
Five common bot retention errors.
Promising zero storage: NO-FAKE-ZERO-STORAGE if transcript exists
Improvising duration: RETENTION-COPY from registry only
Handling deletion alone: DELETE-ROUTE agent or DPO
Confusing lost session: CHATINT-REROUTE #882 not convrec
Ignoring feed #899: CONVREC-FEED-LOOP updates copy widget
CONVRECBOT with Qstomy
Qstomy on Shopify: retention registry sync #899, tier 1 templates widget, copy delete route handoff, consent banner, KPI convrec_bot dashboard.
Scenario: retail DTC, 7 tickets/month convrec privacy. Registry gate + tier 1 bot. convrec_bot_deflect +38%, convrec_ tickets -34% in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
CONVRECBOT Checklist (8 steps)
Sync CONVREC-MAP #899: registry retention access consent SLA
Policy CONVRECBOT-SUP: 6 rules REGISTRY-GATE NO-FAKE-ZERO
8 intents bot_convrec_*: flow CHB-1 to CHB-8
4 templates TPL-CONVRECBOT-*: RECORDING RETENTION ACCESS COPY-ROUTE
Widget banner: consent_banner_copy aligned with registry
copy_route handoff: conversation context to agent #899
Recording Red team: recording_answer no improvisation test
KPI Dashboard: convrec_bot_* section 9 + delta convrec_
FAQ
Difference #899?
#899 = agents copy deletion DPO. #900 = bot tier 1 info retention widget.
Does the bot clear history?
No, only DELETE-ROUTE handoff agent according to registry conditions.
Difference #882?
#882 = resume session UX. #900 = storage retention policy.
How long to typically keep?
retention_days registry #899. Current target 90 to 365 days depending on customer service purpose.
Going further
This week: sync registry #899, templates recording retention, copy_route handoff, measure convrec_bot_deflect.
Enzo
July 1, 2026
