Identity & entitlements
One server-authoritative access and allowance model serves personal customers and business workspaces.
One platform. Different products. Shared leverage.
Business Solutions and Personal Assistant keep distinct experiences while reusing identity, entitlements, AI actions, communications, billing, developer access and governance.
Public-safe architecture
The important relationship is simple: products sit on a broad shared platform, with administration and governance across the whole.
Public-safe capability view. Provider internals, data structures and privileged controls are intentionally omitted.
AI-action layer
Natural-language intent is translated into scoped actions; important facts are validated by deterministic services.
Voice & messaging
Calling and messaging workflows share provider handling, delivery state, consent and suppression logic.
Operational modules
Leads, calendar, bookings, tables, orders, quotes, enquiries and payments give actions a system of record.
Billing & usage
Plans, entitlements, metering and product configuration are central platform concerns, not duplicated client logic.
APIs & governance
Developer access and the Admin Console sit on the same foundation with separately authorised operational controls.
Built once, applied in context.
A business workspace and a personal workspace present different interfaces, but the access decision beneath them comes from the same shared model.
Discuss the platform, not just the products.
Talk to us about technology, partnership or investment diligence.