E-commerce
July 1, 2026
UK client at 11 p.m. requests an agent. The bot quotes Paris hours. The client opens a suphours_ ticket.
An e-commerce localized hours AI chatbot detects market country channel, quotes region timezone hours, adapts urgency promise and routes handoff if live, distinct from the general hours bot (#402).
This guide #922 covers intents bot_hourreg_*, flow HOURREGBOT HRB-1 to HRB-8 and guardrails HOURS-REGISTRY-GATE. Bot pair of the playbook SUPHOURS (#921). Usecase: hours by country channel urgency widget-side.
Summary
Why localize schedules on the bot side?
Multi-market stores: chat, email, and phone hours differ by region. Without country detection, the bot cites the wrong timezone. HOURS-REGISTRY-GATE reduces support tickets during off-hours #921.
What the tier 1 regional hours bot solves
Region detection: market country session
Localized hours: hours_copy by region
Distinct channel: chat vs email vs phone
Adapted urgency: route P1 closed vs async
Timezone conversion: client timezone map
DTC retail example
DTC FR UK US, region gate widget. hourreg_bot_deflect +43%, hourreg_bot_wrong_region 0 in 5 weeks.
HOURREGBOT #922 vs SUPHOURS #921, HOURS-BOT #402, NOHUMAN #918 and Markets
Seven bot hourly contents, seven distinct roles.
Quick matrix
#922 HOURREGBOT: localized hours bot by country for tier 1 emergency channel
SUPHOURS #921: agents handling tickets suphours SH-4
HOURS-BOT #402: general holiday hours distinct regional availability
NOHUMAN #918: unavailable at moment T distinct regional planning
Markets bot: Markets ops config distinct client copy hours
MULTI #16: multilingual strategy distinct time zone
SLA #101: response time distinct opening slots
#402 = general hours. #922 = localized emergency channel country.
Which bot_hourreg_* intents should be configured?
Eight regional business hours intents mapped SUPHOURS-MAP #921.
Eight bot_hourreg intents
bot_hourreg_region_detect: detect country market session
bot_hourreg_open_now: open_status region channel
bot_hourreg_schedule_answer: schedule_copy region map
bot_hourreg_timezone_convert: customer timezone conversion
bot_hourreg_channel_answer: hours_chat email phone map
bot_hourreg_urgency_route: P1 closed vs promise async
bot_hourreg_holiday_answer: exception holiday region
bot_hourreg_feed_loop: consume LOG #921 hours_copy
Each response logs region_detected intent suphours_* deflect_or_handoff.
How do I consume SUPHOURS-MAP #921?
The bot reads SUPHOURS-MAP #921 + bot fields by region: hours_fr hours_uk hours_us, channel_hours_copy, timezone_ref, urgency_rules, promise_closed_sla, holiday_calendar_region, agent_handoff_url.
Bot Region Hours Guardrails
HOURS-REGISTRY-GATE: canal registry region hours only
REGION-DETECT-BOT: market country before hours copy
TIMEZONE-GROUNDED-BOT: map timezone conversion
CHANNEL-GROUNDED-BOT: distinct chat email phone
URGENCY-ROUTE-BOT: P1 dispute route if region rule applies
NOHUMAN-REROUTE-BOT: saturation → #918
AGENT-HANDOFF-BOT: display_wrong → agent #921
SUPHOURS-FEED-LOOP-BOT: LOG #921 enriches hours_copy
HOURREGBOT-SUP policy in six rules
Six localized hourly rules responsible on the widget side.
HOURS-REGISTRY-GATE: tier 1 from register #921 region
REGION-DETECT-BOT: detection before schedule answer
CHANNEL-GROUNDED-BOT: explicit channel if requested
URGENCY-ROUTE-BOT: urgency adapted to regional hours
TIMEZONE-GROUNDED-BOT: timezone always cited internationally
SUPHOURS-FEED-LOOP-BOT: LOG #921 review widget within 48 hours
HRB-1 to HRB-8 HOURREGBOT Flow
Eight-step flow: incoming question detect region classify answer urgency route log handoff.
HRB-1 Ingest: message open closed hours timezone
HRB-2 Region detect: REGION-DETECT country market IP session
HRB-3 Classify: suphours_* vs nohuman #918 vs hours #402
HRB-4 Registry gate: HOURS-REGISTRY-GATE region lookup
HRB-5 Tier 1 answer: open schedule timezone channel
HRB-6 Urgency route: P1 promise_closed handoff live
HRB-7 Feed loop: LOG #921 adjusts hours_copy region
HRB-8 Log: deflect wrong_region urgency_route
Example TPL-HOURREG-OPEN
"Support {{region}} : {{open_status}}. Timezone : {{timezone_ref}}. Local time : {{conversion}}. Chat channel : {{channel_hours}}."
TPL-HOURREG and touchpoints templates
Four short regional hours embed templates.
TPL-HOURREG-OPEN
[open_status region map.] [timezone_ref.] REGION-DETECT.
TPL-HOURREG-SCHEDULE
[schedule_copy region map.] [holiday exception.] HOURS-REGISTRY.
TPL-HOURREG-CHANNEL
[channel_hours_copy map.] Chat email phone. CHANNEL-GROUNDED.
TPL-HOURREG-URGENCY
[urgency_copy map.] [promise_closed_sla.] URGENCY-ROUTE.
Touchpoints
"Open?": region_detect + open_now
US Client timezone: timezone_convert
"Email or chat?": channel_answer
LOG SUPHOURS #921: feed_loop hours_copy
Edge cases: unknown market, closed P1 emergency, regional BFCM
Five cases out of the standard flow.
Unmapped region: fallback main market + handoff #921
P1 dispute after hours: URGENCY-ROUTE priority ticket
BFCM extended hours US only: holiday_calendar_region
General holiday question: #402 HOURS-BOT
Ticket suphours_ despite bot: feed_loop review region gaps
Essential hourreg_bot KPIs
Five steering metrics for HOURREGBOT and correlation #921.
hourreg_bot_deflect: working hours resolved without a suphours_ ticket
hourreg_bot_region_accuracy: % correct region detected
hourreg_bot_wrong_region: incorrect target zone 0
hourreg_bot_channel_cited: % explicit channel if requested
hourreg_bot_urgency_route_rate: % urgency correctly routed
Target: wrong_region at zero and region_accuracy above 95%.
Anti-patterns HOURREGBOT
Five common regional bot schedule errors.
Main market hours for all: REGION-DETECT mandatory
Forgetting customer timezone: TIMEZONE-GROUNDED international
Confusing channels: CHANNEL-GROUNDED chat email phone
Ignoring P1 urgency: URGENCY-ROUTE closed
Duplicating #402: #922 region channel urgency only
HOURREGBOT with Qstomy
Qstomy on Shopify: SUPHOURS-MAP sync #921 by market, region detect Markets, templates open channel urgency, KPI hourreg_bot dashboard.
Scenario: DTC FR UK US, 9 tickets/month suphours. Region gate tier 1. hourreg_bot_deflect +43%, suphours_ tickets -38% in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist HOURREGBOT (8 steps)
Sync SUPHOURS-MAP #921: hours by region emergency channel
Policy HOURREGBOT-SUP: 6 rules REGION-GATE TIMEZONE
8 intents bot_hourreg_*: flow HRB-1 to HRB-8
4 templates TPL-HOURREG-*: OPEN SCHEDULE CHANNEL URGENCY
region_detect: Markets session country IP
urgency_rules: P1 closed vs promise async
Red team region: wrong timezone channel test
Dashboard KPI: hourreg_bot_* section 9 + delta suphours_
FAQ
Difference #921?
#921 = agents tickets display_wrong. #922 = bot tier 1 region emergency channel.
Difference #402?
#402 = general holiday hours. #922 = country localization emergency channel.
Difference #918?
#918 = unavailable saturation. #922 = regional structural schedule planning.
P1 Emergency off-hours?
URGENCY-ROUTE priority ticket or callback according to region registry.
Going further
Support delays (#101)
This week: sync SUPHOURS-MAP #921 by market, region detect, templates channel urgency, measure hourreg_bot_deflect.
Enzo
July 1, 2026
