Skip to main content
For automatic GHL chat, Assistable attempts to add AI Replying to the contact before queueing response generation. The tag has a space; it is not ai_replying. The run attempts to remove the tag when it finishes or is cleaned up, including some skipped and failed paths. These tag updates depend on GHL accepting the request, so the indicator can be delayed or remain after a failure.

​
What it tells you

Neither the presence nor absence of this tag proves delivery. The strongest check is the actual outgoing message and its status in the customer conversation.

​
Build an escalation workflow

If you monitor this tag in GHL, allow for the assistant’s Wait time, normal processing, and provider delay. After the waiting period, check the latest message and error state before notifying your team. Prefer a review or notification step before an automatic fallback message. If the AI reply arrives late, an unconditional fallback can send the customer two answers.

​
When asking for help

Include the contact, conversation, approximate time, matching active tag, and whether the customer received a reply. Say whether the indicator remained or disappeared; do not use that observation as the only evidence of the failure. This indicator applies to the GHL chat path. Direct conversations and voice calls do not use it as the same reply marker. See GHL chat setup and pausing a contact.