Integrating Voice AI: Directories, CRM, and Host Notifications

Voice AI connects to your existing stack through four layers: notification channels like Slack, Teams, email, and SMS; CRM and ticketing systems that receive leads and issues; identity providers such as Azure AD, Google Workspace, and Okta; and industry systems from EHR scheduling to badge printers — all wired together with REST APIs and webhooks. Get those four layers right and the assistant does real work. Skip them and you have deployed a talking FAQ.

Conversation is the interface — integrations are the hands

Consider two moments from a typical deployment. A visitor tells a lobby kiosk, "I'm here to see Priya." Resolving that sentence requires a directory lookup, a notification to Priya on the channel she actually watches, and — in many offices — a badge printed on the spot. Meanwhile, on the website, someone asks about pricing for a rollout across three sites. That conversation should end as a lead in your CRM with the context attached, not as a transcript nobody reads.

Neither moment is a language problem. The understanding part is table stakes; the value is created when the assistant can touch the systems where your organisation actually keeps its people, records, and schedules. That is why integration questions belong at the start of an evaluation, not the end — a theme that runs through our product architecture as a whole.

Layer 1 — Notifications: reach people where they already look

The fastest integration to stand up, and often the one that earns the most goodwill, is notifications. When a visitor checks in, their host gets pinged through Slack, Teams, email, or SMS — whichever channel that person actually monitors. The difference between an email a host opens after the meeting and a Slack message that lands on their phone in seconds is the difference between a visitor waiting awkwardly and a lobby that feels run.

Notifications also carry context: who arrived, who they are here for, and why. The host can reply in kind — "be right down" or "send them to room 4" — without walking to reception to find out. This is the operational core of the AI receptionist pattern: the assistant absorbs the arrival, and a human enters exactly when needed, fully briefed.

Layer 2 — Records: CRM and ticketing

Every conversation that should become a record needs to become one automatically. Two flows cover most of it. First, lead capture to CRM: when a website visitor or kiosk user expresses buying intent, the assistant collects the details conversationally and writes them into your CRM — no re-keying, no forms abandoned halfway. Second, ticketing: when an issue can't be resolved in conversation, it lands in your ticketing system with the transcript context attached, so the human who picks it up starts informed rather than cold.

The discipline here is completeness. If capturing a lead requires a person to copy details from a dashboard into the CRM later, the integration is not done — it has just moved the manual work downstream.

Layer 3 — Identity: directories, SSO, and who can do what

Identity integration has two distinct faces. The visitor-facing one is directory lookup: "I'm here to see Priya" only works if the assistant can resolve names against the directory you already maintain — Azure AD, Google Workspace, or Okta — rather than a spreadsheet that drifts out of date. The list of who can be visited stays in sync with who actually works there.

The admin-facing one is access control for your own team. Sign-in to the management console goes through SSO via OIDC or SAML, so access follows your identity provider's rules — joiners, leavers, and MFA policies included. Inside the platform, role-based access control separates admins, editors, viewers, and auditors, and every action lands in an audit log. Content editors can update answers without touching integration settings; auditors can review without changing anything.

Layer 4 — Industry systems: where deployments get specific

Beyond the horizontal layers, most sectors have one system that defines the deployment. In healthcare, it is EHR and scheduling — integrations with Epic, Cerner, and Athenahealth let an assistant handle non-clinical check-in and appointment logistics against the systems of record. On campuses, it is SIS and LMS platforms — Banner, PeopleSoft, Workday, Canvas. At conferences and venues, event platforms — Cvent, Bizzabo, Swapcard — drive registration and session answers. And in lobbies, the humble badge printer matters more than any dashboard: supported Brother, Dymo, and Zebra printers turn a spoken check-in into a physical credential.

The pattern to notice: industry systems are where "voice AI" stops being generic. Two deployments with identical language capability can differ enormously in usefulness depending on whether this layer is connected.

The connective tissue: REST APIs and webhooks

Underneath the named integrations sit two general-purpose mechanisms. REST APIs handle lookups and writes on demand — check a calendar, create a record, query a status. Webhooks push events outward the moment they happen — check-in completed, lead captured, escalation triggered — so your systems react in real time instead of polling. Between them, they also cover the system nobody else has heard of: the internal tool your operations team built in 2019 integrates through the same two mechanisms as everything above.

Security across the seams

Every integration widens the surface area, which is why the security posture has to span the seams rather than stop at the assistant. Data moves encrypted in transit and rests encrypted at rest; tenants are isolated; retention is configurable with automatic purge; and audit logs record what crossed each boundary and when. Kuyil never trains public models on customer data, and deployments can stay in-region — US, EU, or India — or run on-premise where policy demands it. The full control set is on our security overview, with reports and a DPA available on request.

Sequencing the work

Integration depth drives timeline more than any other factor. A website assistant with notifications and lead capture can be live in days. A first kiosk — acoustics, badge printing, host notify — typically runs four to six weeks from discovery to go-live. Deep integrations into EHR, SIS, or event platforms generally take eight to twelve weeks, and enterprise pilots often run 60 to 90 days. The practical sequence mirrors the layers above: start with notifications, add CRM and ticketing, wire identity, then tackle the industry system once the assistant has proven itself on the simpler surfaces.