E-commerce
July 1, 2026
"I have never accepted your AI recommendations." "How do I disable automated suggestions?" "Where did you record my consent?" Three tickets where the AI recommendations consent lacks a clear support response.
The e-commerce AI reco consent support covers opt-in, withdrawal, legal basis, and the distinction between AI reco vs. profile preferences. Completes pref management (#857) and privacy toggles (#849): here, the customer queries the explicit consent to the AI recommendation engine.
This guide #861 deploys the AIRECOCON-SUP policy, flow RC-1 to RC-8, and the AIRECOCON-MAP matrix. CS pair of the future consent bot (#862).
Summary
Why does the AI recommendation consent generate tickets?
AI recommendation widgets, shopping assistants, and model-personalized emails trigger suggestions without the customer understanding the consent mechanism. They confuse AI recommendations, tracking #853, and profiling #857. The agent redirects to privacy #849 without explaining the specific AI recommendation opt-out.
Five typical AI recommendation consent frictions
Never consented: active AI recommendations without remembering accepting them
Opt-out requested: wants to disable automated suggestions
Consent withdrawal: wants to retract previously given agreement
Legal basis: inquires about the basis for the AI processing
Channel confusion: mixes up AI recommendations, cookies, and account profiling
The CNIL points out that consent must be free, specific, and revocable (CNIL, consent 2026).
DTC Example
DTC mode, 10 airecocon_/month tickets. After AIRECOCON-MAP: airecocon_clarity_resolution_rate 90 %, useless PRIVPREF #849 routings -40 %.
AIRECOCON #861 vs PERFPREF #857, PRIVPREF #849, TRACKOPT #853 and bot #862
Seven pieces of content, seven distinct consent personalization angles.
Quick Matrix
#861 AIRECOCON: explicit consent AI recommendations opt-in opt-out
PERFPREF #857: interests profile distinct content AI engine agreement
PRIVPREF #849: toggles privacy marketing cookies legal
TRACKOPT #853: opt-out pixels retargeting distinct AI reco
OVERPERS #855: intrusive discomfort distinct formal consent
IRECO #439: off-topic reco quality distinct consent
#861 = did I consent to AI reco? #857 = I want to adjust my taste profile.
Promise #861
Policy AIRECOCON-SUP, tree AIRECOCON-GATE, 8 macros, consent vs prefs vs tracking matrix, KPI airecocon_clarity_resolution_rate.
Which airecocon_* typologies should be classified?
Action-oriented classifier: AI reco opt-out u2260 handoff PERFPREF #857 u2260 handoff PRIVPREF #849.
Eight AIRECOCON-MAP typologies
airecocon_opt_out_ai_reco: wants to deactivate AI recommendations
airecocon_opt_in_ai_reco: wants to activate or reactivate AI reco
airecocon_consent_ask: how and when did I consent
airecocon_withdraw_consent: withdraw consent for AI reco
airecocon_default_on_concern: AI reco active without explicit request
airecocon_confused_privacy: mixes up AI reco and marketing cookies
airecocon_consent_history: requests reco consent history
airecocon_gdpr_combo: formal GDPR request + AI reco
AIRECOCON-SUP Policy: agents and escalation rules
The AIRECOCON-SUP policy defines AI recommendation consent pedagogy without promising zero suggestions or ignoring withdrawal.
Six AIRECOCON-SUP rules
CHANNEL-DIFF first: macro AIRECOCON-CHANNEL-DIFF AI reco vs cookies vs profile
AI reco opt-out only: AIRECOCON-OPT-OUT without cutting off transactional
Explain legal basis: AIRECOCON-CONSENT-BASIS documented consent or legitimate interest
Withdrawal as simple as granting: AIRECOCON-WITHDRAW self-service guide
48-hour sync delay: AIRECOCON-SYNC after opt-out or opt-in
Formal GDPR → DPO: airecocon_gdpr_combo legal handoff
Channel matrix (agent)
Engine AI Reco: widgets, assistant, AI-model emails
Declared profile: PERFPREF #857 handoff if style interests
Marketing tracking: TRACKOPT #853 handoff if pixels
Legal privacy: PRIVPREF #849 handoff if CMP toggles
Flow RC-1 to RC-8: standard resolution
Eight sequential steps, SLA P3 consent < 24 h, escalate DPO if gdpr_combo.
Flow RC-1 to RC-8
RC-1 Triage: read request, tag airecocon_*, AI or privacy recommendation?
RC-2 Lookup: recommendation consent status, date, channel, active profile
RC-3 Educate: CHANNEL-DIFF if confused_privacy
RC-4 Classify: airecocon_* via AIRECOCON-MAP
RC-5 Execute: OPT-OUT, OPT-IN, WITHDRAW, handoff #857 #849 #853
RC-6 Confirm: macro AIRECOCON-DONE scope and timeline
RC-7 Test: client understands consent status and action taken
RC-8 Close: KPI airecocon_clarity_resolution_rate
Eight ready-to-paste AIRECOCON-* macros
Educational macros aligned with the internal AI reco consent registry.
AIRECOCON-* Library
AIRECOCON-EXPLAIN: "Our AI recommendations personalize suggestions based on your browsing and profile, with your consent."
AIRECOCON-OPT-OUT: "Disable AI recommendations in Account > Preferences > AI Recommendations. Orders remain unchanged."
AIRECOCON-OPT-IN: "Enable AI recommendations in the same preferences for more relevant suggestions."
AIRECOCON-CONSENT-BASIS: "Basis: {{basis}}. Consent recorded on {{date}} via {{canal}}."
AIRECOCON-WITHDRAW: "Withdraw your AI reco consent in one click. Just as simple as the initial acceptance."
AIRECOCON-CHANNEL-DIFF: "AI reco, marketing cookies, and taste profile are separate settings."
AIRECOCON-SYNC: "After modification, allow 24 to 48 hours to see the change across the entire site."
AIRECOCON-DONE: "Summary: {{action}}. Delay {{delay}}. Contact us if AI reco persist."
AIRECOCON-GATE tree and agent-ready consent registry
Decision tree before unjustified PRIVPREF or PERFPREF handoff.
AIRECOCON-GATE
Wants to turn off AI recommendation? → OPT-OUT + SYNC
Asks when did I consent? → CONSENT-BASIS registry lookup
Cookie confusion? → CHANNEL-DIFF + handoff #853 or #849
Wants to adjust profile preferences? → handoff PERFPREF #857
Formal GDPR request? → DPO, do not use macro alone
Minimum internal registry
Document helpdesk: AI recommendation toggle path, legal basis, engine sync delay, withdrawal procedure. Train agents: AI recommendation consent ≠ marketing toggle #849.
KPI, QA and handoff to bot #862
Measuring AIRECOCON detects wrong privacy silo and under-explained withdraw.
Four AIRECOCON KPIs
airecocon_clarity_resolution_rate: customer understands consent / total
airecocon_wrong_silo_rate: % routed to #849 or #857 in error alone
airecocon_withdraw_guided_rate: % withdraw with WITHDRAW or OPT-OUT
airecocon_repeat_7d: same consent question within 7 days
Handoff bot #862
Export AIRECOCON-MAP to intents bot_airecocon_opt_out, bot_airecocon_consent_ask. Guardrail AIRECOCON-NO-FORCE-BOT: ask for consent recommendation without blocking navigation.
Edge cases: guest, legitimate interest, shopping assistant
Three cases outside the standard flow.
Guest without an account
Opt-out via CMP banner or footer link. CHANNEL-DIFF + cookies if no account center.
Documented legitimate interest
CONSENT-BASIS explains legal basis and right to object if applicable. Do not promise consent alone.
AI shopping assistant
Separate assistant consent from recommendation widgets. EXPLAIN perimeter of each AI tool.
Agent training: 20 minutes AIRECOCON
Module: AI reco ≠ privacy, simple WITHDRAW, systematic CHANNEL-DIFF, PERFPREF if taste profile.
Exercises
Ticket A: stop AI reco → OPT-OUT not #849 alone
Ticket B: when did I consent → CONSENT-BASIS lookup
Ticket C: adjust skincare makeup → handoff #857 not AIRECOCON
How Qstomy structures AIRECOCON in your stack
Qstomy route airecocon_*, displays AI recommendation consent status and handoff #862 for progressive opt-in request.
Three building blocks
Routing: intent ai_reco_consent vs privacy_prefs vs perfpref_profile
Consent registry: sync macros AIRECOCON-* client state
Bot #862: ask for tier 1 agreement without forcing
Scenario: lifestyle brand, 9 tickets/month recommendation consent. Bot #862 offers skippable opt-in, agents handle withdraw and history. airecocon_clarity_resolution_rate goes from 71% to 89% in 5 weeks.
FAQ and AIRECOCON deployment checklist
FAQ
AI reco opt-out = no more suggestions?
Generic suggestions are still possible. OPT-OUT disables AI personalization, not the catalog.
Difference from #857?
#861 = AI reco engine agreement. #857 = declared interest centers and taste profile.
Difference from #849?
#861 = AI reco consent. #849 = legal marketing cookies privacy toggles.
7-day Checklist
D1: AIRECOCON-SUP + AIRECOCON-MAP + consent register
D2: 8 helpdesk macros
D3: routing matrix #857 #849 #853
D4: 20 min agent training
D5: airecocon_* tags + KPIs
D6: WITHDRAW vs OPT-OUT test
D7: bot brief #862 NO-FORCE-GATE
Interlinking
Enzo
July 1, 2026
