E-commerce
July 1, 2026
"The bot says renewal tomorrow, that was yesterday." "AI promises skip even though cut-off has passed." "Postpone to the 15th, the bot confirms without a portal link." Three failures where an ungrounded renewal bot invents a date, skip, or billing change.
A subscription e-commerce renewal AI chatbot does not replace RENEWDATE agents (#505). It reads Recharge next_charge and RENEWDATE-MAP, reminds of the date, guides skip or billing change before cut-off, and hands off early charge disputes and missing reminders.
This guide #506 covers intents bot_renew_*, flow RENEWDATEbot, and KPI renew_bot. Companion bot to the RENEWDATE playbook (#505). New AI use case: responsible renewal without invented dates.
Summary
Why automate renewal by bot?
Questions like "when is my next charge?" peak at D-3 and D-1. A calibrated bot quotes next_charge_scheduled_at and skip_cutoff_hours in seconds, without promising a skip after the cutoff time.
What the bot resolves
When next: date amount timezone_display from Recharge
Reminder explain: factual reminder_schedule map
Skip guide: portal link if before skip_cutoff_hours
Postpone hint: change billing date portal deep link
Recharge recommends pre-charge notifications and self-service skip (Recharge, notifications 2026). The bot reduces last-minute renew_date_when_next tickets.
In France, online cancellation must remain accessible (Service Public, online cancellation). The renewal bot does not block cancel, it informs before charging.
RENEWDATEbot vs RENEWDATE #505, subscription and MIXCART #503
Four contents, four responsibilities subscription calendar.
Quick matrix
#506 RENEWDATEbot : bot when next skip postpone reminder tier 1
#505 RENEWDATE : agents early charge dispute change date
General subscription : pause swap termination
#503 MIXCART : billing initial mixed cart
#506 = tier 1 when next reminder skip guide. #505 = early charge dispute and complex date change.
Which bot_renew_* intents should be configured?
Eight subscription renewal bot intents.
Eight intents bot_renew
bot_renew_when_next: when next direct debit delivery is schedule
bot_renew_reminder_info: reminders sent D-7 D-3 schedule
bot_renew_skip_guide: skip this cycle before cut-off
bot_renew_postpone_date: postpone portal billing date
bot_renew_cutoff_late: too late to skip explain options
bot_renew_timezone: debit time FR time zone
bot_renew_early_charge: handoff #505 charge before date
bot_renew_first_vs_recurring: first order vs subsequent cycles
Tier 1 auto: when_next, reminder_info, skip_guide, postpone_date, cutoff_late, timezone, first_vs_recurring.
Intent bot_renew_early_charge routes to agents #505 with payload subscription_id, next_charge_scheduled_at and charge_log.
How should RENEWDATE-MAP #505 be consumed?
The bot reads RENEWDATE-MAP #505 + Recharge API: billing_anchor_day, skip_cutoff_hours, date_change_allowed, reminder_schedule, timezone_display, first_order_offset, portal_url.
Lookup grounded
next_charge_scheduled_at: Recharge exact, converted timezone_display
skip_cutoff_hours: cutoff_datetime calculated, never invented
date_change_allowed: Y/N max changes before portal link
reminder_schedule: D-7 D-3 D-1 if bot_renew_reminder_info
portal_url deep link: #billing-date #notifications skip section
Mandatory alignment with anti-hallucination (#123): subscription dates = Recharge + RENEWDATE-MAP only.
RENEWDATEBOT-SUP policy in six rules
Six rules for safe bot renewal.
NO-DATE-INVENT: never date cut-off outside Recharge + map
CITE-NEXT-CHARGE: next_charge + amount + timezone mandatory
NO-SKIP-AFTER-CUTOFF: skip guide only if before cutoff_datetime
PORTAL-LINK-REQUIRED: postpone skip via portal_url, no direct bot action
REMINDER-GROUNDED: reminder_schedule map if reminder disputed
EARLY-CHARGE-HANDOFF: early charge dispute → #505 finance
Flow RENEWDATEbot RDB-1 to RDB-8
Eight-step renewal bot flow.
RDB-1 Classify: bot_renew_* intent
RDB-2 Auth: customer session or email OTP
RDB-3 Recharge lookup: subscription_id next_charge status
RDB-4 RENEWDATE-MAP: cutoff reminder anchor rules
RDB-5 Guardrail: NO-DATE-INVENT cutoff check
RDB-6 Respond: TPL-RENEWbot grounded
RDB-7 Portal: deep link skip postpone notifications
RDB-8 Log: next_charge_cited cutoff_cited tag renew_bot
Example TPL-RENEWbot-NEXT
"Next payment: [date FR timezone_display], [amount] € incl. VAT. Skip this cycle: [portal_url]#skip before [cutoff_datetime]. Postpone date: [portal_url]#billing-date if [date_change_allowed]."
Templates TPL-RENEWbot and touchpoints
Four essential templates.
TPL-RENEWbot-REMINDER
Scheduled reminders: [reminder_schedule]. Next charge [date]. Check spam. Preferences: [portal_url]#notifications.
TPL-RENEWbot-SKIP-OK
You can skip this cycle until [cutoff_datetime]. Action: [portal_url]#skip. Subscription remains active for the next cycle.
TPL-RENEWbot-SKIP-LATE
Skip cut-off passed ([skip_cutoff_hours] hours before charge). Options: pause next cycle [portal_url]#pause or contact an agent if this is an error.
TPL-RENEWbot-POSTPONE
Billing date change: [date_change_allowed]. Effective next cycle if action is taken before [cutoff]. Portal: [portal_url]#billing-date.
Touchpoints
D-3 renewal Email: bot chip "Skip or postpone?" pre-auth link
Subscription customer account: next charge widget + bot_renew_when_next
SMS reminder: deep link portal skip section
Proactive D-1: bot_renew_skip_guide if cutoff > 6h
Edge cases and reroutes
Five cases outside tier 1 bot.
Early charge dispute: handoff #505 finance Recharge log
Long-term pause: reroute pause subscription
Cancellation: direct portal cancel link, no retention dark pattern
Mixed cart billing: MIXCARTbot #504
No subscription contract: reroute REPREQ #491
Bot without active subscription_id: do not improvise date, DISAMBIG-SUB then reroute REPREQ or general subscription.
Essential renew_bot KPIs
Five metrics for monitoring RENEWDATEbot.
renew_bot_auto_resolve: % tier 1 without agent
renew_bot_next_cited: % with next_charge exact timezone
renew_bot_date_invent_violation: NO-DATE-INVENT, target 0
renew_bot_skip_portal_click: portal clicks skipped post-bot
renew_bot_handoff_early: sessions → #505 charge dispute
Monthly red team: 10 prompts "skip now charge tomorrow", "change date to 20th confirmed", "did not receive reminder refund". Any date outside of Recharge = NO-DATE-INVENT violation.
RENEWDATEbot anti-patterns
Six common mistakes.
Invented date without Recharge: NO-DATE-INVENT
Skip promised after cut-off: NO-SKIP-AFTER-CUTOFF
Confirmed date change without portal: PORTAL-LINK-REQUIRED
Confusing skip and pause: reroute pause abo
Blocking cancellation: cancel link mandatory if requested
Duplicating entire subscription support: calendar focus only
RENEWDATEbot with Qstomy
Qstomy on Shopify + Recharge: next_charge RAG, RENEWDATE-MAP cut-off guardrail, portal deep links, proactive J-3 chip, handoff #505 early charge payload.
Pipeline: #506 proactive reminder skip → #505 dispute date → AI governance #142 audit billing bot.
Explore AI support and request a demo.
Checklist, FAQ and going further
RENEWDATEbot Checklist (8 steps)
Sync RENEWDATE-MAP #505: RAG bot + Recharge API
Policy RENEWDATEBOT-SUP: 6 NO-DATE-INVENT rules
8 intents bot_renew_*: flow RDB-1 to RDB-8
4 templates TPL-RENEWbot-*: NEXT REMINDER SKIP POSTPONE
Portal deep links: skip billing-date notifications
Proactive D-3 email chip: pre-auth bot session
Red team 10 prompts: skip late invented date
Dashboard KPI: renew_bot_* section 9
FAQ
Difference #505?
#505 = dispute early charge change date agents. #506 = bot tier 1 when next skip guide.
Does the bot execute skip?
No. Portal link portal_url. Customer action or ops #505 in case of error.
Can the bot confirm a new date?
Only if date_change_allowed map + portal link, no direct execution.
Responsible renewal?
Grounded reminder, explicit cut-off, accessible cancel, no dark pattern.
Going Further
This week: connect Recharge next_charge to the bot, test red team "skip in 2 hours charge tomorrow", measure renew_bot_next_cited. Activate D-3 email renewal chip.
Enzo
July 1, 2026
