E-commerce
July 1, 2026
"The bot promises my deposit will be released tomorrow even though the product hasn't been returned yet." "The AI waives my late fee without checking the date." "Chatbot confuses weekend rental with 14-day trial kit." Three failures where a miscalibrated rental bot over-promises on deposits or mixes up temporary product models.
A product rental AI chatbot does not replace RENTAL agents (#619). It reads RENTAL-MAP, quotes return deposit duration, checks rental_status API, and hands off damage capture extensions to humans.
This guide #620 covers intents bot_rental_*, flow RENTALbot, and KPI rental_bot. Bot pair of the RENTAL playbook (#619). New rental AI use case: explain return deposit availability without promising release or capturing damage.
Summary
Why automate product rental with a bot?
"How do I rent this product?", "how long has my deposit been blocked?" and "how do I return it before Friday?" frequently recur in the PDP customer rental account. A calibrated bot references RENTAL-MAP, looks up rental_status due_date deposit without promising release prior to inspection.
What the tier 1 bot resolves
Explain model: customer_copy duration deposit return_method map
Availability dates: rental_duration_options calendar quotes
Deposit status: deposit_hold_type inspection API status
Return guide: return_method due_date label resend info
Wear vs damage: normal_wear_vs_damage explain pre return
Circular rental models gain adoption when deposit and return dates are clear right from the digital journey (McKinsey, circular retail 2026). The bot intercepts bot_rental_deposit_status before a NO-DEPOSIT-RELEASE-PROMISE violation occurs.
RENTALbot vs RENTAL #619, trial kit #538, deposit #412 and return of new item
Five types of content, five distinct temporary product models.
Quick matrix
#620 RENTALbot: bot tier 1 explain dates deposit return handoff
#619 RENTAL: agents extension damage capture escalate ops
Trial kit bot #538: try-before-buy return refund distinct location
Locker #412: deposit packaging not the product rented
Return new: policy 14-day purchase distinct rental_id
Pipeline: bot explain dates deposit tier 1 → #619 extension damage capture buyout execute.
Which bot_rental_* intents should be configured?
Eight bot location intents mapped to rental_* typologies #619.
Eight bot_rental intents
bot_rental_explain: customer_copy how works duration pricing
bot_rental_availability: dates slots rental_duration_options
bot_rental_deposit_status: deposit hold status inspection cite
bot_rental_return_guide: return_method due_date label info
bot_rental_due_reminder: D-2 return due_date grace_hours
bot_rental_late_fee_info: late_fee_policy cite without waive
bot_rental_condition_info: normal_wear_vs_damage checklist explain
bot_rental_handoff: extension damage buyout capture → #619
Tier 1 auto: explain, availability, deposit_status, return_guide, due_reminder, late_fee_info, condition_info if RENTAL-MAP + rental API.
bot_rental_handoff extension damage dispute capture → agents #619 payload rental_id order_ref photos.
How do I use RENTAL-MAP #619?
The bot reads RENTAL-MAP #619: rental_program_id, sku_or_category, rental_duration_options, pricing_model, deposit_amount_rules, deposit_hold_type, late_fee_policy, return_method, return_window_hours, condition_checklist, normal_wear_vs_damage, buyout_option_rules, customer_copy.
Lookup grounded
PDP rental badge detect: program sku → RENTAL-MAP row
RENTAL-STATUS-VERIFY-BOT: rental API due_date deposit status before cite
NO-DEPOSIT-RELEASE-PROMISE-BOT: no release promised before ops inspection
NO-CAPTURE-BOT: capture partial deposit handoff #619 only
NO-LATE-FEE-WAIVE-BOT: late fee cite map without bot waiver
TRIAL-REROUTE-BOT: trial kit → #538 TRIALKITbot distinct
Alignment anti-hallucination (#123): deposit return late fee = RENTAL-MAP whitelist + rental_status API only.
RENTALBOT-SUP Policy in six rules
Six rules for safe bot rental.
RENTAL-MAP-GROUNDED: duration deposit return late fee from map only
RENTAL-STATUS-VERIFY-BOT: rental API status before deposit due_date cite
NO-DEPOSIT-RELEASE-PROMISE-BOT: bot does not promise deposit release before inspection
NO-CAPTURE-BOT: bot does not capture or refund damage deposit
NO-LATE-FEE-WAIVE-BOT: bot does not waive late fee
EXTEND-HANDOFF-BOT: extension buyout damage dispute → #619 agents
Flow RENTALbot RNB-1 to RNB-8
Eight-step flow for the product rental bot.
RNB-1 Classify : bot_rental_* intent detect
RNB-2 Collect : rental_id order_ref sku dates question
RNB-3 RENTAL-MAP : program duration deposit return rules
RNB-4 Rental API : rental_status due_date deposit inspection status
RNB-5 Guardrail : NO-DEPOSIT-RELEASE NO-CAPTURE NO-LATE-FEE-WAIVE
RNB-6 Respond : TPL-RENTALbot grounded map API
RNB-7 Handoff : extension damage capture buyout → #619
RNB-8 Log : intent rental_program_id tag rental_bot
TPL-RENTALbot-DEPOSIT Example
“Rental deposit [rental_id]: [deposit_amount_rules map] [deposit_hold_type]. Current status: [API rental_status]. [If inspection: release after ops check, indicative delay [release_sla_days] days.] Bot cannot speed up release.”
TPL-RENTALbot templates and touchpoints
Four essential templates.
TPL-RENTALbot-EXPLAIN
Rental [sku]: [customer_copy map]. Durations: [rental_duration_options]. Pricing: [pricing_model map]. Deposit: [deposit_amount_rules deposit_hold_type]. Return: [return_method map].
TPL-RENTALbot-DEPOSIT
Deposit [rental_id]: [montant map]. Status [API]. [If active: standard hold during rental.] [If inspection: check [condition_checklist] in progress.] Release after ops validation according to policy.
TPL-RENTALbot-RETURN
Return before [due_date]. Method: [return_method map]. [If late: [late_fee_policy map] LATE-FEE-CITE.] Label [sent email / resend link via agent if lost]. Condition checklist: [condition_checklist map].
TPL-RENTALbot-HANDOFF
Request [extension / disputed damage / buyout / capture] forwarded to rental team. Rental [rental_id] order [order_ref]. Turnaround time [handoff_sla].
Touchpoints
Rental badge PDP: bot_rental_explain embed
Date calendar: bot_rental_availability widget
Rental customer area: bot_rental_deposit_status entry
D-2 return email: bot_rental_return_guide deep link
Edge cases and reroutes
Five cases outside tier 1 bot standard location.
Calendar extension: EXTEND-HANDOFF-BOT #619 RN-7 extend rental
Disputed damage capture: NO-CAPTURE-BOT handoff #619 RENTAL-DAMAGE-01
Mid-rental buyout: handoff #619 buyout_option_rules formula
Trial kit confusion: TRIAL-REROUTE-BOT #538 distinct
New purchase return: standard return policy no rental_id
Bot never executes extension capture or waive late fee: agents #619 ops rental workflow.
Essential rental_bot KPIs
Five RENTALbot steering metrics.
rental_bot_explain_deflect: explain model resolved without agent
rental_bot_deposit_deflect: deposit status resolved TPL-DEPOSIT
rental_bot_return_deflect: return guide resolved due_date quote
rental_bot_handoff_rate: extension damage / total rental bot
rental_bot_deposit_promise_violations: promised release before inspection audit target 0
Target: rental_bot_deposit_promise_violations 0 and rental_bot_explain_deflect greater than 65% with RENTAL-MAP sync PDP.
RENTALbot anti-patterns
Five common bot rental location errors.
Deposit released promised bot: NO-DEPOSIT-RELEASE-PROMISE-BOT inspection ops
Direct damage capture bot: NO-CAPTURE-BOT handoff #619
Waive late fee bot: NO-LATE-FEE-WAIVE-BOT late_fee_policy cite
Invented status without API: RENTAL-STATUS-VERIFY-BOT rental_id lookup
Confusing trial kit: TRIAL-REROUTE-BOT #538 distinct location
RENTALbot with Qstomy
Qstomy on Shopify: detect bot_rental intent, RENTAL-MAP RAG grounded, rental_status API lookup, deposit cite, handoff #619 extension damage payload rental_id.
Pipeline: #620 bot explain dates deposit tier 1 → #619 extension capture escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
RENTALbot Checklist (8 steps)
Sync RENTAL-MAP #619: RAG bot PDP rental
Policy RENTALBOT-SUP: 6 rules NO-DEPOSIT-RELEASE-PROMISE
8 intents bot_rental_*: flow RNB-1 to RNB-8
4 templates TPL-RENTALbot-*: EXPLAIN DEPOSIT RETURN HANDOFF
Rental status API: due_date deposit inspection connect RNB-4
PDP calendar embed: bot_rental_availability entry
Red team 10 prompts: released deposit promised waive late fee capture
Dashboard KPI: rental_bot_* section 9
FAQ
Difference #619?
#619 = agents extension damage capture escalate. #620 = bot tier 1 explain dates deposit handoff.
Does the bot promise a released deposit?
No. NO-DEPOSIT-RELEASE-PROMISE-BOT INSPECTION-BEFORE-RELEASE ops #619.
Is bot extension possible?
No. EXTEND-HANDOFF-BOT #619 calendar stock ops.
Difference from trial kit bot #538?
#538 = try-before-buy refund convert. #620 = rental return due_date deposit.
Going further
This week: index RENTAL-MAP RAG, connect rental status API bot, red team released deposit promised.
Enzo
July 1, 2026
