A PCWorld writer asked Claude to book a table for three in Midtown Manhattan via the Resy connector; it picked a restaurant but the exchange was clunky, with raw JSON and permission prompts.
A PCWorld writer asked Claude to book a table for three in Midtown Manhattan via the Resy connector; it picked a restaurant but the exchange was clunky, with raw JSON and permission prompts.
The writer added the Resy connector to Claude through Customize > Connectors, then chatted about where to eat near his Midtown apartment (table for three, around 6:30 pm). Claude suggested The Smith and pulled up availability. A raw JSON permission prompt appeared and he clicked Always allow. Claude couldn't complete the booking itself, so he tapped the 7:15 slot and finished on Resy's site.
Claude picked a good restaurant and showed open slots, but the writer still had to finish the reservation on Resy himself. He concluded the Resy app on his iPhone would have been faster.
The connector only exposes the tool calls the developers defined, so it can show availability but not book. Expect to finish the reservation yourself on Resy.
Open Resy in my browser and find a table for [number] people in [neighborhood, city] on [date] around [time], serving [cuisine or budget]. Show me up to three options with times and any cancellation policy. Pause and wait for me to choose before booking, and show the booking details before you confirm. Finish when I have a confirmation.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.