AI concierge
An AI concierge is an AI system designed to serve customers across their entire relationship with a business — not just reactive support tickets, but acquisition, onboarding, growth, and retention interactions. The term distinguishes a full-lifecycle approach from narrower applications like support chatbots or FAQ deflection tools.
Where a traditional AI support agent waits for inbound tickets, an AI concierge proactively reaches out: following up on abandoned carts, checking in after onboarding, surfacing relevant product features based on usage patterns, or intervening before a customer churns. It maintains memory of the full customer relationship and uses that context to personalize every interaction.
The concierge model reflects how customers actually experience a business. Customers don't think in terms of "support" vs. "sales" vs. "success" — they have one relationship with the brand and expect it to be coherent. An AI concierge serves that entire relationship rather than operating in a single departmental silo.
This approach is particularly valuable for businesses with complex customer lifecycles: financial services companies where customers hold multiple products, healthcare platforms managing ongoing patient relationships, or subscription businesses where retention depends on proactive engagement.
The key architectural requirements for an AI concierge differ from a support-only AI agent. It needs cross-system memory (not just ticket history), multi-channel capability (not just chat), outbound as well as inbound interaction, and the ability to operate across different business functions with different rules and objectives.
Related terms: AI agent, customer journey mapping, customer lifetime value, proactive customer service
Learn more
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.