All Collections
Flow basic concepts
Flow basic concepts
Updated over a week ago


You can think of them as mediums or channels and each of them must be connected to 2Chat to be usable.


A trigger is what will make the flow start executing its internal steps. You can think of them as external stimuli that will make the flow go off.

The most common trigger is the Message Received. You can use it to create bots that reply automatically.

Execution window

This will control the amount of time a conversation context should be kept before considering it expired.

For example, let's say a customer writes you a text saying "Hey" and you reply with an automated greeting flow to introduce them to your services or products. If you use an execution window that is 1 minute, every minute that passes will restart the conversation and for every new message the customer writes, you will be greeting them as it was the first time you see them.

The window should be conversation-specific. In the example above with a greeting flow, a 24-hour window sounds plausible in most cases. Greeting the user each new day is something that wouldn't be considered too much in most cases.

Another practical example is with customers writing outside normal business hours. When they do that, you may want to message them with information about your business hours but only one time instead of for every message they write. In those cases, an 8 hours window should be reasonable.

Did this answer your question?