SMS CRM customer guide
Sign in to your workspace and select your business. Open SMS CRM after selecting it. Your role and enabled products determine which screens you can open.
This guide explains how to use SMS CRM in plain, everyday language. Each chapter tells you what to do, what you will see on screen, what each result means, and what to do if something goes wrong. You do not need any technical background to follow it.
Everything described here has actually been tried out and recorded by the team. The proof (test runs, recorded outcomes, screenshots) is kept and cited at the end of every chapter, so you can check where each statement comes from. All screenshots in this guide show test data created for verification — they never show a real message delivery, a real customer, or live systems. Anything that has not been verified yet is listed honestly in Not yet covered — we do not invent features that are not there.
Language
This guide is written in English only, following the convention used across this guide collection (the product itself may appear in other languages, but guide copy stays English for now).
Start here
| If you want to… | Read | How well it is verified |
|---|---|---|
| Turn on SMS CRM for a business | Activating SMS CRM | Independently accepted (2026-10-14 corrective acceptance, 46 leaves) |
| Follow a portal link into the CRM (first use, incl. MFA) | Entering the CRM from a portal link | Independently executed Chief checks + verified release |
| See what the opening screen shows | The CRM overview | Approved lane evidence (run06 19/19, run11 1/1) |
| Import, search, export contacts | Contacts | Locally qualified PASS (actual HTTP + PostgreSQL) + approved import round trip + worker-tested phone-outcome lane (2026-10-25) |
| Understand a contact's timeline and privacy | Contact timeline and privacy | Approved lane evidence + actual-HTTP/PG qualification |
| Look up, filter and save SMS delivery evidence for a contact | SMS delivery evidence | Worker-tested isolated lane (real Chromium, synthetic loopback fixtures; 2026-10-25) |
| Work pipelines and leads | Pipelines and leads | Approved lane evidence + independent first-use run |
| Work follow-ups (incl. the MFA check) | Follow-ups | Approved lane evidence (run06) |
| Know exactly what is NOT yet verified | Not yet covered | — |
How to read each chapter
Every chapter follows the same shape:
- Before you start — who can do this (your role) and what you need.
- Step-by-step instructions — what you do, what you see, what it means.
- If something goes wrong — the messages you might see and what to do about them.
- What this does not do — honest limits, in plain words.
- Evidence and receipts — the technical proof behind the chapter, with the exact paths to the retained records. You never need this section to use the feature; it is there so every claim can be checked.
How to read the verification labels
The "How well it is verified" column and each chapter use a small set of labels. In plain terms:
- Independently accepted — after the building team finished, a separate senior reviewer re-tested everything and formally accepted it (the 2026-10-14 activation acceptance). The strongest label in this guide.
- Independently executed — a senior reviewer ran these checks personally (the 2026-10-18 entry first-use journey and connected regression), but a real production customer doing the same journey has not yet been observed.
- Locally qualified PASS / approved lane evidence — real browsers talking to a real running copy of the system and database, using safe test identities created for the purpose. Solid component proof — but not the same as a production acceptance.
- Worker-tested (isolated lane) — written from a builder lane's own reproducible records (both 2026-10-25 lanes re-run green twice), but not independently accepted by the senior reviewer and not on this repository's Main branch. The lane is named per chapter; every fact cites its record. The two chapters using this label are the import phone-outcome section (source-level, real disposable tenant database with security rules enforced, no browser) and SMS delivery evidence (real Chromium browser on the real component, with clearly synthetic test responses from the messaging side — explicitly not real provider/database/single-sign-on acceptance, and no live message delivery anywhere).
All five retained evidence roots are on this repository's Main branch:
tools/chief-sms-crm-review-20261012/actual-http-pg/tools/sms-crm-approved-overview-20261013/(incl.evidence/)tools/sms-crm-voluntary-activation-20261014/docs/reviews/2026-10-14-sms-crm-activation-corrective-acceptance.mddocs/reviews/2026-10-18-sms-crm-entry-rca.md
A sixth evidence base — the 2026-10-25 3867 worker lane (import phone
outcomes and delivery-evidence journeys; commits 8d779dd7 and edff3888
on branch codex/zcode-3867-smscrm, checkout C:/CT-ZC-3867-smscrm) — is
not on Main: its evidence directories are untracked worker receipts under
C:/CT-ZC-3867-smscrm/docs/delivery/evidence/3867-* and its lane record is
C:/CT-ZCODE-FULL3747/lane-3867smscrm-ledger.json. Chapters built only on it
carry the worker-tested label above.