E-commerce
July 1, 2026
"Send me our conversation." The bot promises immediate delivery without verifying who is asking. Or it blocks without collecting the email and order number.
An e-commerce history access AI chatbot detects the sensitive request, collects the identity slots, announces the SLA, and escalates to the export agent without delivering a transcript from the widget.
This guide #902 covers bot_histacc_* intents, flow HISTACCbot HAB-1 to HAB-8, and HISTACC-VERIFY-GATE guardrails. Bot pair from the HISTACC playbook (#901). Use case: sensitive identity verification request on the widget side.
Summary
Why must the bot verify before escalating?
Access request = personal data: uncontrolled export exposes transcripts to third parties. HISTACC-VERIFY-GATE and NO-EXPORT-WITHOUT-VERIFY-BOT reduce risks and histacc_identity_pending tickets #901.
What the historical access bot solves
Request detected: copy of historical chat transcript
Identity slots: email order date conversation
Announced SLA: delivery time from registry #901
No bot export: agent handoff HA-5 #901
Fewer tickets: decrease in incomplete histacc_copy_request
Retail DTC Example
DTC fashion, verify gate widget. histacc_bot_identity_complete_rate 84 %, histacc_bot_deflect +32 % in 5 weeks.
HISTACCbot #902 vs HISTACC #901, CONVRECBOT #900, DELETEbot #904 and EXPORT #905
Six historical access contents, six distinct roles.
Quick matrix
#902 HISTACCbot : bot detect collect identity escalate export agent
HISTACC #901 : agents verify lookup export deliver HA-5
CONVRECBOT #900 : tier 1 retention policy copy_route guides
CONVREC #899 : recording who accesses distinct execution copy
DELETE #903 : deletion distinct copy access
DELETEbot #904 : bot deletion route distinct access
EXPORT #905 : export third-party assurance distinct customer request
Pipeline : widget copy request → #902 identity slots → handoff #901 SLA export.
Which bot_histacc_* intents should be configured?
Eight access intents mapped HISTACCESS-MAP #901.
Eight bot_histacc intents
bot_histacc_detect_request: intent copy history transcript map
bot_histacc_slot_email: collect verification email map
bot_histacc_slot_order: order number crossover map
bot_histacc_slot_date: partial conversation date map
bot_histacc_sla_commit: announce delivery time map
bot_histacc_escalate_agent: handoff export agent map
bot_histacc_dpo_handoff: GDPR formal portability map
bot_histacc_feed_loop: consume LOG #901 slots map
Each request logs slots_filled identity_verified escalate_reason histacc_* tag.
How should HISTACCESS-MAP #901 be consumed?
The bot reads HISTACCESS-MAP #901 + access fields: export_sla_hours, verify_fields_required, format_default, histacc_feed_priority, guest_otp_enabled, dpo_trigger_phrases.
Historical access guardrails
HISTACC-VERIFY-GATE: email order slots before escalating to agent
NO-EXPORT-WITHOUT-VERIFY-BOT: never send transcript from widget
ONE-SLOT-PER-TURN-BOT: email then order then date
SLA-COMMIT-BOT: sla_commit from registry #901
CONVREC-REROUTE-BOT: policy question only → #900
DELETE-REROUTE-BOT: deletion → #904
DPO-HANDOFF-BOT: immediate formal portability
HISTACC-FEED-LOOP-BOT: LOG #901 enriches verify_fields
HISTACCBOT-SUP policy in six rules
Six rules request sensitive responsible access.
HISTACC-VERIFY-GATE: complete identity slots before handoff
NO-EXPORT-WITHOUT-VERIFY-BOT: bot does not deliver transcript directly
ONE-SLOT-PER-TURN-BOT: progressive collection of email order date
SLA-COMMIT-BOT: always announce export_sla_hours
ESCALATE-AGENT-BOT: export executed by agent #901 only
HISTACC-FEED-LOOP-BOT: each LOG #901 review verify within 48 hours
Flow HISTACCbot HAB-1 to HAB-8
Eight-step flow: slot detection, SLA verification, escalate, log, handoff.
HAB-1 Ingest: message copy history transcript
HAB-2 Detect: bot_histacc_detect_request vs convrec #900
HAB-3 Slot collect: email order date ONE-SLOT-PER-TURN
HAB-4 Verify gate: HISTACC-VERIFY-GATE complete slots
HAB-5 SLA commit: sla_commit export_sla_hours format
HAB-6 Escalate: escalate_agent context slots #155
HAB-7 Feed loop: LOG #901 adjusts verify_fields
HAB-8 Log: identity_complete deflect escalate_rate
Example TPL-HISTACCbot-VERIFY-EMAIL
“To secure the delivery of your history, please confirm the email associated with the conversation or your order.”
TPL-HISTACCbot and touchpoints templates
Four short templates with embed access.
TPL-HISTACCbot-VERIFY-EMAIL
[verify_email_copy map.] ONE-SLOT-PER-TURN. HISTACC-VERIFY-GATE.
TPL-HISTACCbot-VERIFY-ORDER
[verify_order_copy map.] Cross-referencing order number. Slot order.
TPL-HISTACCbot-SLA-COMMIT
[sla_copy map.] Delay {{export_sla_hours}}. NO-EXPORT-WITHOUT-VERIFY.
TPL-HISTACCbot-ESCALATE
[escalate_copy map.] Export team handoff. Joint slots #155.
Touchpoints
"Chat copy": detect + verify_email
Precise date: slot_date after email order
GDPR Portability: immediate dpo_handoff
LOG HISTACC #901: feed_loop verify_fields
Edge cases and reroutes
Five cases out of the standard flow.
Retention question only: #900 CONVRECBOT
Deletion requested: #904 DELETEbot
Third-party joint lawyer: escalate agent DPO mandate
Client refuses email: handoff #12 without auto export
Ticket histacc_ despite bot: feed_loop review missing slots
Essential histacc_bot KPIs
Five HISTACCbot management metrics and correlation #901.
histacc_bot_identity_complete_rate: handoffs with complete email order slots
histacc_bot_deflect: requests prepared without incomplete ticket
histacc_bot_verify_before_escalate_rate: % escalate after VERIFY-GATE
histacc_bot_sla_announced_rate: % handoffs with sla_commit
histacc_bot_wrong_export_attempts: export attempts target widget 0
Target: identity_complete increasing and wrong_export_attempts at zero.
HISTACCbot anti-patterns
Five common bot access errors.
Sending widget transcript: NO-EXPORT-WITHOUT-VERIFY strict
Escalating without email: VERIFY-GATE mandatory slots
Three fields in the same turn: ONE-SLOT-PER-TURN progressive
SLA not announced: SLA-COMMIT before escalate
Confusing deletion: DELETE-REROUTE #904 not histacc
HISTACCbot with Qstomy
Qstomy on Shopify: slot engine verify, HISTACCESS-MAP sync #901, SLA templates, escalate context #155, KPI histacc_bot dashboard.
Scenario: retail DTC, 4 tickets/month incomplete access. Verify gate + escalate slots. histacc_bot_identity_complete_rate 84%, histacc_access_fulfilled_rate #901 +12 pts in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
HISTACCbot Checklist (8 steps)
Sync HISTACCESS-MAP #901: export_sla verify_fields format
Policy HISTACCBOT-SUP: 6 rules VERIFY-GATE NO-EXPORT ONE-SLOT
8 intents bot_histacc_*: flow HAB-1 to HAB-8
4 templates TPL-HISTACCbot-*: VERIFY-EMAIL VERIFY-ORDER SLA ESCALATE
verify_fields: email order date configurable
escalate_agent handoff: joint slots #155 to #901
Red team chat copy: detect slots no direct export test
KPI Dashboard: histacc_bot_* section 9 + delta histacc_
FAQ
Difference #901?
#901 = agents export deliver. #902 = bot collect identity escalate.
Does the bot send the copy?
No. NO-EXPORT-WITHOUT-VERIFY. Agent #901 executes HA-5.
Difference #900?
#900 = explain retention. #902 = process sensitive copy request.
Minimum identity fields?
email + order register #901. date if histacc_partial_date.
Going further
This week: activate detect_request, verify email order templates, sla_commit export_sla, measure histacc_bot_identity_complete_rate.
Enzo
July 1, 2026
