Choose one customer segment and a limited pilot group.
Integration readiness checklist
Prepare your software platform for an AI receptionist integration.
A useful discovery call starts with business outcomes and real system constraints. This checklist helps product, engineering and partnership teams arrive with the information needed to scope a responsible pilot.
Direct answer
A platform is ready to explore SANAA when it can identify a customer segment, high-value call outcomes, systems of record, account hierarchy, permitted actions, escalation rules, data requirements and a measurable pilot goal.
Built for platform teams
- Product and engineering teams
- Partnership and commercial leaders
- Security and legal reviewers
- Customer-success and implementation teams
What SANAA can support
- Customer and tenant map
- Call-outcome inventory
- Calendar and CRM ownership
- Telephony and transfer rules
- Security and data review
- Pilot metrics and rollout criteria
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.
Document the calls and actions that matter most.
Map systems, permissions, data and human escalation.
Agree success measures, test cases and expansion criteria.
1. Customer and account model
Document the platform, customer company, location and user hierarchy. Identify who can activate SANAA, change business configuration and review usage.
2. Call outcomes and actions
List the questions SANAA may answer, records she may read or update, appointments she may manage and situations that always require a person.
3. Systems and source of truth
Identify the calendar, CRM, scheduling or operating system that owns availability, customers, services and final appointment status.
4. Telephony and escalation
Define number requirements, hours, routing, transfer destinations, fallback behavior and what happens when a system or staff member is unavailable.
5. Security and measurement
Bring data-flow, authentication, retention, consent and access requirements. Choose measurable pilot outcomes such as answered calls, completed actions, transfers and customer activation.
Questions software teams ask
Integration FAQ
Do we need every answer before contacting SANAA?
No. A preliminary customer segment, use case and system overview are enough to begin. The discovery process helps identify the remaining decisions.
Should a pilot cover every workflow?
No. Start with a small number of valuable, testable call outcomes and expand after accuracy, operations and customer experience are verified.
Is technical documentation required for the first conversation?
Not necessarily. A system overview and the people responsible for product and integration are usually sufficient for initial discovery.
What makes a pilot measurable?
Define the expected call volume, permitted actions, success and failure states, transfer behavior, customer feedback and a review period before launch.
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