E-commerce
July 1, 2026
Customer: "Your ad promises -30%, the site shows full price." The bot denies it or promises a refund without proof. Ticket adlc_ad_landing_gap.
An e-commerce campaign mismatch AI chatbot collects UTM URLs and screenshots, qualifies the ad-to-landing-checkout gap from ADLC-MAP #931, deflects tier 1, and escalates to marketing if the pattern is confirmed.
This guide #932 covers bot_adlc_* intents, flows ADLCBOT ALB-1 to ALB-8, and PROOF-COLLECT-BOT guardrails. Bot pair of the ADLC playbook (#931). Use case: widget marketing escalation proof collection.
Summary
Why botify the mismatch proof collection?
The customer describes a discrepancy even before attaching a screenshot. Without a proof structure, the bot denies or promises without a registry. FUNNEL-REGISTRY-GATE aligns the widget and agents #931.
What the tier 1 bot mismatch resolves
Proof collection: URL UTM, landing page screenshot
Discrepancy qualification: ad-landing vs landing-checkout
Registry comparison: funnel map promise
Corrected link: fix_link if registry mismatch is known
Marketing escalation: ops_flag massive pattern
DTC Retail Example
DTC Fashion, 14 tickets/month adlc_. Bot proof collect. adlc_bot_deflect +44%, adlc_ops_flag_rate +38% structured reports in 5 weeks.
ADLCBOT #932 vs ADLC #931, EXPIAD #930, CHECKOUT #386 and ATTACH #877
Seven funnel bot contents, seven distinct roles.
Quick matrix
#932 ADLCBOT: tier 1 bot collects proof qualifies gap marketing escalation
ADLC #931: agents reproduce resolve ops ALC-4
EXPIAD #930: expired offer distinct mismatch live
CHECKOUT #386: checkout form distinct ad promise
ATTACH #877: attachment procedure handoff agents
PROMO sync #886: active promo sync distinct funnel mismatch
Pipeline: customer reports gap → #932 proof classify tier 1 → handoff #931 if reproduce bridge.
Which bot_adlc_* intents should be configured?
Eight campaign mismatch intents mapped to ADLC-MAP #931.
Eight bot_adlc intents
bot_adlc_mismatch_detect: detect gap between ad, landing, and checkout quotation
bot_adlc_proof_collect: request UTM URL and path screenshot
bot_adlc_registry_compare: compare funnel promise with registry
bot_adlc_gap_classify: shipping mismatch (ad_landing vs landing_checkout)
bot_adlc_fix_link_offer: corrected code link if registry is known
bot_adlc_no_mismatch_explain: compliant user journey explanation
bot_adlc_ops_escalate: massive pattern → marketing #931
bot_adlc_feed_loop: consume LOG #931 funnel_registry
Each interaction logs utm_campaign, adlc_* intent, and deflect_or_handoff.
How to consume ADLC-MAP #931?
The bot reads ADLC-MAP #931 + bot fields: campaign_id, ad_copy, landing_url, checkout_code, shipping_promise, sku_collection, proof_fields_required, fix_link_url, fix_code, no_mismatch_explain_copy, ops_escalate_threshold, agent_handoff_url, funnel_registry_active.
Bot campaign mismatch guardrails
FUNNEL-REGISTRY-GATE : compares promise from registry only
PROOF-COLLECT-BOT : URL capture before mismatch confirmation
NO-AUTO-CONFIRM-BOT : do not confirm mismatch without minimum proof
NO-AUTO-BRIDGE-BOT : agent goodwill gesture #931 only
FIX-LINK-GROUNDED-BOT : link code from known registry
OPS-ESCALATE-BOT : UTM ticket threshold → marketing flag
AGENT-HANDOFF-BOT : reproduce bridge → agent #931
ADLC-FEED-LOOP-BOT : LOG #931 enriches funnel_registry widget
ADLCBOT-SUP policy in six rules
Six mismatch campaign manager rules on the widget side.
FUNNEL-REGISTRY-GATE: registry lookup before gap response
PROOF-COLLECT-BOT: proof_collect before gap_classify
NO-AUTO-CONFIRM-BOT: no MISMATCH-OK without proof
FIX-LINK-GROUNDED-BOT: fix_link known registry only
OPS-ESCALATE-BOT: UTM pattern marketing threshold
ADLC-FEED-LOOP-BOT: LOG #931 widget review within 48 hours
ADLCBOT ALB-1 to ALB-8 flow
Eight-step flow: mismatch detect proof collect registry classify answer escalate log.
ALB-1 Ingest: gap message ad landing checkout abandon
ALB-2 Mismatch detect: quote broken promise
ALB-3 Proof collect: UTM URL ad landing capture
ALB-4 Registry compare: FUNNEL-REGISTRY-GATE lookup
ALB-5 Classify gap: ad_landing landing_checkout shipping
ALB-6 Tier 1 answer: fix_link no_mismatch ops_escalate
ALB-7 Handoff: bridge reproduce → agent #931
ALB-8 Log: deflect proof_complete ops_escalate
Example TPL-ADLC-PROOF
"To verify the gap, please share the page URL or an ad + landing image."
TPL-ADLC Templates and touchpoints
Four short mismatch embed templates.
TPL-ADLC-PROOF
[proof_fields map.] URL or screenshot. PROOF-COLLECT.
TPL-ADLC-GAP
[gap_type map.] Qualified gap. Under verification. NO-AUTO-CONFIRM.
TPL-ADLC-FIX
[fix_link_url map.] [fix_code map.] FIX-LINK-GROUNDED.
TPL-ADLC-ESCALATE
[ops_flag_copy map.] Reported to marketing. OPS-ESCALATE.
Touchpoints
"Lying ad": proof_collect + gap_classify
Shared URL: registry_compare classify
Known registry fix: fix_link_offer tier 1
LOG ADLC #931: feed_loop funnel_registry
Edge cases: incomplete proof, compliant path, massive pattern
Five cases outside the standard flow.
Incomplete proof: proof_collect follow-up without denying
Registry compliant path: no_mismatch_explain copy map
Known registry fix: fix_link_offer without agent handoff
Refund request: NO-AUTO-BRIDGE handoff #931
5+ sessions same UTM 24 h: immediate marketing ops_escalate
Essential adlc_bot KPIs
Five ADLCBOT monitoring metrics and #931 correlation.
adlc_bot_deflect: qualified mismatches without adlc_ ticket
adlc_bot_proof_complete_rate: % of sessions with collected proof
adlc_bot_gap_classify_accuracy: % gap type aligned agent #931
adlc_bot_ops_escalate_rate: % patterns routed to marketing
adlc_bot_false_confirm: confirmations without proof target 0
Target: false_confirm at zero and proof_complete above 70%.
ADLCBOT anti-patterns
Five common errors mismatch campaign bot.
Confirming without proof: NO-AUTO-CONFIRM mandatory
Promising refund: NO-AUTO-BRIDGE agent #931
Invented link: FIX-LINK-GROUNDED registry only
Ignoring ops pattern: OPS-ESCALATE UTM threshold
Duplicating #386: #932 funnel promise ads only
ADLCBOT with Qstomy
Qstomy on Shopify: ADLC-MAP sync #931, proof fields UTM, templates PROOF FIX ESCALATE, ops escalate marketing dashboard, KPI adlc_bot.
Scenario: DTC mode, 14 tickets/month. Funnel registry sync. adlc_bot_deflect +44 %, adlc_ tickets -35 % in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist ADLCBOT (8 steps)
Sync ADLC-MAP #931: promise funnel fix_link proof fields
Policy ADLCBOT-SUP: 6 rules REGISTRY-GATE PROOF-COLLECT
8 intents bot_adlc_*: flow ALB-1 to ALB-8
4 templates TPL-ADLC-*: PROOF GAP FIX ESCALATE
proof_fields: URL capture ad landing minimum
ops_escalate_threshold: threshold UTM sessions 24 h
Red team mismatch: false confirm bridge link test
Dashboard KPI: adlc_bot_* section 9 + delta adlc_
FAQ
Difference #931?
#931 = agents reproduce resolve bridge ops. #932 = bot collects proof qualifies tier 1.
Difference #930?
#930 = expired ad offer. #932 = mismatch live current user journey.
Difference #386?
#386 = checkout fields. #932 = ads funnel campaign promise.
Does bot confirm mismatch alone?
No if fix registry unknown. Handoff #931 reproduce.
Going further
This week: sync ADLC-MAP #931, proof_collect flow, ops escalate threshold, measure adlc_bot_deflect.
Enzo
July 1, 2026
