Better to have a dedicated 2FA campaign or mix with other messaging? 10DLC best practices?

[ahp_sinch]

I'm stumbling through setting up campaigns - I'm sending 80% 2FA and like 20% other (non-marketing) notifications and welcome messages for our service.    The campaign interface asks many questions that seem oriented towards marketing 'campaigns' that don't seem to apply very well for us.

Should I have multiple campaigns for different purposes?   -- like one for 2FA, another for account management, and another for reminders that users have signed up for.   Or is it normal to just mix it all together in one (which is how it seems to work today in non-campaign mode). The cost of multiple numbers and campaigns might be a problem for our tiny start-up.

If we mix all purposes in one campaign I'm concerned that a user who needs 2FA to log in might just casually send an opt-out on a regular notification message - on the other hand, if they see that the same message stream includes log-in stuff they might understand that it is all tied together and not just block it all.  Any advice from people who have done this?

Can multiple campaigns use the same 10DLC number?   

do opt-outs affect just the one campaign or any campaign with that 10DLC - or the whole brand?   

In general the whole requirement to switch to 10DLC campaigns is confusing me - it was never communicated clearly when we signed up and implemented the SMS api and customer service just says to read some unhelpful pages that are not oriented for a developer or an existing user.

[Alex_Sberna]

Hi ahp,

There are multiple options available. It all depends on the kinds of volume you're sending. One option could be the "low volume mixed" campaign and then choose the sub use cases that are applicable for you.

We also have a Verification API product that might work for your 2FA needs and then you could reserve your 10DLC campaign for the other uses you need.

If you could provide more details about the kinds of volume you're sending and what you're trying to accomplish I can go back to the team and try to get a more specific and detailed answer for you.

Thanks,

[ahp_sinch]

Hi Alex,  we are very low volume currently - like less than a dozen messages a day, total.   We expect this could ramp up to hundreds of messages per day in the next 6 mo.  and thousands to 10s of thousands per day if everything works out right over the next couple of years.    I expect that the mix of 2FA to general notifications and account management to be about 70% : 25% : 5%

We are using the verification API already, is that already something outside the campaign stuff?  Do I need to change it at all as I migrate to campaigns?

[Alex_Sberna · Accepted solution]

So, if you are using Verification API already, you shouldn't need to use the number you have assigned to your 10DLC campaign to do 2FA. The Verification API has its own pool of numbers it uses to send SMS to users for logging in/authorizing.

And Verification is different from 10DLC, so you don't need to change it as you migrate to campaigns.