AiSensy: Start WhatsApp support with a fixed menu or generated answers?
Test the initial inbound message, expiry and a fresh inbound message separately.
AiSensy’s Flow Builder describes static paths and a human-support button. Its 2025 notice defines a 24-hour support window after a customer message, reset by another inbound message. For routine inbound questions about help pages or opening hours, start with a menu. Add controlled retrieval for varied phrasing if needed, but keep send eligibility with explicit rules or people, not the model.
Test three clock states
Simulate three events on paper, without real numbers or channels. A customer writes Monday at 10:00; Tuesday at 09:50 is still inside. Without a new message, Tuesday at 10:10 is outside. If the customer writes again Tuesday at 09:55, 10:10 is only 15 minutes later and should not be rejected on the original clock. Record latest inbound time, route and human-review flag. An unmatched menu choice goes to a person; a menu click is not marketing permission.

Original timeline, not the product interface. Tuesday at 10:10 falls in different states depending on inbound history.
Separate permission and cost
The 2025 billing notice distinguishes delivered templates from service replies and eligible utility templates inside the window. The window does not make your subscription or all templates free. Check actual category, region and plan before budgeting. If any of three cases has the wrong state, fix the rules first. Add a model only if boundaries pass and menus leave major questions uncovered. No messages or payments are triggered here.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:news.aisensy.com