Integration Library
Lorikeet works inside the ticketing system you already run and takes action through your own APIs, so there’s nothing to migrate. Built-in connectors cover Zendesk, Intercom, Salesforce, HubSpot, Front, and more.
Trusted by CX leaders in fintech, health tech and complex industries
What setup actually involves
Most AI support vendors promise a one-click install and then send you a scoping questionnaire. Here’s the real sequence, not the brochure version.
1. Connect where tickets live
Point Lorikeet at your ticketing system, or use our chat widget if you don’t have one. Most connect through an admin-approved authorization flow and don’t need engineering help. Lorikeet works in the same queue as your team, not in a new tool.
2. Connect the systems it acts on
Lorikeet reads and writes through your APIs, webhooks and MCP servers, and you choose read-only or write access for each one in the app.
3. Train it on how you actually work
Help docs, SOPs, policies and brand guidelines, in plain language. Coach builds the workflows, and changes go live without an engineering ticket.
4. Test before a customer sees it
Replay your historical tickets and synthetic scenarios in bulk, and see projected resolution quality before go-live.
5. Go live topic by topic
Deploy on the topics where the evidence holds, and leave the rest with your team.
You won’t do this alone. Every plan includes forward-deployed support, starting with a dedicated onboarding session, and higher tiers add a dedicated deployment team that configures integrations and workflows alongside yours.
How long it takes depends on your systems, not on us wanting it to sound fast. For reference, Hnry went live in mid-May 2026 from zero automation and handled 17,000+ conversations in its first month, and Wonderschool’s parent phone line went from a 10% to a 100% answer rate in its first full month live.
Frequently asked questions
How long does it take to integrate Lorikeet?
It depends on which systems Lorikeet needs to read from and act in. A ticketing connector plus a few API-based actions is a much smaller job than a legacy system with no API. Most connect through an admin-approved authorization flow without engineering help, every plan includes forward-deployed support, and you test on replayed historical tickets before anything goes live. Published examples: Hnry went live in mid-May 2026 and handled 17,000+ conversations in its first month, and Wonderschool’s parent phone line went from a 10% to a 100% answer rate in its first full month live.
Does Lorikeet integrate with my helpdesk?
Probably, in one of three ways. Built-in connectors cover Zendesk (including Zendesk Messaging), Intercom, Salesforce (including Salesforce Messaging live chat), HubSpot, Front, Help Scout, Kustomer, Slack and Genesys Cloud. Any other helpdesk that sends webhooks connects through Flexible Ticketing, set up with our team. And if you don’t run a helpdesk at all, use our chat widget or SDK. For voice, anything that forwards calls works, including Amazon Connect, Twilio, Five9, AirCall, Dialpad, Vonage and Talkdesk. The one real constraint is a system with no API and no webhooks.
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.