E-commerce
July 1, 2026
"The bot created a -30% code for me even though I'm not eligible." "The AI explains why my friend has a better offer." "Chatbot promises to extend my expired code without checking the segment." Three failures where a poorly calibrated personalized offer bot creates fraudulent codes or leaks segment information.
A personalized offers AI chatbot does not replace POFF agents (#573). It reads POFF-MAP, verifies profile eligibility, quotes min_spend exclusions stack_rules expiry_ttl, and hands off reissue adjust to humans.
This guide #574 covers intents bot_poff_*, flow POFFbot, and KPI poff_bot. Paired bot of the POFF playbook (#573). New segmented AI use case: verify eligibility and explain terms without issuing a code or disclosing third-party criteria.
Summary
Why automate personalized offers with a bot?
"My code is not working," "am I eligible?" and "can I combine this with another promo?" are common questions after a CRM email. A calibrated bot looks up offer_campaign_id, checks the Shopify Klaviyo segment, and cites POFF-MAP conditions.
What the tier 1 bot resolves
Eligibility check: profile in segment map or not
Conditions cited: min_spend, exclusions, discount_type
Code status: valid, expired, max usage Shopify API
Combination policy: cites stack_rules without making promises
Expiration: cites expiry_ttl deadline
McKinsey estimates that marketing personalization can increase revenues by 10 to 15%, but it also multiplies support tickets if terms are opaque (McKinsey, personalization 2026). The bot intercepts bot_poff_conditions before any invented code is used.
POFFbot vs POFF #573, promo #111, private sale #250 and ambassador #575
Five contents, five discount and code models.
Quick matrix
#574 POFFbot: bot tier 1 elig conditions code status
#573 POFF: agents reissue extend adjust execute
Promo #111: general site offers reroute
Private sale #250: gated distinct CRM offer access
#575 ambassador: distinct attribution influencer code
Pipeline: bot elig conditions cite → #573 reissue adjust execute. Public site code → promo #111.
Which bot_poff_* intents should be configured?
Eight bot personalized offer intents mapped to #573 typologies.
Eight bot_poff intents
bot_poff_eligibility: profile segment yes no map
bot_poff_conditions: min_spend exclusions discount
bot_poff_code_status: Shopify API code status
bot_poff_stack_info: stack_rules accumulation quote
bot_poff_expiry_info: expiry_ttl deadline
bot_poff_campaign_info: offer_campaign summary public
bot_poff_fairness: third-party comparison without disclosing segment
bot_poff_handoff: reissue extend adjust → #573
Tier 1 auto: eligibility, conditions, code_status, stack_info, expiry_info if email auth + POFF-MAP + guardrails.
bot_poff_handoff, reissue extend → agents #573 payload code email intent.
How to consume POFF-MAP #573?
The bot reads POFF-MAP #573: offer_campaign_id, segment_rules, discount_type, code_type, min_spend, exclusions, stack_rules, expiry_ttl.
Lookup grounded
Campaign lookup: offer_campaign_id email flow
POFF-MAP row: segment discount conditions stack expiry
Profile API: Klaviyo Shopify segment tag match
Discount API: Shopify code status usage
ELIG-VERIFY-BOT: profile API eligibility only
SEGMENT-PRIVACY-BOT: third-party criteria never disclosed
Alignment anti-hallucination (#123): conditions = POFF-MAP or discount API only.
POFFBOT-SUP policy in six rules
Six rules bot secure personalized offer.
POFF-MAP-GROUNDED: stack expiry conditions from map only
ELIG-VERIFY-BOT: profile API eligibility before response
NO-CODE-ISSUE-BOT: bot does not issue or extend code
SEGMENT-PRIVACY-BOT: third-party segment criteria never cited
NO-EXTEND-PROMISE-BOT: extension → handoff #573
PROMO-REROUTE-BOT: general site promo → #111 intents
Flow POFFbot POB-1 to POB-8
Eight-step flow personalized offer bot.
POB-1 Classify: bot_poff_* intent detect
POB-2 Email collect: email code offer_campaign_id
POB-3 POFF-MAP: segment conditions stack expiry
POB-4 Profile verify: Klaviyo Shopify segment ELIG-VERIFY
POB-5 Guardrail: NO-CODE SEGMENT-PRIVACY NO-EXTEND
POB-6 Respond: TPL-POFFbot grounded
POB-7 Handoff: reissue extend adjust → #573
POB-8 Log: intent offer_campaign_id tag poff_bot
Example TPL-POFFbot-COND
"Offer [offer_campaign_id]: [discount_type] [If eligible: code [code] valid until [expiry_ttl].] Min [min_spend]. Exclusions [exclusions]. Accumulation [stack_rules map]. [If not eligible: no extension, site offers [link].]"
TPL-POFFbot and touchpoint templates
Four essential templates.
TPL-POFFbot-ELIG
Profile [email]: [eligible / not eligible offer_campaign_id]. [If yes: conditions below.] [If no: segment_rules summary public without third-party criteria.] Current offers: [promo link].
TPL-POFFbot-CODE
Code [code]: [Shopify status: valid / expired / max usage / product excluded]. Min [min_spend]. Exclusions [exclusions]. Valid [expiry_ttl].
TPL-POFFbot-STACK
Stacking other promos: [stack_rules map]. [If refused: active checkout discount only.] Agent if exception map.
TPL-POFFbot-HANDOFF
Request [reissue / extension / price adjust] forwarded to agent. Code [code]. Email [email]. SLA [handoff_sla].
Touchpoints
Checkout code error: bot_poff_code_status chip
Email offer landing: bot_poff_conditions embed
Post-open chat: bot_poff_eligibility entry
FAQ personal offers: bot embed POFF-MAP RAG
Edge cases and reroutes
Five cases out of tier 1 bot standard conditions.
Code reissue requested: NO-CODE-ISSUE-BOT handoff #573 POFF-CODE-01
Expired extension: NO-EXTEND-PROMISE handoff #573 POFF-EXPIRED-01
General site promo: PROMO-REROUTE #111
Ambassador code: #575 attribution influencer reroute
Ad hoc discount request: discount request outside POFF map
Bot never issues code: reissue extend adjust → agents #573 ops CRM.
Essential poff_bot KPIs
Five POFFbot management metrics.
poff_bot_elig_deflect: eligible sessions under conditions without human ticket
poff_bot_code_status_deflect: tier 1 bot code diagnostics
poff_bot_code_issued: codes issued by bot, target 0
poff_bot_segment_leaked: third-party criteria cited by bot, target 0
poff_bot_handoff_rate: sessions → #573 agents
Monthly red team: 10 prompts "create a code for me", "why him not me detail", "extend my code". Code issued = NO-CODE-ISSUE-BOT violation.
POFFbot anti-patterns
Six common mistakes.
Issued code bot : NO-CODE-ISSUE-BOT
Promised extension : NO-EXTEND-PROMISE-BOT
Disclosed third-party segment : SEGMENT-PRIVACY-BOT
Eligibility without verification : ELIG-VERIFY-BOT
Made-up conditions : POFF-MAP-GROUNDED
Site promo confusion : PROMO-REROUTE #111
POFFbot with Qstomy
Qstomy on Shopify: detect bot_poff intent, POFF-MAP RAG, Klaviyo segment lookup, Shopify discount verify, NO-CODE guardrail, handoff #573 reissue payload.
Pipeline: bot tier 1 elig conditions → #573 reissue adjust execute → AI governance #142 audit poff bot.
Explore AI support and request a demo.
Checklist, FAQ and going further
POFFbot Checklist (8 steps)
Sync POFF-MAP #573: RAG bot + Klaviyo segment API
Policy POFFBOT-SUP: 6 NO-CODE-ISSUE-BOT rules
8 intents bot_poff_*: flow POB-1 to POB-8
4 templates TPL-POFFbot-*: ELIG CODE STACK HANDOFF
Checkout error chip: bot_poff_code_status entry
Shopify discount API: code verify live
Red team 10 prompts: code issued segment leak extend
Dashboard KPI: poff_bot_* section 9
FAQ
Difference #573?
#573 = agents reissue extend adjust execute. #574 = bot tier 1 elig conditions handoff.
Does the bot create a code?
No. NO-CODE-ISSUE-BOT. Handoff #573.
Why not me?
TPL-POFFbot-ELIG SEGMENT-PRIVACY. Does not meet third-party criteria.
Difference ambassador #575?
#575 = influencer code attribution. #574 = segmented CRM email offer.
Going further
This week: sync POFF-MAP Klaviyo bot, red team "create code -30%", measure poff_bot_code_issued. Activate checkout code error chip.
Enzo
July 1, 2026
