E-commerce
July 1, 2026
"The bot says I'm eligible without checking my date of birth." "The AI promises to extend my expired code without escalation." "Chatbot creates a birthday code even though I already had one this year." Three failures where a miscalibrated birthday bot breaks lifecycle trust.
An AI birthday offers chatbot does not replace BDAY agents (#585). It reads BDAY-MAP, verify birthday_field DOB, cite eligibility_window expiry_ttl one_per_year stack_rules and handoff resend extend DOB fix to humans.
This guide #586 covers intents bot_bday_*, flow BDAYbot and KPI bday_bot. Bot pair from the playbook BDAY (#585). New relational AI use case: explain eligibility expiration code without issuing code or extending TTL.
Summary
Why automate birthday offers with a bot?
"My code didn't arrive", "am I eligible?" and "why expired?" return every peak anniversary month. A calibrated bot looks up BDAY-MAP, verifies DOB profile, cites TTL window without improvising extension.
What the tier 1 bot resolves
Eligibility check: birthday_field eligibility_window map
Code status: valid expired used Shopify API
Expiration cite: expiry_ttl_days since sending map
Stack policy: stack_rules cumul cite
Resend info: resend_flow map explain handoff if needed
Ometria estimates that birthday emails convert 2 to 3× the lifecycle average but generate tickets if DOB profile is missing (Klaviyo, birthday lifecycle 2026). The bot intercepts bot_bday_eligibility before agent-invented code.
BDAYbot vs BDAY #585, POFFbot #574, MEMSALEbot #584 and loyalty bot
Five contents, five distinct discount lifecycle triggers.
Quick matrix
#586 BDAYbot: bot tier 1 elig code expiry stack
#585 BDAY: agents resend DOB fix extend execute
#574 POFFbot: CRM segment behavior distinct offer
#584 MEMSALEbot: member sale distinct tier
Loyalty bot: loyalty program current rules
Pipeline: bot elig code expiry cite → #585 resend DOB fix extend marketing. CRM segment offer → POFFbot #574.
Which bot_bday_* intents should be configured?
Eight birthday bot intents mapped to typologies #585.
Eight bot_bday intents
bot_bday_eligibility: DOB window eligible yes no map
bot_bday_code_status: Shopify API code status map
bot_bday_expiry_info: expiry_ttl_days deadline mention
bot_bday_stack_info: stack_rules accumulation mention
bot_bday_resend_info: flow sent resend_flow explain
bot_bday_dob_info: birthday_field missing wrong account fix
bot_bday_campaign_info: campaign_id discount_value summary
bot_bday_handoff: resend extend DOB fix → #585
Tier 1 auto: eligibility, code_status, expiry_info, stack_info, resend_info if email auth + BDAY-MAP + guardrails.
bot_bday_handoff, resend execute, extend TTL, DOB fix → agents #585 payload email campaign_id intent.
How should BDAY-MAP #585 be consumed?
The bot reads BDAY-MAP #585: campaign_id, birthday_field_source, eligibility_window, discount_code_type, discount_value, expiry_ttl_days, one_per_year_policy, stack_rules, resend_flow.
Lookup grounded
Campaign lookup: campaign_id email birthday flow
Profile DOB API: Klaviyo Shopify birthday_field verify
Flow sent check: Klaviyo event birthday email sent
Discount API: code status usage one_per_year
DOB-VERIFY-BOT: birthday_field before eligibility yes
ONE-PER-YEAR-SCOPE-BOT: usage current year before new code
Alignment anti-hallucination (#123): elig expiry = BDAY-MAP or profile API only.
BDAYBOT-SUP policy in six rules
Six safe birthday bot rules.
BDAY-MAP-GROUNDED: elig expiry stack from map only
DOB-VERIFY-BOT: birthday_field profile API before elig yes
NO-CODE-ISSUE-BOT: bot does not issue or replace birthday code
NO-EXTEND-PROMISE-BOT: TTL extension → handoff #585
ONE-PER-YEAR-SCOPE-BOT: one offer per year map before reissue
POFF-PROMO-REROUTE-BOT: CRM segment → #574, site promo → #111
Flow BDAYbot BDB-1 to BDB-8
Flow eight steps birthday bot offer.
BDB-1 Classify: bot_bday_* intent detect
BDB-2 Email collect: email code campaign_id
BDB-3 BDAY-MAP: window expiry one_per_year stack
BDB-4 DOB verify: birthday_field Klaviyo Shopify DOB-VERIFY
BDB-5 Guardrail: NO-CODE NO-EXTEND ONE-PER-YEAR
BDB-6 Respond: TPL-BDAYbot grounded map
BDB-7 Handoff: resend extend DOB fix u2192 #585
BDB-8 Log: intent campaign_id tag bday_bot
Example TPL-BDAYbot-ELIG
u00ab Birthday offer [campaign_id] [email]: profile date [birthday_field]. Window [eligibility_window map]. [Eligible / out of window / missing date.] [If eligible: code [status] expires [expiry_ttl_days].] [If DOB fix: handoff agent.] u00bb
TPL-BDAYbot templates and touchpoints
Four essential templates.
TPL-BDAYbot-ELIG
Offer [campaign_id]: [eligible / not eligible]. Profile date [birthday_field]. Window [eligibility_window]. [If no: correction [account_url] or handoff #585.]
TPL-BDAYbot-CODE
Code [code]: [status: valid / expired / already used / conditions]. Discount [discount_value map]. Expires [expiry date TTL]. Exclusions [exclusions].
TPL-BDAYbot-STACK
Birthday code stacking [code]: [stack_rules map]. [If rejected: one discount applicable at checkout.] Site offers: [promo link #111].
TPL-BDAYbot-HANDOFF
Request [resend / extend / DOB fix] forwarded to agent. Email [email]. Campaign [campaign_id]. Delay [handoff_sla].
Touchpoints
Birthday landing email: bot_bday_code_status embed
Checkout code error: bot_bday_code_status chip
Account birthday field: bot_bday_dob_info widget
FAQ lifecycle: bot embed BDAY-MAP RAG
Edge cases and reroutes
Five non-tier 1 cases bot standard birthday.
Code resend execute: NO-CODE-ISSUE handoff #585 BDAY-RESEND-01
Extension TTL requested: NO-EXTEND-PROMISE handoff #585 EXTEND-ESCALATE
Segmented CRM offer: POFFbot #574 reroute
Third-party birthday gift: DGIFT #419 distinct profile
Member sale: MEMSALEbot #584 reroute
Bot never issues code: resend extend DOB fix → agents #585 ops CRM marketing.
Essential bday_bot KPIs
Five BDAYbot steering metrics.
bday_bot_elig_deflect: eligibility resolved without agent
bday_bot_code_deflect: code_status resolved without handoff
bday_bot_handoff_rate: resend extend DOB / total bday bot
bday_bot_hallucination_rate: elig expiry out of audit map
bday_bot_reroute_accuracy: POFF MEMSALE promo reroute correct
Target: bday_bot_elig_deflect higher than 70% in peak birthday month with BDAY-MAP sync DOB profile.
BDAYbot anti-patterns
Five common birthday bot errors.
Eligible without DOB verify: DOB-VERIFY-BOT profile first
TTL extension promise: NO-EXTEND-PROMISE-BOT handoff #585
Bot-issued code: NO-CODE-ISSUE-BOT marketing ops
Double offer same year: ONE-PER-YEAR-SCOPE-BOT usage check
POFF CRM confusion: POFF-PROMO-REROUTE #574 #111
BDAYbot with Qstomy
Qstomy on Shopify: detect bot_bday intent, BDAY-MAP RAG grounded, Klaviyo DOB flow lookup, Shopify discount verify, handoff #585 resend extend payload campaign_id.
Pipeline: #586 bot elig code expiry → #585 resend DOB fix execute marketing.
Explore AI support and request a demo.
Checklist, FAQ and going further
BDAYbot Checklist (8 steps)
Sync BDAY-MAP #585: RAG bot + Klaviyo DOB API
Policy BDAYBOT-SUP: 6 NO-CODE-ISSUE-BOT rules
8 intents bot_bday_*: flow BDB-1 to BDB-8
4 templates TPL-BDAYbot-*: ELIG CODE STACK HANDOFF
Checkout error chip: bot_bday_code_status entry
Account DOB widget: bot_bday_dob_info embed
Red team 10 prompts: code issued extend promised double offer
Dashboard KPI: bday_bot_* section 9
FAQ
Difference #585?
#585 = agents resend DOB fix extend execute. #586 = bot tier 1 elig code expiry handoff.
Does the bot create a code?
No. NO-CODE-ISSUE-BOT. Handoff #585 CRM ops.
Expired code extend?
NO-EXTEND-PROMISE-BOT. Handoff #585 EXTEND-ESCALATE.
Difference POFFbot #574?
#574 = CRM segment offer. #586 = birthday date trigger one per year.
Going further
This week: index BDAY-MAP RAG, embed birthday email bot landing, red team extend TTL promised bot.
Enzo
July 1, 2026
