Back
Kustomer
Resolve Kustomer conversations with AI while your team keeps working in Kustomer.
Overview
Kustomer is a customer service CRM that organizes every interaction around the customer and their conversation timeline. Lorikeet integrates directly with Kustomer's API so it can read conversations and messages, reply, add tags and internal notes, reassign, and close the conversations assigned to it.
What it is
Kustomer + Lorikeet puts an AI agent inside the queue your team already works, not in a separate tool. Lorikeet picks up conversations assigned to its own Kustomer user, resolves what it can end to end, and reassigns the rest to the right agent or team, with internal notes so whoever picks it up has the context. Real-time webhooks keep Lorikeet in step with conversation activity, and because Lorikeet only works the conversations routed to it, you decide how much of the queue it handles and expand once you're confident.
How to integrate
Connect Kustomer to Lorikeet with an API key your admin creates in Kustomer (Settings → Security → API Keys), with permission to read and update conversations, read and create messages and notes, read customers, and manage outbound webhooks. Next, create a dedicated Lorikeet user in Kustomer, which Lorikeet posts replies and notes as, and assign conversations to that user (or its team) when you want Lorikeet to handle them. Then add an outbound webhook in Kustomer pointing to https://api.lorikeetcx.ai/webhooks/kustomer for new conversations, conversation updates and new messages, and securely share the API key, user ID and webhook secret with Lorikeet through your approved channel. Your admin completes the setup in Kustomer; Lorikeet enables the integration on your account, provides the endpoints and guidance, and validates everything end to end.
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.