Grok Bot books a hospital appointment through phone transfers
@Jayahos5 says Grok Bot called a hospital, waited on hold, handled 2 transfers and booked his wife's appointment while he worked, then added it to his calendar.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Call the hospital to arrange an appointment using the details I authorise you to share. Confirm my availability and ask for approval before committing to a slot, then add the confirmed appointment to my calendar.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @Jayahos5
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- @Jayahos5 reports that Grok Bot booked his wife's hospital appointment after waiting on hold and handling 2 transfers, then added it to his calendar while he worked. He also says his wife hung up on the bot twice, mistaking it for a robocall.
- Human involvement
- The poster delegated the call while he worked. The post does not describe the information or permissions he supplied, any booking approval or a review of the calendar entry.
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
- The poster had Grok Bot call the hospital to book his wife's appointment while he worked.
- The bot waited on hold and handled 2 transfers during the call.
- The poster reports that the bot completed the booking and added the appointment to his calendar.
@Jayahos5 says he had Grok Bot call a hospital to book his wife's appointment while he worked. The bot waited on hold, dealt with 2 transfers and completed the booking. He also reports that it added the appointment to his calendar.
The phone call is the central part of this account. The reported task went beyond drafting a message or finding a telephone number: the bot stayed in the hospital's call process through the hold and transfers until an appointment was arranged. The post gives no call duration, appointment date or hospital name.
There was also a practical snag. The poster says his wife hung up on the bot twice because she thought it was a robocall. He does not explain when those calls happened relative to the hospital booking, so they should not be treated as a documented retry sequence.
The result is a personal report, not an independently checked hospital or calendar record. The post does not describe the information supplied to the bot, a final approval step or which calendar service it used. It supports an administrative booking task, not medical advice or treatment decisions.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @Jayahos5
Frequently asked questions
What did the bot do during the hospital call?
@Jayahos5 says it waited on hold, handled 2 transfers and booked his wife's appointment.
Did it add the appointment to a calendar?
The poster says it added the appointment to his calendar. He does not name the calendar service.
Why did his wife hang up on the bot?
He says she hung up twice because she thought it was a robocall. The timing of those calls is not specified.
More details
About this account
Grok Bot reportedly handled the hospital phone call through a hold and 2 transfers, booked the appointment and added it to the poster's calendar.
Scout supplied the verbatim post and profile capture from the public X API, reported read live on 2026-11-17, and explicitly authorised its use instead of reopening X. This entry uses that supplied capture, not independent retrieval or reproduction. The supplied bio was checked for maker affiliation and self-promotion. Results remain attributed to the poster. The suggested prompt is an editorial addition, not a quoted task prompt.
Credit: @Jayahos5
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot
appointments · phone calls · calendar
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.