Send SMS App - Cant Authenticate using alternative Twilio Active Number

I think I need to create a sub project and have the porting team port the number to the subproject - doesnt look like I can do it myself if it is an SMS number. 

Hmmm… not sure, because I’ve got the Send SMS app working with all of my clients’ alternative Twilio numbers.

Does it work if you try it with Make’s Twilio integrations for Airtable? If you’ve never used Make before, here’s how you can instantly trigger a Make automation from Airtable.

However, if you still can’t get it to work, it may be a blessing in disguise, because Twilio is actually a terrible SMS provider, and I do not recommend them. Twilio is extremely complicated to setup & maintain, Twilio is extremely overpriced, and Twilio’s customer support is essentially nonexistent.

There are actually much better SMS providers out there than Twilio, all of which are much cheaper and much easier to use — and can all be automated from Airtable using Make’s automations and integrations.

Instead of Twilio, there is MessageBird, TextMagic, SimpleTexting, and much more.

SimpleTexting is my current favorite, and I give a demonstration on Airtable and SimpleTexting on this Airtable podcast episode.

I’m currently in the process of switching several of my clients away from Twilio to these other services, because they’re so much easier and cheaper.

If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable. 

I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

I see it’s been a while since you’ve posted, but I just want to ask—has anyone here had success using a Twilio number that's already active in another integration? I’m curious if re-verifying or managing sender IDs in Twilio made a difference for anyone. I'm trying to figure out if switching to a new subaccount could be a workaround or just adds more issues.

I ran into something similar before. We ended up setting up a system where the primary number handles all outgoing text messaging, and any replies get forwarded to the right person. It’s simple, keeps messages from getting lost, and makes sure customers actually get a response.