Waiting for Kate

Waiting for your team

The lead is replying to a team member, so the reply is yours, not Kate's.

Currently active

Conversations GHL's own automation currently marks Kate as handling (the ai-active tag) — not what's flagged, just who's on it right now.

Recent bookings

The positive counterpart to quality flags — leads who reached booking-confirmed, and whether Kate was ever part of that conversation.

Monitor coverage

What the monitor actually captured — a quiet client and a broken feed should never look the same.

Quality flags

Deterministic checks on Kate's replies, with a fix suggestion per flag. Click a flagged message for the full detail — confirm/dismiss there, with a reason, feeds back into which rules to trust and which to fix.

Recent incidents

Recent Kate replies

"Contacted" onward are CRM stages, not proof the lead replied — see Replied for that. Hover any column header for how it's worked out.
Fleet-wide. Correlation, not proof — a flag can be a symptom of a conversation already going nowhere, not the cause.

Alerts

… While paused, incidents are still detected and shown here — only Slack messages are held.

Add client

Configured clients