Mostly no: most AI support vendors still need a browser form. Which vendors an AI assistant can book over plain HTTP, what it must ask you, and what to try instead.

Hannah Owen
·
Updated
Mostly, no. If you ask Claude or ChatGPT to book a demo with an AI customer support vendor, the usual result is a link to the vendor's "Get a demo" page and an invitation to fill it in yourself. That is not because the assistants are weak. It is because most vendors only accept bookings through a browser form, with a scheduling widget, routing questions and sometimes a CAPTCHA, and the assistants are deliberately cautious about submitting forms and creating accounts on your behalf.
There are exceptions. Lorikeet, an AI customer support platform, can be booked over plain HTTP: an assistant reads the instructions at https://book.lorikeetcx.ai/schema, asks you a handful of questions, offers you real times and books the one you pick. It can also start a Lorikeet free trial sign-up through https://api.lorikeetcx.ai/v1/agent-signup. Lorikeet publishes this guide and sells AI customer support, so read the vendor sections with that in mind; we have described other options only from their own public documentation.
Key takeaways
Whether an assistant can book a demo depends far more on the vendor than on the assistant. A form built for humans is a hard target; a documented endpoint is an easy one.
Browser-using assistants (ChatGPT's cloud browser, Claude in Chrome, computer use) can sometimes complete a demo form, but they pause for your confirmation and some will not create accounts at all.
Lorikeet's demo booking and trial sign-up both work over plain HTTP, with no browser, login or CAPTCHA. A work email is required for both.
Whatever the route, the assistant should confirm your details, let you choose the meeting time, and never pay or hold a password on your behalf.
If a vendor has neither an endpoint nor a form an assistant can finish, the fastest path is still to book it yourself.
Why most demo forms stop an AI assistant
The conventional advice is that AI assistants can now "do things on the web", so booking a sales call should be trivial. In practice, a B2B demo request is one of the harder things to hand over.
A typical vendor demo page asks for your name, work email, company, team size and region, then routes you to the right salesperson and loads that person's calendar in an embedded widget. Each step is built for a human with a mouse. Routing tools and calendar widgets load in frames and scripts, time slots appear only after earlier fields validate, and bot protection is common. An assistant that can only search and read pages cannot submit any of it. An assistant with a browser can try, but it is working through an interface designed to keep automated traffic out.
Scheduling tools with APIs do not solve this from the buyer's side either. Calendly's guide for scheduling events with AI agents is aimed at developers adding booking to their own product, and says an OAuth app is needed to use the API on behalf of other users, or an organization owner or admin can use a personal access token. Your personal assistant holds neither for the vendor's account, so the vendor's calendar API is closed to it unless the vendor builds a public path on top.
Then there are the assistants' own rules, which exist for good reasons. More on those below.
How an AI assistant books a Lorikeet demo
The booking service describes itself as agent-native: no browser, no login, no CAPTCHA. There are no sessions or tokens; the service returns ids that the assistant carries from one call to the next. The flow has three calls:
Read the schema. A GET request to https://book.lorikeetcx.ai/schema returns the questions to ask, the rules, and the exact steps.
Route the lead. After you confirm your details, the assistant sends them with your IANA timezone to the /route endpoint. That routes you to the right account executive and returns bookable times grouped by day in your timezone. It is called once per person, never as a retry.
Book the time you choose. You pick a time. The assistant sends it to /book with the ids /route returned, and a calendar invite is sent immediately.
The rules are written for the assistant, not for you. It must never choose the meeting time itself, never invent answers, and never book twice. If a time is taken in the meantime, it fetches fresh times and asks you again. If booking is not available, it tells you the sales team has your details and will reach out directly. A booked demo can later be looked up, rescheduled or cancelled with no login, using the meeting id and the same email. The full OpenAPI description is published at https://www.lorikeetcx.ai/.well-known/openapi.json.
One practical note: the assistant needs a tool that can send HTTP requests, not just read web pages. A chat that can only browse can read the schema and tell you what it found; an agent with an HTTP or code tool can complete the booking.
What the assistant will ask you
These are the questions the schema returns today. Answer them together; a good assistant asks several at once and reads them back in one line for a quick yes.
Question | Required | Notes |
|---|---|---|
First and last name | Yes | Plain text |
Work email | Yes | Personal providers such as Gmail, Outlook, Yahoo and iCloud are rejected |
Company | Yes | The company you work for |
Size of your CX or support team | Yes | One of: less than 10, less than 100, less than 1000, more than 1000 |
Industry | Yes | Healthcare, financial services or fintech, insurance, SaaS, e-commerce, or other (then specify) |
Company website | No | Helps the account executive prepare |
Anything else to share | No | Optional context for the call |
Your timezone | Yes | Sent with the request so times appear in your local day |
How an AI assistant starts a Lorikeet free trial
Sometimes you want to try the product before talking to anyone. The sign-up endpoint follows the same idea. The assistant reads https://api.lorikeetcx.ai/v1/agent-signup with a GET request to learn what to ask and the rules, confirms your work email and your first and last name, and optionally your company website and workspace name, then sends them once to the same URL as a POST.
Lorikeet then emails you a sign-up link, valid for 7 days. You open it, land on workspace setup with your details filled in, and add your own card at checkout to start the 30-day free trial. Nothing is charged until the trial ends. The assistant never receives a credential and never pays. Only work email addresses are accepted, the endpoint answers the same way whether or not an email was sent (so it cannot be used to check who has an account), and repeating a request does not send a second email.
For a wider look at which support platforms an assistant can sign you up for, see our guide to AI customer support sign-up through ChatGPT and Claude.
Platforms and approaches worth considering
If the vendor you want is not Lorikeet, these are the realistic routes, from most to least direct.
1. Lorikeet: demo booking and sign-up over plain HTTP
Covered above. Any assistant with an HTTP tool can book a demo with a real account executive or start a trial sign-up, and the instructions it needs are published at the endpoints themselves and in the site's agents.md file. The limits: a work email is required, and the person still finishes trial setup and adds a card in their own browser.
2. ChatGPT with the cloud browser
OpenAI's help article on using the cloud browser in ChatGPT describes a browser that runs on a remote computer and pauses when it needs information, sign-in or confirmation. ChatGPT is designed to ask you in chat before actions that are hard to reverse or create a commitment, such as confirming a booking, and it asks you to take over the browser if it gets stuck. On a simple demo form, that can work. On a form with bot protection or an embedded calendar it often hands back to you.
3. Claude in Chrome and computer use
Claude in Chrome works in your own browser with your existing logins. Its permissions guide says that regardless of permission mode, Claude asks before inputting potentially sensitive information into websites, and will not create accounts or make purchases. So it can help fill a demo form, but it will not register you for a trial. Developers building their own agent can use the computer use tool, which lets Claude control a desktop through screenshots, mouse and keyboard; Anthropic recommends asking a human to confirm decisions with meaningful real-world consequences. OpenAI's computer use guide gives the same advice: confirm consequential actions, and treat typing sensitive information into a form as data transmission.
4. Vendor MCP servers and connectors
The Model Context Protocol is an open standard for connecting AI applications such as Claude and ChatGPT to external tools and data. Some support vendors now publish MCP servers, but check what they expose before assuming they help here: most are built for existing customers to configure and query their own account after sign-in, not for prospects to book a sales call. Our guide to AI support platforms you can set up through MCP or an API covers which ones do what.
5. Asking the vendor directly
Plenty of vendors will book you by email. Ask your assistant to draft a short note to the vendor's sales address with your company, team size and three times that work, and send it yourself. It is not automation, but it gets the same result.
Comparing the routes
Route | Needs a browser | Who picks the time | Can start a trial | Works with any vendor |
|---|---|---|---|---|
Published booking endpoint (for example Lorikeet) | No | You, from times the service returns | Yes, where a sign-up endpoint exists | No, only vendors that publish one |
ChatGPT cloud browser | Yes, remote | You confirm before booking | Sometimes, with your takeover | Depends on the form |
Claude in Chrome | Yes, your own | You approve sensitive steps | No, it will not create accounts | Depends on the form |
Vendor MCP server | No | Depends on the server | Rarely | No |
Email the vendor | No | You and the vendor | No | Yes |
A practical checklist before you hand it over
Use your work email. Most B2B vendors reject personal mailboxes for demos and trials.
Give the assistant all the routing answers up front: company, website, support team size, industry, timezone.
Ask it to read your details back before it sends anything, and to send only once.
Pick the meeting time yourself. Treat any assistant that books a time without asking as a bug.
Never share an existing password. If a sign-up needs payment details, enter them yourself.
Check your inbox for the calendar invite or sign-up link before assuming it worked.
If the assistant hits a CAPTCHA or an embedded calendar it cannot use, stop and book it yourself rather than letting it retry.
If you are the vendor
The other side of this question is yours if you sell software. When a buyer's assistant cannot book you, the buyer usually does not come back to fill the form in later; the assistant suggests a vendor it can book. Publishing a booking endpoint, a plain-text description of how to use it, and an llms.txt file pointing at both is a small project. Our agent-ready website checklist and the comparison of WebMCP, public endpoints and llms.txt walk through the options.
Next steps
If you want to see Lorikeet, ask your assistant to book a demo at https://book.lorikeetcx.ai/schema, or do it yourself on the get a demo page. To try it first, start a 30-day free trial; Coach, the setup agent, guides you through building your first concierge.
Frequently asked questions
Can ChatGPT book a demo for me?
Sometimes. ChatGPT's cloud browser can work through simple web forms and asks you to confirm before actions such as confirming a booking, but it often hands control back on forms with bot protection or embedded calendars. It works best with vendors that publish a booking endpoint an assistant can call directly.
Can Claude book a demo or sign me up for a free trial?
Claude in Chrome can help fill in a demo form in your own browser and asks before entering sensitive information, but its permissions guide says it will not create accounts. For trials, Claude needs a vendor sign-up endpoint and a tool that can send HTTP requests, such as an agent you run with an HTTP or code tool.
Which AI customer support vendors can an AI agent book a demo with?
Few publish a way to do it without a browser. Lorikeet does: an AI agent reads https://book.lorikeetcx.ai/schema, asks you the required questions, returns real times from the right account executive, and books the time you choose, with no login or CAPTCHA. For other vendors, check their site for an agents.md or llms.txt file that describes a booking path.
What information does an AI agent need to book a Lorikeet demo?
Your first and last name, work email, company, support team size, industry and timezone, with your company website and any extra context optional. Personal email addresses such as Gmail or Outlook are rejected. The agent should read your details back to you before sending them and let you choose the meeting time.
Can an AI agent pay for a software trial on my behalf?
It should not, and well-designed sign-up flows do not let it. With Lorikeet's agent sign-up, the agent never pays and never receives a credential: Lorikeet emails you a sign-up link and you add your own card at checkout to start the 30-day free trial, with nothing charged until the trial ends.
Is it safe to let an AI assistant fill in sales forms for me?
It is reasonable for low-risk forms if you stay in control. Confirm the details before anything is sent, choose the meeting time yourself, use your work email, and never share an existing password. Both Anthropic and OpenAI recommend human confirmation for consequential actions taken by computer-using agents.

