Call4me puts Claude Code and Codex on the phone with businesses at $0.25 a minute

Khami built it because he spends much of his workday in a terminal and wanted phone errands there ^[15]. He said in his launch thread that he had already used it for dozens of calls ^[16]. The listed clients include Claude Desktop and ChatGPT as well as the two coding agents ^[4]. Once connected, the service says it can get through phone menus and hold queues. It says it handles reservations, scheduling, service questions, quotes and cancellations ^[5].

The billing design is good engineering for a tool an agent might call in a loop. Each call holds its worst-case cost against a prepaid balance before dialing ^[6], so total spend is capped at whatever the user loaded. The minimum load is $10 ^[2]. At $0.25 a minute, $10 buys 40 minutes of talk ^[1]. The first U.S. number comes with the account, and extra numbers cost the carrier rate plus an upfront charge and a monthly renewal ^[7]. The agent cannot overdraw a prepaid balance, whatever it thinks the dentist said.

Commitments are harder to cap than money. Call4me publishes its example calls and recordings on its site ^[18]. In the dentist call, dated September 30, the agent negotiated a Monday slot with the same provider and the office confirmed the change ^[8]. The Costco tire-center call found the order had arrived, but no installation was booked ^[9]. An Amazon Pharmacy representative agreed to mark delayed prescriptions as important, but the transcript did not confirm the review was completed ^[11]. Add the junk-removal address error ^[10] and one of the four ended with a confirmed outcome and no follow-up ^[2]. The vendor chose which examples to publish, so they cannot be read as a failure rate for anyone else's errands.

Telnyx, Call4me's telephony provider, records each call, and users get the recordings and transcripts ^[12]. Runtimewire's assessment is that those records let a user review a conversation but do not guarantee the agent understood every detail or that the business followed through ^[17]. In the junk-removal case the error was the street number ^[10]. That is a detail the business acts on, and a skimmed summary can miss it.

For a team, the permission that matters is the MCP authorization. The setup Runtimewire describes has three steps: add the server, authorize access, give a request ^[4]. The report does not mention any step where a person approves each call before it goes out. The service's rules restrict the type of call. Telemarketing, surveys, emergency and premium-rate calls are barred, along with harassment, threats and impersonation ^[14]. Nothing in those rules checks whether a booking matches what the user wanted. That check belongs to whoever reads the summary. I think the authorization should go to the people who would answer for a wrong booking, and the prepaid balance should be kept small enough that a bad afternoon costs little.