![]() ![]() This will tell you the limits that each carrier will allow. From your Customer Dashboard you will need to register the brand you are sending as, and register a campaign. This is a carrier-imposed system that further dictates what and how many SMS messages you can send. ![]() 30/sec is also our API limit, so you will need to contact to get that raised if you want to send more than 30/sec no matter what.įor US traffic you will also need to register any Application-To-Person SMS traffic (A2P Traffic) with the carriers ahead of time through what is known as 10DLC. ![]() So as you mentioned 1/sec or 30/sec depending on the number type. Those are general limits that, by default, apply to all accounts and then the country they are sending in. The first is the throughput you listed above. Then you only need to schedule that single lead to request the bulk-based webhook campaign, since you only call the webhook once.There's a few things that go into the actual number of messages you can send per day. Like here you would call the lead "Resource: Demand Response SMS" or something like that. You create a Resource Lead by calling it by the name of a program, campaign, special process, etc. It's similar to the idea of Conference Rooms, Copiers, and Printers being resources in a Microsoft Exchange or other collaboration environment, alongside the actual people. ![]() This is the concept of a "Resource Lead": a person in your Marketo db that represents a process or service rather than a human. "(You can send the webhook in the context of a special lead you dedicate for this purpose, so you can use the Marketo batch scheduler as you usually do.)"Īlso, what do you mean by this statement? Right, this is a Twilio-specific meaning of "segment." Not related to Mkto segments. When you say Notify segment, is this segment located within Twilio's platform and not Marketo? (You can send the webhook in the context of a special lead you dedicate for this purpose, so you can use the Marketo batch scheduler as you usually do.) Then on the day of the send you only call the webhook once, telling it to notify everyone who's been added. The way to use Notify in this case is to run everyone who qualifies through a webhook that only adds them to a Notify "segment" you can run this webhook the day before the send, for example, or whenever you know someone should be added to the future send. In this case it's better to use the Notify service, which can send all your messages with a single API call. So for high-volume, time-sensitive sends, the key is to get things into Twilio faster than a webhook's inherent speed limitation. At that stage, a shortcode is vastly better because they'll send the outbound SMS at 100 messages per second if you have a shortcode but only 1 per second if you do not - in other words, you get 100x faster delivery with a shortcode. The shortcode difference comes into play after the webhook stage is complete and relates to how fast Twilio pulls messages off its internal queue and actually sends outbound via SMS. You'll never have to worry about this w/a Marketo webhook because Mkto will only parallelize ~8 concurrent requests. AFAIK the Twilio limit (regardless of shortcode or full sending #) is 100 concurrent inbound requests to the API per API key. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |