E-commerce
July 1, 2026
"The bot changed the name without checking that it was my order." "The AI suggests modifying the address when I just wanted to correct the first name." "Parcel shipped under the old name despite my chat request." Three failures where a poorly calibrated recipient bot confuses name, address, and pre-shipping window.
An AI recipient correction chatbot does not replace WRONGNAME agents (#541). It reads WRONGNAME-MAP, collects verify_identity, cites change_allowed pre-ship, and handoff fix before cutoff.
This guide #542 covers intents bot_recipient_*, flow RECIPIENTbot, and KPI recipient_bot. Bot pair of the playbook WRONGNAME (#541). New AI use case: correct recipient name before shipping without distracting or promising post-label.
Summary
Why automate recipient correction using a bot?
The "wrong name on label" request arrives minutes post-purchase, before warehouse pick. A calibrated bot collects verify checklist, cites cutoff map, and refuses change if label_created without void.
What the bot resolves tier 1
Verify collect: billing_last4 zip amount checklist
Scope explain: name_field change_allowed map
Name typo guide: client provides new_shipping_name post-verify
Pre-ship gate: unfulfilled only PRE-SHIP-ONLY
Cutoff cite: correction deadline grounded map
Shopify allows editing shipping name on unfulfilled orders (Shopify, edit orders 2026). The bot intercepts bot_recipient_name_typo before unsafe handoff.
RECIPIENTbot vs WRONGNAME #541, CONTVERIFY #524, address #183 and phone #523
Five contents, five pre-shipment recipient layers.
Quick matrix
#542 RECIPIENTbot: bot verify collect name pre-ship tier 1
#541 WRONGNAME: agents execute fix label regen
#524 CONTVERIFY: bot proactive detect phone email
#183 address: complete address change
#523 PHNINV: delivery phone correction
Pipeline: bot verify OK new_name → #541 execute Shopify update → 3PL label regen. #524 = prevent. #542 = reactive name correction.
Which bot_recipient_* intents should be configured?
Eight bot intents for recipient correction.
Eight bot_recipient intents
bot_recipient_name_typo: spelling mistake in recipient's first/last name
bot_recipient_name_change: change shipping name pre-shipment
bot_recipient_verify: collect billing proof checklist
bot_recipient_gift_label: correct name on gift label
bot_recipient_pickup_name: pickup point name must match ID
bot_recipient_phone_combo: name + phone → reroute #523
bot_recipient_too_late: label_created explain CARRIER-LABEL-LIMIT
bot_recipient_confirm_fix: verify OK → handoff #541 execute
Tier 1 auto: name_typo explain, verify collect, too_late scope if order lookup without direct Shopify update.
Intent bot_recipient_confirm_fix, gift_label billing invoice → agents #541 or #463 with payload verify_result order_id new_name.
How to consume WRONGNAME-MAP #541?
The bot reads WRONGNAME-MAP #541: name_field, fulfillment_stage, change_allowed, verify_identity, carrier_impact, invoice_impact, bot_intent_map.
Lookup grounded
Order lookup: shipping_name fulfillment label_status
WRONGNAME-MAP row: name_field x fulfillment branch
Verify gate: billing_last4 zip amount match API
Change scope cite: Y note_only carrier_void_required
Cutoff deadline: 3PL pick time from map or ops config
Alignment anti-hallucination (#123): bot never modifies name without verify pass.
RECIPIENTBOT-SUP policy in six rules
Six bot rules for secure recipient correction.
PRE-SHIP-ONLY: unfulfilled before label_created gate
VERIFY-BEFORE-CHANGE: verification required before new_name
NO-NAME-UPDATE-BOT: bot collect verify handoff #541 execute
WRONGNAME-MAP-GROUNDED: change_allowed from map only
NAME-NOT-ADDRESS: street postal code city → reroute #183 address
CARRIER-LABEL-LIMIT: post label = explain void handoff #541
Flow RECIPIENTbot RCB-1 to RCB-8
Eight-step recipient correction bot flow.
RCB-1 Classify: bot_recipient_* intent
RCB-2 Order lookup: shipping_name fulfillment stage
RCB-3 WRONGNAME-MAP: change_allowed carrier cutoff
RCB-4 Verify collect: billing_last4 zip amount ask
RCB-5 Verify match: API compare pass fail
RCB-6 Respond: TPL-RECIPIENTbot scope or too_late
RCB-7 Handoff fix: verify OK new_name → #541
RCB-8 Log: verify_result tag recipient_bot
Example TPL-RECIPIENTbot-VERIFY
"To secure order [order_num], please confirm: last 4 digits of card OR amount [amount] € AND billing zip code. Then provide the correct recipient name."
TPL-RECIPIENTbot templates and touchpoints
Four essential templates.
TPL-RECIPIENTbot-VERIFY
Let's secure your order. Confirm the amount of [amount] € and billing postal code. Then send the correct recipient name for the label.
TPL-RECIPIENTbot-SCOPE
Name correction allowed: [change_allowed map]. Status: [fulfillment_stage]. Shipping cutoff: [cutoff_time]. Identity verification required.
TPL-RECIPIENTbot-TOO-LATE
Label already generated. Name correction subject to 3PL label void. Agent #541 is processing within [sla]. Status: [status_url].
TPL-RECIPIENTbot-ADDRESS-REROUTE
Street address, postal code, city change: separate process (#183). For name only, stay here after verification.
Touchpoints
Order status page: "Incorrect recipient name?" chip
Post-checkout email: pre-ship recipient correction link
Confirmation unfulfilled: bot_recipient_proactive webhook option
Help center recipient FAQ: bot embed verify checklist
Edge cases and reroutes
Five cases outside tier 1 bot.
Full address: #183 NAME-NOT-ADDRESS reroute
Phone only: #523 PHNINV or #524 CONTVERIFY
Contact email: #522 WEMAILbot distinct
Invoice billing name: #463 INVADDR rebilling
Verify fail 3x: handoff #541 manual review fraud
Bot never updates Shopify shipping name directly: handoff #541 post bot_recipient_confirm_fix verify pass.
Essential recipient_bot KPIs
Five RECIPIENTbot management metrics.
recipient_bot_verify_collect_rate: % sessions with verify ask
recipient_bot_verify_pass_rate: % verify match success
recipient_bot_pre_ship_fix: fixes before label_created
recipient_bot_unauthorized_change: change without verify, target 0
recipient_bot_address_reroute: sessions → #183 full address
Monthly Red Team: 10 prompts "change name without proof", "modify address via bot name", "correct after dispatch guaranteed". Change without verify = VERIFY-BEFORE-CHANGE violation.
RECIPIENTbot anti-patterns
Six common mistakes.
Name changed without verify: VERIFY-BEFORE-CHANGE
Bot update Shopify directly: NO-NAME-UPDATE-BOT
Confusing address #183: NAME-NOT-ADDRESS
Promising post-scan carrier fix: CARRIER-LABEL-LIMIT
Active post-ship: PRE-SHIP-ONLY gate
Invoicing via ship macro: INVOICE-REROUTE #463
RECIPIENTbot with Qstomy
Qstomy on Shopify: detect bot_recipient intent, WRONGNAME-MAP RAG, verify widget billing match, PRE-SHIP-ONLY gate, handoff #541 fix payload, cutoff cite, audit unauthorized change.
Pipeline: bot verify collect → #541 execute label regen → AI governance #142 audit identity claims.
Explore AI support and request a demo.
Checklist, FAQ and going further
RECIPIENTbot Checklist (8 steps)
Sync WRONGNAME-MAP #541: RAG bot whitelist only
Policy RECIPIENTBOT-SUP: 6 PRE-SHIP-ONLY rules
8 intents bot_recipient_*: flow RCB-1 to RCB-8
4 templates TPL-RECIPIENTbot-*: VERIFY SCOPE TOO-LATE ADDRESS
Billing verify API match: last4 zip amount gate
Order status chip recipient: bot_recipient_name_typo entry
Red team 10 prompts: change without proof post-ship
Dashboard KPI: recipient_bot_* section 9
FAQ
Difference #541?
#541 = agents execute fix label regen. #542 = bot tier 1 verify collect handoff.
Bot directly changes name?
No. Verify pass then handoff #541 Shopify update.
Difference #524 CONTVERIFY?
#524 = proactive detect phone email. #542 = reactive client name correction.
Address change?
NAME-NOT-ADDRESS reroute #183.
Going further
This week: index WRONGNAME-MAP bot corpus, test red team "change name without proof", measure recipient_bot_unauthorized_change. Activate incorrect name order status chip.
Enzo
July 1, 2026
