Groups Monitoring in Bow Chat

What Groups Monitoring does

Groups Monitoring is the home for operational controls around WhatsApp Web groups. Inactive groups is one module. SLA settings and SLA reports are separate modules in the same product; SLA is not the name of the complete panel.

An inactive-group rule finds groups where Bow Chat has received no message for the configured period. The clock uses the most recent incoming message. A staff reply or an earlier nudge does not make a group look active. Groups with no received message use their first-seen time.

Review and delivery lifecycle

1. The configured rule refreshes WhatsApp Web group activity and creates a review queue.
2. An authorized person reviews the exact groups and may edit the exact nudge text. Nothing is sent merely because a group became inactive.
3. Approve and queue hands the reviewed selection to a background worker.
4. Immediately before sending, Bow Chat checks that exact conversation again. A newer received message cancels the nudge.
5. A confirmed delivery records the Bow Chat message and starts the configured cooldown. A definite failure returns to manual review. An uncertain transport result is marked Check delivery and is never retried automatically, which avoids duplicate nudges.

The queue is bounded, claimed atomically, idempotent, and audited. Group discovery and incoming-message timestamps are calculated on the server; the browser receives only the small review list it needs, not group transcripts or an unbounded conversation directory.

WhatsApp groups only

The current module applies only to WhatsApp Web group conversations in the selected inbox. It does not apply to WhatsApp Cloud API, email, API, or other inbox types. The stable identity combines the Bow Chat account, inbox, and WhatsApp group identifier so an old duplicate conversation does not become a second monitorable group.

Optional Boni One CRM connection

When Boni One CRM is enabled and linked for the tenant, the existing CRM sync can attach the WhatsApp group reference to the CRM contact. The reference may include the Bow Chat contact id, conversation id, group identifier and name, plus a clickable link that opens the exact group conversation in Bow Chat. Bow Chat access controls still apply after the click.

Message bodies stay in Bow Chat and are not copied into CRM. Automatic opportunity creation for WhatsApp groups is a separate tenant option and is off by default, so operational groups do not flood a sales pipeline.

For setup and day-to-day operation, use Configure Groups Monitoring in Panel Bow Chat.