Let’s look at a completed pipeline to see how this all comes together. This pipeline has four actions and was designed to handle inquiries about small groups and connecting. Below each screenshot we’ll highlight the key points. As pictured above, when an incoming text contains the word 'group', an auto-response will be sent to the person with more information about joining a group. In this case the processing stops, because the Continue option is not enabled. If the SMS message doesn't contain the word 'group' then the "Connect Response" action will be evaluated because it's the next in line. If the message contains the word 'volunteer' or 'serve' an auto response gets sent with more information about getting connected to a serving team. The arrow on the action indicates that the continue functionality is enabled, and the next action will run if the message meets the requirements. You'll note in the screenshot above that the workflow action has the same filters as the "Connect Response" action. That means any message which activates the "Connect Response" action will also launch this workflow. Lastly, the pipeline continues down to the “SMS Conversations” action so that a staff member can directly connect with this person. In this case, the "SMS Conversations" action has no filters applied. Knowing this, and looking at the pipeline as whole, all incoming SMS messages will end up in the SMS Conversations page except messages that contain the word 'group'. If we enabled Continue in the "Group Response" action, then every incoming SMS message would go to the SMS Conversations page. In that case, a message containing the word 'group' would not satisfy the "Connect Response" and "Launch Workflow" filter criteria, so those actions won’t be performed. In this example pipeline, if an SMS message is received that says "I'd like to learn more about your services" it would pass through the pipeline straight to the "SMS Conversations" action. No automated replies would be sent, and no workflows would be launched for that message because it does not meet the criteria for those actions. SMS Pipeline Lava You can use Lava to customize and personalize your pipeline’s actions. There are different merge fields depending on whether you're working with the Reply or Launch Workflow action. Launch Workflow Action Lava Below is a list of Lava merge fields you can include in your pipeline when you're working with the Launch Workflow action. These are the same workflow attribute merge fields we cover in the SMS Pipeline Workflows chapter of the Blasting Off With Workflows guide. SMS Pipeline Workflow Lava Merge Fields Merge FieldDescriptionField Type {{ FromPerson.PrimaryAlias.Guid }}The pipeline uses the person's phone number to look up the first person with that phone number. If it finds a match, it assigns that individual's record to FromPerson. If the phone number is used in more than one profile, the pipeline defaults to the first record of an adult with children.Person {{ FromPhone }}The person's phone number, pulled from the inbound message, from the SMS gateway. This will automatically get added to the workflow as FromPhone and will include the country code (i.e., the raw phone number 18645555555).Phone Number {{ ToPhone }}The SMS gateway number where the message was sent.Phone Number {{ ReceivedDate }}The date the message was received.Date {{ ReceivedTime }}The time the message was received.Time {{ ReceivedDateTime }}The date and time the message was received.Date Time {{ MessageBody }}The content of the SMS message that was received.Text or Memo {{ MatchedGroups }}If the RegEx expression provided contains matched groups, they are loaded into an array here. This is an advanced feature, so if you’re not sure what this means, don’t worry. You probably don’t need it.Typically, you fill in a text field with a merge expression of a single result from the MatchedGroups array. Reply Action Lava Below is a list of Lava merge fields you can use when you're working with the Reply action. Note that each uses a prefix of Message. SMS Pipeline Reply Lava Merge Fields Merge FieldDescription {{ Message.FromNumber }}The person’s phone number from the inbound message {{ Message.ToNumber }}The SMS number where the message was sent {{ Message.FromPerson }}The pipeline uses the person's phone number to look up the first person with that phone number. If it finds a match, it assigns the value to FromPerson. If the phone number is used in more than one profile, the pipeline defaults to the first record of an adult with children. This is the full Person object, so, for instance, you'll need {{ Message.FromPerson.FullName }} to get the person's full name. {{ Message.Message }}The content of the SMS message that was received