@FlorianAure Agree on the price line. A good setup lets the bot answer, qualify and book a slot, and hands anything that sounds like a quote or a commitment to a human. Bots negotiating gutters with each other is coming faster than anyone's ready for though.
@spencerldixon Built one for phone calls (Patch). What sticks for non-devs is the boring errands: checking opening hours or stock, asking about appointment availability, following up with a supplier. The agent calls from your own number and hands back a transcript and summary.
@Hamiversez Agree, disclosure should be the default. With Patch, the agent opens by saying who it's calling for and why, says the call is recorded, and confirms it's an AI if asked. If the person doesn't want to continue, it hangs up.
@ViralKumar2841@brentdsummers Fair point, and that's the right metric. A text that only says "we'll call you back" is just a slower missed call. Booked jobs per 100 missed calls cuts through the vanity numbers.
@AdamDudleyX That's a nice design. Splitting schema changes from description-only changes makes sense, since a quietly reworded description can steer an agent just as much as a new parameter. Hashes keep the lockfile clean too.
@XFreeze if you're waiting for this to roll out, patch is already supported on any agent like grok @bot in the americas and europe in 10+ languages. just tell @bot to set up patchmcp with your existing phone number https://t.co/l3ESOQyguG
@constantalad@elonmusk Agreed, the summary is the real product. The useful version isn't "call completed," it's a clear outcome: what was actually agreed, what's still pending, and what needs a follow-up.
Completely agree. Suppliers, banks, clinics: so much back office work still lives behind a phone line. That's why we built Patch as an MCP server. Your agent calls from your own verified number, can work through phone menus and wait on hold, then brings back a transcript and summary.
@cozzoio@ElevenLabs@retellai@Vapi_AI@usebland Thanks for sharing the spread, the p90 gap is the useful part. A 2 second tail is exactly where callers start talking over the agent. Did you also measure how fast each one recovers after a barge-in, or just time to first audio?
@rishabincloud@twilio@GoogleDeepMind Nice demo. How are you finding Gemini Live's interruption handling over a real phone line? That's usually the part that makes or breaks a call.
@EslamAHussien@claudeai Nice use of Tasks. Long-running jobs are exactly where this shines. Phone calls are a good example too: a call can sit on hold for minutes, and getting pinged when it's done beats polling.