Back
Salesforce
Execute support workflows inside Salesforce for consistent, auditable outcomes. Connect CRM data to unify sales and service workflows
Overview
Salesforce Service Cloud is an enterprise-grade customer service platform that manages cases, knowledge bases, and customer interactions at scale. Lorikeet integrates with Service Cloud via Email-to-Case to process cases as tickets, using ContentNotes for internal messages and Topics for tagging while maintaining connection to your broader Salesforce CRM ecosystem.
What it is
Salesforce Service Cloud + Lorikeet brings AI assistance into enterprise support operations while preserving the CRM context that makes Salesforce valuable. Lorikeet can use account and case history to personalize responses and help reduce resolution time, while keeping Salesforce as the system of record. You get faster handling of routine work and cleaner escalation to humans for complex cases—without changing how your team operates inside Service Cloud.
How to integrate
Connect Salesforce Service Cloud to Lorikeet using an admin-approved authorization flow and standard Salesforce integration methods. You’ll share the Email-to-Case routing configuration so Lorikeet can receive case updates through your established intake path, and you’ll provide the Salesforce identity Lorikeet should use when writing back so notes and responses appear under the correct user. For real-time case updates, you’ll enable Salesforce Change Data Capture (CDC) for the relevant objects and share the required Connected App details with Lorikeet through your approved secure channel. If your workflow relies on specific Salesforce features for internal notes or tagging, Lorikeet will confirm the exact Salesforce objects and fields used in your org and align the integration accordingly.
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.