We’ve recently begun venturing into the bot-space and are wondering if HubSpot is working on an additional Bot action for delaying messages. I know that we can do message delays in the Settings tab, but that feels very restricting. It would be awesome if we could add custom delays between each message on a case-by-case basis, just like what we can do within the Workflows tool.
I agree. It’d be nice if HubSpot can implement this feature.
Pllllllleeeeeeease!
Same - I want to be able to ask visitors to take an action, pause for 15 seconds, then send another message.
any updates here? My chat bot is shouting out several messages at the same time. this is not what I want. a delay would be great.
thx, angela.
This seems like a quick win to improve chatbot builder functionality. It is currently very minimal what you can do without the option to add a delay. PLease update on where this is at?
agreed! please please add
We need the ability to chose the amount of time to delay in between messages. The user exerience is terrible otherwise. The reader can not finish the first message before they are bombarded with any of the following messages. Seems like a no brainer if your intention is to offer a tenable chatbot solution to your clients.
With more than a year of people asking for this simple functionality, why has it not been addressed?
It would be very useful if you add this functionality.
This is a critical feature. Please add!
I completely agree!
This is definitely a needed feature!
We’d need that to here, please 
Yes please!!! I echo everyone. This is a simple and needed feature.
Yes, please. 
Yes please, it needs addressing!
Yes please. We need this!
We need a delay. Chatbots are supposed to fit with conversation flow, as close to human as possible. We need to not hammer them with thenext message bubble shot out of a cannon right after the previous sentence/answer.
We need this so bad!! HubSpots chat bots are a great feature, but they are abysmal for our corporate website while they are urgently dropping all the messages at once. We may have to cut them altogether until this functionality is solved.