<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/745f8784-f3ef-41bb-be1d-543c2b4e3c43/bf818a0c-5f35-4853-abca-8421cb160547/Favcion_Typie_colors.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/745f8784-f3ef-41bb-be1d-543c2b4e3c43/bf818a0c-5f35-4853-abca-8421cb160547/Favcion_Typie_colors.png" width="40px" /> Right now we’re a little in between updates 🤫 While we (slowly) deprecate message opt-ins in favour of Journeys, we still need to create a message opt-in that acts as a sort-of “bucket” that collects the subscribers. So excuse us, because this is going to seem weird…🙃
</aside>
Go to Automations → Message Opt-ins
Select Add opt-in. A window will open
Name your opt-in
Add placeholder
as the Opt-in Trigger (don’t worry, we’ll fill this out later in Journeys…see, weird 😉)
Select Save & Next
On the next screen, select the grey rectangle on the left. Then Save & Next (leave blank)
Now select the grey rectangle on the right. Then Save & Next (leave blank)
On the Opt-out page, add your opt-out keywords like STOP
Now we need to add a blank template by selecting Create Template → clicking through to Save (we’ll cover this with a Global opt-out flow):
On the final page, select Finish
Now, we continue the setup in Journeys.