InstaBrain iQ

Read-only command center for the iQ payment-failure pipeline: what it recovered, what it saved, what it sent to agents and clients, what it held for a human, and how each policy turned out.

Modes: waiting for config
Times in your zone

Latest run decisions

what the last run did with what it read

Channel reporting

ChannelCurrent modeShadow only, not sentSentDeliveredOpenedClickedReplied
More columns to the right

Cases

One row per policy, newest 200 by last update. Click a row for the full trail. The search box above filters by policy number, agent email or name, product, or client state.
PolicyProductLatest eventLadderAgentClientTouchesOutcomeUpdated
More columns to the right
waiting for data

Agent messages

Email and text to writing agents. Live rows are real sends; shadow rows are would-be sends that never reached a provider. Newest 200 of each.
CreatedPolicyModeChannelToStateSubjectTemplateDeliveryReplies
More columns to the right
waiting for data

Client messages

Email and text to insured clients. Contact details never appear here; the client is named by state only. Newest 200 of each.
CreatedPolicyModeChannelClientStateSubjectTemplateDeliveryReplies
More columns to the right
waiting for data

Replies

Inbound email and text, newest 200 by the time iQ saw them. Text senders show a hash prefix, never a number.
ReceivedChannelClassificationFromPolicyMessageHubSpot ticket
More columns to the right
waiting for data

Review queue

Cases iQ held for a human, newest 200.
ReasonPolicyEventNotice emailDirectory emailAgent nameCreatedResolved
More columns to the right
waiting for data

Outcomes

Labeler output, newest 200 by label time. Labels are advisory.
waiting for data
PolicyLabelEvidenceDays to outcomeLabeled
More columns to the right
waiting for data

Health

Pipeline status, the last 24 hours, and operator alerts (last 50). Shadow rows never feed health.

Last 24 hours

Counts come from the newest 200 rows per collection. A value shown as 200+ means the window is saturated.
waiting for data

Alerts

KindPolicyDetailByCreated
More columns to the right
waiting for data

Text opt-ins

waiting for data
Signed upAudienceNumber endingNameConsent version
More columns to the right
waiting for data

Runs

The last 20 ticks, newest first.
RunStartedReadEventsCasesImmediateBriefsHeldStaleSteps foldedDedupedSkippedErrorsModes
More columns to the right
waiting for data

Operator Guide

The users manual for the people who operate iQ: David, Frank, Meteena, Evan. Rendered from the manual in this repository at build time, behind the same sign-in.
Open the Operator Guide

What iQ is and is not, where the signals come from, the one-touch promise, how an alert flows, what every panel shows, the daily rhythm, the review queue reasons, shadow versus live and the GO procedure, pause and resume, how replies flow, what to do when something looks wrong, and the glossary.

  1. What iQ is, and what it is not
  2. The two audiences and the four channels
  3. Where the signals come from
  4. The one-touch-per-incident promise
  5. How an alert flows
  6. What an operator sees on the dashboard
  7. The daily rhythm
  8. The review queue: reasons and what to do
  9. Shadow mode versus live, and the GO procedure
  10. Pause and resume
  11. How replies flow
  12. When something looks wrong
  13. The review site
  14. Text opt-in
  15. Glossary