Troubleshooting

Check in this order: (1) Is the bot paused? In the settings on the Verbindung tab, the Bot antwortet switch (bot replies) must be on. While paused, the bot records everything but does not reply. (2) Is the bot live at all? The wizard under connection shows in the Live step whether number, office name and privacy link are set. (3) Is the contact blocked or opted out? Both are visible on the contact card in the inbox; blocked and opted-out contacts receive no replies. (4) Is a human currently in charge? If your team took over the conversation, the bot stays silent until it is handed back with Zurück an Bot.

If an unusually high number of messages arrives from one contact in a short time (more than 15 per minute), the message storm protection kicks in: the bot records silently and pauses its replies until things calm down. STOP is still honored immediately. Details under Rules and privacy.

In the current version the bot is a menu bot: it guides through buttons, selection lists and the quick digits 1 to 9, not through free conversation. With the word "Menü" the guest returns to the main menu at any time. If the bot fails to understand an input twice, it offers the solution itself: "Das habe ich nicht ganz verstanden. Bitte nutzen Sie die Auswahl, oder schreiben Sie „Menü“." (I did not quite understand that. Please use the selection, or write "Menü".) followed by the buttons Ja, verbinden (yes, connect me, a handover to a human) and Zurück zum Menü (back to the menu). Free-form questions will only be answered by the upcoming AI assistant (coming soon).

WhatsApp's reason is shown in plain text on the message status in the inbox. The most common one is "Meta 131047: Re-engagement message": the 24-hour window was already closed and WhatsApp no longer allows a free-form message. In that case: wait until the contact writes again on their own, then replying is possible again. Other reasons (such as temporary Meta disruptions) are also shown in plain text on the message.

The lock notice below the input field states the reason verbatim: the contact is blocked (lift the block in the contact card), the contact opted out (they must reach out again themselves) or the 24-hour window is closed (replying only works once the contact writes). All three texts are documented on the inbox page.

The publish gate blocks as long as the check chip shows errors. Click the chip and work through the list. Typical causes: dead ends (a step without an exit), connections to deleted steps, cards unreachable from the start, missing mandatory building blocks (greeting, privacy notice, opt-out) and missing required fields before the appointment booking: the booking action needs details such as name and email captured earlier in the path. Unknown, free-typed placeholders are errors too. Details: Flows and Flow Studio.

That is the honest start: installation only activates flows whose data source actually exists. The viewing booking waits for the configured booking tool; property info and brochure delivery wait for your first listing. Once the source exists, you enable the flow in the flow list with one click.

Most likely someone clicked In FAQ-Flow übernehmen (transfer into FAQ flow) in Knowledge & FAQ. That click rebuilds the FAQ flow from the approved entries and overwrites studio changes; the confirmation dialog points this out. Therefore always maintain FAQ content through Knowledge & FAQ, not directly in the studio.

The bot automatically stores received files in the file storage under Tools, folder "WhatsApp-Bot, Empfangene Dateien" (received files). Two limits exist: files above 25 MB are not taken over, and when the workspace storage is full the filing fails. In both cases the message remains in the conversation history with an honest note, so nothing is lost silently. If your quota is full, free up space in the file storage or upgrade your plan.

WhatsApp rates the quality of your number; on a downgrade the workspace owner is notified immediately. You can see the current state in the settings on the Verbindung tab; the rating keeps itself up to date. A downgrade signals that recipients perceive messages as unwanted. The bot itself follows the protective rules (STOP, 24-hour window) automatically; make sure personal team replies stay wanted and relevant as well.

The connection to Meta is interrupted; the bot can neither send nor receive. Check the status card under connection. If waiting does not help, disconnect the number (Nummer trennen, the conversation history is kept) and reconnect it through the Meta wizard.

That is the connection watchdog: if a live number receives no events for 24 to 48 hours, the platform notifies you once, before customers write into the void. A disrupted or disconnected connection is often the cause. Check the status under connection and reconnect the number if necessary. If there is simply no traffic (no incoming messages), the warning is harmless.