Console
Documentation/Twenty outlets, one organization

Twenty outlets, one organization

Organize locations and agents without sharing unrelated customer data.

Example structure

A restaurant business operates twenty outlets under one customer organization. Create a production project, twenty outlet groups and one or more numbers per outlet. Add a separate project for development.

text
Restaurant organization
  Production project
    Orchard outlet → number A → reservations integration
    Tampines outlet → number B → support integration
    ... eighteen other outlets
  Development project
    Simulator number → development agent

Outlet groups are optional organizational labels; the platform does not require every customer to be a retail business. A single default project and number is sufficient for a small business.

Credentials

A central operations integration can have access to the production project. A local outlet agent receives a number-restricted key. A support employee receives an organization role appropriate to their work. Revoke access independently when a contractor leaves.

Shared and separate agents

One endpoint may serve every outlet when it uses the number and project in each event to select business context. Alternatively, create independent endpoints and keys for each outlet. Never use the contact's phone number as a global customer identity across unrelated businesses.

Agencies

Each client has its own organization and owns its own Meta assets. Agency staff are explicitly granted access to those organizations. The agency does not place all clients inside one organization merely to share an API key or free-number allowance.

Number charges

The first connected number is free per customer organization, across its projects and outlets. Twenty connected numbers therefore have S$152/month in planned number fees, before usage and Meta charges. Billing collection remains disabled until activation.

Prepared 18 November 2026 · Sqkii Pte. Ltd.