pardot scheduling blasts based on time zone

#Pardot scheduling blasts based on time zone code

The User Phone and Email fields are who the text is coming from, since TextUs allows text messages to come from specific users (as opposed to a generic short code, which is what is available from MobileStudio). The Message Text is what you are going to want the SMS message to say.

The first step is creating a custom object in Salesforce with the following fields: For this example, we are going to create a record on a custom record type called Marketing Cloud Message. These are both actions that can be triggered from Marketing Cloud’s Journey Builder. You can trigger the Process Builder by creating a record or changing a record. When you build out a process, you will be calling that Apex class and sending it values that it needs in order to send a message to the correct person. It is also not yet well documented, so the below screenshot applies to TextUs Next, which I have built and tested with the guidance of one of their developers.īoth TextUs for Salesforce and TextUs Next come with an Apex class that is installed with the managed package. TextUs Next is not an the AppExchange, but is available from the company. TextUs for Salesforce is what you will find in the AppExchange and the implementation guide on that listing has a nice step-by-step guide to deploying SMS messages with Process Builder. TextUs has two versions: TextUs for Salesforce, and TextUs Next. For this example, we are going to focus on TextUs, though Twilio uses the same method to leverage Process Builder. I am sure there are even more options out there. Both TextUs and Twilio have apps on the App Exchange, and both have a method of using Process Builder to send SMS messages. However, if your Marketing Cloud is connected to Salesforce core, you can leverage Process Builder to achieve this integration in a fraction of the time with zero coding resources.įirst, you want to choose a third-party SMS service that has an app in the Salesforce AppExchange and leverages Process Builder to trigger messages. The conventional solution to including a third-party service in a Journey is to spend at least 30 hours of development time creating a Custom Journey Builder Activity, which requires creating a web app that takes the Journey data as an input and sends the SMS request out as an API call to the third-party SMS app. There are several third-party SMS companies out there. You want to blast out an SMS nurturing campaign and also allow for a back-and-forth conversation to continue on.

So, now we have a use case for both Marketing Cloud Journeys and two-way SMS. You also want to schedule a dog walker for them over SMS, rather than directing them to your app or website. However, you don’t want to just blast out a coupon code.

#Pardot scheduling blasts based on time zone code

You would like to create a journey that blasts out a SMS message with a coupon code for unengaged subscribers as a way to get them to use your service.

By two-way SMS, I am referencing the ability to have a back-and-forth conversation with the subscriber.įor example, let’s imagine that you are a company that provides dog walking services. So, a lot of marketers look to other solutions for two-way SMS. MobileConnect only allows you to broadcast an SMS and craft auto-responses if the subscriber replies. Combined with Ad Studio, you can even create a Journey that sends your subscribers an email, an SMS message, and a Facebook ad either in tandem or based off of their current and past behaviors. Marketing Cloud has a native product for SMS messages called MobileConnect, which is a great built-in way to combine SMS messages with other types of marketing messaging.