Systems Monitor Explained: How to Audit Queued Messages, Replies, and Suppressed Sends in KaiCalls

How KaiCalls Systems Monitor works — a read-only control room that surfaces queued work, unread replies, suppressed sends, and lead timelines, so nothing silently falls through the cracks.

July 7, 20266 min readBy Connor Gallic

Systems Monitor is a read-only screen in the KaiCalls dashboard that shows you everything queued, stuck, suppressed, or waiting on a person, across your leads, texts, emails, and calls, in one place. Open Dashboard > Activity > Systems Monitor, pick a time window, and the top cards tell you whether anything is stalled before a customer ever notices.

Automated systems fail quietly. A text that never sent, a reply that needed a human and got buried, a lead the system stopped messaging for a reason nobody double-checked — none of that throws an error a person sees. It just sits there until a customer calls annoyed that nobody followed up.

Systems Monitor exists to close that gap. This guide covers what the screen actually shows, what it can't do, how to run a check, and where it fits next to the rest of KaiCalls.


Table of Contents

  1. What Systems Monitor actually is
  2. What it surfaces
  3. What it can't do
  4. How to run a check, step by step
  5. Reading the statuses
  6. What it costs
  7. FAQ

What Systems Monitor actually is

Open Dashboard > Activity > Systems Monitor and choose a window: 24 hours, 72 hours, 7 days, or 30 days. The top cards summarize active conversations, unread inbound messages, queued SMS, pending email approvals, stale queue items, transcript gaps, and failed or suppressed communications for that window.

It's built for owners and operators who want a single place to confirm nothing is stuck — that queued messages are actually going out, that replies needing a human aren't piling up unread, and that anything Kai stopped or suppressed was supposed to stop. Instead of trusting that the automation is working, you can look.

What it surfaces

Systems Monitor organizes what it finds into four operational views:

  • Work Queue — pending, stale, or failed operational work, each with its due time, current state, and a preview of what it is.
  • Needs Intake — replies or transcript gaps that need a person to review the lead before anything else happens.
  • No Longer Messaging — leads that were stopped, suppressed, canceled, or handed off, so you can see who dropped out of contact and why.
  • Recent Events — SMS, email, SDR, call, and system activity across the window you selected, in one feed.

From any row in these views you can open a lead timeline — a side panel with the lead's source, score, latest call summary when available, and recent events, each linked back to the underlying call or conversation.

What it can't do

Systems Monitor is explicitly read-only. It doesn't take action on anything it shows you — it's built for auditing and triage before you jump into the related lead, call, or conversation to actually fix something.

  • It can't resend a failed message. Seeing a failed send here just tells you it failed; you still have to open the lead, call, or conversation to act.
  • It can't change automation. It won't restart a stalled workflow, cancel a suppression, or re-queue anything on its own.
  • It doesn't explain intent, only state. A lead in "No Longer Messaging" tells you it was stopped, suppressed, canceled, or handed off — you still open its timeline to see which one and when.

Think of it as the instrument panel, not the controls. It tells you where to look; the fix happens on the lead, call, or conversation page it points you to.

How to run a check, step by step

  1. Go to Dashboard > Activity > Systems Monitor.
  2. Pick a time window that matches what you're checking — start with 24 hours for a quick daily sanity check.
  3. Scan the top cards for anything non-zero in stale queue items, pending email approvals, or failed or suppressed communications.
  4. Switch to the matching view below (Work Queue, Needs Intake, No Longer Messaging, or Recent Events) to see the individual rows behind a count.
  5. Open a lead timeline on any row that needs follow-up, then jump to the related call or conversation to act.

Reading the statuses

  • Pending / queued — work that's scheduled and waiting to run. Normal in small numbers.
  • Stale — a queued item that has waited longer than expected. Worth a look; something may be blocking it.
  • Failed — the send did not go through. Open the row to see why and decide whether to handle the lead manually.
  • Suppressed — a send was intentionally held back, for example because the lead opted out. This is the system protecting you, not an error.
  • Transcript gap — a call or conversation is missing expected content and may need a person to review the lead.

A high count on its own isn't a problem — a 30-day view naturally shows more than a 24-hour one. Narrow the window first, then drill into the view to see whether the items are recent or backlog.

What it costs

Systems Monitor is included on every KaiCalls plan — Solo starts at $69/mo, Pro at $199/mo, both with a generous answered-call allowance and no per-minute overage. There's no extra fee to open it or run a check; it's a view into activity you're already generating, not a metered feature.

FAQ

Can I resend a failed message from Systems Monitor? No. Systems Monitor is read-only. Open the lead, call, or conversation behind the failed row to take action.

Why is a lead showing up in "No Longer Messaging"? It was stopped, suppressed, canceled, or handed off. Open its lead timeline to see which one applies and when it happened.

A count looks unusually high — is something broken? Not necessarily. Narrow the time window first — a 30-day view naturally shows more activity than 24 hours. Then drill into the specific view to see whether the items are recent or older backlog.

What's the difference between "stale" and "failed"? Stale means the item is still queued but has waited longer than expected — something may be blocking it. Failed means the send already tried and did not go through. Both are worth opening to see why.

Does Systems Monitor change how Kai handles calls or messages? No. It doesn't send messages or change automation — it only surfaces what already happened or is queued so you can decide what to do next.


See it on your own account. Open Dashboard > Activity > Systems Monitor and run a 24-hour check, or call the KaiCalls demo line at (417) 386-2898 to talk to Kai first, or visit kaicalls.com.

Topics:

kaicalls systems monitoraudit ai receptionist queuesuppressed sms sendsfailed communications dashboardlead timeline auditai answering service reliability

Ready to Try AI Call Answering?

Start your 7-day free trial.

Start Free Trial
    Systems Monitor Explained: How to Audit Queued Messages, Replies, and Suppressed Sends in KaiCalls | KaiCalls Blog