Appendix
Last updated
Was this helpful?
Last updated
Was this helpful?
This appendix outlines the contents of the Scheduling and Follow-Up tutorial and provides some links to more in-depth documentation. Return to this document any time you want to review:
Digital scheduling
Timers and reminders
Automatic outreach and TCPA compliance
Creating and managing multi-Step Journeys
Appointments are made via the Web Control, which must be associated with a and an .
Schedule Objects are defined in .
Availability Schedules are defined in .
Selecting an appointment time in a Scheduler Web Control automatically saves the relevant information to the associated Schedule Object, but if you want to save the appointment information locally, you will need to use the Action within the Scheduler's to define a local variable as event.value.
Local variables are defined and managed in the .
Working comfortably with appointment information requires familiarity with the data type as well as . Some useful Airscript functions include:
Initializing the Actor with set values for different variables in the Actor namespace influences the behavior of outgoing messages in different ways.
An appropriate value for actor.calendar_restriction must be set for Notifications send from a Journey Step to be TCPA compliant.
If appropriate values have been set for actor.region and actor.timezone, the correct value for actor.calendar_restriction will be generated automatically.
Assuming the Actor is initialized properly, all Notifications sent from a Journey Step will be TCPA complaint. Enforcing TCPA-compliance while scheduling a Notification within an Action Chain, however, requires the calendar restriction be set manually.
Steps are subsections of an application flow.
Each Step must begin with a new Web Flow, but Web Flows and Journey Steps are distinctly different things.
Journey Steps can contain any number of Web Flows.
Web Flows are typically built around a specific purpose, such as filling out an individual form or making a single appointment. Meanwhile, Journey Steps conceptualize a broader perspective focused on funnel milestones.
Actions can be associated with a timer by nesting them under the Action in any .
To send reminders, it is common to nest a Action under the Start Timer Action.
SMS Notifications that can be sent through this Action are defined in .
Timers can be canceled using the Action.
The must be initialized before outgoing messages can be sent.
An appropriate value for actor.phone must be set to send .
An appropriate value for actor.email must be set to send .
Values for variables in the Actor namespace are set via the Action. The Actor is initialized via the Action.
To remain TCPA compliant, the Action must be nested under a Action. While setting the timer, under Which Availability Schedule > Custom Expression, you will need to define an Availability Schedule Key that looks something like this:
This string is an Availability Schedule Key that references an out-of-the-box Availability Schedule, encompassing all times that TCPA allows messages to be sent given a particular region and timezone, assuming assumes actor. region describes the user's region by its and actor.region describes the users timezone by its .
For more on TCPA compliance, see .
In multi-Step Journeys, users are guided from one Step to another using the Action.