E-commerce
July 1, 2026
"The bot should have detected the invalid number before shipping." "The AI sends the confirmation to gmial.com without an alert." "Parcel blocked on phone_hold, nobody notified the customer." Three failures where a contact bot without preventive verification lets typo phone email slip through and generates an avoidable delivery incident.
An AI contact verification pre-shipping chatbot does not replace PHNINV (#523) or WEMAIL (#521) agents. It reads PHNINV-MAP, detects unfulfilled invalid format, proactively confirms phone email, and hands off the fix before labelling.
This guide #524 covers intents bot_contact_verify_*, flow CONTVERIFY, and KPI contactverify_bot. Companion bot of the playbook PHNINV (#523). New AI use case: preventing contact delivery incident before shipping cutoff.
Summary
Why automate contact verification with a bot?
Between payment and pick, the window to correct phone/email is short. A calibrated bot scans unfulfilled orders, validates E164 format, and alerts on domain typos before phone_hold or shipping.
What the tier 1 bot solves
Phone invalid detect: regex PHNINV-MAP format_rule
Email typo flag: suspicious domain gmial gmal
Proactive confirm: customer confirms contact details before shipping
Hold explain: phone_hold tag ops grounded
Handoff fix: corrected value → #523 #521 agents
Colissimo relies on the recipient's phone number for notifications (Colissimo, notification 2026). The bot intercepts bot_contact_verify_proactive before pick invalid.
CONTVERIFY vs PHNINV #523, WEMAIL #521 and recipient #542
Four contents, four contact order layers.
Quick matrix
#524 CONTVERIFY: bot pre-ship detect confirm prevent tier 1
#523 PHNINV: agents fix phone post-incident
#521 WEMAIL: agents fix email verify identity
#542 recipient: future recipient name correction pre-ship
Pipeline: #524 detect unfulfilled → client confirm fix → #523 or #521 execute → release phone_hold pick.
Which bot_contact_verify_* intents should be configured?
Eight contact verification bot intents.
Eight bot_contact_verify intents
bot_contact_verify_phone_invalid : invalid format number detected
bot_contact_verify_email_typo : suspicious email domain flagged
bot_contact_verify_confirm_all : confirm phone and email before shipping
bot_contact_verify_proactive : auto scan of unfulfilled via webhook
bot_contact_verify_fix_phone : collect new phone handoff #523
bot_contact_verify_fix_email : collect new email handoff #521
bot_contact_verify_hold_explain : phone_hold reason for delay
bot_contact_verify_post_ship : shipped reroute incident #523
Tier 1 auto: phone_invalid, email_typo, confirm_all, hold_explain if unfulfilled + PHNINV-MAP lookup.
Intent fix_phone fix_email post confirm → agents #523 #521 with payload order_id corrected_value verify pass.
How to use PHNINV-MAP #523 and email rules?
The bot reads PHNINV-MAP #523: format_rule, phone_required, hold_ship_if_invalid, sms_tracking, change_allowed. Plus the email typo domain list from WEMAIL-MAP #521.
Lookup grounded
Order scan: phone email shipping_address unfulfilled only
Phone validate: regex format_rule E164 fail pass
Email typo list: gmial gmal .con domain whitelist block
Hold gate: hold_ship_if_invalid Y → phone_hold tag
Carrier row: shipping method → PHNINV-MAP branch
Alignment anti-hallucination (#123): validation = map regex only, no LLM guess.
CONTVERIFYBOT-SUP Policy in six rules
Six bot rules for safe contact verification.
PRE-SHIP-ONLY: scan fix unfulfilled before label only
PHNINV-MAP-GROUNDED: format hold from map only
NO-AUTO-FIX: bot alert confirm handoff agents execute
VERIFY-BEFORE-UPDATE: identity gate before corrected value
PROACTIVE-CONSENT: customer confirms new phone email explicit
POST-SHIP-REROUTE: shipped → #523 #521 incident playbook
Flow CONTVERIFY CVB-1 to CVB-8
Flow eight steps bot contact verification.
CVB-1 Trigger: webhook unfulfilled or client ask
CVB-2 Order scan: phone email address carrier method
CVB-3 Validate: PHNINV-MAP regex email typo list
CVB-4 Flag: invalid typo hold_required classify
CVB-5 Proactive msg: TPL-CONTVERIFY alert client
CVB-6 Confirm collect: client OK or corrected value
CVB-7 Handoff fix: verify → #523 phone #521 email
CVB-8 Log: prevent_tag release_hold tag contactverify_bot
Example TPL-CONTVERIFY-PHONE
"Order [order_num]: phone [phone_mask] seems invalid format [format_rule]. Confirm or correct before shipping. Shipping pending phone_hold."
TPL-CONTVERIFY templates and touchpoints
Four essential templates.
TPL-CONTVERIFY-PHONE
Phone [phone_mask]: [carrier] format required [format_rule]. Confirm OK or send corrected number.
TPL-CONTVERIFY-EMAIL
Email [email_mask]: suspicious domain detected. Confirm address or correct before order confirmation.
TPL-CONTVERIFY-CONFIRM
Contact recap: tel [phone_mask] email [email_mask]. All correct? Reply YES or indicate correction.
TPL-CONTVERIFY-HOLD
Shipping paused phone_hold: contact to be corrected. Correction window: [cutoff_hours] hrs before pick.
Touchpoints
Post-purchase e-mail 5 min : bot_contact_verify_confirm_all link
Shopify Flow unfulfilled : auto scan invalid phone email
Order status page : chip « Verify my contact info »
WMS phone_hold Slack : bot proactive client notify
Edge cases and reroutes
Five cases out of tier 1 bot.
Already shipped: POST-SHIP-REROUTE #523 PHNINV incident
Suspicious address: #183 address verify
Recipient gift: #205 contact split
Expat dialing code: #467 intl format
Recipient name: future #542 recipient correction
Bot does not modify Shopify contact directly: handoff #523 #521 post bot_contact_verify_fix confirm and verify identity.
Essential contactverify_bot KPIs
Five CONTVERIFY management metrics.
contactverify_bot_scan_rate: % unfulfilled scanned daily
contactverify_bot_invalid_detect: invalid phone email flagged
contactverify_bot_fix_before_ship: % corrected before label
contactverify_bot_prevent_incident: estimated avoided phone incidents
contactverify_bot_proactive_response: % customers reply to alert within 24 hours
Monthly red team: 10 test orders with invalid phone and email typos. Target: contactverify_bot_fix_before_ship > 85% if phone_hold is active.
Anti-patterns CONTVERIFY
Six frequent mistakes.
Auto-fix without confirmation: NO-AUTO-FIX violation
Scan shipped orders: PRE-SHIP-ONLY
Invented format: PHNINV-MAP-GROUNDED
Duplicate #523 incident: preventive vs reactive focus
Ignore email typo: email_typo list WEMAIL
Release hold without fix: handoff #523 confirm first
CONTVERIFY with Qstomy
Qstomy on Shopify + WMS: Flow unfulfilled scan, PHNINV-MAP validate, proactive e-mail alert, phone_hold sync, handoff #523 #521 fix payload, dashboard prevent KPI.
Pipeline: CONTVERIFY prevent → #523 #521 fix → pick release → AI governance #142 audit contact changes.
Explore AI support and request a demo.
Checklist, FAQ and going further
CONTVERIFY Checklist (8 steps)
Sync PHNINV-MAP #523: RAG regex hold rules
Email typo list #521: domain whitelist block
Policy CONTVERIFYBOT-SUP: 6 PRE-SHIP-ONLY rules
8 intents bot_contact_verify_*: flow CVB-1 to CVB-8
4 templates TPL-CONTVERIFY-*: PHONE EMAIL CONFIRM HOLD
Shopify Flow unfulfilled trigger: daily scan invalid
WMS phone_hold integration: release post fix confirm
Dashboard KPI: contactverify_bot_* section 9
FAQ
Difference #523?
#523 = agents fix phone post-incident. #524 = bot prevent pre-ship detect alert.
Difference #521 email?
#521 = fix email verify. #524 = flag typo proactive pre-ship.
Bot modifies contact?
No. Alert confirm handoff #523 #521 execute.
Parcel already shipped?
POST-SHIP-REROUTE playbook incident #523.
Going Further
This week: activate Flow scan unfulfilled invalid phone, test TPL-CONTVERIFY-PHONE on simulated typo order, measure contactverify_bot_fix_before_ship.
Enzo
July 1, 2026
