Personal agents are coming. No one is ready.

Personal agents are coming. No one is ready.

Headshot of Robbie Tilleard, a male blog author, smiling at the camera wearing a dark blazer and white shirt.

Robbie Tilleard

|

|

0 Mins

For the last 6 months, we've talked a lot about how personal agents will change the nature of customer support.

Individuals with access to relentless, 24/7 agents are going to unleash a tidal wave of questions onto organisations. The natural instinct of most organisations will be to ban or deflect agents. We think that is a mistake.

Organisations and brands that set up systems to help and resolve queries from personal agents will attract even more agents and, simply, get more business.

Last week, we saw the first breakthrough of personal agents into the mainstream.

On September 6, 2026, JC Bahr-de Stefano posted a screenshot of an email from Resy. The reservation platform had deactivated his account and canceled every future reservation on his account.

Bahr-de Stefano had asked Instinct, an invite-only personal AI agent, to get him a table at 4 Charles Prime Rib in New York. The agent's activity log showed it sent Resy about 200 API requests an hour. It checked availability every 10 minutes through the day, and every 0.4 seconds around the time the restaurant released tables each morning.

From Resy's side, an agent that polls every 0.4 seconds looks like the scalper tools people use to resell tables. Bahr-de Stefano saw it the same way once he read the log: "Of course, this account got flagged for spam, because it was acting like a bot." Resy reinstated the account on September 8.

Great experiences remain the north star - agents or not

Resy is an early sign of the new agentic economy.

Reservations got there first because the prize is obvious (exclusive bookings!) and the target is one API. Personal agents are already here for consumer businesses but this is coming for everyone.

The best businesses will start updating their terms of service and creating the guardrails for personal agents to engage constructively. As Bahr-de Stefano says "most of these sellers or providers need to get to a point where they can understand the difference between a verified agent acting on someone's behalf versus a bot farm."

We think the answer is an AI concierge equipped to handle personal agents.

If Bahr-de Stefano's agent could ask and be told the rules, it wouldn't need to poll constantly. If it was a verified personal agent, Resy may have helped it achieve its goals instead of instituting a ban.

When an agent asks a clear question, your own AI concierge should give it an accurate answer within seconds, under the same policies and identity checks a human would get. Your concierge can set request limits, tell agents when to check back, and explain the rules. The agent can still achieve its goals but within appropriate constraints.

We're building for this at Lorikeet now. If you run a consumer business and more of your traffic or contacts come from AI agents, or you expect them to within the next year, we'd love to hear what you're seeing.

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.