Back
Flexible Ticketing
Connect a ticketing system that doesn't have a built-in connector, as long as it sends webhooks.
Overview
Flexible Ticketing is how Lorikeet connects to ticketing systems that don't have a built-in connector. Instead of purpose-built software for each helpdesk, the connection is defined by configuration: rules that describe how to read the events your ticketing system sends, and how to send Lorikeet's replies, tags, reassignments and closes back to it.
What it is
If your helpdesk isn't listed on this page, that's not a dead end. Flexible Ticketing adapts to how your system is actually set up (your fields, tags, routing and teammates) rather than assuming a standard configuration. Lorikeet still works inside your existing queue, tells customers, human agents and other bots apart so it never talks over a teammate, and logs every decision the integration makes, so when a ticket is or isn't picked up, you can see exactly why.
How to integrate
Flexible Ticketing is set up with our team, not self-serve. You point your ticketing system's webhooks at Lorikeet and provide API credentials for the actions Lorikeet should take. Our forward-deployed engineers write and test the configuration against your real events, run it quietly so it observes traffic without acting, then switch it on once tickets, messages, customers and tags read correctly. The requirements are that your system sends webhooks for ticket and message events and accepts replies and updates through an API. Because the integration works from what each event contains, we confirm up front which fields come through and map the ones you need.
Other apps
Ticketing System
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.