E-commerce
July 1, 2026
"The bot says it's normal even though I have blisters." "The AI accepts my return at D+2 without checking the policy." "Chatbot promises guaranteed effect in 3 days outside instructions." Three failures where a poorly calibrated adaptation period bot minimizes symptoms, promises premature return, or confuses adaptation with guaranteed results #731.
An e-commerce adaptation period AI chatbot does not replace ADPTPER agents (#733). It reads ADPTPER-MAP, cites adaptation_timeline_copy progressive_usage_steps, distinguishes expected vs abnormal symptoms, and hands off medical exception returns to humans.
This guide #734 covers intents bot_adaptper_*, flow ADPTPERbot, and KPI adaptper_bot. Companion bot to the ADPTPER playbook (#733). Post-purchase AI use case: reassure, guide timeline, measure satisfaction without promised returns or medical advice.
Summary
Why automate the onboarding period with a bot?
"Is it normal that it stings?", "how many days until comfort?" and "I want to return now" arrive D+2 to D+14 post-delivery, often before an agent ticket. A calibrated bot cites ADPTPER-MAP timeline steps symptoms without confirming premature return nor reassuring outside map on abnormal reaction.
What the bot resolves tier 1 adaptation period
Timeline explain: adaptation_timeline_copy TIMELINE-CITE map
Progressive usage: progressive_usage_steps STEPS-CITE map
Normal symptoms: expected_symptoms_copy SYMPTOM-CITE map
No effect yet: days_remaining gate adaptation_period_days map
Check-in D+7: checkin_touchpoints proactive satisfaction map
User Intuition points out that calibrated post-purchase education reduces expectation-reality returns (User Intuition, post-purchase expectations 2026). Without a grounded bot, the AI accepts D+2 returns or minimizes allergies.
ADPTPERbot vs ADPTPER #733, PERFGUARbot #732, onboarding bot and feedback
Six pieces of content, six distinct post-purchase moments.
Quick matrix
#734 ADPTPERbot: bot tier 1 timeline steps symptoms check-in handoff
#733 ADPTPER: agents return exception medical escalate ops
PERFGUARbot #732: guarantee outcome remedy distinct adaptation phase
Onboarding bot: first buyer relationship D+90 distinct product timeframe map
Returns bot: return change of mind distinct break-in adjustment
PRODWARNbot: warnings instructions distinct timeline adaptation
Pipeline: #734 bot reassure guide timeline tier 1 → #733 agents return exception medical escalate ops.
Which bot_adapter_* intents should be configured?
Eight adaptation period bot intents mapped to adaptper_* typologies #733.
Eight bot_adaptper intents
bot_adaptper_timeline : adaptation_timeline_copy TIMELINE-CITE map
bot_adaptper_progressive : progressive_usage_steps STEPS-CITE map
bot_adaptper_normal_symptoms : expected_symptoms_copy SYMPTOM-CITE map
bot_adaptper_abnormal_symptoms : abnormal_symptoms_copy handoff escalate
bot_adaptper_early_return : early_return_policy_copy NO-EARLY-RETURN handoff
bot_adaptper_no_effect : days_remaining gate adaptation_period_days map
bot_adaptper_vs_perf_guar : PERFGUAR731-REROUTE claim distinct
bot_adaptper_checkin : checkin_touchpoints satisfaction proactive map
Tier 1 auto : timeline, progressive, normal_symptoms, no_effect if ADPTPER-MAP active + guardrails NO-EARLY-RETURN.
bot_adaptper_abnormal_symptoms and bot_adaptper_early_return exception → agents #733 payload order days_elapsed intent.
How do I consume ADPTPER-MAP #733?
The bot reads ADPTPER-MAP #733: adaptper_program_id, eligible_skus, adaptation_period_days, adaptation_timeline_copy, progressive_usage_steps, expected_symptoms_copy, abnormal_symptoms_copy, early_return_policy_copy, checkin_touchpoints, perf_guar_link_flag, customer_communication_copy.
Lookup grounded
TIMELINE-CITE-BOT: adaptation_timeline_copy cites map verbatim
STEPS-CITE-BOT: progressive_usage_steps cites map only
SYMPTOM-CITE-BOT: expected vs abnormal symptoms cite map
NO-EARLY-RETURN-PROMISE-BOT: no return OK bot before early_return_policy_copy map
NO-MEDICAL-ADVICE-BOT: no personal diagnosis handoff abnormal
PERFGUAR731-REROUTE-BOT: claim remedy → #731 distinct adaptation
REG119-REROUTE-BOT: health claim → #119 REG legal distinct timeline
ADPTPER733-HANDOFF-BOT: medical exception return → #733 agents ADP-7
Alignment anti-hallucination (#123): timeline symptoms = ADPTPER-MAP whitelist only.
ADPTPERBOT-SUP six-rule policy
Six bot rules for the responsible adaptation period.
ADPTPER-MAP-GROUNDED-BOT : timeline steps symptoms from map only
TIMELINE-CITE-BOT : adaptation_timeline_copy cite without invented effect promise
NO-EARLY-RETURN-PROMISE-BOT : no confirmed return bot handoff #733 policy
SYMPTOM-CITE-BOT : expected abnormal cite map abnormal handoff escalate
NO-MEDICAL-ADVICE-BOT : do not reassure allergy severe reaction bot alone
PERFGUAR731-REROUTE-BOT : claim remedy guarantee → #732 PERFGUARbot distinct adaptation
ADPTPERbot Flow ADPB-1 to ADPB-8
Eight-step adaptation period bot flow.
ADPB-1 Classify: bot_adaptper_* intent detect email D+7 post-delivery widget
ADPB-2 Collect: order_ref sku days_since_delivery symptom question
ADPB-3 ADPTPER-MAP: timeline steps symptoms early_return perf_guar_link
ADPB-4 Order lookup: adaptation_period_flag delivery_date days_elapsed verify
ADPB-5 Guardrail: TIMELINE STEPS SYMPTOM NO-EARLY-RETURN NO-MEDICAL HANDOFF
ADPB-6 Respond: TPL-ADPTPERbot grounded customer_communication_copy
ADPB-7 Handoff or close: abnormal early_return exception #733 payload
ADPB-8 Log: intent adaptper_program_id tag adaptper_bot timeline_cited handoff Y/N
Example TPL-ADPTPERbot-TIMELINE
" [sku map] program [adaptper_program_id]: [adaptation_timeline_copy map.] Adaptation period [adaptation_period_days map] days, [days_remaining map] days remaining. [progressive_usage_steps map.] TIMELINE-CITE-BOT NO-EARLY-RETURN-PROMISE-BOT. "
TPL-ADPTPERbot and touchpoint templates
Four essential templates.
TPL-ADPTPERbot-TIMELINE
Program [adaptper_program_id]: [adaptation_timeline_copy map.] [adaptation_period_days map] days minimum. [progressive_usage_steps map if applicable.] TIMELINE-CITE-BOT STEPS-CITE-BOT.
TPL-ADPTPERbot-SYMPTOM
During adaptation, normal: [expected_symptoms_copy map.] Contact us if: [abnormal_symptoms_copy map.] SYMPTOM-CITE-BOT NO-MEDICAL-ADVICE-BOT.
TPL-ADPTPERbot-EARLY-RETURN
Delivered [days_elapsed] days ago. Adaptation period [adaptation_period_days map] days. [early_return_policy_copy map.] NO-EARLY-RETURN-PROMISE-BOT ADPTPER733-HANDOFF-BOT if exception.
TPL-ADPTPERbot-CHECKIN
Check-in Day+[day map]: [checkin_touchpoints map.] Everything okay or question about adaptation? [Chat widget link.] Satisfaction measured post-response.
Touchpoints
Email Day+3 Day+7 post-delivery: bot_adaptper_checkin proactive
Packaging QR insert: bot_adaptper_timeline entry
Keyword return now: bot_adaptper_early_return NO-EARLY-RETURN trigger
PDP badge adaptation widget: bot_adaptper_progressive pre-buy post-buy
Edge cases and reroutes
Five cases outside tier 1 bot standard adaptation period.
Severe allergy reaction: abnormal_symptoms ADPTPER733-HANDOFF-BOT #119 REG without minimizing
Result guarantee claim: PERFGUAR731-REROUTE-BOT #732 remedy distinct adaptation
Standard return policy: returns bot change of mind distinct run-in
Product warnings: PRODWARNbot notice distinct timeline
Return execute bot: ADPTPER733-HANDOFF-BOT agents #733 only
Bot explain timeline tier 1. Medical exception return escalate → agents #733.
Essential adapter_bot KPIs
Five ADPTPERbot management metrics.
adaptper_bot_timeline_deflect: timeline steps symptoms resolved without agent
adaptper_bot_timeline_cite_rate: TIMELINE-CITE-BOT / bot_adaptper_timeline no_effect
adaptper_bot_early_return_violations: bot promised return audit target 0
adaptper_bot_checkin_csat: post check-in satisfaction D+7 D+14 map
adaptper_bot_handoff_rate: abnormal early_return exception / total adaptper bot
Target: adaptper_bot_early_return_violations 0 and adaptper_bot_timeline_deflect greater than 50%.
ADPTPERbot anti-patterns
Five common mistakes bot adaptation period.
Confirmed return bot D+2 : NO-EARLY-RETURN-PROMISE-BOT handoff #733 policy
Minimize abnormal reaction : abnormal_symptoms ADPTPER733-HANDOFF-BOT escalate
Invented timeline bot : TIMELINE-CITE-BOT adaptation_timeline_copy map only
Confusing warranty #731 bot : PERFGUAR731-REROUTE remedy distinct adaptation
Medical advice bot : NO-MEDICAL-ADVICE-BOT handoff abnormal symptoms
ADPTPERbot with Qstomy
Qstomy on Shopify: detect bot_adaptper intent, ADPTPER-MAP RAG grounded, timeline steps cite, NO-EARLY-RETURN guardrail, check-in CSAT, handoff #733 ops tier 2.
Pipeline: #734 bot reassure guide timeline tier 1 → #733 agents return exception medical escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
ADPTPERbot Checklist (8 steps)
Sync ADPTPER-MAP #733 : RAG bot email D+7 insert packaging PDP
Policy ADPTPERBOT-SUP : 6 rules TIMELINE NO-EARLY-RETURN SYMPTOM NO-MEDICAL
8 intents bot_adaptper_* : flow ADPB-1 to ADPB-8
4 templates TPL-ADPTPERbot-* : TIMELINE SYMPTOM EARLY-RETURN CHECKIN
adaptation_period_flag API sync : delivery_date days_elapsed bot agents test
Email D+7 check-in embed chat : bot_adaptper_checkin proactive CSAT
Red team 10 prompts : promised return minimized symptom invented timeline
KPI Dashboard : adaptper_bot_* section 9 early_return_violations deflect csat
FAQ
Difference #733?
#733 = agents return exception medical escalate ops. #734 = bot tier 1 timeline steps symptoms check-in handoff.
Does the bot accept D+3 return?
No. TPL-ADPTPERbot-EARLY-RETURN NO-EARLY-RETURN-PROMISE-BOT ADPTPER733-HANDOFF-BOT.
Difference in result guarantee?
Adaptation = normal documented phase. Claim remedy → PERFGUAR731-REROUTE-BOT #732.
How to measure satisfaction?
adaptper_bot_checkin_csat post TPL-ADPTPERbot-CHECKIN D+7 D+14 email widget.
Go further
This week: index ADPTPER-MAP RAG email D+7, red team early_return_violations audit, sync check-in CSAT payload Klaviyo widget.
Enzo
July 1, 2026
