Original Summary

I wanted a plain text interface to trigger a phone call and read back what happened! No app, no dashboard. Just an SMS in, a call out, a result back. First step was picking a number. I grabbed one from Twilio and pointed the voice webhook at a small server I run behind ngrok while testing. Texting didn't need a separate number; the same one handled both. Second step was the call leg. I used a WebSocket to stream audio both ways instead of waiting on recorded prompts. That part took the longest to get right. VAD kept cutting off the start of replies until I loosened the threshold. Third step was speech. STT ran on Deepgram, fast enough that the call didn't feel laggy. TTS was Cartesia, picked mostly because it started talking quick after the text arrived. Fourth step was the text side. I parsed incoming SMS as commands: call this number, say this line, hang up after done. Each command maps to a short script the call runs through. There's no branching logic beyond that yet. Last step was closing the loop. When the call ends, the server texts back a short line: call connected, or call failed. That's the whole product so far, a text box that makes a phone do something! Biggest lesson: build the hang up path before the happy path. I spent a day debugging calls that just sat there after the script finished, because I hadn't handled the end state at all. Fixing that felt like a small win! Happy to share the webhook setup if anyone's doing something similar.   submitted by   /u/Kindly-Duty272 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/16 01:01:40