Grok Makes Calls for People: The Demo Goes Smoothly, but Apple Support Hangs Up as Soon as It Hears AI

Elon Musk retweeted a demo: Grok @Bot can now make calls on a user’s behalf. The demo came from Sawyer Merritt, and the task was very everyday: call Barbara Merritt to ask about returning a door handle. The user only has to tell the bot whom to call and why; the bot handles the rest of the conversation.

The call interface shows real-time transcription. After Barbara answers with “Hello,” the bot introduces itself: a virtual assistant representing Sawyer Merritt, on a recorded line, asking whether Barbara is available. When additional information is needed, an input box pops up in the interface; the user types or selects something, and the bot relays it to the other person. Sawyer Merritt’s own words were “pretty incredible.” Elon Musk’s retweet was just one line: “Try asking Grok @Bot to make calls.”

This feature addresses the waiting and repetitive communication involved in outbound calls. Returns, appointments, checking business hours, and waiting in support queues are all low-value calls that eat up time. Some commenters say they’ll never call customer service themselves again, some want to have Grok wait on hold with the Danish tax authority’s hold music while they spend time with their kids, and others want to use it to screen incoming calls.

The comments are more real than the demo. User Devin Olsen said he had Grok call Apple, the agent asked whether it was an AI assistant, Grok said yes, and the support agent hung up—twice in a row. Another user asked why their bot had a female voice and sounded seductive. Someone asked how to get the feature, since their version was 0.78.1 but there was no entry point. Users in the EU, Canada, and Washington State all said they couldn’t use it. Someone switched to a US network just to use the feature.

Others pointed out an awkward design issue: while the bot is on a call, the user has to sit nearby watching the transcription and answer the bot’s questions at any moment. This is more of an outbound-call assistant. A digital stand-in is still a long way off. The bot can handle standard procedures, but when it runs into identity verification, authorization, or a last-minute change of mind, the decision still has to go back to the user. In the demo, asking about a door-handle return is a low-risk task and a good place to start. High-value negotiations and calls that require strong identity verification should not be handed to it for now.

What’s more telling is the moment Apple support hung up. The bottleneck for AI outbound calls is whether the other party is willing to keep talking to AI. Whether the voice sounds human is actually secondary. Proactively disclosing that it is AI is a compliance move, but it also triggers defenses. In the demo, Grok says from the start that it is on a recorded line and is a virtual assistant. That’s the right thing to do, but it also turns connection rates into a product problem. Some commenters want to use it to call Verizon and refuse to answer support agents’ questions; that kind of use will accelerate the other side’s rollout of AI screening.

Regional restrictions also show that it’s not yet a general-purpose tool. Users outside the US are waiting, and parts of the US are blocked by law. The feature’s entry point, voice, accent, and usage limits are all being criticized. Grok @Bot can dial for you, transcribe for you, and ask you for instructions. What it can’t take over is responsibility. Start by using it for returns and queueing, and don’t rush to hand over important calls.

Reference links: Elon Musk’s tweet, Sawyer Merritt’s demo.