Miss Blue : built-in waits and reply-aware follow-ups

A wait should not erase the conversation

The automation guide describes durable workflow state and timers. A sequence can wait between messages and branch on whether a reply arrived. Stop-on-reply is enabled by default in the documented editor.

Those behaviors address a practical failure: a customer answers, but an old follow-up still sends. Review them on the exact published workflow before activating it.

Check every gate, not just the trigger

The documented business-hours switch checks day, time and timezone for each message. An overnight reply can still affect a later reply condition. That is more useful than applying office hours only at initial enrollment.

List and tag triggers can start outbound-first flows when approved. Keyword matching is exact full-message matching, so write and test the intended keyword rather than assuming a fuzzy phrase search.

Keep the live test small

A sandbox can test the shape of a workflow without establishing delivery on a live number. Validate the dedicated line, opt-in source, business-hours settings and a real reply using owned contacts.

Miss Blue’s public guides distinguish new-contact controls from healthy-use recommendations. Build capacity planning around the actual account rules, not the word unlimited in a billing description.

The decision in one sentence

Evaluate Miss Blue against the trigger, stop rule and recovery responsibilities described above.