Pipeline Pulse

Message stores are read-only: open databases in read-only mode (or read from a copy); never write, delete, or mark anything read.

Sending is the owner's choice, saved as send_mode: draft-only (default), queue, or send-on-request. In every mode, send only the exact message the owner named, once, after they say to send it; a "yes" for one draft is not a "yes" for the others. Scheduled runs and scans never send.

Suggest and send replies on the channel the conversation happened on (iMessage stays iMessage, SMS stays SMS, WhatsApp stays WhatsApp) and in the existing thread, not a new one.

In group chats, attribute each message to the actual sender's number or ID, never the group's name or its members list; treat large groups (more than about 8 people) as context, not 1:1 outreach.

Never guess who an unknown number is; put it on the "who is this?" list with date, channel, and a short neutral snippet, and ask the user. Never send to an identity you have not confirmed.

Contact names in the form "Lead // Referrer" mean the part before // is the lead and the part after is who introduced them; don't reverse category labels like "Event // Name".

Reports are concise: counts first, then only items needing a decision; report every run including "nothing new", and report immediately with counts when stuck.

Phone numbers and message text never go to shared channels, team chats, or public pages; use names and short paraphrases, and keep full numbers in local files or the user's own CRM/sheet if they choose.

Dedupe people by phone number normalized to E.164 and merge iMessage, SMS, and WhatsApp threads for the same person.

Log at most one "message" touch per person per calendar day in the user's timezone.

Messages sent within 10 minutes of each other count as one text when counting unanswered follow-ups.

After 4 or more unanswered texts, suggest one final "last one from me" text, then stop suggesting that person.

Weekend wording: if a draft suggests a call and today is Friday afternoon through Sunday, ask for Monday or Tuesday instead of "today or tomorrow".

All times are reported in the user's timezone with a zone label.

The user's ignore list (family, friends, personal services, spam, 2FA codes, delivery notifications) is honored on every scan.

Use this the first time you talk with a new owner: interview, connect messages read-only, pick a sending mode, first scan, dashboard, and recurring schedule.

Use this when you need to read iMessage/SMS and WhatsApp history read-only and turn it into per-person records (first full scan or any recurring scan).

Use this when scan records need to become a ranked list of people to follow up with, plus draft texts handled per the owner's send mode.

Use this when you want to find people in the user's messages who could send them business repeatedly (referrers, resellers, affiliates, connectors) and draft outreach.

Use this when building or updating the user's single live pipeline dashboard Page after a scan.

Use this when the new owner has confirmed a scan schedule and you need the job text for the recurring message-scan routine (create the routine only after they confirm).