E-commerce
July 1, 2026
"The bot says I am refunded when it is an annulled authorization." "The AI promises the void tomorrow without checking the return scan." "Chatbot confuses Klarna and try before you buy." Three failures where a poorly calibrated TBYB bot over-promises void capture or mixes up payment models.
A try-before-you-buy AI chatbot does not replace TBYB agents (#629). It reads TBYB-MAP, looks up auth_status API, cites trial_days capture_trigger, and hands off void dispute partial to humans.
This guide #630 covers intents bot_tbyb_*, flow TBYBbot, and KPI tbyb_bot. Companion bot of the TBYB playbook (#629). New AI conversion use case: explaining auth capture void without executing payment.
Summary
Why automate TBYB with a bot?
"Why is my card blocked?", "if I send it back before the end of the trial am I charged?" and "when does the final payment go through?" come up as early as checkout and D+3 post-delivery. A calibrated bot cites TBYB-MAP trial_end_date capture_trigger_rule without promising void capture or refund bot.
What the tier 1 bot resolves
Explain model: customer_copy auth hold vs debit map
Card imprint: auth_hold_amount_rule quotes API status
Trial window: quotes trial_days trial_end_date
Capture timing: capture_trigger_rule info without executing
Void return: VOID-NOT-REFUND return_method guide
TBYB programs reduce tickets when auth and capture are explained before card validation (Loop Returns, TBYB 2026). The bot intercepts bot_tbyb_auth_status before NO-CAPTURE violation.
TBYBbot vs TBYB #629, BNPL, TRYHOME #628 and kit #538
Five contents, five different payment and trial models.
Quick matrix
#630 TBYBbot: bot tier 1 auth capture delays void handoff
#629 TBYB: agents void dispute partial escalate finance
BNPL payhelp: bot_payhelp_bnpl Klarna Alma distinct auth TBYB
TRYHOME bot #628: home trial deposit keep return distinct checkout TBYB
Trial kit bot #538: mini kit TRIALKIT distinct cart TBYB
Pipeline: bot explain auth capture tier 1 → #629 void dispute partial execute finance.
Which bot_tbyb_* intents should be configured?
Eight TBYB bot intents mapped to tbyb_* typologies #629.
Eight bot_tbyb intents
bot_tbyb_explain : customer_copy how works auth capture map
bot_tbyb_auth_status : auth_hold_amount status authorized voided API
bot_tbyb_trial_window : trial_days trial_end_date mention
bot_tbyb_capture_info : capture_trigger_rule when charged mention
bot_tbyb_return_guide : return_method return_window_days void_auth_on_return guide
bot_tbyb_void_explain : VOID-NOT-REFUND return before capture explain
bot_tbyb_bnpl_reroute : Klarna Alma confusion → payhelp bot
bot_tbyb_handoff : void execute dispute partial → #629
Tier 1 auto : explain, auth_status, trial_window, capture_info, return_guide, void_explain if TBYB-MAP + payment API.
bot_tbyb_handoff manual void charge dispute partial keep → agents #629 payload tbyb_id order_ref return scan.
How do I consume TBYB-MAP #629?
The bot reads TBYB-MAP #629: tbyb_program_id, sku_or_eligibility, auth_hold_amount_rule, trial_days, capture_trigger_rule, return_window_days, return_method, void_auth_on_return, partial_return_policy, bnpl_distinction_copy, customer_copy.
Lookup grounded
Order TBYB detect: checkout flag TBYB → TBYB-MAP row
TBYB-STATUS-VERIFY-BOT: auth_status capture_status API before cite
NO-CAPTURE-BOT: bot does not capture nor trigger auto_capture
NO-VOID-BOT: void auth execute handoff #629 only
VOID-NOT-REFUND-BOT: return before capture = void explain no refund promised
TRYHOME628-REROUTE-BOT: home trial drop-off → #628 TRYHOMEbot distinct
Alignment anti-hallucination (#123): trial_days capture void = TBYB-MAP + auth_status API whitelist only.
TBYBBOT-SUP policy in six rules
Six rules for a safe try-before-you-buy bot.
TBYB-MAP-GROUNDED: trial_days captures void auth from map only
TBYB-STATUS-VERIFY-BOT: auth_status API status before trial_end cite
NO-CAPTURE-BOT: bot neither captures nor confirms charge execute
NO-VOID-BOT: bot neither voids auth nor confirms void execute
VOID-NOT-REFUND-BOT: return before capture explain void not refund promised
DISPUTE-HANDOFF-BOT: charge dispute partial → #629 agents
Flow TBYBbot TBB-1 to TBB-8
Eight-step try-before-you-buy bot flow.
TBB-1 Classify: bot_tbyb_* intent detect
TBB-2 Collect: tbyb_id order_ref auth capture return question
TBB-3 TBYB-MAP: trial_days capture void return rules
TBB-4 Payment API: auth_status capture_status trial_end_date return_scan
TBB-5 Guardrail: NO-CAPTURE NO-VOID VOID-NOT-REFUND-BOT
TBB-6 Respond: TPL-TBYBbot grounded map API
TBB-7 Handoff: void dispute partial → #629
TBB-8 Log: intent tbyb_program_id tag tbyb_bot
TPL-TBYBbot-AUTH Example
“Order [order_ref] TBYB: authorization [auth_hold_amount_rule map] status [auth_status API]. Not an immediate charge. Trial end [trial_end_date map]. Capture if keep: [capture_trigger_rule map info without executing]. Bot does not trigger payment.”
Templates TPL-TBYBbot and touchpoints
Four essential templates.
TPL-TBYBbot-EXPLAIN
Program [tbyb_program_id]: [customer_copy map]. Card authorization [auth_hold_amount_rule], no immediate charge. Trial [trial_days] days. [bnpl_distinction_copy map]. Return [return_method].
TPL-TBYBbot-CAPTURE
End of trial [trial_end_date]. Capture according to [capture_trigger_rule map]. Keep: charge [montant map info]. Return before [return_window_days] days: void auth [void_auth_on_return map explain]. Capture dispute: agent #629.
TPL-TBYBbot-RETURN
TBYB Return [tbyb_id]: [return_method map]. Due [date]. Return before capture: authorization cancellation, not a standard refund VOID-NOT-REFUND. Bank hold release: [bank_release_days map] days (banking processing time).
TPL-TBYBbot-HANDOFF
Request [void execute / charge dispute / partial keep] forwarded to TBYB team. Order [order_ref] tbyb [tbyb_id]. SLA [handoff_sla].
Touchpoints
TBYB Checkout widget: bot_tbyb_explain embed
Email Day+0 order : bot_tbyb_auth_status entry
Customer trial area: bot_tbyb_capture_info widget
Email Day-3 end of trial: bot_tbyb_trial_window deep link
Edge cases and reroutes
Five cases outside tier 1 standard TBYB bot.
Void auth execute: NO-VOID-BOT handoff #629 TB-7
Charge dispute litigation: DISPUTE-HANDOFF-BOT proof scan #629
Partial keep shopping cart: partial_return_policy handoff #629 split capture
BNPL confused: bot_tbyb_bnpl_reroute payhelp distinct
Home trial confused: TRYHOME628-REROUTE-BOT #628 distinct
Bot never executes capture void or waive auto_capture: agents #629 workflow TB-7.
Essential TBYB bot KPIs
Five TBYBbot management metrics.
tbyb_bot_auth_deflect: auth hold explained without agent
tbyb_bot_capture_deflect: capture timing info resolved TPL-CAPTURE
tbyb_bot_void_deflect: VOID-NOT-REFUND return guide resolved
tbyb_bot_handoff_rate: void dispute partial / total tbyb bot
tbyb_bot_capture_promise_violations: capture or void promised bot target audit 0
Target: tbyb_bot_capture_promise_violations 0 and tbyb_bot_auth_deflect greater than 70% with TBYB-MAP sync.
TBYBbot Anti-patterns
Five common errors with the try-before-you-buy bot.
Promise capture bot: NO-CAPTURE-BOT handoff #629
Confirmed void bot: NO-VOID-BOT agents execute only
Promise refund before capture: VOID-NOT-REFUND-BOT void explain
Invented deadline: TBYB-STATUS-VERIFY-BOT trial_end API
Confusing BNPL or TRYHOME: reroute payhelp #628 distinct
TBYBbot with Qstomy
Qstomy on Shopify: detect bot_tbyb intent, TBYB-MAP RAG grounded, auth_status API lookup, VOID-NOT-REFUND cite, handoff #629 void dispute payload.
Pipeline: #630 bot explain auth capture tier 1 → #629 void dispute partial escalate finance.
Explore AI support and request a demo.
Checklist, FAQ and going further
TBYBbot Checklist (8 steps)
Sync TBYB-MAP #629: RAG bot checkout widget TBYB
Policy TBYBBOT-SUP: 6 NO-CAPTURE NO-VOID rules
8 intents bot_tbyb_*: flow TBB-1 to TBB-8
4 templates TPL-TBYBbot-*: EXPLAIN CAPTURE RETURN HANDOFF
Payment status API: connect TBB-4 auth_status trial_end
Email D-3 embed: bot_tbyb_trial_window widget
Red team 10 prompts: void promis capture bot BNPL confused
KPI Dashboard: tbyb_bot_* section 9
FAQ
Difference #629?
#629 = agents void dispute partial execute finance. #630 = bot tier 1 auth delays capture handoff.
Does the bot confirm void and cancel the authorization?
No. NO-VOID-BOT void_auth_on_return info only handoff #629.
Difference from TRYHOME bot #628?
#628 = home trial deposit keep return. #630 = auth capture checkout TBYB.
Does the customer think they will be refunded?
TPL-TBYBbot-RETURN VOID-NOT-REFUND: void auth if returned before capture, not standard refund.
Going further
This week: index TBYB-MAP RAG, connect auth_status API bot, red team void promis bot.
Enzo
July 1, 2026
