Handling Delayed AI Triggers: Creating a Fallback Workflow for GHL

Hey everyone,

I’ve been running into an issue with my GHL setup where the tag that triggers my AI is sometimes added too late. Specifically, I noticed that while the workflow was triggered, it actually started running about four minutes after the tag was applied—probably because GHL was experiencing a heavy load or some other technical hiccup.

This delay can lead to unresponded messages when the AI should be jumping in right away. Has anyone here implemented a fallback workflow or found a best practice that ensures the AI can still catch and respond to messages if the main trigger is delayed? Any ideas or tips would be greatly appreciated!

Thanks in advance for your help!

Martin

4 comments