Daily Operations and Safe Controls

Guide intro

Once automation is live, day-to-day control matters as much as the initial setup. Teams need a simple way to pause risky conversations, resume normal behavior, and distinguish between a workflow issue and a connection issue.

This guide focuses on the client-facing daily controls that help businesses run automation more safely during normal operations.

Auto-reply control and active review

Auto reply should be treated as an operational switch, not a set-and-forget button. Keep a routine for checking live conversations, especially after content changes, billing changes, or connection resets.

If the workflow starts behaving unexpectedly, pause first and investigate before assuming the customer flow should continue as normal.

Pause and resume shortcuts: .0, .00, .1

These controls help staff take direct control when a conversation needs manual handling. Use them consistently so the team understands which chats are paused temporarily and which are stopped until later review.

In practice, .00 is commonly used to stop bot replies for a specific customer until resumed, and .1 can be used to resume where that shortcut behavior is enabled. Treat these as business controls, not as secret staff tricks.

Warnings

• Do not rely on shortcuts as a substitute for fixing a broken workflow.
• Make sure the team understands when a paused chat should be resumed and by whom.

Stop Engine versus Reset Login

Stop Engine affects active operation behavior, while Reset Login removes the current WhatsApp session and requires a fresh scan. The distinction matters because a team may need to pause replies without tearing down the connection, or reconnect the session without confusing that action with normal support escalation.

Related docs