Checking your plan and your phone numbers
Who this guide is for: every member of the business — owner, administrators and employees can open these two screens at any time.
These are read-only screens: they show what your business's plan includes and which phone numbers are allocated to it. Opening them, refreshing them and switching between them changes nothing — the test run behind this guide counted every change-request the browser made during the whole visit, and the total was zero.
What you will see
The Plan screen shows the plan currently in force for your business — in the pictures below, a test Growth plan, version 2 — together with its allowances: what your business is allocated, such as seats, numbers and the monthly message allowance. A Refresh button re-reads the same facts; the view settles back with the allowances still shown and no error.
The Number allocation screen (in the same menu area) shows a table of every phone number allocated to your business.
About the pictures. The plan (Growth, version 2), allowances and numbers in these screenshots belong to an isolated test business created for product testing on a throwaway database. They are not live customer data; no real WhatsApp/Meta message was sent and no real phone number was allocated. Your own screens will show your own plan's real values in the same layout.
Step by step
- Open the plan/entitlements screen from the navigation.
- Read your plan's allowances. Press Refresh any time to re-read them.
- Open the number-allocation screen to see your business's numbers table.
Works on every screen size
The plan screen was tested at three widths — a small phone (320 px), a tablet (768 px) and a desktop (1440 px). At every width the page fits without sideways scrolling, and an accessibility scan of the screen during the test reported zero issues.
Screenshots
All four are full-page captures of the same passing test journey, in the app's dark theme.




What these screens do NOT do
- They do not buy, change or cancel a plan, and they do not request a number. Those are separate flows, and no guide for them exists yet — these screens only read what is already in force.
- The numbers table shows allocation facts only. No message of any kind was sent during the run behind this guide.
Evidence record (kept for honesty).
- FULL3747-BROWSER lane journey 1, "shell-mounted P13 reads
(entitlement-status + number-allocation)" — final: PASSED, final suite
result
2026-10-25T00:10:00Z, recorded inC:/CT-ZCODE-FULL3747/lane-browser-ledger.json. - SHA-bound spec
"shell-mounted P13 reads and refresh stay tenant-bound, read-only and responsive"(spec sha25691525180213363c87101971381d00502cd2b17600d5f66fa97782ea3edfba181, config sha256ddb112f63fb26b8f542a23bd3338351c561c4308b5ab1b029a93528c51728d0b, both VERIFIED in the lane ledger at2026-10-24T23:14:00Z) drove a real Chromium browser against the composed candidate app over a real, isolated PostgreSQL database. - Lane ledger verbatim:
"real chromium; axe violations []; responsive 320/768/1440; zero non-GET /v1/; allowances + numbers table render real API facts". - Attempt history preserved honestly: attempt 1 failed with
usage.allowances=null (no plan assignment)— a fixture gap in the test rig (the synthetic business had no plan yet), not a product defect; attempt 2 passed after the fixture was completed. - Screenshots are byte-exact copies; SHA256 hashes and provenance in assets/ASSETS-MANIFEST.json.
- Standing: local candidate only — screens and APIs really exercised by a real browser over a real database in the combined candidate branch; Chief acceptance and publication OPEN; no live or Main-built runtime claimed.