E-commerce
July 1, 2026
"The bot confirms delivery to my parents' house while Recharge indicates home address." "The AI promises multi-address rotation on an ineligible plan." "Chatbot changes the address without respecting the cutoff." Three failures where a poorly calibrated multi-address subscription bot invents rotation, ignores cutoff, or executes address changes.
A multi-address subscription AI chatbot does not replace MULTIADDR agents (#721). It reads MULTIADDR-MAP, lookups Recharge next_ship_address, quotes rotation cutoff, and handoffs change ops to humans.
This guide #722 covers intents bot_multiaddr_*, flow MULTIADDRbot, and KPI multiaddr_bot. Bot pair of the playbook MULTIADDR (#721). AI use case: guide next address rotation setup without modify execute or invented rotation.
Summary
Why automate multi-address subscriptions with a bot?
"How do I alternate between two addresses?", "where will the next box go?" and "can I change it for this cycle?" appear on the subscriber portal and reminder emails. A calibrated bot cites MULTIADDR-MAP rotation, portal_path and next_ship_address API without promising out-of-plan rotation or direct address modification.
What the bot resolves for tier 1 multi-address subscriptions
Setup guide: portal_path max_addresses rotation map
Next address: Recharge next_ship_address API verify
Rotation explain: rotation_rule ROTATE-CITE map
Cutoff explain: address_change_cutoff CUTOFF-CITE map
Billing clarify: billing_model one_charge_multi_ship map
Recharge exposes subscription addresses via customer portal and API (Recharge, subscription addresses 2026). Without a grounded bot, AI amplifies wrong_next or promises rotation out-of-map.
MULTIADDRbot vs MULTIADDR #721, address #183, gift #273 and SUBEDIT #531
Six contents, six distinct delivery address moments.
Quick matrix
#722 MULTIADDRbot: bot tier 1 setup next rotate cutoff handoff
#721 MULTIADDR: agents cutoff exception ops address execute redirect
Address change #183: one-off order distinct sub rotation
Gift sub #273: gift giver distinct recipient holder multi-address
SUBEDIT #531: edit cycle in progress distinct rotation program
RENEWbot #506: charge date distinct delivery address
Pipeline: #722 bot setup next rotate tier 1 → #721 agents cutoff exception ops execute.
Which bot_multiaddr_* intents should be configured?
Eight bot multi-address intents mapped to multiaddr_* typologies #721.
Eight bot_multiaddr intents
bot_multiaddr_setup: portal_path max_addresses rotation map
bot_multiaddr_next_address: next_ship_address API SUB-LOOKUP
bot_multiaddr_rotate: rotation_rule ROTATE-CITE map
bot_multiaddr_cutoff: address_change_cutoff CUTOFF-CITE map
bot_multiaddr_change_guide: portal_path change handoff #721
bot_multiaddr_recipient_prefs: recipient_label_policy map
bot_multiaddr_not_supported: NO-ROTATE-PROMISE eligible_plans map
bot_multiaddr_handoff: cutoff exception ops change → #721
Tier 1 auto: setup, next_address, rotate, cutoff if MULTIADDR-MAP active + guardrails.
bot_multiaddr_handoff cutoff exception address execute → agents #721 payload subscription intent.
How to consume MULTIADDR-MAP #721?
The bot reads MULTIADDR-MAP #721: multiaddr_program_id, eligible_plans, max_addresses, rotation_rule, address_change_cutoff, portal_path, recipient_label_policy, billing_model, customer_communication_copy.
Lookup grounded
ROTATE-CITE-BOT: rotation_rule cite map verbatim
CUTOFF-CITE-BOT: address_change_cutoff cite if late change map
SUB-LOOKUP-VERIFY-BOT: Recharge next_ship_address API before confirm
NO-ROTATE-PROMISE-BOT: rotation only eligible_plans map
NO-ADDRESS-MODIFY-BOT: guide portal_path handoff #721 execute
ADDR183-REROUTE-BOT: one-time order → #183 distinct sub rotation
GIFTSUB273-REROUTE-BOT: gift → #273 GIFT-SUB distinct holder
MULTIADDR721-HANDOFF-BOT: ops change → #721 agents MA-7
Alignment anti-hallucination (#123): rotation cutoff address = MULTIADDR-MAP whitelist only.
MULTIADDRBOT-SUP policy in six rules
Six responsible multi-address sub bot rules.
MULTIADDR-MAP-GROUNDED-BOT: max cutoff rotation from map only
ROTATE-CITE-BOT: rotation_rule cite plan confirmed
CUTOFF-CITE-BOT: address_change_cutoff cite if change concern map
SUB-LOOKUP-VERIFY-BOT: next_ship_address API before address claim
NO-ADDRESS-MODIFY-BOT: no address modification bot handoff #721
SUBEDIT531-REROUTE-BOT: edit cycle SKU → #531 SUBEDIT distinct rotation program
Flow MULTIADDRbot MAB-1 to MAB-8
Eight-step multi-address subscription bot flow.
MAB-1 Classify: bot_multiaddr_* intent detect portal email widget
MAB-2 Collect: subscription_id email plan question
MAB-3 MULTIADDR-MAP: rotation cutoff max portal billing
MAB-4 Sub lookup: Recharge addresses next_ship_address verify
MAB-5 Guardrail: ROTATE CUTOFF SUB-LOOKUP NO-MODIFY HANDOFF
MAB-6 Respond: TPL-MULTIADDRbot grounded customer_communication_copy
MAB-7 Handoff or close: cutoff exception ops change #721 payload
MAB-8 Log: intent multiaddr_program_id tag multiaddr_bot rotate handoff Y/N
TPL-MULTIADDRbot-NEXT Example
“Sub [subscription_id map]: next delivery [API next_ship_address map.] Rotation [rotation_rule map.] Modify before [address_change_cutoff map] days via [portal_path map.] SUB-LOOKUP-VERIFY-BOT ROTATE-CITE-BOT.”
TPL-MULTIADDRbot and touchpoints templates
Four essential templates.
TPL-MULTIADDRbot-SETUP
Multi-address [multiaddr_program_id]: up to [max_addresses map] addresses. Rotation [rotation_rule map.] Configure: [portal_path map.] ROTATE-CITE-BOT.
TPL-MULTIADDRbot-NEXT
Next delivery: [API next_ship_address map.] Modification cutoff [address_change_cutoff map] days. SUB-LOOKUP-VERIFY-BOT.
TPL-MULTIADDRbot-CUTOFF
Cutoff exceeded: change applied to the next cycle. [address_change_cutoff map verbatim.] CUTOFF-CITE-BOT MULTIADDR721-HANDOFF-BOT if exception.
TPL-MULTIADDRbot-HANDOFF
Request [ops address change / cutoff exception] forwarded to team. Summary [subscription_id intent]. MULTIADDR721-HANDOFF-BOT.
Touchpoints
Subscription portal addresses widget: bot_multiaddr_setup proactive
Delivery reminder email footer chat: bot_multiaddr_next_address entry
Wrong address keyword: bot_multiaddr_cutoff handoff
Ineligible plan detected: bot_multiaddr_not_supported trigger
Edge cases and reroutes
Five cases outside tier 1 standard multi-address subscription bot.
Gift subscription: GIFTSUB273-REROUTE-BOT #273 distinct single recipient
One-time order change: ADDR183-REROUTE-BOT #183 distinct sub rotation
Edit cycle SKU qty: SUBEDIT531-REROUTE-BOT #531 distinct program addresses
Bulk corporate CSV: #158 one-shot distinct recurring sub
Address modify execute bot: NO-ADDRESS-MODIFY-BOT agents #721 only
Bot guide setup tier 1. Cutoff exception address execute → agents #721.
Essential multiaddr_bot KPIs
Five MULTIADDRbot management metrics.
multiaddr_bot_setup_deflect: next setup resolved without agent
multiaddr_bot_rotate_cite_rate: ROTATE-CITE-BOT / bot_multiaddr_rotate setup
multiaddr_bot_lookup_verify_rate: SUB-LOOKUP-VERIFY / bot_multiaddr_next_address
multiaddr_bot_address_promise_violations: bot promised address audit target 0
multiaddr_bot_handoff_rate: cutoff exception change / total multiaddr bot
Target: multiaddr_bot_address_promise_violations 0 and multiaddr_bot_setup_deflect greater than 60%.
MULTIADDRbot anti-patterns
Five common errors for the multi-address subscription bot.
Confirmed address without bot API: SUB-LOOKUP-VERIFY next_ship_address
Promise rotation outside of bot plan: NO-ROTATE-PROMISE eligible_plans map
Direct bot address modification: NO-ADDRESS-MODIFY handoff #721
Ignore bot cutoff: CUTOFF-CITE address_change_cutoff map
Confuse gift sub #273 bot: GIFTSUB273-REROUTE gift recipient
MULTIADDRbot with Qstomy
Qstomy on Shopify + Recharge: detect bot_multiaddr intent, MULTIADDR-MAP RAG grounded, rotate cutoff cite, address lookup, handoff #721 ops tier 2.
Pipeline: #722 bot setup next rotate tier 1 → #721 agents cutoff exception ops execute.
Explore AI support and request a demo.
Checklist, FAQ and going further
MULTIADDRbot Checklist (8 steps)
Sync MULTIADDR-MAP #721: RAG bot portal sub email reminder
Policy MULTIADDRBOT-SUP: 6 rules ROTATE CUTOFF SUB-LOOKUP NO-MODIFY
8 intents bot_multiaddr_*: flow MAB-1 to MAB-8
4 templates TPL-MULTIADDRbot-*: SETUP NEXT CUTOFF HANDOFF
Recharge address API sync: next_ship_address bot agents test
Embed address portal: bot_multiaddr_setup proactive widget
Red team 10 prompts: promised address rotation invented modify bot cutoff ignored
Dashboard KPI: multiaddr_bot_* section 9 setup_deflect address_violations
FAQ
Difference #721?
#721 = agents cutoff exception ops address execute. #722 = bot tier 1 setup next rotate handoff.
Difference address change #183?
#183 = one-off order. #722 = recurring sub N addresses rotation.
Bot modifies the address?
No. NO-ADDRESS-MODIFY-BOT TPL-MULTIADDRbot-HANDOFF #721.
Next delivery where bot?
TPL-MULTIADDRbot-NEXT SUB-LOOKUP-VERIFY-BOT Recharge API map.
Going further
This week: index MULTIADDR-MAP RAG sub portal, sync Recharge next_ship_address API bot, red team promised address bot violations.
Enzo
July 1, 2026
