Define the partner’s customers, use cases, systems and commercial goals.
Multi-tenant AI receptionist
One software partnership. Many customer businesses. A receptionist configured for each.
SANAA can support a software-company relationship that includes multiple customer accounts while keeping each business’s hours, knowledge, phone routing and connected records within its configured workflow.
Direct answer
A multi-tenant AI receptionist serves separate customer businesses through one platform relationship. SANAA supports this commercial model, while tenancy, permissions, data isolation, provisioning and authentication are defined with the partner during integration planning.
Built for platform teams
- Vertical SaaS and business operating-system providers
- Scheduling, CRM, field-service and customer-experience platforms
- Software companies serving many independent customer businesses
- Product teams evaluating an embedded or partner-branded AI receptionist
What SANAA can support
- Multiple customer businesses under one software partnership
- External calendar and CRM reading and updates
- Phone numbers and telephony provided by the SANAA team
- Usage tracking and partner billing support
- Human call transfer to a number supplied by the business
- Partner branding while the receptionist keeps the SANAA name
Defined during discovery
API access, webhooks, authentication, customer-specific workflows, data isolation, security requirements, deployment and commercial terms are reviewed for the partner’s platform before implementation.
Integration journey
From platform discovery to a customer-ready receptionist.
Map calendars, CRM records, appointment actions, call routing and escalation.
Agree on authentication, data isolation, workflows, testing and deployment.
Launch a controlled integration, measure usage and expand customer access.
Model the partner’s real hierarchy
The integration may need to represent a platform, customer company, location and authorized user. Discovery documents the hierarchy that already exists instead of forcing every partner into the same account model.
Keep business behavior customer-specific
Business hours, services, transfer destinations, appointment policies and approved knowledge can differ between customer accounts even when they share the same underlying platform integration.
Provision with control
The rollout plan should define who can activate SANAA, which configuration is required, how numbers are assigned, how usage is measured and how service is suspended or transferred.
Review isolation before launch
Data boundaries, access controls, authentication, logging and retention requirements are technical-discovery items. SANAA does not publish a universal security architecture that may not match a partner’s deployment.
Questions software teams ask
Integration FAQ
Is SANAA a public self-service API?
SANAA is currently offered through a managed integration process. API access, webhooks, authentication and implementation details are discussed with each software partner rather than promised as a one-size-fits-all public API.
Can a software company support multiple customer businesses?
Yes. SANAA can support a software-company relationship involving multiple customer accounts. The exact account hierarchy, permissions and rollout model are defined during integration discovery.
Can SANAA connect with external calendars and CRMs?
Yes. SANAA can read and update compatible external calendars and CRM systems. The available actions and source-of-truth rules are mapped with the partner before implementation.
Who provides the phone numbers and telephony?
The SANAA team provides the phone-number and telephony layer for the agreed deployment. Routing, coverage, escalation and number requirements are reviewed during planning.
Can partners use their own branding?
Yes. The experience can use partner branding without presenting it as Book With AI. The AI receptionist retains the SANAA name, so the accurate description is a partner-branded integration powered by SANAA rather than a completely anonymous white-label product.
What happens when SANAA needs a person?
SANAA can transfer the call to the human phone number the business provides, according to the escalation rules agreed for that customer workflow.
Continue researching SANAA for platforms
SANAA embedded partnership
Bring SANAA to the businesses your software already serves.
Tell us about your platform, customers and desired workflows. We will review the integration model with your team.
Discuss an integration