Define the partner’s customers, use cases, systems and commercial goals.
Build versus integrate
Should your software company build an AI receptionist—or integrate one?
The answer depends on where your product creates unique value. Building provides maximum control, while integration may reduce the amount of telephony, conversational, scheduling and escalation infrastructure your team must own.
Direct answer
Build when proprietary voice infrastructure is central to your product strategy and your team is prepared to operate it. Consider SANAA integration when you want to add receptionist capabilities while keeping engineering focused on the software and industry workflows that differentiate your platform.
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.
What an internal build must own
A production receptionist involves telephony, numbers, call routing, speech and conversation behavior, business knowledge, calendars, CRM updates, customer configuration, usage measurement, escalation, monitoring and support. The exact stack varies, but the responsibility remains with the builder.
What a managed integration changes
SANAA supplies the receptionist and telephony layer, then works with the partner on compatible systems, customer workflows, usage and deployment. The partner retains responsibility for its own platform and the agreed integration boundary.
Do not compare only prototype speed
A demonstration call can be created quickly. A customer-ready multi-business offering must also handle provisioning, permissions, failures, human transfer, billing, customer support and changing source data.
Run a controlled evaluation
Select one customer segment and a small number of high-value call outcomes. Compare implementation responsibility, customer experience, operational burden and measurable adoption before expanding.
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