E-commerce
July 1, 2026
“The bot confirmed that my COA is authentic without checking the registry.” “The AI promises a duplicate even though the policy refuses.” “The chatbot confuses my gift voucher with my product certificate of authenticity.” Three failures where a badly calibrated COA bot creates false trust or reissue liability.
An AI chatbot for certificates of authenticity does not replace AUTHCERT agents (#565). It reads AUTHCERT-MAP, cites coa_format verify_url duplicate_policy, guides verification and hands off reissue mismatch to humans.
This guide #566 covers intents bot_authcert_*, flow AUTHCERTbot and KPI authcert_bot. Bot pair of the playbook AUTHCERT (#565). New premium AI use case: find explain verify COA without reissuing or inventing auth status.
Summary
Why automate COAs using a bot?
"Will I get a certificate?", "how do I verify this serial?", and "where can I find my COA PDF?" are recurring questions on PDP premium and resale pages. A calibrated bot looks up authcert_sku_id, cites coa_format verify_url duplicate_policy from AUTHCERT-MAP.
What the bot resolves at tier 1
COA format: physical digital both according to map
Serial verification: verify_url registry auth status
Serial location: engraving label QR serial_field
Digital access: customer account COA PDF if auth buyer
Duplicate policy: duplicate_policy cites without promising
Authentify estimates that 40% of premium COA requests are pre-purchase or second-hand verification, which can be handled as self-service if the registry is connected (Authentify, COA e-commerce 2026). The bot intercepts bot_authcert_verify before status is invented.
AUTHCERTbot vs AUTHCERT #565, NUMEDbot #564, PHYGCERTbot #548 and counterfeiting #567
Five contents, five distinct proof types.
Quick Matrix
#566 AUTHCERTbot: tier 1 bot COA verify explain lookup
#565 AUTHCERT: reissue agents mismatch duplicate execute
#564 NUMEDbot: numbered edition bot rarity serial
#548 PHYGCERTbot: gift voucher bot distinct balance
#567 counterfeit: support suspicion counterfeit human product
Pipeline: bot verify explain → #565 reissue mismatch execute. #548 reroute if gift certificate intents.
Which bot_authcert_* intents should be configured?
Eight COA bot intents mapped to #565 typologies.
Eight bot_authcert intents
bot_authcert_coa_info: coa_format included pre-purchase
bot_authcert_verify: serial status register verify_url
bot_authcert_serial_location: where to find product serial
bot_authcert_digital_find: PDF COA customer area
bot_authcert_duplicate_info: duplicate_policy quotes without executing
bot_authcert_secondhand: buyer resale verify only
bot_authcert_verify_how: QR process register steps
bot_authcert_handoff: missing damaged mismatch → #565
Tier 1 auto: coa_info, verify, serial_location, digital_find, duplicate_info, verify_how if authcert_sku_id + AUTHCERT-MAP + guardrails.
bot_authcert_handoff, reissue demand → agents #565 payload serial intent proof.
How do I use AUTHCERT-MAP #565?
The bot reads AUTHCERT-MAP #565: authcert_sku_id, coa_format, serial_field, verify_url, duplicate_policy, reissue_proof_required, reissue_sla_days, counterfeit_escalation.
Lookup grounded
SKU lookup: authcert_sku_id PDP metafield
AUTHCERT-MAP row: format verify duplicate proof
Registry API: verify_url serial status auth only
Order COA link: digital PDF if buyer session matches
AUTH-VERIFY-BOT: status auth registry only never oral
OWNER-PRIVACY-BOT: initial owner serial never cited
Alignment anti-hallucination (#123): status auth = registry API or verify_url only.
AUTHCERTBOT-SUP policy in six rules
Six safe COA bot rules.
AUTHCERT-MAP-GROUNDED: duplicate format verify from map only
AUTH-VERIFY-BOT: auth status via verify_url registry only
NO-REISSUE-BOT: bot does not reissue or send COA
NO-DUPLICATE-PROMISE-BOT: quotes duplicate_policy without promising
OWNER-PRIVACY-BOT: initial owner never disclosed
GIFT-CERT-REROUTE: gift voucher → #548 PHYGCERTbot intents
AUTHCERTbot flow ACB-1 to ACB-8
Eight-step flow for certificate of authenticity bot.
ACB-1 Classify: bot_authcert_* intent detect
ACB-2 SKU collect: authcert_sku_id or serial provided
ACB-3 AUTHCERT-MAP: coa_format verify_url duplicate
ACB-4 Registry lookup: verify_url API if verify intent
ACB-5 Guardrail: AUTH-VERIFY NO-REISSUE OWNER-PRIVACY
ACB-6 Respond: TPL-AUTHCERTbot grounded
ACB-7 Handoff: missing mismatch reissue → #565
ACB-8 Log: intent serial_id tag authcert_bot
Example TPL-AUTHCERTbot-VERIFY
"Verification serial [serial]: [registry status: authentic / not found / revoked]. Official page: [verify_url]. Only this source is authoritative. Reissue or duplicate: see policy [duplicate_policy map] or agent if eligible."
TPL-AUTHCERTbot and touchpoints templates
Four essential templates.
TPL-AUTHCERTbot-COA
[product_name]. Certificate: [coa_format map]. Serial: [serial_field location]. Verification: [verify_url]. Duplicate: [duplicate_policy summary].
TPL-AUTHCERTbot-VERIFY
Serial [serial]: [registry status]. Page: [verify_url]. Out-of-channel proof brand invalid.
TPL-AUTHCERTbot-DIGITAL
Digital COA [product_name]: [client space link if auth session]. [Otherwise: included in shipment coa_format map.] Proof of reissue: agent if missing.
TPL-AUTHCERTbot-HANDOFF
Request [missing / damaged / mismatch / reissue] forwarded to agent. Serial [serial]. Delay [handoff_sla]. Proof required: [reissue_proof_required map].
Touchpoints
Premium PDP: bot_authcert_coa_info chip
/verify Page: bot_authcert_verify embed
Post-purchase email: bot_authcert_digital_find link
Authenticity FAQ: bot embed AUTHCERT-MAP RAG
Edge cases and reroutes
Five cases outside tier 1 bot verify standard.
Missing package COA: NO-REISSUE-BOT handoff #565 AUTHCERT-REISSUE-01
Serial mismatch: handoff #565 AUTHCERT-MISMATCH-01
Product counterfeit: COUNTERFEIT-HANDOFF #567 if outside COA scope
Gift voucher confusion: GIFT-CERT-REROUTE #548
Numbered edition: #564 if numbered_sku overlap serial collector
Bot never reissues COA: missing damaged reissue → agents #565 ops proof collect.
Essential authcert_bot KPIs
Five steering metrics for AUTHCERTbot.
authcert_bot_verify_deflect: verify sessions without human ticket
authcert_bot_coa_info_deflect: COA format sessions solved by bot
authcert_bot_auth_invented: invented auth status by bot, target 0
authcert_bot_privacy_violation: owner cited by bot, target 0
authcert_bot_handoff_rate: sessions → #565 agents
Monthly Red team: 10 prompts "confirm authentic without serial", "send duplicate", "who bought this serial?". Invented status = AUTH-VERIFY-BOT violation.
AUTHCERTbot anti-patterns
Six common mistakes.
Unregistered auth: AUTH-VERIFY-BOT
Duplicate promise: NO-DUPLICATE-PROMISE-BOT
Reissued COA bot: NO-REISSUE-BOT
Cited owner: OWNER-PRIVACY-BOT
Gift certificate confusion: GIFT-CERT-REROUTE #548
Policy off-map: AUTHCERT-MAP-GROUNDED
AUTHCERTbot with Qstomy
Qstomy on Shopify: detect bot_authcert intent, AUTHCERT-MAP RAG, verify_url registry lookup, NO-REISSUE guardrail, OWNER-PRIVACY filter, handoff #565 reissue payload.
Pipeline: bot tier 1 verify explain → #565 reissue mismatch execute → AI governance #142 audit COA bot.
Explore AI support and request a demo.
Checklist, FAQ and going further
AUTHCERTbot Checklist (8 steps)
Sync AUTHCERT-MAP #565: RAG bot + verify_url registry API
Policy AUTHCERTBOT-SUP: 6 AUTH-VERIFY-BOT rules
8 intents bot_authcert_*: flow ACB-1 to ACB-8
4 templates TPL-AUTHCERTbot-*: COA VERIFY DIGITAL HANDOFF
Page verify embed: bot_authcert_verify entry
GIFT-CERT reroute: phygcert intents → #548
Red team 10 prompts: fake auth duplicate promised owner
Dashboard KPI: authcert_bot_* section 9
FAQ
Difference #565?
#565 = reissue agents mismatch duplicate execute. #566 = bot tier 1 verify explain lookup handoff.
Authentic serial?
TPL-AUTHCERTbot-VERIFY verify_url registry API only.
Duplicated COA?
bot_authcert_duplicate_info cite policy. Execution → #565.
Missing COA?
NO-REISSUE-BOT. Handoff #565.
Going further
This week: sync AUTHCERT-MAP verify_url bot, red team "confirm authentic", measure authcert_bot_auth_invented. Activate premium COA PDP chip.
Enzo
July 1, 2026
