Back
Salesforce Messaging
Hand chat conversations to live agents in Salesforce Messaging, with the full conversation attached.
Overview
Salesforce Messaging for In-App and Web is Salesforce's live messaging channel, routed to agents through Omni-Channel. Lorikeet's AI runs the conversation in the Lorikeet Chat Widget, and when a customer needs a person, it hands the chat to a Salesforce Messaging channel where a live agent takes over. Messages flow both ways until the conversation closes.
What it is
This is a handoff, not a second front door. Lorikeet resolves what it can in the widget, and when a handoff happens it opens the Salesforce conversation, posts the conversation so far, and lets your existing Omni-Channel flows, queues and agent presence decide who picks it up. Your agents work in Salesforce as they do today, and the customer keeps chatting in the same widget without repeating themselves. You can also show the customer an estimated wait time when Salesforce provides one.
How to integrate
Your Salesforce org needs the Digital Engagement add-on, Omni-Channel with a routing flow, and a messaging-capable queue. In Salesforce, your admin enables Messaging for In-App and Web, creates a messaging channel, attaches your Omni-Channel Flow, then creates and publishes an Embedded Service Deployment of type Custom Client. Copy the organization ID, developer name and messaging URL from that deployment's code snippet into the Salesforce Chat integration in Lorikeet, in the same environment as your Chat Widget (our team enables it on your account). Finally, point the handoff step in your chat workflow at the Salesforce Messaging channel, and test end to end by driving a widget chat to handoff and confirming it lands in Omni-Channel.
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.