Launching Team of Agents: great support is a multiplayer game

Launching Team of Agents: great support is a multiplayer game

Steve Hind

Steve Hind

|

|

0 Mins

Today we're launching our Team of agents: Lorikeet concierges can now dispatch other Lorikeet agents to contact third parties via phone, SMS, email, or Slack to resolve customer issues.

For example, in response to a customer email about delayed medication, a Lorikeet concierge could spawn another Lorikeet agent that calls a doctor to make sure their consultation notes are submitted. Once the doctor submits, the concierge can email the patient to let them know the problem is solved. 

Team of Agents is a great example of Lorikeet’s focus on solving the most complex issues and opens up massive possibilities. We’re excited to see what people continue to build with it. We talk through the problem we are trying to solve in the following video, and expand upon it in later sections of the blog post after.

The problem: Great support in complex environments is a multiplayer game

Nearly two years ago Jamie and I started Lorikeet because we observed a massive mismatch between the work of doing support in complex spaces and the FAQ summary-based tools available.

Our conviction was – and remains – that deflection-focused tools that tell customers how to solve problems themselves isn’t enough. We think what’s required is a universal concierge that solves customer problems 24/7 through the channel of their choice by taking actions.

Lorikeet is leading the market in taking actions via first and third party APIs and MCP servers. But across the whole market the gap in action taking is actions that involve other people through phone, SMS, email and Slack. 

Lots of support requires this:

  • Financial Services: Checking with the KYC team before resolving onboarding issues

  • Healthcare: Calling clinics to reschedule patient appointments or chase consultation notes

  • Travel: Calling hotels to arrange late checkouts or special requests

  • Creator Economy: Getting manager approval in Slack for discount codes

Until now companies need to give up on resolving these with AI, or attempt the impossible task of fully re-engineering their (and their vendors’) business processes to be API-first.

The solution: A Team of Agents to play the multiplayer game

Since Lorikeet isn’t satisfied with deflection, we stared at this problem and built Team of Agents to solve it. Here’s how it works:

Your main Lorikeet concierge handles the customer conversation. When it needs something from a third party, it spawns a specialized agent to handle that specific task (e.g. calling the doctor, emailing the vendor, texting the delivery driver).

Each spawned agent has clear parameters: what information to gather, what outcome to achieve, and how long to try before escalating. For example, when calling a hotel about a customer request, the agent knows the booking details, the specific request, and that it should wrap up within four minutes (since the customer is waiting).

This works within Lorikeet’s proven framework for safe and controllable AI action-taking. You maintain complete control over how agents operate (natural language instructions or structured workflows), with customizable guardrails for safe, predictable operations.

The result: better customer experiences, and better ROI

The impact of Team of Agents is simple: more delightful customer experiences. This will lead to customer problems getting solved faster and in ways that wow.

As a sweetener it also offers great ROI and greater scalability: the types of issues you can resolve with Team of Agents are meaningfully more expensive than even more complicated procedural tickets as they often involve hand offs to other teams or breaks in workflow to contact third parties.

The possibilities are endless

The part of this launch we’re most excited by isn’t the impact it will have on automating existing manual workloads. It is the way it opens up brand new possibilities. 

There are things businesses simply cannot afford to do today that Team of Agents unlocks. A bank could place a call to a merchant about a dispute before filing the dispute on behalf of their customer. A booking service could call a restaurant for availability as soon as the customer gets in touch with them, instead of handing off.

What will you build?

We love to partner with the most ambitious teams to do cool things for their customers. We’d love to talk to you about what you can build with Team of Agents. Reach out to start building.

Book a call

See what Lorikeet is capable of

Share this article

Related posts

Ready to deploy human-quality CX?

© 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

Ready to deploy human-quality CX?

© 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

Ready to deploy human-quality CX?

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