Hi ManyChat team and fellow builders,

I’d like to propose adding second-level filtering in Conditional blocks (and anywhere we compare timestamps). Right now the smallest time unit we can work with is one minute. For most automations that’s fine, but when you’re trying to build responsive, conversational experiences it becomes a real bottleneck.

Why seconds matter

1. Smart Delay + Conditional check loops

   A common pattern is:

   1. set a short Smart Delay,

   2. check the last user message time,

   3. decide whether to bundle new input or push a follow-up.

   With minute-only precision we’re forced to wait at least 60 seconds before the Condition can evaluate, which feels like an eternity in live chat.

2. Message grouping & spam prevention

   Many builders try to merge multiple quick user replies into a single logical block, or throttle highly active users so we don’t spam agents. We currently can’t distinguish someone who answered 3 s ago from someone who answered 58 s ago.

Proposed change

• Allow seconds as a valid unit anywhere we compare or add time (e.g., {{last_input}} is less than 15 seconds ago).

• If UI clutter is a concern, hide “seconds” behind an “Advanced” toggle—builders who need it will find it.

Impact

• Faster user experience → conversations feel natural, which improves retention and conversion.

• Cleaner flows → no more hacky work-arounds (multiple branches, external APIs, or unnecessary tags).

• Competitive edge → other bot platforms already allow sub-minute delays; adding this keeps ManyChat best-in-class.

If you’ve run into the same limitation—or have ideas on implementation—please add your voice below. The more real-world examples we share, the easier it’ll be for the product team to prioritize.

Thanks for considering, and happy building! 🚀