Original Summary

I wanted my app to answer real phone calls, not just texts! Here's the order I actually did it in. First I bought a number instead of trying to use my own cell. Twilio and Telnyx both work fine for this; I went with the one whose SIP setup made more sense to me at 11pm. Second, I set up a WebSocket server that the phone number could stream audio to. This is the part people skip. Then they wonder why their agent lags. Call audio comes in as a stream, not a file. Your server needs to handle it live. Third, speech to text. I tried Whisper first since it's what I knew. Then I moved to Deepgram because streaming STT out of the box saved me a bunch of glue code. Fourth, the actual brain. I kept this boring on purpose. A small state machine that knows what question it's on beats a clever prompt that can wander! Grok and Gemini both worked for the reasoning step. I just picked whichever answered faster in testing. Fifth, text to speech going back out. ElevenLabs and Cartesia both sound fine; the thing that mattered more was cutting the silence between the caller finishing and the agent starting. Sixth, I used ngrok to test the whole pipeline locally before touching a real phone number. That saved me from debugging DTMF and VAD issues on a live line. The whole thing clicked once I stopped treating it like a chatbot with a phone number bolted on. It's a different medium! Turns are shorter, silence matters, and callers hang up if the pause runs a beat too long. Build for that first.   submitted by   /u/Kindly-Duty272 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/25 02:10:09