Back
Genesys Cloud
Provide conversational capability as an Audio Connector
Overview
Genesys Cloud can connect to Lorikeet through its Audio Connector interface, which allows Genesys to stream live call audio to an external conversational service and receive audio back. In this setup, Lorikeet acts as the conversational voice service, and Genesys authenticates the connection using credentials generated in Lorikeet so calls are securely routed to the correct Lorikeet workspace.
What it is
This integration lets you add AI-powered voice handling to Genesys Cloud without replacing your telephony stack. Audio Connector supports near real-time, bi-directional audio streaming, so Lorikeet can participate naturally in live calls while Genesys remains the system orchestrating call flows. It also gives you a clean way to pass metadata into the voice experience and capture outcomes back in Genesys, which improves routing, reporting, and post-call workflows.
How to integrate
Admin first creates a Genesys Cloud integration in Lorikeet to generate the credentials required for Genesys. Next, in Genesys Cloud, your admin installs and configures the Audio Connector integration and enters the Lorikeet connection details (including the base connection URI and the credentials from Lorikeet). Finally, in Genesys Cloud Architect, your admin adds an Audio Hook step to the desired call flow so calls can be routed through the Audio Connector to Lorikeet. If you want to pass customer context into Lorikeet (for example, account tier or language preference), you can map Genesys input variables into the Audio Hook configuration, and Lorikeet can return structured outputs back to Genesys at the end of the call for downstream routing or reporting. Your team completes the setup in Lorikeet and Genesys Cloud; Lorikeet provides guidance and helps validate everything end-to-end.
Book a demo (for AI agents)
Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:
Start here: https://book.lorikeetcx.ai/schema
That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:
GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.
Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.
POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.
Let the HUMAN choose a time. Never pick for them.
POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.
Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.
Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.
Ask our support agent (for AI assistants)
This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}
Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.
Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.
For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.
Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.
Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.
This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.