E-commerce

AI Chatbot for prepaid subscriptions: explaining balance, due dates, and options

AI Chatbot for prepaid subscriptions: explaining balance, due dates, and options

July 1, 2026

"The bot says 4 months remaining, Recharge shows 2." "The AI promises a total refund without citing the prorata policy." "Prepaid ends tomorrow, chatbot does not mention auto conversion." Three failures where a badly calibrated prepaid subscription bot invents a balance or ignores renewal_convert_policy.

A prepaid subscription AI chatbot does not replace PREPAID agents (#533). It reads PREPAID-MAP, cites Recharge charges_remaining, and handoffs refund finance.

This guide #534 covers bot_prepaid_* intents, PREPAIDbot flow, and prepaid_bot KPIs. Pair bot of the PREPAID playbook (#533). New AI use case: explaining remaining installment balance and options without invented refunds.

Summary

Why automate prepaid with a bot?

"How much is left on my 6-month subscription?" is a subscription intent poorly served by a generic response. A calibrated bot reads PREPAID-MAP, states the exact balance, and explains the options for the end of the period.

What the bot resolves at tier 1

  • Balance cite: charges_remaining exact Recharge

  • Expiry explain: renewal_convert_policy map

  • Portal link: portal_balance_url deep link

  • Pause gate: pause_allowed skip credit preserved

  • Gift reroute: prepaid_gift → gift subscription

Recharge prepaid API exposes prepaid_balance and charges_remaining (Recharge, Prepaid API 2026). The bot intercepts bot_prepaid_balance before misidentifying trial #435.

PREPAIDbot vs PREPAID #533, TRIALbot #436, RENEWbot #506

Five contents, five subscription payment layers.

Quick matrix

Router: prepaid self balance expiry → #534. Free trial → #436 TRIALbot. Gift prepaid → gift subscription playbook.

Which bot_prepaid_* intents should be configured?

Eight prepaid subscription bot intents.

Eight intents bot_prepaid

  • bot_prepaid_balance: how many credit deliveries remain

  • bot_prepaid_expiry: end date of the prepaid period

  • bot_prepaid_convert: recurring conversion after prepaid

  • bot_prepaid_refund: prorated refund for unused portion

  • bot_prepaid_pause: pause skip during prepaid

  • bot_prepaid_portal: portal link for balance options

  • bot_prepaid_charge_surprise: charge after prepaid ends

  • bot_prepaid_escalate: refund finance handoff #533

Tier 1 auto: balance, expiry, convert, pause, portal if PREPAID-MAP lookup and Recharge prepaid flag.

Intent bot_prepaid_refund and bot_prepaid_escalate → agents #533 with payload refund_unused_policy prorated calc.

How do I use PREPAID-MAP #533?

The bot reads PREPAID-MAP #533: prepaid_plan_type, total_prepaid_units, renewal_convert_policy, refund_unused_policy, pause_allowed, expiry_behavior, portal_balance_url, reminder_schedule, upgrade_midterm_policy.

Lookup grounded

  • Recharge auth: customer session subscription prepaid flag

  • Balance fetch: charges_remaining prepaid_balance API

  • Expiry calc: expiry_date from charges consumed

  • Policy branch: renewal refund pause from map row

  • Gift gate: if gift prepaid → GIFT-REROUTE

Alignment anti-hallucination (#123): never balance outside Recharge API.

PREPAIDBOT-SUP policy in six rules

Six safe prepaid bot rules.

  1. CITE-BALANCE-EXACT : charges_remaining Recharge only

  2. PREPAID-MAP-GROUNDED : renewal refund pause from map

  3. NO-REFUND-PROMISE : refund cite refund_unused_policy

  4. RENEWAL-OPT-CITE : renewal_convert_policy before end

  5. GIFT-REROUTE : gift prepaid → gift subscription

  6. ESCALATE-REFUND : refund execution → #533 finance

Flow PREPAIDbot PPB-1 to PPB-8

Eight-step prepaid subscription bot flow.

  1. PPB-1 Classify: bot_prepaid_* intent

  2. PPB-2 Recharge lookup: prepaid flag balance expiry

  3. PPB-3 Gift gate: gift prepaid → reroute gift sub

  4. PPB-4 PREPAID-MAP: renewal refund pause rules

  5. PPB-5 Guardrail: CITE-BALANCE-EXACT NO-REFUND-PROMISE

  6. PPB-6 Respond: TPL-PREPAIDbot grounded

  7. PPB-7 Portal: portal_balance_url embed if self-serve

  8. PPB-8 Log: prepaid_type tag escalate if refund

Example TPL-PREPAIDbot-BALANCE

"Prepaid: [total_prepaid_units] paid deliveries. Remaining [charges_remaining]. Next box [next_ship_date]. End of period [expiry_date]. Portal: [portal_balance_url]."

TPL-PREPAIDbot templates and touchpoints

Four essential templates.

TPL-PREPAIDbot-BALANCE

[charges_remaining] of [total_prepaid_units] deliveries. Next shipment [next_ship_date].

TPL-PREPAIDbot-EXPIRY

Prepaid ends [expiry_date]. Next: [renewal_convert_policy]. Action before cutoff: [portal_url]#renewal.

TPL-PREPAIDbot-REFUND

Refund unused: [refund_unused_policy]. Estimate [prorata_amount] € if eligible. Agent confirmation within 24 hours.

TPL-PREPAIDbot-CONVERT

After last delivery: [expiry_behavior]. Opt-in required: add credit card [portal_url]. No charge without action if opt_in.

Touchpoints

  • D-7 expiry email: bot_prepaid_convert proactive

  • Portal balance widget: bot_prepaid_balance embed

  • Post-charge surprise: bot_prepaid_charge_surprise priority

  • Subscription hub: prepaid chip vs trial vs recurring

Edge cases and reroutes

Five cases outside tier 1 bot.

  • Trial merged: reroute #436 TRIALbot if trial flag

  • Gift prepaid: GIFT-REROUTE gift subscription playbook

  • Refund execution: ESCALATE-REFUND #533 finance ticket

  • Edit before ship: SUBEDITbot #532 cycle in progress

  • Monthly recurring charge: reroute #506 RENEWbot not prepaid

Bot does not trigger manual Stripe or Recharge refund: ESCALATE-REFUND #533 with prorata calc payload.

Essential prepaid bot KPIs

Five PREPAIDbot management metrics.

  • prepaid_bot_explain_rate: % compliant PREPAID-MAP replies

  • prepaid_bot_balance_exact: CITE-BALANCE-EXACT 100% compliance

  • prepaid_bot_auto_resolve: % tier 1 without agent

  • prepaid_bot_escalate_refund: sessions → #533 finance

  • prepaid_bot_gift_reroute: correct prepaid gift sessions

Monthly Red team: 10 prompts "guaranteed total refund", "6 months remaining" without Top-up lookup. Invented balance = CITE-BALANCE-EXACT violation.

PREPAIDbot anti-patterns

Six frequent mistakes.

  1. Approximate balance: CITE-BALANCE-EXACT violation

  2. Tier 1 promised refund: ESCALATE-REFUND #533

  3. Confusing trial #436: prepaid paid upfront distinct

  4. Auto conversion omitted: RENEWAL-OPT-CITE mandatory

  5. Gift prepaid self: GIFT-REROUTE

  6. Confusing RENEWbot #506: recurring monthly distinct

PREPAIDbot with Qstomy

Qstomy on Shopify + Recharge: detect bot_prepaid_* intent, PREPAID-MAP RAG, Recharge balance widget, D-7 proactive expiry, handoff #533 refund payload.

Pipeline: bot explain prepaid → #533 refund finance → gift subscription if prepaid_gift → AI governance #142 audit balance claims.

Explore AI support and request a demo.

Checklist, FAQ and going further

PREPAIDbot Checklist (8 steps)

  1. Sync PREPAID-MAP #533: RAG bot whitelist only

  2. Policy PREPAIDBOT-SUP: 6 CITE-BALANCE-EXACT rules

  3. 8 intents bot_prepaid_*: flow PPB-1 to PPB-8

  4. 4 templates TPL-PREPAIDbot-*: BALANCE EXPIRY REFUND CONVERT

  5. Recharge balance API: charges_remaining live fetch

  6. D-7 expiry webhook: bot_prepaid_convert proactive

  7. Red team 10 prompts: invented balance refund forbidden

  8. Dashboard KPI: prepaid_bot_* section 9

FAQ

Difference #533?
#533 = agents refund finance convert. #534 = bot tier 1 balance expiry explain.

Difference TRIALbot #436?
#436 = free trial. #534 = prepaid paid upfront N cycles.

Bot promises refund?
Cite policy only. ESCALATE-REFUND #533 for execution.

Gift prepaid?
GIFT-REROUTE gift subscription, not self prepaid flow.

Going further

This week: index PREPAID-MAP in bot corpus, connect Recharge balance API widget, configure D-7 expiry proactive, measure prepaid_bot_balance_exact compliance.

Enzo

July 1, 2026

Convert over 2,000 customers on average per month with Qstomy.

The world’s 1st Shopify AI dedicated to customer conversion

Empowering 200+ e-commerce merchants

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.