"With Lorikeet I didn't have to make that choice. Lorikeet takes the edge off the support volume, then the team can absorb the rest."

Gonzalo Cayo

Chief Customer Officer

"With Lorikeet I didn't have to make that choice. Lorikeet takes the edge off the support volume, then the team can absorb the rest."

Gonzalo Cayo

Chief Customer Officer

"With Lorikeet I didn't have to make that choice. Lorikeet takes the edge off the support volume, then the team can absorb the rest."

Gonzalo Cayo

Chief Customer Officer

Company

Firm360

Industry

Complex SaaS

Company size

Scale-up

The headcount question

Firm360 started how the best businesses often do: someone fed up with the tools they had, with an idea for a better solution, and a small group of like-minded professionals willing to try it first. What began as a tool one accountant needed for his own firm has grown into a platform used by accounting firms across the United States.

Today, the company faces a familiar challenge: increases in customer volume require increases in team capacity. When Gonzalo Cayo joined a year ago to structure operations, the choice was a Customer Success Manager to drive renewals and upsell, or dedicated support agents to take tickets off the people doing onboarding and customer success.

A self-improving knowledge base

The most distinctive thing about how Firm360 runs Lorikeet is what happens to the knowledge base. The team treats Lorikeet as a contextual data layer, not a frontend. Every two weeks, Firm360 runs analysis against three sources at once: Lorikeet’s MCP server, Slack, and recent customer conversation transcripts. The output is a ranked list of knowledge base gaps with draft answers attached.

Once new articles are published, Lorikeet’s Auto QA reviews them continually. The next time a similar conversation comes in, Lorikeet handles it end-to-end. With each cycle the gaps decrease.

This is the loop that compounds. Most AI support deployments stall when a knowledge base isn’t updated, because nobody owns the work of finding gaps. At Firm360, the work of finding gaps is automated, and the work of closing them is heading the same way.

From support to operations

At Firm360, the teams Lorikeet assists are not support agents. They are onboarding specialists, CSMs, and ops leads, all answering tickets between other priorities. By helping reduce the load, Lorikeet acts as both customer operations and customer experience. It makes sense that the next use case is internal. Lorikeet also lives in Slack, where the Firm360 sales team can ask product questions during demos. Months of historical Q&A in that channel become the seed context for an internal-facing knowledge base that the sales team can talk to in real time to improve and scale capability without scaling the team.

“Now the team can ask Lorikeet, get responses in the moment, and immediately act on customer needs. Hiring is a full-time job, onboarding is a full-time job. Lorikeet makes everyone more efficient.”

Gonzalo Cayo

Chief Customer Officer

Read other stories

Connect, configure and preview

Read other stories

Connect, configure and preview

Read other stories

Connect, configure and preview

Read other stories

Connect, configure and preview

Complex is our comfort zone

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. 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.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Complex is our comfort zone

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. 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.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Complex is our comfort zone

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. 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.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

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:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. 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.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. 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:

  1. 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 }.

  2. 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 }.

  3. 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.