E-commerce
July 1, 2026
"The bot says my discount is still active while Recharge bills full price." "The AI promises a -15% extension without checking the grandfather policy." "Chatbot invents an off-map transition code." Three failures where a poorly calibrated end-of-discount bot denies the expiration, promises an extension, or ad hoc discount.
An e-commerce recurring end-of-discount AI chatbot does not replace RECDISC agents (#713). It reads RECDISC-MAP, quotes duration_rule end_trigger, notification_schedule, and handoff grandfather cancel to humans.
This guide #714 covers intents bot_recdisc_*, flow RECDISCbot, and KPI recdisc_bot. Bot pair of the RECDISC playbook (#713). AI use case: explain expiration, propose transition without invented extension or denying end of discount.
Summary
Why automate the end of discounts using a bot?
"Why did my discount disappear?", "how much is the next charge?" and "can I keep current -15%?" come up as early as the D-7 end-of-discount email or the updated next_charge subscription portal. A calibrated bot cites RECDISC-MAP duration, end, notify, transition without denying the renewal date or promising an out-of-policy extension.
What the bot resolves tier 1 recurring discount end
Why end: duration_rule end_trigger END-CITE map
Notification: notification_schedule NOTIFY-CITE map
Renewal price: Recharge next_charge API verify
Transition offer: transition_offer_copy suggest map
Extension refusal: grandfather_policy NO-EXTEND-PROMISE map
Recharge points out that subscription discounts may expire after N cycles (Recharge, subscription discounts 2026). Without a grounded bot, AI amplifies churn or commercial promises outside the map.
RECDISCbot vs RECDISC #713, promo #111, autodisc #602 and cancel #373
Six contents, six distinct pricing benefit moments.
Quick matrix
#714 RECDISCbot: bot tier 1 end notify transition extend handoff
#713 RECDISC: agents grandfather exception redirect #373
Promo #111: distinct site campaign offer recurring account benefit
Autodiscbot #602: auto cart discount distinct diagnostic end personal discount
Cancel save #373: retention cancellation distinct explain commitment first
REXOFFbot #698: returning-only eligibility distinct expired recurring discount
Pipeline: #714 bot explain end transition tier 1 → #713 agents grandfather exception redirect #373.
Which bot_recdisc_* intents should be configured?
Eight discount end bot intents mapped to recdisc_* typologies #713.
Eight bot_recdisc intents
bot_recdisc_why_ended: duration_rule end_trigger END-CITE map
bot_recdisc_not_notified: notification_schedule NOTIFY-CITE map
bot_recdisc_renewal_price: Recharge next_charge amount verify
bot_recdisc_transition: transition_offer_copy transition_offer_id map
bot_recdisc_extend: grandfather_policy NO-EXTEND-PROMISE
bot_recdisc_cancel_threat: END-CITE then CANCEL373-REROUTE
bot_recdisc_sub_lookup: subscription_id discount status API
bot_recdisc_handoff: grandfather exception → #713
Tier 1 auto: why_ended, renewal_price, transition, not_notified if RECDISC-MAP active + guardrails.
bot_recdisc_handoff grandfather exception transition apply → agents #713 payload subscription intent.
How should RECDISC-MAP #713 be consumed?
The bot reads RECDISC-MAP #713: recdisc_program_id, discount_type, discount_rate_summary, duration_rule, end_trigger, end_date_or_order, notification_schedule, transition_offer_id, transition_offer_copy, grandfather_policy, customer_communication_copy.
Lookup grounded
END-CITE-BOT: duration_rule end_trigger cite map verbatim
NOTIFY-CITE-BOT: notification_schedule cite si not_notified map
NO-EXTEND-PROMISE-BOT: grandfather_policy cite map only
NO-INVENT-DISCOUNT-BOT: transition_offer_id map only validated
RECHARGE-VERIFY-BOT: discount status next_charge API before claim
TRANSITION-SUGGEST-BOT: transition_offer_copy map only
CANCEL373-REROUTE-BOT: intent cancel → #373 after END-CITE explained
RECDISC713-HANDOFF-BOT: grandfather exception → #713 agents RD-7
Alignment anti-hallucination (#123): duration end transition = RECDISC-MAP whitelist only.
RECDISCBOT-SUP Policy in six rules
Six bot rules end recurring discount manager.
RECDISC-MAP-GROUNDED-BOT : duration end transition from map only
END-CITE-BOT : end_trigger duration_rule cite confirmed expiration
NOTIFY-CITE-BOT : notification_schedule cite if not_notified map
NO-EXTEND-PROMISE-BOT : grandfather_policy cite map only
NO-INVENT-DISCOUNT-BOT : no bot discount outside of transition_offer map
AUTODISC602-REROUTE-BOT : cart checkout discount → #602 autodisc distinct account benefit
Flow RECDISCbot RDB-1 to RDB-8
Eight-step recurring discount end bot flow.
RDB-1 Classify: bot_recdisc_* intent detect portal email widget
RDB-2 Collect: subscription_id email order_ref if dispute
RDB-3 RECDISC-MAP: duration end notify transition grandfather
RDB-4 Sub lookup: Recharge discount status next_charge verify
RDB-5 Guardrail: END NOTIFY NO-EXTEND NO-INVENT CANCEL373 HANDOFF
RDB-6 Respond: TPL-RECDISCbot grounded customer_communication_copy
RDB-7 Handoff or close: grandfather exception cancel #713 #373 payload
RDB-8 Log: intent recdisc_program_id tag recdisc_bot end handoff Y/N
Example TPL-RECDISCbot-END
"Discount [recdisc_program_id map] [discount_rate_summary map]: [duration_rule map verbatim.] End based on [end_trigger map]: [end_date_or_order map.] Next charge [next_charge amount] €. END-CITE-BOT."
TPL-RECDISCbot and touchpoints templates
Four essential templates.
TPL-RECDISCbot-END
Discount [recdisc_program_id] [discount_rate_summary map]: [duration_rule map.] End [end_trigger map] [end_date_or_order map.] END-CITE-BOT.
TPL-RECDISCbot-NOTIFY
Scheduled notifications: [notification_schedule map.] [If Klaviyo log: send date.] NOTIFY-CITE-BOT.
TPL-RECDISCbot-TRANSITION
After expiration: [transition_offer_copy map.] [transition_offer_id map if eligible.] Next cycle [next_charge amount] €. TRANSITION-SUGGEST-BOT.
TPL-RECDISCbot-HANDOFF
Request [grandfather exception / transition apply / cancel] forwarded to team. Recap [subscription_id intent]. RECDISC713-HANDOFF-BOT or CANCEL373-REROUTE-BOT.
Touchpoints
D-7 discount end email footer chat: bot_recdisc_why_ended proactive
Subscription portal next_charge widget: bot_recdisc_renewal_price entry
Extend discount keyword: bot_recdisc_extend handoff
Post-charge full price: bot_recdisc_not_notified trigger
Edge cases and reroutes
Five cases outside tier 1 bot draft standard discount.
Subscription cancellation: CANCEL373-REROUTE-BOT #373 cancel save after END-CITE
Auto cart discount: AUTODISC602-REROUTE-BOT #602 distinct checkout diagnostic
Simultaneous catalog increase: #712 PRICEINCbot price increase reroute
Returning offer: #698 REXOFFbot distinct eligibility expired discount
Transition apply bot: NO-INVENT-DISCOUNT-BOT transition_offer agents #713 only
Bot explain end tier 1. Grandfather exception transition apply → agents #713.
Essential recdisc_bot KPIs
Five RECDISCbot management metrics.
recdisc_bot_end_deflect: why renewal resolved without agent
recdisc_bot_end_cite_rate: END-CITE-BOT / bot_recdisc_why_ended
recdisc_bot_transition_suggest_rate: transition proposed / bot_recdisc_transition extend
recdisc_bot_extend_promise_violations: promised extension bot audit target 0
recdisc_bot_discount_violations: invented discount bot audit target 0
Target: recdisc_bot_extend_promise_violations 0 and recdisc_bot_end_deflect greater than 50%.
RECDISCbot anti-patterns
Five common mistakes concerning the end of a recurring discount.
Denying the bot end date: END-CITE-BOT duration_rule map
Promising a bot extension: NO-EXTEND-PROMISE grandfather_policy map
Inventing a bot transition code: NO-INVENT-DISCOUNT transition_offer_id map
Confusing promo #111: separate campaign/site, recurring benefit account
Canceling the save without explaining: END-CITE-BOT before CANCEL373-REROUTE
RECDISCbot with Qstomy
Qstomy on Shopify: detect bot_recdisc intent, RECDISC-MAP RAG grounded, end notify cite, transition suggest, handoff #713 grandfather tier 2.
Pipeline: #714 bot explain end transition tier 1 → #713 agents grandfather exception redirect #373.
Explore AI support and request a demo.
Checklist, FAQ and going further
RECDISCbot Checklist (8 steps)
Sync RECDISC-MAP #713: RAG bot email portal D-7 widget
Policy RECDISCBOT-SUP: 6 rules END NOTIFY NO-EXTEND NO-INVENT
8 intents bot_recdisc_*: flow RDB-1 to RDB-8
4 templates TPL-RECDISCbot-*: END NOTIFY TRANSITION HANDOFF
Recharge API sync: discount status next_charge bot agents test
Subscription portal next_charge embed: bot_recdisc_renewal_price proactive
Red team 10 prompts: deny deadline promised extension invented bot code
KPI Dashboard: recdisc_bot_* section 9 end_deflect extend_violations
FAQ
Difference #713?
#713 = agents grandfather exception transition apply redirect #373. #714 = bot tier 1 explain end handoff.
Difference promo #111?
#111 = site campaign offer. #714 = recurring personal expired advantage according to map.
Does bot extend the discount?
No, except grandfather_policy map. NO-EXTEND-PROMISE-BOT TPL-RECDISCbot-HANDOFF #713.
Does the customer want to cancel?
END-CITE-BOT explain deadline then CANCEL373-REROUTE if cancel intent.
Going further
This week: index RECDISC-MAP RAG sub portal, sync Recharge discount API bot, red team promised extension bot violations.
Enzo
July 1, 2026
