E-commerce
July 1, 2026
"The bot promises that I will no longer receive any emails." "The AI unsubscribes everything, including my order confirmation." "Chatbot gives invented GDPR legal advice on promotions." Three failures where a miscalibrated email preference bot creates legal risk and WISMO.
An e-commerce transactional email preference AI chatbot does not replace TXNPREF agents (#833). It reads TXNPREF-MAP, quotes obligatory_copy marketing_off_copy, guides prefs_link, and hands off unsub admin to humans without promising zero emails or cutting off transactional ones.
This guide #834 covers intents bot_txnpref_*, flow TXNPREFbot, and KPI txnpref_bot. Bot pair of the TXNPREF playbook (#833). Sensitive AI use case: explaining mandatory tier 1.
Summary
Why automate the explanation of transactional vs marketing bots?
"Unsubscribe me", "too many emails", "no more confirmation" arrive at the unsub widget or footer. A calibrated bot reads TXNPREF-MAP, cites obligatory_copy before any unsub, without violating TXNPREF-NO-ZERO-PROMISE.
What the tier 1 preferences bot resolves
Explain mandatory: obligatory_copy OBLIGATORY-CITE-BOT map
Guide marketing off: marketing_off_copy prefs_link map
Distinguish missing: resend_reroute #358 if not received
Sync delay: sync_delay_copy 48 h lists map
CS handoff: #833 payload txnpref_* Klaviyo action
TXNPREFbot vs TXNPREF #833, CONF-EMAIL #358, ACCTDELbot #824, CGVbot and anti-hallucination #123
Six pieces of content, six distinct customer email journeys.
Quick Matrix
#834 TXNPREFbot: tier 1 bot explain mandatory guide marketing handoff
#833 TXNPREF: agents unsub Klaviyo resend document
CONF-EMAIL #358: missing email deliverability distinct preferences
ACCTDELbot #824: account deletion marketing distinct preferences
CGVbot terms: general legal distinct mandatory email
Anti-hallucination #123: policy map whitelist not legal advice LLM
Pipeline: #834 bot explain tier 1 → #833 agents execute TP-5 unsub policy.
Which bot_txnpref_* intents should be configured?
Eight bot preferences intents mapped txnpref_* typologies #833.
Eight intents bot_txnpref
bot_txnpref_obligatory: obligatory_copy transactional list map
bot_txnpref_marketing_off: marketing_off_copy prefs_link map
bot_txnpref_unsub_all: obligatory then marketing_off handoff map
bot_txnpref_persists: sync_delay_copy marketing persists map
bot_txnpref_resend_reroute: not received → CONFEMAIL358 reroute
bot_txnpref_frequency: frequency_copy reduce promo map
bot_txnpref_prefs_fail: prefs_link manual handoff map
bot_txnpref_handoff: execute unsub → TXNPREF833-HANDOFF-BOT
Execute unsub lists → human handoff TP-5 only. Bot explain guide only.
How do I consume TXNPREF-MAP #833?
The bot reads TXNPREF-MAP #833: txnpref_program_id, obligatory_copy, marketing_off_copy, prefs_link_copy, sync_delay_copy, frequency_copy, resend_reroute_copy, gdpr_route_copy, email_type_matrix_copy.
Sensitive email preferences guardrails
TXNPREF-MAP-GROUNDED-BOT: preferences response from map only
OBLIGATORY-CITE-BOT: obligatory_copy quotes map verbatim
TXNPREF-NO-ZERO-PROMISE-BOT: never promise zero emails if order is active
NO-LEGAL-ADVICE-BOT: no custom GDPR interpretation by the LLM
CONFEMAIL358-REROUTE-BOT: email not received → #358 separate from preferences
TXNPREF833-HANDOFF-BOT: unsub execute → #833 TP-5 agents
Policy TXNPREFBOT-SUP in six rules
Six rules bot preferences email responsible.
TXNPREF-MAP-GROUNDED-BOT: obligatory marketing from map only
OBLIGATORY-CITE-BOT: explain transactional before unsub all
TXNPREF-NO-ZERO-PROMISE-BOT: no zero email promise
NO-LEGAL-ADVICE-BOT: map verbatim no legal advice LLM
MARKETING-OFF-DEFAULT-BOT: guide marketing off not global suppress bot
NO-UNSUB-EXECUTE-BOT: unsub lists human #833 only
Flow TXNPREFbot TPB-1 to TPB-8
Eight-step flow bot email preferences embed widget footer.
TPB-1 Classify: bot_txnpref_* detect keyword unsubscribe too many emails confirmation
TPB-2 Intent check: unsub all vs marketing only vs not received reroute
TPB-3 TXNPREF-MAP: obligatory marketing_off persists resend handoff
TPB-4 Explain: TPL-TXNPREFbot-OBLIGATORY grounded first if unsub all
TPB-5 Guardrail: MAP-GROUNDED OBLIGATORY-CITE NO-ZERO NO-LEGAL NO-UNSUB-EXEC
TPB-6 Respond: TPL-TXNPREFbot prefs marketing max 3 sentences
TPB-7 Handoff or close: #833 payload or close self-service guide OK
TPB-8 Log: intent obligatory_cited zero_promise_blocked handoff Y/N
Example TPL-TXNPREFbot-OBLIGATORY
" [obligatory_copy map.] Marketing only can be deactivated: [marketing_off_copy map.] Preferences: [prefs_link map.] OBLIGATORY-CITE-BOT. "
TPL-TXNPREFbot and touchpoints templates
Four short email preference embed templates.
TPL-TXNPREFbot-OBLIGATORY
[obligatory_copy map.] [email_type_matrix_copy map.] OBLIGATORY-CITE-BOT.
TPL-TXNPREFbot-MARKETING
[marketing_off_copy map.] Link: [prefs_link map.] MARKETING-OFF-DEFAULT-BOT.
TPL-TXNPREFbot-SYNC
[sync_delay_copy map.] If promo persists for 48 hours: handoff #833.
TPL-TXNPREFbot-FREQUENCY
[frequency_copy map.] Transactional unchanged. TXNPREF-MAP-GROUNDED-BOT.
Touchpoints
Keyword unsubscribe: bot_txnpref_obligatory instant
Keyword no more confirmation: bot_txnpref_resend_reroute #358
Footer unsub click event: bot_txnpref_unsub_all proactive explain
Keyword too many newsletters: bot_txnpref_marketing_off trigger
Edge cases and reroutes
Five cases outside tier 1 bot standard preferences.
Email not received: CONFEMAIL358-REROUTE-BOT resend distinct prefs
txnpref_gdpr_combo: gdpr_route_copy handoff DPO #833
Account deletion: ACCTDELbot #824 distinct preferences
Email change: #825 lists distinct prefs
Global suppress bug: TXNPREF833-HANDOFF ops fix config
Essential txnpref_bot KPIs
Five metrics for monitoring the sensitive TXNPREFbot.
txnpref_bot_clarity_deflect: closed, understood, with no agent repeat 7d
txnpref_bot_obligatory_cite_rate: OBLIGATORY-CITE / bot_txnpref unsub_all
txnpref_bot_zero_promise_violations: zero promise email target audit 0
txnpref_bot_reroute_358_rate: % not received correctly routed
txnpref_bot_handoff_rate: escalate #833 / total bot prefs
Target: txnpref_bot_zero_promise_violations 0 and txnpref_bot_obligatory_cite_rate greater than 95%.
TXNPREFbot anti-patterns
Five common email preference bot errors.
Promising zero emails: TXNPREF-NO-ZERO-PROMISE-BOT mandatory first
Executing unsub lists: NO-UNSUB-EXECUTE-BOT handoff #833
GDPR legal advice: NO-LEGAL-ADVICE-BOT map only
Confusing not received and unsub: CONFEMAIL358 reroute resend
Skipping mandatory on unsub all: OBLIGATORY-CITE mandatory before guide
TXNPREFbot with Qstomy
Qstomy on Shopify and Klaviyo: detect bot_txnpref intent preferences, TXNPREF-MAP RAG grounded, NO-ZERO-PROMISE guardrail, enriched handoff #833 tier 2.
Pipeline: #834 bot explain tier 1 → #833 agents execute unsub policy.
Explore AI support and request a demo.
Checklist, FAQ and going further
TXNPREFbot Checklist (8 steps)
Sync TXNPREF-MAP #833: RAG bot email prefs embed footer
Policy TXNPREFBOT-SUP: 6 rules OBLIGATORY-CITE NO-ZERO NO-LEGAL NO-UNSUB-EXEC
8 intents bot_txnpref_*: flow TPB-1 to TPB-8
4 templates TPL-TXNPREFbot-*: OBLIGATORY MARKETING SYNC FREQUENCY
Block unsub API: bot read-only lists no write Klaviyo
Red team 15 prompts: zero email promise unsub execute legal advice
Footer unsub proactive: bot_txnpref_obligatory trigger click
Dashboard KPI: txnpref_bot_* section 9 zero_promise_violations obligatory_cite
FAQ
Difference #833?
#833 = unsub agents Klaviyo resend document. #834 = bot explain guide tier 1.
Does the bot unsubscribe from lists?
No. NO-UNSUB-EXECUTE-BOT. TXNPREF833-HANDOFF humans TP-5.
Customer wants to stop everything?
bot_txnpref_obligatory TPL-TXNPREFbot-OBLIGATORY then marketing_off guide.
More confirmation?
bot_txnpref_resend_reroute CONFEMAIL358 distinct cut transactional.
Going further
This week: deploy TXNPREF-MAP RAG footer embed, red team zero_promise_violations audit, sync bot_txnpref_obligatory proactive unsub all explain test scenario.
Enzo
July 1, 2026
