Launching B2A: win the personal agent revolution

Launching B2A: win the personal agent revolution

Steve Hind

Steve Hind

|

|

0 Mins

Update: the next part of the B2A suite is live. Read Not all your customers are human any more, the launch post for agent traffic detection.

Personal agents like Instinct, Muse, Grok bot and Town are the fastest growing consumer product since ChatGPT. On behalf of your customers they now research, recommend and buy, and they engage businesses persistently, repeatedly and ruthlessly along the way. If your business cannot engage those agents effectively, you will lose control of your customer relationships. The B2A (business to agent) channel will be the most important and fastest growing channel in 2027.

Today we’re launching Lorikeet B2A. Our B2A suite arms your business to win from the B2A revolution. B2A is built for businesses that receive agent traffic. Your customers use their personal agent and B2A lets your business serve it. It enables three things:

Deploy a Lorikeet concierge specially adapted to engage with personal agent traffic with one click and a copy paste code snippet on your site or app.

Understand what agents want when they visit your page, so you can ensure you serve them effectively.

Convert agent traffic into meetings, bookings and sales by integrating into your systems with the Lorikeet platform.

New to B2A? Start with our guide, What is B2A (business to agent)?



What personal agents do, and how B2A handles it

Agents will research, recommend and buy

They read your site before your customer does. One user asked Meta’s Muse to shop for cheaper car insurance while he was at the gym. “15 min later I’m saving $1156 a year,” he wrote. B2A gives that agent a straight answer from you. Agents that support WebMCP, a proposed web standard, call tools on your website. Every other agent calls a public endpoint. Both answer from your knowledge, and your team does no backend work.

They complete the purchase. Agents now finish the job: “The Progressive policy is bound. Policy is effective at 6pm today.” With B2A, the agent talks to the same concierge that serves your customers, with the same knowledge, workflows and actions behind it. A conversation that starts with a question can end in a sale.

They switch for a few dollars. The founder of Instinct lists “cancelled hundreds of dollars of subscriptions” as a top use. One user’s agent took a bill from $80 a month to $40 a month, plus three months free. B2A keeps your business in that conversation. Your concierge can engage, personalize and retain while the agent is still deciding.


Agents will engage persistently, repeatedly and ruthlessly

They come in volume. Earlier this month an agent looking for a restaurant table sent Resy about 200 requests an hour, and checked every 0.4 seconds when tables opened. Resy banned the customer. We wrote about it here. B2A gives agents a path built for machine traffic. An agent asks, then checks back for the answer. Rate limits cap the volume, and a retry avoids opening a second ticket.

They use every channel. This week Instinct started making phone calls for its users: to book restaurants, get on cancellation lists and sort out cable bills. B2A runs on your Lorikeet concierge, which also answers chat, email and voice. The agent reaches the same concierge whichever way it comes in.

They push the rules. When one agent could not sign in to Resy with a saved password, it used the one-time-code path instead: it “read the code from your Gmail, signed in as you”. Another user’s agent “went to war with AT&T over the phone bill”. B2A gives an agent no more authority than the customer has. Agents go through the same guardrails, identity verification and action policies as a person, and they see only what a customer would see.

Try Lorikeet on your own tickets

Start a 30-day free trial. Coach sets up your first concierge in minutes.

Book a call

See what Lorikeet is capable of

Related posts

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.