@Nicholas_Manojl I work at a CPaas company called Telnyx and the reason we throttle long code numbers is to prevent bad actors from easily signing up for our portal and sending a bunch of spam to people before we catch them.   If you want to increase your throughput on long code you can make a case to our sales team who will increase it if your use case is legitimate.   The reason why you can send more messages per minute with short code or toll-free numbers is because you have to go through a verification process to obtain these numbers and specify how you will opt people in and out.   I discuss the throughputs of different number types as well as their different pros and cons (international capability, number cost, message cost, 2 way capability) in this post if anyone wants more detail:  https://theworkflowpro.com/marketo-sms-marketing/ ... View more

@Jay00031987  my company Telnyx has just launched a Whatsapp API: https://developers.telnyx.com/docs/api/v2/whatsapp     You can integrate this into Marketo webhooks as you would do normally when integrating with Twilio or Nexmo. If you want a Telnyx specific example of how to call the Telnyx API from a Marketo webhook then you can see this post: https://theworkflowpro.com/marketo-text-messaging/     Here is the product page to give you more info about it: https://telnyx.com/products/WhatsApp-api ... View more

Sharing this screenshot here to supplement what Sanford already confirmed about using lead tokens in the webhook body. You can also  use the {{campaign.description}} token in the SMS webhook so that you can change the SMS message from smart campaign to smart campaign and still use a single webhook (as detailed in this blog post: https://theworkflowpro.com/marketo-sms-integration/)   ... View more

While this post uses a different vendor it does detail how to incorporate an SMS webhook into your smart campaigns and how you can  use the {{campaign.description}} token in the SMS webhook so that you can change the SMS message from smart campaign to smart campaign and still use a single webhook: https://theworkflowpro.com/marketo-sms-integration/ ... View more

Hi Ronen,   I built the workflow that @Phillip_Wild mentioned in Zapier.   https://theworkflowpro.com/2-way-sms-marketo/   The post above will show you how to  Parse the inbound SMS for keywords and choose an appropriate response Send the SMS response to the customer and optional alerts to your team Set the person's SMS subscription field in Marketo to TRUE or FALSE if the "STOP" or "START" keywords are present As both Sanford and Philip mention Twilio (or in this case Telnyx) have inbuilt functionality to stop SMS from being sent to a person who replies with a "STOP" keyword. This Zap will let Marketo know the person is unsubscribed so you are not unnecessarily sending SMS from Marketo that will not be delivered. ... View more

@Pavel_Plachky your use case of sending confirmation SMS messages to customers and handling responses is something I have built in Marketo and Zapier:   https://theworkflowpro.com/marketo-sms-integration/ https://theworkflowpro.com/2-way-sms-marketo/ The first post shows you how to use webhooks to send confirmation and reminder SMS messages to customers when they fill out a form to register for a webinar.   The second post shows you how to handle customer responses by: Parsing the inbound SMS for keywords and choosing an appropriate response (which addresses @Nicholas_Manojl 's point " but what about the times when someone replies to an SMS with something other than one of these predefined words " by using a default response to reach out to support if the parser does not find any keywords Sending the SMS response to the customer and optional alerts to your team Sets the person's SMS subscription field in Marketo to TRUE or FALSE if the "STOP" or "START" keywords are present Also to provide more detail on @Nicholas_Manojl 's comment. What he refers to as a "word" number is an alphanumeric sender id and this can only be used for one-way messaging as he correctly states. If you want 2 way SMS then you will need to use long code, short code, or toll-free numbers with SMS capability. There are different pros and cons to each number type (i.e. international capability, number cost, SMS cost, message per minute rate, 2 way capability), which I summarize in this post:  https://theworkflowpro.com/marketo-sms-marketing/ ... View more

@Trevor_Sparks I actually built out this exact workflow in Zapier!   https://theworkflowpro.com/2-way-sms-marketo/   In the post above, I show how to: Parse the inbound message for the "STOP" or "START" keyword Use the Marketo REST API to lookup the lead's email based on their phone number Use the lead's email to update their SMS subscription to TRUE or FALSE ... View more

Just to provide people with another vendor option for SMS I recently published a blog on the Marketo forum that shows how to use webhooks to integrate with the Telnyx SMS API:    https://theworkflowpro.com/marketo-text-messaging/     @Victor_Herrero I saw your later comments about wanting to do number lookup, response mapping, and use tokens to populate the SMS message.   This blog post shows how to do a number lookup (for free!) with webhooks and map the response variables to Marketo fields: https://theworkflowpro.com/marketo-data-enrichment/   This blog post shows how to use the {{campaign.description}} token in the SMS webhook so that you can change the SMS message from smart campaign to smart campaign and still use a single webhook: https://theworkflowpro.com/marketo-sms-integration/ I hope these posts are helpful. If there are any questions let me know.   Full disclosure I am a Telnyx employee. I have been using Marketo for close to 2 years now and got tired of seeing all these Twilio posts so I wanted to balance the scales and let people know that there are other options out there. ... View more

Thanks Sanford! ... View more

Hey Sanford,   Yes, there is an SFDC sync step in the "02a MQL Request with Routing campaign".   So would you say this is expected behavior?   It seems odd to me because SFDC is changing these fields as opposed to a flow action within the campaign, which is what this insinuated to me initially ... View more

@SanfordWhiteman linking this post here: https://blog.teknkl.com/marketo-json-fields-in-velocity/   Since I think it will be helpful to others so they can see examples and read about the pros and cons e.g. not being able to use the "contains" keyword with JSON formatted strings in Marketo ... View more

I do not have direct experience using recurring Zoom webinars   I imagine you would want to create a new Marketo program for each instance of a recurring webinar to track the attendants for each instance ... View more

We use Zoom for webinars which syncs registered leads to Marketo just like GTW   They do have recurring webinar functionality: https://support.zoom.us/hc/en-us/articles/216354763-How-to-Schedule-A-Recurring-Webinar ... View more