Filter the Lines
Objective
In the next set of steps you are going to filter out all the lines that are actually not allowed to be targeted with a SMS message due to the their opt'ing out at the line level. You can not rely here on Profile consent because this is a line level target.
Setup Split activity
- Click the + icon on the bottom transition of the Fork activity and select the Split activity on the popup.

- In the right rail update the Label to state the following: Filter out opt'd out lines

- In the right rail expand the default segment Subset section and click the Create filter button

- Add a condition to ensure that you remove all Customer Lines that are opt'd out of SMS messaging.

You need to figure out how to create the condition but the final result should match the screenshot above. You got this!
- Click the Save button in the upper to save your work. Your canvas should look like so now...

Add the SMS Activity
- On the workflow canvas, click the + icon after the split condition you added and select the SMS Activity


- In the right rail click on the Edit SMS button to start configuration of the SMS message

- In the top nav click on the Actions menu item and then from the SMS configuration drop-down select the SMS channel Relational-SMS-Multi-Entity.

Oh no 🫨! Why are you getting No results? Did your Summit lab break? Did your instructors screw this up? FREAK OUT!!!!!!!!!
Freak Out Moment
The transition of the fork currently has a targeting dimension of Customer Line (i.e what table the current result relates to in the Relational Store). What is unique with Orchestrated Campaigns though is you always join back to the Real-Time Customer Profile at send time so delivery and tracking information from messages is attributed to a profile. This join was pre-build for you from the Customer Account table. The channel configuration for SMS was already setup for you beforehand and it currently looks like so...

How you read this is as follows:
- Deliver one message per the target dimension (i.e. Customer Account) on the number of related records found in the secondary dimension (i.e. Customer Line)
- Execute each SMS delivery using the mobile phone number found in the secondary dimension (i.e. Customer Line)
This unique ability to send many messages to one profile is one of the primary features of Orchestrated Campaigns that makes it different from Journeys.
So how do you get this to work? Add a change dimension 😀
Add Change dimension
- Click the back button on the SMS edit screen

- On the workflow canvas, click the + icon between the Filter and SMS activities and select Change Dimension.

- In the right update the change dimension with the following information:
- Label: Convert Line to Account
- New target dimension: Customer Account

- Click the Save button in the upper right of the canvas to save your work. When done your workflow should now look like this...

SMS Message Configuration
Now that you've fixed the workflow let's try re-configuring the SMS.
- Click on the SMS activity in the workflow canvas and then, in the left rail, click on the Edit SMS button

This screen takes a while to load. I know its annoying, trust me its being fixed
- In the top nav click on the Actions menu item and then from the SMS configuration drop-down select the SMS channel Relational-SMS-Multi-Entity.

Feels good doesn't it 😮💨
Recap
You made it through this one and hopefully learned two very important things:
- You final results targeting dimension has to match the channel configuration you want to use
- The Change dimension activity is likely going to become your best friend for ensuring this happens