From 8eff849e837c7aa44042a07028254d28496503fe Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Mar 2026 22:48:29 +0000 Subject: [PATCH] story-kit: create 322_story_whatsapp_24_hour_messaging_window_and_template_support --- ...r_messaging_window_and_template_support.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .story_kit/work/1_backlog/322_story_whatsapp_24_hour_messaging_window_and_template_support.md diff --git a/.story_kit/work/1_backlog/322_story_whatsapp_24_hour_messaging_window_and_template_support.md b/.story_kit/work/1_backlog/322_story_whatsapp_24_hour_messaging_window_and_template_support.md new file mode 100644 index 0000000..9c3f4c3 --- /dev/null +++ b/.story_kit/work/1_backlog/322_story_whatsapp_24_hour_messaging_window_and_template_support.md @@ -0,0 +1,21 @@ +--- +name: "WhatsApp 24-hour messaging window and template support" +--- + +# Story 322: WhatsApp 24-hour messaging window and template support + +## User Story + +As a project owner, I want the bot to handle WhatsApp's 24-hour messaging window correctly, so that proactive notifications (build failures, merge completions) work within Meta's rules. + +## Acceptance Criteria + +- [ ] Bot tracks the 24-hour window per user — free-form replies only within 24h of last user message +- [ ] After 24h, bot uses approved message templates for notifications +- [ ] At least one message template registered with Meta for pipeline notifications (e.g. 'Story {name} has moved to {stage}') +- [ ] Bot gracefully handles 'outside messaging window' errors from the API without crashing +- [ ] Template registration documented in setup guide + +## Out of Scope + +- TBD