E-commerce
July 1, 2026
"The bot says my voucher is credited even though the trade-in is still in transit." "The AI accepts my torn jacket when the map requires clean condition." "Chatbot promises €20 credit without verifying submission_id." Three failures where a poorly calibrated textile trade-in bot invents rewards or validates items out of rules.
An AI textile trade-in chatbot does not replace TEXTTB agents (#605). It reads TEXTTB-MAP, verifies submission queue status, cites condition_rules reward_amount_rules, and hands off rejected credit missing to human ops.
This guide #606 covers intents bot_texttb_*, flow TEXTTBbot, and KPI texttb_bot. Bot pair of the TEXTTB playbook (#605). New AI circularity use case: qualify eligibility explain procedure without promising credit or accepting item.
Summary
Why automate textile take-back with a bot?
"How does it work?", "is my labelless pair of jeans accepted?" and "where is my voucher?" are frequently asked questions regarding fashion circularity programs. A calibrated chatbot looks up TEXTTB-MAP, verifies submission status, and cites condition_rules without improvising credit.
What the tier 1 chatbot resolves
Procedure explained: customer_copy shipping_method map
Category eligibility: accepted_categories brand_scope map
Condition status: condition_rules rejection_rules cite
Reward status: submission queue processing_sla API
Proof of postage: proof_required deposit_fee_policy guide
ThredUp notes that fashion take-back programs convert better when eligibility and reward timelines are clear from the very beginning of the chat (ThredUp, resale programs 2026). The chatbot intercepts bot_texttb_eligibility before any dummy acceptance takes place.
TEXTTBbot vs TEXTTB #605, return to customer service, eco #225 and second hand
Five contents, five distinct circularity moments.
Quick matrix
#606 TEXTTBbot: tier 1 bot eligibility procedure status reward handoff
#605 TEXTTB: agents credit reject escalate ops marketing
New return: refund order policy distinct return
Eco #225: eco_end_of_life reroute trade-in program
Second hand: pre-owned purchase SNAD distinct
Pipeline: bot explain elig status → #605 credit reject escalate. New return → RETURN-REROUTE.
Which bot_texttb_* intents should be configured?
Eight textile return bot intents mapped to texttb_* typologies #605.
Eight bot_texttb intents
bot_texttb_explain : customer_copy shipping procedure reward map
bot_texttb_eligibility : accepted_categories brand_scope map
bot_texttb_condition : condition_rules rejection_rules cite
bot_texttb_label_check : label_required without label map
bot_texttb_reward_status : submission queue processing_sla cite
bot_texttb_proof_guide : proof_required upload tracking receipt
bot_texttb_deposit_info : deposit_fee_policy deposit map
bot_texttb_handoff : rejected reward missing → #605
Tier 1 auto: explain, eligibility, condition, label_check, reward_status, proof_guide, deposit_info if TEXTTB-MAP + guardrails.
bot_texttb_handoff, rejected dispute credit issue → agents #605 payload submission_id program_id.
How should TEXTTB-MAP #605 be consumed?
The bot reads TEXTTB-MAP #605: program_id, accepted_categories, brand_scope, condition_rules, min_items_qty, reward_type, reward_amount_rules, deposit_fee_policy, shipping_method, proof_required, processing_sla_days, rejection_rules, customer_copy.
Lookup grounded
Program detect: program footer page → TEXTTB-MAP row
Submission queue API: ops portal status SUBMISSION-VERIFY-BOT
Customer email match: submission_id lookup by email
NO-REWARD-PROMISE-BOT: reward_amount_rules map only
NO-ACCEPT-BOT: bot never approves accepted parts ops
CONDITION-CITE-BOT: refusal eligibility cites condition_rules map
Alignment anti-hallucination (#123): reward status = submission queue API only.
Policy TEXTTBBOT-SUP in six rules
Six rules bot textile return safe.
TEXTTB-MAP-GROUNDED: reward condition deposit from map only
SUBMISSION-VERIFY-BOT: queue API before status reward cite
NO-REWARD-PROMISE-BOT: bot does not promise credit off map
NO-ACCEPT-BOT: bot neither approves nor validates received item
CONDITION-CITE-BOT: elig refusal according to condition_rules rejection_rules
RETURN-REROUTE-BOT: new order return → distinct return policy
Flow TEXTTBbot TTB-1 to TTB-8
Flow eight steps bot textile take-back.
TTB-1 Classify: bot_texttb_* intent detect
TTB-2 Collect: email submission_id items category question
TTB-3 TEXTTB-MAP: program reward condition shipping proof
TTB-4 Submission verify: queue API status SUBMISSION-VERIFY
TTB-5 Guardrail: NO-REWARD-PROMISE NO-ACCEPT CONDITION-CITE
TTB-6 Respond: TPL-TEXTTBbot grounded map
TTB-7 Handoff: rejected reward missing → #605
TTB-8 Log: intent program_id tag texttb_bot
Example TPL-TEXTTBbot-REWARD
“Take-back [submission_id]: status [queue API: received / processing / credited / rejected]. [If pending: reward within [processing_sla_days map] d.] [If credited: [reward_type] [amount map] sent [date].] [If rejected: TPL-TEXTTBbot-ELIG handoff #605.]”
TPL-TEXTTBbot and touchpoints templates
Four essential templates.
TPL-TEXTTBbot-EXPLAIN
Program [program_id]: [customer_copy map]. Accepted: [accepted_categories brand_scope]. Min [min_items_qty] items. Shipping: [shipping_method]. Reward: [reward_type reward_amount_rules]. Processing time: [processing_sla_days] days.
TPL-TEXTTBbot-ELIG
Item [catégorie]: [eligible / rejected according to map]. Conditions: [condition_rules]. [If label: [label_required map].] [If rejected: [rejection_rules].] [Bot does not approve: shipment subject to ops review.]
TPL-TEXTTBbot-REWARD
Submission [submission_id]: [queue status]. [If pending: SLA [processing_sla_days].] [If credited: [reward_type] [amount].] Tracking link: [portal status].
TPL-TEXTTBbot-HANDOFF
Request [rejected / reward missing / dispute] forwarded to trade-in team. Submission [submission_id]. Program [program_id]. Processing time [handoff_sla].
Touchpoints
Trade-in program page: bot_texttb_explain embed
Eligibility FAQ: bot_texttb_eligibility widget
Submission status portal: bot_texttb_reward_status entry
Circularity checkout footer: bot_texttb_explain chip
Edge cases and reroutes
Five cases outside tier 1 bot standard textile recovery.
Disputed rejected item: NO-ACCEPT-BOT handoff #605 TEXTTB-REJECT escalate
Missing credit SLA exceeded: handoff #605 TEXTTB-REWARD-01 issue credit
New order return: RETURN-REROUTE retour refund distinct
General sustainability question: eco #225 reroute
Second-hand purchase: SNAD grading reroute distinct
Bot never issues credit or validates items: ops decision → agents #605 workflow queue.
Essential bot KPIs
Five TEXTTBbot monitoring metrics.
texttb_bot_elig_deflect: eligibility condition resolved without agent
texttb_bot_explain_deflect: explain procedure resolved without handoff
texttb_bot_reward_deflect: reward_status resolved without ticket
texttb_bot_handoff_rate: rejected reward missing / total texttb bot
texttb_bot_hallucination_rate: promised accepted credit out of target audit map 0
Target: texttb_bot_elig_deflect greater than 70% with TEXTTB-MAP sync program page API submission.
Anti-patterns TEXTTBbot
Five common textile takeback bot errors.
Invented promised credit: NO-REWARD-PROMISE-BOT reward_amount_rules map
Bot approved item: NO-ACCEPT-BOT handoff ops #605
Invented credited status: SUBMISSION-VERIFY-BOT queue first
Confusing return as new: RETURN-REROUTE refund distinct
Accepting outside condition_rules: CONDITION-CITE-BOT rejection_rules cite
TBbot with Qstomy
Qstomy on Shopify: detect bot_texttb intent, TEXTTB-MAP RAG grounded, submission queue lookup, condition_rules cite, handoff #605 reject credit payload submission_id.
Pipeline: #606 bot status elig → #605 credit reject escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
TEXTTBbot Checklist (8 steps)
Sync TEXTTB-MAP #605: RAG bot + submission API
Policy TEXTTBBOT-SUP: 6 NO-ACCEPT-BOT rules
8 intents bot_texttb_*: flow TTB-1 to TTB-8
4 templates TPL-TEXTTBbot-*: EXPLAIN ELIG REWARD HANDOFF
Program page embed: bot_texttb_explain entry
Portal status widget: bot_texttb_reward_status
Red team 10 prompts: promised credit, torn item accepted, invented "credited" status
Dashboard KPI: texttb_bot_* section 9
FAQ
Difference with #605?
#605 = credit reject escalate ops agents. #606 = tier 1 bot elig procedure handoff status.
Does the bot approve my item?
No. NO-ACCEPT-BOT. Ops control after receipt.
Voucher delivery time?
TPL-TEXTTBbot-REWARD processing_sla_days map queue API.
New order return?
RETURN-REROUTE policy, refund return distinct from textile take-back.
Going further
This week: index TEXTTB-MAP RAG, embed program page bot take-back, red team promised credit, invented "credited" status.
Enzo
July 1, 2026
