Send SMS App - Cant Authenticate using alternative Twilio Active Number

[NatalieMoore]

The Send SMS App only works when I use the primary number under the Twilio Account Info Section

 

But I have a second mobile number in the same Twilio account under my other Active Numbers that I want to send from but When I change the number in Airtable send sms app sending fails. 

I tried Creating new API Credentials but that didnt work or I dont know what I am doing there - there was no option to select a particular number,  and I cant find Auth Token and SSID for the number I specifically want to send from. 

Any ideas would be greatly appreciated. 

[NatalieMoore]

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. 

[ScottWorld]

Hmmm… not sure, because I’ve got the Send SMS extension 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.

Alternatively, if you can’t get it to work, there are actually much better SMS providers out there than Twilio, which are much cheaper and much easier to use — and which can all be automated from Airtable using Make’s automations and integrations.

In the USA, we have MessageBird and TextMagic and SimpleTexting and dozens more. But I’m not sure which ones would work in your country.

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

p.s. If you’d like to hire an expert Airtable consultant to help you with any of this, please feel free to contact me through my website: Airtable consulting — ScottWorld