Hi all, new here. I added SMS chat to one of my agents (assistants) and it works. Some things I noticed which I think are going to preclude VAPI for my customers who want one agent that can provide a great UX over both phone calls and SMS (and eventually other messaging channels): 1. The first message configured for the agent does not get sent on SMS chat, so the user who sent the SMS never sees that message. The agent just jumps into the middle of the conversation without any kind of hello, welcome greeting, or identification of who they are. It’s not a good UX. 2. There’s no way I know of to put instructions in the system prompt that handle differences between voice and text communication. For example, currently when the agent texts back numbers, it sends the words, so an address like 835 Any St comes out in the text message as “eight hundred thirty five Any Street”. Not a good UX. In text messaging it should be “835 Any St” If there was a dynamic variable I could put in the system prompt to indicate the channel used to reach the agent (eg

{{contactMethod}}

), I should be able to address these issues in the prompt, but I don’t see a way to do that with SMS. So I am very nervous about the ability of VAPI to support good SMS conversations. I’ve had good success with voice+SMS agents with other agents I’ve built directly on top of Twilio, where the prompt can have a section with different instructions for voice vs text as needed.