Back
Lorikeet SDK
Initialize Inbound and Outbound Voice Calls
Overview
Inbound Voice Calls (SDK) is a developer-friendly way to initialize a Lorikeet voice conversation before routing the live call to Lorikeet. It provides the same capabilities as the API approach—passing customer identifiers and context for personalization—while simplifying implementation through an SDK.
Outbound Voice Calls lets Lorikeet place calls to customers as part of proactive workflows—such as appointment reminders, delivery updates, verification calls, surveys, and follow-ups. Each call follows the workflow you configure, and outcomes can be captured for reporting and downstream actions.
What it is
The SDK approach reduces implementation effort and avoids common authentication pitfalls, making it faster to get to production while still enabling context-aware voice support. You can enrich calls with real-time customer data, improve routing and first-call resolution, and keep the integration maintainable as your voice workflows evolve.
Outbound calling helps you reach customers proactively without tying up your support team, which can reduce inbound volume and prevent issues from escalating. It’s especially valuable for time-sensitive outreach and structured campaigns where consistency matters, and it gives you clear visibility into outcomes so you can measure effectiveness and improve over time.
How to integrate
Your team installs the Lorikeet SDK in the service that receives inbound call events (for example, your telephony middleware). When a call arrives, your application uses the SDK to create a Lorikeet voice conversation and includes the customer context you want Lorikeet to use for routing and workflow execution. After the conversation is created, your voice provider forwards the live call to your assigned Lorikeet number. Your team completes the setup in your application and voice infrastructure; Lorikeet provides the endpoints, guidance, and validates everything end-to-end.
Your team enables a Telephony integration in Lorikeet and uses the Lorikeet SDK (or API) from your application to initiate outbound calls. When you trigger a call, you provide the phone number and the workflow to run, along with the key inputs that workflow needs (for example, customer name, order number, or appointment time). Your team completes the setup in Lorikeet and your application layer; Lorikeet provides guidance and helps validate the end-to-end call flow, including how results are captured after the call.
