HighLevel Conversation AI Stopped Replying? How to Find Out Why and Fix It

Is the bot off for everyone, or just for one contact?

Start here, because the fix is different. Send a test message from a new contact on the same channel. If the bot answers the new contact but not the lead you care about, the problem is that lead’s bot status. If it answers nobody, look at the bot itself.

For the bot itself, check three things in AI Agents, Conversation AI, then the bot’s settings (Conversation AI explained):

• The mode. Off means no replies. Suggestive means it drafts replies for your team to send by hand. Only Auto-Pilot replies on its own.
• The channels. The bot only works on channels assigned to it, such as SMS, Facebook, Instagram or WhatsApp. A bot that works on SMS can be silent on Instagram because Instagram is not switched on for it.
• Primary or not. HighLevel says non-primary agents usually only respond when a workflow calls them. If your bot is non-primary and no workflow calls it, don’t expect it to answer general inbound messages.

How do I see exactly why it stopped for this contact?

Open the conversation, then click Audit logs at the bottom of the Contact Details panel. HighLevel says this shows the recorded changes to the bot’s status, when they happened, what triggered them and who started them. For a view across the whole sub-account, go to Settings, Audit Logs and filter the module to Conversation AI Activity (Bot Status for Individual Contacts).

I always do this before changing any setting. Guessing at causes wastes time when the log already says which one it was.

Why does the bot go to sleep after my team replies?

HighLevel lists these as the reasons the bot can become inactive for a contact (Bot Status for Individual Contacts):

• The contact replied with an opt-out keyword such as STOP.
• The bot reached its maximum message limit.
• Someone on your team sent a manual message, and the bot’s sleep setting for manual messages is on.
• A workflow sent a message or changed the bot’s status.
• An advanced setting sends the bot to sleep during a human handover.

The manual message one catches a lot of teams. Someone jumps in to answer a question, the bot steps back as designed, and nobody wakes it up again. If you want the bot to keep going after a person replies, turn that sleep setting off. If you want the pause, plan who wakes it up and when. The contact-level status menu lets you set a reactivation time in minutes, hours or days.

Workflows are the other quiet cause. A workflow that sends a text or runs Update Conversation AI Bot and Status can change the bot’s status for that contact. Check the contact’s workflow history if the audit log points to a workflow.

Did the bot hit its message limit?

Each bot has a Maximum messages a Bot can send in a Conversation setting, from 1 to 100, and the default for new bots is 100 (Advanced Settings). Only the bot’s own messages count. Once it sends its last allowed message it goes dormant in that thread, and HighLevel says it does not send a goodbye message when that happens (Auto-Pilot Mode).

If you lowered the limit to keep costs down, long qualifying chats will run into it. Either raise it, or tell the bot in its prompt to keep answers short so it gets to the point sooner. HighLevel notes that a higher limit can mean more Conversation AI usage.

Why does it end the conversation when the lead still needs help?

HighLevel’s docs don’t describe a status with that exact wording, so I look at the bot’s own actions that can end or pause a chat. In Bot Goals, the actions list can include Human Handover and Stop Bot (Bot Goals Overview). If the condition you wrote for Stop Bot is broad, such as “the lead has their answer”, the bot will stop on plenty of chats that are not finished. Tighten the condition and give it clear example phrases, then test it in the Bot Goals test panel.

Auto Follow-Up has its own rules. HighLevel says it skips or cancels follow-ups when the contact opts out, shows no interest, is disqualified, or closes the chat softly with something like “thanks for the chat” (Auto Follow-Up). A polite lead who says thanks may get no follow-up even though they never booked. If that matters, add a workflow follow-up for contacts who have not booked, but don’t trigger a second follow-up through a workflow while Auto Follow-Up is on; HighLevel warns that breaks its logic.

How do I wake the bot back up?

Three ways, all from HighLevel’s own docs (Auto-Pilot Mode, Bot Status for Individual Contacts):

1. Mark the conversation as Read. This wakes a sleeping bot and resets its message counter.
2. Set the status to Active from the bot icon in the message composer.
3. Use a workflow. The Update Conversation AI Bot and Status action can wake the bot on rules you choose, for example only when the contact replies with a certain keyword.

Contacts who replied STOP are different. Don’t wake the bot for them to send marketing again.

What I would check before switching a bot to Auto-Pilot

• Send yourself a test on every channel the bot is assigned to.
• Write down which sleep settings are on, and who on the team is responsible for waking the bot after they reply.
• Read the Stop Bot and Human Handover conditions out loud. If a normal “thanks” would match them, they are too broad.
• Check the message limit against the longest real conversation you expect.