Entering the CRM from a portal link (first use)
This chapter explains what happens when you follow an SMS CRM link from the portal into your workspace — what you will see the first time, including setting up your second login factor (MFA), and what to do if the link does not take you straight in.
Before you start — who this is for
You are a customer of a business with an SMS account, following the CRM link from the portal. What you see depends on whether your business has already been switched on for SMS CRM (see Turning on SMS CRM — an owner/admin of the business must do that part).
What the link is
The portal's SMS CRM entry opens after you sign in and select your business. When you follow it, the workspace checks, on the server side, which business you have selected and whether that business has SMS CRM — then shows you the right screen.
What you will see — three situations
- Your business already has SMS CRM — the link opens your working CRM straight away.
- Your business has an SMS account but has not switched on SMS CRM — the link now opens an activation offer: a screen asking you to activate SMS CRM for this business (the journey in Turning on SMS CRM). If you are the owner/admin you can complete it there; otherwise ask your business's admin.
- If you ever see a plain "Not available for this business" message — that was an older problem, described below. It should no longer appear; if it does, your business needs activation first.
First use, step by step (including MFA)
The first time through, expect this order of events:
- If you try to activate before setting up your second login factor, the screen visibly refuses and offers to enroll you.
- Enroll your authenticator (the self-service MFA flow) and confirm it.
- Activate SMS CRM explicitly (tick the opt-in and confirm).
- The workspace re-finds your business and loads the CRM.
- Open contacts and the CRM tools, create a pipeline with the form — then reload the page: everything you saved is still there, and you are not asked to activate again.
A problem customers actually saw (now fixed)
On 18 October 2026 the owner photographed a real failure: a customer with a valid SMS account whose selected business had not opted into SMS CRM hit a dead-end screen reading "Not available for this business" — with no way to reach the activation form from there.
- The failure was reproduced exactly as customers saw it, on the unmodified
Main
11c34aabworkspace at 2026-10-17T20:44:48Z (through the real shared account page, real business resolution and ordinary database security, with safe test providers): Chromium and WebKit both reported the refusal (denied-view=1,activation-gate=0), with no page errors. - Two earlier failed setup attempts while preparing that reproduction (an identity-tool timeout and a stale dev-cache HTTP 500) are preserved as failures — they are not counted as evidence.
The fix (commit 616fe3cc; only the workspace shell and the existing
activation form — no backend, schema or portal change) is exactly situation
2 above: the same link now offers activation instead of a dead end. The
existing MFA flow and normal business re-discovery were kept.
If something goes wrong
| What you see | What it means | What to do |
|---|---|---|
| "Not available for this business" | Your business has not been switched on for SMS CRM (older builds showed this as a dead end) | Ask your owner/admin to activate SMS CRM (see Turning on SMS CRM); on the corrected page you should instead see the activation offer directly |
| You are asked for an MFA code but have none enrolled | First-time owners must enroll an authenticator before making changes | Follow the enrollment offer on screen, then continue |
| Activation refused | You are not signed in as an owner/admin of that business, or the opt-in was not confirmed | Sign in with the right account / tick the confirmation |
What is honestly still open
The corrected page was published and verified byte-for-byte on both workspace servers, but a real customer actually using the live link has not yet been observed and recorded. A link that opens green is not the same as customer acceptance. Everything verified so far used safe test identities. See Not yet covered.
Evidence and receipts
- Evidence base:
docs/reviews/2026-10-18-sms-crm-entry-rca.md - Evidence kind: independently executed Chief checks on the real workspace shell with loopback synthetic identity/SMS providers and ordinary-role local PostgreSQL, plus a verified production page release. The real production customer journey (an actual customer login observed) remains open and is not claimed here.
| Fact in this chapter | Receipt |
|---|---|
| Owner's live failure observation, technical cause, process RCA | docs/reviews/2026-10-18-sms-crm-entry-rca.md (first section) |
| Failing baseline reproduction (denied-view=1, activation-gate=0) | same doc, "Verified failing baseline" (2026-10-17T20:44:48Z, Main 11c34aab) |
| Correction scope and first-use browser run | same doc (commit 616fe3cc; first-use run 2026-10-17T21:33Z) |
Connected regression 13/13 (services/wa-app/tests/sms-crm-entry-connected.test.ts: activation, canonical rediscovery, retry deduplication, foreign-account/member/disabled-binding refusals, tenant isolation, saved contact/deal/follow-up persistence, WhatsApp membership/trial/plan unchanged) |
same doc, Chief1186 run |
Verified release bytes and activation time (GitHub Main 767814b9; both instances at 2026-10-17T22:00Z, image sha256:44aa2e0a034c8ebac48857c813f993c5e2f24416a243c617d95e424d75a0767c, identical corrected page asset c2826e5f…; no password, auth-policy, SMS send, payment or schema change) |
same doc, "Subsequent verified release" |
| First-use run with no pre-enrolled MFA (refusal → enrollment → activation accepted → business rediscovered → CRM tools/contacts → pipeline created through form → survives reload; 390px mobile screenshot; scoped axe serious/critical zero; no overflow/page errors) | apps/workspace/tests/sms-crm-first-use.run.cjs (source 8bc4def7, 2026-10-17T21:33Z), cited in the same RCA |