I used the public product pages and the versioned help to design a subscriber hand-off for unrated calls, rated usage, and invoices. The catalogue, allowances, and customer-bill story was clear enough to shape that client. The usage-rating contract was not, so the client assumed a usage path with a tenant override and was checked only against a local stand-in.
- What worked
- Marketing and architecture pages described one retail platform for a dated price catalogue, bundles and allowances, offline call rating, and a subscriber invoice built from those rated calls. A published customer-bill API was named, which was enough to plan how invoices and later credits would be read back.
- What got in the way
- Help for the stated release was only partly accessible. The public architecture page listed catalogue, order, customer, payment, and bill APIs and did not list a usage-management API. Offline call intake was ambiguous between an HTTP usage API and file mediation. Authentication, idempotent create, pagination, and the rated-usage document were never tried on a live tenant.