As noted in the prior section, all actions share some common properties. However, each type of action has unique features and properties that we’ll describe in detail below. SMS Conversations This action will send the message over to the SMS Conversations page, at which point you’re messaging with the person directly. There is only one filter for this action, and no additional unique properties. Remember, the phone number filter references the number to which the person sent the message, not the person’s phone number. If this is left blank, then every message that reaches this action will go to the SMS Conversations page. As pictured above, the SMS Conversations action is typically at the bottom of the pipeline. If the person’s message doesn’t meet the criteria for any of the other actions, this is how you can ensure it doesn’t fall through the cracks. Reply The Reply action is an easy way to automate responding to an incoming text. You can customize the content of your response and personalize it for the recipient using Lava. The reply action can in some cases eliminate the need for a workflow if a specific message is always to be returned. 1 Message Filter - You can check the content of the incoming text message against key words you provide. You can add as many of these conditions as needed. You can also select whether the message requires "any" or "all" of those criteria to match. 2 Response - This is the content of your organization's response, which will be sent if the incoming message meets the filter requirements. You can personalize the response using Lava, and you can even add an attachment. You can attach JPG, GIF, and PNG images for all carriers, but other file types may not work depending on the carrier and device. Send a few test messages to different carriers and phone types to confirm the attachment is delivered correctly before sending to a wider audience. The example pictured above will only perform the Connect Response action if the words "serve" or "volunteer" are somewhere in the message's text. If the incoming text says "I would like to serve" then the contents of the Response field will be sent to the person as a text message. In this particular example a workflow might also be launched for this message, because the Continue option is enabled. NoteReserved KeywordsIf one of the below keywords is received (as the entire body of the message), the SMS Pipeline will uncheck the SMS box for the person's phone number, as seen when editing the Person Profile. In this case, any additional SMS message processing that may be in the pipeline will be skipped.- STOP- STOPALL- UNSUBSCRIBE- CANCEL- END- QUIT Launch Workflow As the name implies, this action will launch a workflow. You’ll want to configure your workflow to receive information from the pipeline, using the same workflow attribute merge fields we cover in the SMS Pipeline Workflows chapter of the Blasting Off with Workflows guide. Launch Workflow Action 1 Workflow Type - You’ll use the drop down to choose your preconfigured workflow. 2 Pass Nameless Person - You can control whether Nameless person records (see 3 Workflow Name Template - This Lava-enabled field is where you can create a string to use as the workflow name. 4 Workflow Attributes - This lets you pass information, like the person or their phone number, to the workflow you want to launch. See the Give This action enables Text Giving functionality, allowing a person to send a text to donate using their phone. The Give action isn't ready to use out of the box. An administrator will need to configure the settings for the Utility Payment Entry block in addition to SMS Pipeline setup. For details on Text Giving and the required configuration, head over to the Rock Solid Finances manual.