Workflows contain a message or a series of messages that are activated by a trigger event. There are multiple ways a workflow can be triggered, some of those methods include via API, QR code, the Rally Zapier integration, and Keywords (most popular method). A Workflow can also have multiple triggers as well. Additionally, all Workflows are associated with a specific Keyword on a specific phone number such as 24-365 (the Rally Shortcode) or your dedicated Toll-Free number (Essential or higher plans). The most common Workflow trigger event is by someone texting your Keyword to 24-365.

Workflows are comprised of a Prompt or Prompts (optional) and a Final Response. Depending on your use case your Workflow might only include a Final Response.
​
​What are Prompts?

Prompts are designed to capture data, such as email address, name, etc. A Workflow can have multiple Prompts and the first Prompt in a Workflow is triggered by either someone texting the associated Keyword or by one of the methods mentioned above. Each subsequent Prompt is triggered by a reply, for example, let's say you have a Workflow with two Prompts the first Prompt is What is your name? and the second Prompt is What is your email address? The first Prompt will be sent when someone texts your Keyword (or any of the other trigger events), the second Prompt will only be sent when there is a reply to the first Prompt. This is why it is crucial to phrase your prompts in the form of a question.
​
​Prompt Components

Prompts are composed of three components, Contact Field, Parameter Name, and Body. Here is a brief description of each:
​
Contact Field (Optional): the contact field is where you select which field in your accounts contact record you would like updated when the respondent replies to the prompt. For instance if you select First Name in the contact field then the response provided by the respondent will be added as the contacts First Name in your accounts contact records. *The number of fields available for selection is currently limited while this feature is still in Beta.

Parameter Name (Optional): the Parameter Name field is where you provide the value for your pass-through parameter. For example, if you are trying to pass an email address to a Classy.org form your Parameter Name would be email but in other systems, it might be email_address.
​
Body: this is where you add the message people receive when they trigger your prompt. For example, if you trying to collect an email address your Body might be: What is your email address?
​
​

Final Response
​

Depending on your use case the Final Response will either be the last message in your Workflow (if you are using Prompts) or the first and only message in your Workflow. If you are not planning on collecting any data in your Workflow then we recommend only using the Final Response. If you want to include a link to a website such as a donation page then we recommend doing so in the Final Response.
​
The Final Response is composed of three components, the Destination URL field, the Map Link Button, and the Final Response body. Here is a brief description of each:
​
Destination URL: if you would like people to click a link to go to another site such as a donation page then include the link in the Destination URL field. Do not add any additional parameters to the link such as UTM Parameters. You will do this when you map the link.

Map Link button: this is where you can select what parameters you want to pass-through your URL. In addition to passing values collected in your prompts (if you are using them) you can also configure your UTM Parameters here.
​
Final Response Body: This is where you add your message if you are using the Destination Url Field you will want to add {{destination_url}} to the message. This will create a shortened trackable link. An example Final Response body message utilizing the Destination Url could be something like Thank you for your support to complete your gift click here {{destination_url}}
​
​
​