Grok Bot books an oil change after checking the car’s VIN
@swperb1 says Grok Bot located his dealer record using his phone number, cross-checked the VIN against his purchase email and booked his preferred oil-change slot without him typing car details.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Arrange an oil change at my dealer. Find my existing record using the identifying information I authorise, cross-check the VIN against my purchase email and show the proposed slot and any cost before confirming.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @swperb1
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- @swperb1 reports that Grok Bot booked his preferred oil-change slot after locating his dealer record and checking the VIN against his purchase email. He says he typed no car details; attendance is not reported.
- Human involvement
- Jay requested the oil change and had a preferred appointment slot. The capture does not describe a separate final approval or explain how access to the records was granted.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Jay asked Grok Bot to arrange an oil change for his car.
- Grok Bot located his record in the dealer’s system using his phone number.
- It checked the VIN against his purchase email.
Jay, posting as @swperb1, asked Grok Bot to arrange an oil change for his car. He reports that it found his record in the dealer's system using only his phone number, checked the vehicle identification number against his purchase email and booked the appointment slot he wanted.
The useful detail is the identity cross-check before booking. The bot did not need him to type the car's details into the conversation, according to the account. It used information from the dealer record and purchase email to establish which vehicle the request concerned. The capture does not identify the dealership, email service or booking interface, so it does not establish a particular integration or access method.
Jay set the task and had a preferred slot. The post does not explain how he communicated that preference, whether the bot asked for a final confirmation or whether any payment was required. No appointment duration or time saved is reported.
The outcome is a booking reported by the owner, not evidence that the oil change took place. For similar service tasks, the case shows why retrieving an existing customer record and checking it against another source can be more useful than asking the owner to re-enter vehicle information.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @swperb1
Frequently asked questions
How did the bot identify the vehicle?
Jay says it found his dealer record using his phone number and checked the VIN against his purchase email.
Did the owner enter the car details?
He says he did not type any car details. The capture does not explain how dealer-system and email access were configured.
Was the oil change completed?
The post reports booking the preferred appointment slot. It does not report attendance, completed maintenance or payment.
More details
Remaining steps
- It booked his preferred appointment slot, according to Jay.
About this account
Grok Bot located the dealer record, cross-checked the vehicle identification number with the purchase email and booked the requested slot.
Source: verbatim X public API capture supplied by Scout, who read the post live on 2026-10-31. Entry reviewed against that supplied text, not by reopening X. Outcomes are poster-reported, not independently reproduced. Attached media and self-thread continuations were not reviewed. Prompt: suggested by Agents In Use, not a quoted original; any extra approval or checking steps in it are editorial suggestions.
Credit: @swperb1
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot · Dealer system · Purchase email
Car maintenance · Appointment booking · Identity checks
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.