A contact's timeline and your privacy guarantees
This chapter explains the history you see when you open a single contact — what it contains, how the window behaves, and the protections that keep one business's contacts invisible to every other business.
Before you start — who this is for
Any business member viewing contacts. Viewing a timeline is read-only — it records and shows what happened; it never changes anything.
What the timeline is (and is not)
Open a contact and you see that contact's own history — real saved events, most recent first, up to a fixed limit (100 entries) per contact:
- A saved consent event is shown exactly as it was recorded.
- If there is nothing yet, you see an honest empty message — nothing is padded, guessed or filled in to look busy.
- The timeline is per contact only. There is deliberately no combined "all contacts activity feed" anywhere in the product, and the system does not infer or display message replies, clicks, enquiries or revenue for anyone.
- Consent information is descriptive — it shows what was recorded. Importing a contact or looking at a consent event grants no opt-in and changes nothing. Delivery of a message, a contact's interest, and permission for future marketing remain three separate things.
Selecting a contact switches the timeline
Whichever contact you click is whose history you see — only theirs. In the retained verification, selecting "Alpha" showed Alpha's note and excluded Beta's; selecting Beta switched to Beta's note. Arrive here via search or import as described in Contacts.
The contact window: closing it and keyboard use
Opening a contact opens a standard dialog window:
- Press Escape (or the close control) and it closes, and keyboard focus returns exactly to where you were before opening it. (This exact behaviour was once a real defect caught during verification — focus was lost on close — it was fixed and re-verified.)
- Keyboard use and dialog containment passed across the Chromium, Firefox and WebKit browsers.
The same window also carries the SMS delivery evidence section — that surface has its own chapter, SMS delivery evidence.
Your data stays yours (how seriously that is enforced)
These are server-side and database-side guarantees, not just screen layout. In the retained verification, the same signed-in test identity deliberately tried to reach another business's data:
- A request dressed as another organization → refused with 403 MEMBERSHIP_REQUIRED (you do not belong to that business).
- Another business's contact asked for under your business → 404 NOT_FOUND (as far as your business can see, it does not exist).
- A database read pinned to your business sees zero foreign contacts — the separation is enforced in the database itself (row-level security), not merely hidden in the interface.
If something goes wrong
| What you see | What it means | What to do |
|---|---|---|
| Empty timeline with a "nothing yet" message | No events are recorded for this contact yet | Nothing wrong — the screen is being honest |
| You cannot find a contact you expected | It may belong to a different business, or the row was refused at import | Check the import refusal reasons (Contacts); contacts from other businesses can never appear in yours |
Evidence and receipts
- Evidence base:
tools/sms-crm-approved-overview-20261013/(evidence/run06/result.json, 19/19) for the timeline surface and dialog behaviour, andtools/chief-sms-crm-review-20261012/actual-http-pg/(attempt 02) for the per-contact switching and cross-tenant refusal receipts. - Evidence kind: locally qualified PASS, real HTTP + ordinary-role PostgreSQL + real browsers, synthetic loopback identities. No live provider, no SMS sent, no real customer data.
| Fact in this chapter | Receipt |
|---|---|
Bounded limit=100 per-contact source; consent event rendered; truthful empty state |
tools/sms-crm-approved-overview-20261013/HANDOFF.md surface table (timeline row), evidence/run06/result.json |
| Native dialog Escape + focus return (defect found in run02, fixed, passing in run06) | same HANDOFF failure-history and accessibility paragraphs |
| Alpha/Beta per-contact switching | tools/chief-sms-crm-review-20261012/actual-http-pg/HANDOFF.md "Executed outcomes", attempt 02 |
| Foreign-org 403 / foreign contact 404 / RLS zero | tenant-refusal.json, final-sql-witness.json in the same root |
| Consent descriptive; no aggregate feed; no attribution | 2026-10-13 HANDOFF "Consent display" and limitations sections |