I asked an AI to book a table on three Indianapolis restaurant websites (it only worked once)

Two weeks ago I opened Comet, Perplexity's AI browser, and asked it to book a table for two, Friday at seven, on three different Indianapolis restaurant websites. A barbecue spot downtown. A Thai restaurant on Mass Ave. A family-run Italian place in Zionsville. Then I sat back and watched the cursor move on its own.

It typed a name. It picked a party size. On two of the three sites, it stalled. The restaurants were not booked solid. It hit a date picker it could not drag, or a "reserve" button buried behind a scroll animation it could not trigger. My assistant told me it could not complete the reservation. One booking out of three.

Most shop owners have no idea this is already happening on their own site, or how often it fails.

What changed this month?

On July 9, OpenAI told users it's shutting down Atlas, the standalone AI browser it launched last October, for good on August 9. OpenAI is moving that same booking-and-clicking ability into ChatGPT itself, bundled into a new work-focused mode called ChatGPT Work.

Atlas was never the biggest player anyway. Perplexity's Comet, the browser I used for my test, is out ahead of it. HUMAN Security, which tracks this kind of traffic across the web, measured Comet handling 47 percent of all agentic browser activity in May 2026, more than double Atlas's 20.3 percent.

One term is worth knowing: an agentic browser opens your website, reads the page the way a person would, and tries to click, type, and submit things on your behalf. It has no mouse, and it cannot tell what a fancy date-picker widget wants from it.

Why did it get stuck on two of the three?

I went back and looked at what actually broke each booking.

The Thai restaurant used a custom calendar widget with no way to type a date directly. A person clicks through it fine. The AI could not find an interactive element it recognized as a date field, and gave up.

The Italian place in Zionsville had a "Reserve a table" button that only appeared after you scrolled two-thirds down the page and hovered over a photo carousel. A person finds it by accident, or by scrolling far enough. The AI never triggered the hover state, so as far as it was concerned, the button did not exist.

The barbecue spot downtown, the one that worked, had a plain form: name, phone, party size, a time picker with a typed fallback, and a "Book now" button with real text on it, not just an icon. The plainness is what made it work.

If a screen reader can fill out your form, an AI agent probably can too. If neither can, you have the same problem twice.

That is not a coincidence. Screen readers and AI agents both read a webpage's underlying structure, not how it looks on screen. The W3C's own accessibility guidance says placeholder text is not a substitute for a real label, because assistive technology does not treat it as one. An AI agent runs into the same wall a blind customer would.

Is your booking form agent-friendly?

You do not need to rebuild your website to answer this. Open your own contact or booking form and try three things.

Tab through it using only your keyboard, no mouse. If you land on a field and cannot tell its purpose, an AI agent cannot either.

Your date or time picker deserves a second look too. If it is a custom widget with no way to type a date directly, add a plain text fallback next to it. This is usually a small, cheap fix, not a redesign.

Check that your submit button says something. "Book now," "Send," "Reserve." Real words, not just an icon or a color.

What to check this week

Fixing this is usually cheap: swap a widget, add a label, rename a button. The harder part is opening your own site the way a stranger would, and noticing where a person without a mouse gets stuck. The barbecue place downtown won because someone built a plain, honest form years ago and never overcomplicated it.

More of your customers are going to let something else drive on their behalf this year. Some weeks that is a browser agent booking a table. Other weeks it is someone in a hurry, thumbing through your site one-handed while they drive their kid to practice. The fix is the same either way.

---

Sources

#	Source	What it backed up
1	OpenAI sets Aug. 9 end date for ChatGPT Atlas	Confirms the Atlas shutdown date and its move into ChatGPT Work.
2	State of Agentic Traffic (May 2026)	Source of the 47% (Comet) vs 20.3% (Atlas) agentic browser traffic share.
3	Labeling Controls, W3C Web Accessibility Initiative	Backs the claim that placeholder text is not a substitute for a real form label.
4	How to check if your website actually works on a phone	Related Luminest piece on testing your site the way a real visitor uses it.