E-commerce
July 1, 2026
Client opens the chat 30 minutes after the flash SMS. "SMS20 is not working." "Is the offer over?" "How to stop the SMS?" The bot quotes a generic promo. Ticket smscam_code_fail.
An e-commerce SMS campaign AI chatbot reads the SMS registry, answers code condition expiration short link from SMSCAM-MAP #925, deflects the tier 1 peak and handsoff to agent if massive pattern.
This guide #926 covers intents bot_smscam_*, flow SMSCAMBOT SCB-1 to SCB-8 and guardrails SMS-REGISTRY-GATE. Bot pair of the SMSCAM playbook (#925). Use case: offer code expiration questions post-SMS widget.
Summary
Why botify post-SMS questions?
Post-SMS peak concentrates the same questions: code, flash expiration, short link, STOP. Without a campaign registry, the bot improvises and creates smscam_* tickets. SMS-REGISTRY-GATE aligns widget and agents #925.
What the Tier 1 promo SMS bot solves
Promo code: value conditions expiration
Flash offer: end time customer timezone
Short link: corrected mobile landing URL
Offer conditions: exclusions minimum purchase
STOP opt-out: PREF #382 route without auto promise
Retail DTC Example
Beauty DTC, SMS 15k. Bot syncs registry Day-1. smscam_bot_deflect +48%, smscam_code_fail_rate -45% over 4 weeks.
SMSCAMBOT #926 vs SMSCAM #925, POSTSMS #130, NOFFER #924 and PREF #382
Seven SMS bot contents, seven distinct roles.
Quick Matrix
#926 SMSCAMBOT: tier 1 bot post-SMS widget expiration code offer
SMSCAM #925: ops agents peak SC-4 macros
POSTSMS #130: distinct transactional SMS flash promo
NOFFER #924: distinct email newsletter bot SMS channel
PREF #382: distinct STOP opt-out preferences offer
STACK #870: distinct stackable codes SMS code
AGENTWAIT #919: agent waiting ETA spike SMS
Pipeline: post-SMS client → #926 tier 1 code expiry link → #925 handoff if massive ops flag.
Which bot_smscam_* intents should be configured?
Eight SMS campaign intents mapped SMSCAM-MAP #925.
Eight bot_smscam intents
bot_smscam_campaign_detect: detect active SMS campaign flash window
bot_smscam_code_answer: code value expiration terms
bot_smscam_expiry_answer: end time flash client timezone
bot_smscam_terms_answer: offer_copy exclusions minimum
bot_smscam_link_answer: short url mobile landing PDP
bot_smscam_stack_check: SMS code stacking vs other
bot_smscam_stop_route: STOP opt-out route PREF #382
bot_smscam_feed_loop: consume LOG #925 campaign_copy
Each response logs campaign_id intent smscam_* deflect_or_handoff.
How to consume/use SMSCAM-MAP #925?
The bot reads SMSCAM-MAP #925 + bot fields: campaign_id, code_promo, offer_copy, exclusions, expiration_date, flash_end_time, timezone_ref, stack_rules, short_url, stop_process_url, pic_window, eta_spike_copy, agent_handoff_url.
SMS Campaign Bot Guardrails
SMS-REGISTRY-GATE: offer code link from SMS registry only
CODE-GROUNDED-BOT: do not invent code without registry
EXPIRY-GROUNDED-BOT: flash end time map timezone
LINK-GROUNDED-BOT: short link mobile tested
STACK-CHECK-BOT: stacking according to stack_rules map
STOP-REROUTE-BOT: opt-out → #382 without auto-unsub
OPS-ESCALATE-BOT: 3+ code fail session → handoff #925
SMSCAM-FEED-LOOP-BOT: LOG #925 enriches campaign_copy widget
SMSCAMBOT-SUP policy in six rules
Six rules for a responsible SMS campaign on the widget side.
SMS-REGISTRY-GATE: registry lookup before code response
CAMPAIGN-DETECT-BOT: active flash window before tier 1
EXPIRY-GROUNDED-BOT: end time mentioned if flash offer
CODE-GROUNDED-BOT: registry promo code only
STOP-REROUTE-BOT: PREF route opt-out never auto promise
SMSCAM-FEED-LOOP-BOT: LOG #925 widget review within 48 hours
Flow SMSCAMBOT SCB-1 to SCB-8
Eight-step flow: incoming message detect campaign classify answer expiry stop log handoff.
SCB-1 Ingest: message code offer expiration STOP link post-SMS
SCB-2 Campaign detect: CAMPAIGN-DETECT active flash window
SCB-3 Classify: smscam_* vs stop #382 vs stack #870
SCB-4 Registry gate: SMS-REGISTRY-GATE campaign lookup
SCB-5 Tier 1 answer: code expiry terms link stack
SCB-6 Ops escalate: massive pattern agent handoff #925
SCB-7 Feed loop: LOG #925 adjusts campaign_copy
SCB-8 Log: deflect code_fail expiry_answer stop_route
Example TPL-SMSCAM-CODE
u00ab SMS Code: {{code_promo}}. Terms: {{offer_copy}}. Valid until {{expiration_date}}. u00bb
TPL-SMSCAM templates and touchpoints
Four short SMS campaign transition templates.
TPL-SMSCAM-CODE
[code_promo map.] [offer_copy map.] [expiration_date.] CODE-GROUNDED.
TPL-SMSCAM-EXPIRY
[flash_end_time map.] [timezone_ref.] Offer ended or active. EXPIRY-GROUNDED.
TPL-SMSCAM-LINK
[short_url map.] Mobile link tested. LINK-GROUNDED.
TPL-SMSCAM-STOP
[stop_process_url map.] STOP-REROUTE PREF #382. Not auto-unsub bot.
Touchpoints
"Code does not work": code_answer + stack_check
"Offer ended?": expiry_answer timezone
Dead SMS link: link_answer corrected url
LOG SMSCAM #925: feed_loop campaign_copy
Edge cases: outside the flash window, urgent STOP, SMS + newsletter
Five cases outside standard flow.
Outside flash window: EXPIRED registry end time + next offer
Urgent STOP: immediate STOP-REROUTE #382, no tier 1 offer
Stack refused: STACK-CHECK + #870
SMS + newsletter same code: registry distinct campaign_id channel
Ticket smscam_ despite bot: feed_loop review campaign gaps
Essential smscam_bot KPIs
Five SMSCAMBOT steering metrics and correlation #925.
smscam_bot_deflect: SMS questions resolved without a smscam_ ticket
smscam_bot_code_accuracy: % of cited code aligned with registry
smscam_bot_expiry_cited: % of flash with cited end time
smscam_bot_stop_route_rate: % of STOP routed to PREF #382
smscam_bot_registry_stale: obsolete registry answers target 0
Target: code_accuracy above 98% and registry_stale at zero.
SMSCAMBOT anti-patterns
Five common mistakes in an SMS bot campaign.
Invented code: CODE-GROUNDED registry only
Ignoring expiration: EXPIRY-GROUNDED flash mandatory
Auto-unsub STOP: STOP-REROUTE #382 never a bot promise
Desktop link: LINK-GROUNDED mobile tested
Duplicate #924: #926 SMS flash expiration STOP only
SMSCAMBOT with Qstomy
Qstomy on Shopify: SMSCAM-MAP sync #925, Postscript Klaviyo SMS register, CODE EXPIRY STOP templates, ops escalate handoff agent, KPI smscam_bot dashboard.
Scenario: DTC beauty, SMS 15k. Pre-send sync D-1, bot tier 1 offer. smscam_bot_deflect +48%, smscam_ tickets -39% in 4 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
SMSCAMBOT Checklist (8 steps)
Sync SMSCAM-MAP #925: offer code flash link STOP window
Policy SMSCAMBOT-SUP: 6 rules REGISTRY-GATE EXPIRY-GROUNDED
8 intents bot_smscam_*: flow SCB-1 to SCB-8
4 templates TPL-SMSCAM-*: CODE EXPIRY LINK STOP
campaign_detect: active pre-send flash window
timezone_ref: customer end timezone time
Red team SMS: code fail expiry stop link test
KPI Dashboard: smscam_bot_* section 9 + delta smscam_
FAQ
What's the difference with #925?
#925 = ops agents peak macros staffing. #926 =bot tier 1 offer code expiration widget.
What's the difference with #924?
#924 = newsletter email bot. #926 = SMS flash expiration STOP bot.
What's the difference with #130?
#130 = transactional SMS lifecycle. #926 = post-send flash promo.
Can the bot handle STOP opt-out?
No. STOP-REROUTE #382. Never promise auto-unsub bot.
Going further
This week: sync SMSCAM-MAP #925, campaign_detect flash, templates EXPIRY STOP, measure smscam_bot_deflect.
Enzo
July 1, 2026
