When a contact taps a button or picks a list option in a WhatsApp message, your EveryCatch workflow now reliably continues down the branch for the option they chose. Booking, confirmation and service-selection flows run the way you set them up, so you stop losing contacts to the Timeout branch after they have already given you an answer.
When your contact makes a choice, your workflow now consistently follows it.
What’s fixed
Every tap routes to the branch it belongs to
- Personalised options now route correctly: Buttons and list options that include custom values, such as a contact’s appointment time, are now recognised when tapped. Previously, some of these taps were not matched and the contact fell into the Timeout branch instead of the path they picked.
- Fixed and personalised labels behave the same: Whatever text your option shows, the tap now continues down that option’s branch.
Long labels are shortened instead of failing
- Messages send every time: WhatsApp allows up to 20 characters on a button label and 24 on a list option. When a custom value pushes a label past that limit, it is now automatically shortened and ends with "…", rather than the message failing to send.
- Routing still works: A shortened option still sends the contact down the correct branch when tapped.
Where this helps you
- Appointment confirmations: A contact taps "Confirm 3:30 PM" and goes straight to your confirmation path, instead of a follow-up that chases a reply they already gave.
- Slot booking: Options built from your calendar’s available times route each contact to the slot they picked.
- Service menus: List options filled with long service or location names now send successfully, instead of quietly failing.
How to use it
You do not need to change anything. Your existing EveryCatch workflows get this fix automatically, with no need to re-save or rebuild them.
Why this matters for your business
Interactive buttons and lists are one of the fastest ways to move a contact from a question to a decision on WhatsApp, but they only help when the workflow acts on the answer. When a tap is missed, a customer who is ready to book is treated as unresponsive, and that is often the moment you lose them.
- Convert more bookings and confirmations by sending every contact down the path they chose
- Personalise with confidence, knowing custom values in button and list labels do not break routing
- Stop silent send failures caused by labels that run too long
- Keep your follow-ups relevant, so contacts who already answered are not chased again
Your branching WhatsApp workflows in EveryCatch are already running with this fix. You can personalise those buttons and list options as much as you need.
