Inbound call reaches the assigned SANAA number.
Integration architecture
How SANAA can fit into an existing software platform.
This high-level architecture explains the integration responsibilities SANAA and a software partner review together. It is not a public API specification or a security guarantee.
Direct answer
A SANAA integration connects an inbound phone conversation to the correct customer-business configuration, compatible calendar or CRM actions, usage records and human-transfer rules. The exact API, webhook, authentication and deployment design is agreed during technical discovery.
Built for platform teams
- Product and engineering leaders
- Solution architects and integration teams
- Vertical SaaS operators
- Partnership and commercial teams
What SANAA can support
- Partner and customer account mapping
- SANAA-provided numbers and telephony
- Compatible calendar and CRM actions
- Usage tracking and partner billing
- Human call transfer
- Controlled pilot and rollout
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.
The customer-business configuration and approved knowledge are selected.
SANAA answers, reads context and performs permitted actions.
The outcome is recorded or transferred to the business’s human number.
Platform and customer context
The partner platform may represent many customer businesses and locations. Discovery maps that hierarchy, provisioning responsibility, required configuration and the permissions each actor needs.
Conversation and action layer
SANAA handles the caller conversation and can invoke compatible appointment or record actions. Allowed actions, confirmation behavior, error handling and source-of-truth rules are agreed before launch.
Telephony and human transfer
The SANAA team provides the agreed phone-number and telephony layer. Businesses provide the destination number for human transfer and define when escalation should occur.
Integration boundary
API access, webhooks, authentication, rate limits, logging, retention, data isolation and deployment are not represented here as universal specifications. They are technical-discovery decisions for each partnership.
Questions software teams ask
Integration FAQ
Does this page document a public SANAA API?
No. It documents the integration model at a high level. API and webhook details are discussed with qualified software partners.
Can SANAA support multiple businesses?
Yes. The partner can have multiple customer-business accounts. The exact tenant hierarchy and access model are defined during discovery.
Can SANAA update a partner system?
SANAA can read and update compatible external calendars and CRM systems. The permitted actions and failure behavior depend on the partner integration.
Who operates telephony?
The SANAA team provides the phone numbers and telephony for the agreed deployment.
How are human transfers handled?
The customer business supplies a destination number and approved escalation rules.
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