SMS delivery evidence: look up, filter, and save a message record
This chapter shows you how to check what happened to messages sent to one contact, how to narrow the search by date, what each message record means, and how to save a record onto the contact as evidence. It also covers every error message this feature can show you and exactly what to do about each one.
One important meaning upfront: delivery evidence is descriptive only. A message that was delivered says nothing about the contact's interest, and it is never permission to send marketing. The product states this itself in the save confirmation.
Before you start — who this is for
Any business member working a contact. Two things to know:
- You will do this once per business: link your SMS account (Step 1) — you confirm you own the account before anything is read.
- To be verified: delivery evidence currently works with Indian mobile numbers only. A non-Indian contact is fine to store, but no delivery record can be matched or saved against it (see Contacts).
Where the feature lives (there is no separate page)
Delivery evidence is inside the contact detail window on the overview screen. To reach it:
- On the overview, choose View contacts.
- If the contact is not imported yet: Import CRM contacts, pick your file, tick the confirmation and import (the full import journey, including refused rows, is in Contacts).
- Load CRM contacts, then Back to overview.
- Click the contact. The contact window opens (the same window described in Contact timeline and privacy), and the deliveries section is inside it.
Before you have saved anything, the section honestly says: "No saved SMS deliveries yet" — nothing is padded or invented.
Step 1 — link your SMS account to this business (first use only)
Reading your SMS account's delivery records requires a one-time, explicit link:
- Open Link SMS delivery, then Link my SMS account to this business.
- Tick the checkbox confirming you own the SMS account.
- Press Confirm and link account.
- You see: "Your SMS account is linked to this business."
The link is only created after your explicit confirmation — a request without the ownership confirmation is refused by the server (there is no silent link).
Step 2 — choose a date window
Set Start date and End date, then press Preview SMS deliveries.
Two date mistakes are caught in the page itself, before anything is read from your SMS account (verified: the account was read zero times through both refusals):
- End date before start date → "End date must be on or after start date."
- A window longer than 31 days (a 63-day window was tested) → "Choose up to 31 days" — the message tells you the limit; it does not silently shorten your window.
Recovery in both cases: correct the dates and press Preview again. Since nothing was read, nothing needs undoing.
Step 3 — preview: only messages to this contact's exact number
The preview lists messages that match the exact phone number of the
contact you opened — no near-matches. In the verification, the account
offered three records: one to the contact's exact number, one to a different
number, and one to a masked number (*******002) — only the exact match
appeared; the other two never showed. This is the matching rule itself, not
a display choice, and it is why a non-Indian number can never appear here.
- Narrow the dates and press Preview again — the list re-queries for the new window (verified: an out-of-window message disappeared and an in-window one appeared).
- Next page — with more pages available, pressing it loads page 2 and swaps the rows.
Step 4 — errors you might see, and what to do
Every supported failure was actually triggered in the verification and recovered exactly as described:
| What went wrong | Message you see | What to do |
|---|---|---|
| Your connection dropped mid-request | "Could not connect. Check your connection, then try again." | Check your connection and press Preview SMS deliveries again — the retry re-fetched the rows successfully |
| The SMS service is temporarily down | "SMS delivery records are temporarily unavailable. Try the preview again later." | Wait and try again later — the retry succeeded once the service recovered; after a successful preview the error is gone |
| The contact no longer belongs to the selected business (seen on Refresh saved deliveries) | "This contact is no longer available in the selected business." | The contact was removed or belongs elsewhere; close the window and work with a contact that is available |
| The save could not be confirmed (connection dropped during the save) | "The delivery response could not be read. This action may have completed. Refresh saved deliveries before trying a save again" | The feature deliberately does not auto-retry the save (an automatic retry could store it twice). Press Refresh saved deliveries; if the record is not there, press save once more — in the verification the explicit second press completed and the record appeared, with nothing silently added in between |
An account belonging to a different organization never reaches this feature at all: when the verification switched identity and reloaded, a refusal message appeared and no deliveries section was rendered.
Step 5 — save a delivery record to the contact
Each preview match has a save action (for example "Save message 202 to this contact"). Saving writes a real record that captures the exact search window that proved the message — the same start date, end date and page you were looking at, so the evidence is always reproducible. On success you see:
"Message 202 saved. Delivery evidence does not establish interest or consent."
The record then appears under Saved SMS deliveries with its outcome (in the retained save it was shown as delivered). The confirmation's wording is the rule: a delivered message does not opt the contact into anything.
What this feature does not do
- It does not send messages and does not read a live SMS account in any retained verification — every check ran against clearly synthetic test responses (more under Evidence below). No live delivery is claimed.
- There is no combined feed across contacts, no click/reply/open statistics, and no attribution — delivery evidence is per-contact, exact-number and date-windowed, nothing more.
- Saving a record changes no consent, no pipeline and no follow-up.
Screenshots
The captures below are from the synthetic-fixture verification run (a real browser, but test data from a local loopback server — never live):
- Desktop, 1440px:
C:/CT-ZC-3867-smscrm/docs/delivery/evidence/3867-j5-journeys-20261025/deliveries-journeys-1440.png - Mobile, 390px:
C:/CT-ZC-3867-smscrm/docs/delivery/evidence/3867-j5-journeys-20261025/deliveries-journeys-390.png - The independent rerun's captures:
C:/CT-ZC-3867-smscrm/docs/delivery/evidence/3867-j5-rerun/deliveries-journeys-{1440,390}.png
Evidence and receipts
This chapter is written from a worker-tested, isolated lane run on
2026-10-25 — the test sms-crm-deliveries-journeys.test.cjs (commit
edff3888 on the 3867 worker checkout C:/CT-ZC-3867-smscrm), which drives
a real Chromium browser through the real approved navigation and the
real component tree (the actual SmsCrmDeliveries component and its
import/contacts journey), served from an owned loopback server on port
4741 whose API responses are clearly synthetic fixtures. It passed 1/1 and
was independently re-run green a second time (1/1) on a fresh port with a
fresh evidence directory. Evidence kind: isolated, worker-tested,
synthetic-fixture — no live provider, no SMS was or could be sent, no
PostgreSQL, no SSO, no production system, and no live-delivery claim is made
anywhere in this chapter. It has not been independently Chief-accepted;
see Not yet covered for what stays open.
| Fact in this chapter | Receipt |
|---|---|
| Real navigation (contacts → import → load → overview → dialog → deliveries), empty saved state, account link, window refusals with zero provider reads, exact-phone filter, date refine, page 2, transport and 503 failures with recovery, no-auto-replay save then success, CONTACT_NOT_FOUND, foreign identity | C:/CT-ZC-3867-smscrm/apps/workspace/tests/sms-crm-deliveries-journeys.test.cjs (commit edff3888, 1/1 twice) |
Exact HTTP story: 26 receipts; mutations exactly contacts/import 201, account-link 200, observations 200; 7 provider reads incl. one 503; zero page errors; zero external origins; owned port 4741 closed after the run |
C:/CT-ZC-3867-smscrm/docs/delivery/evidence/3867-j5-journeys-20261025/receipts.json (rerun: 3867-j5-rerun/receipts.json) |
| Accessibility of the deliveries surface: axe analysis with zero violations | C:/CT-ZC-3867-smscrm/docs/delivery/evidence/3867-j5-journeys-20261025/axe.json |
| Real-component build (webpack build log of the actual component tree) | same directory, build.log |
| Screenshots (synthetic fixture, desktop + mobile) | same directory, deliveries-journeys-{1440,390}.png |
| Lane status, reproducibility, boundaries (fixtures untracked, no product change) | C:/CT-ZCODE-FULL3747/lane-3867smscrm-ledger.json (worker lane, not Chief-accepted) |