IN BRIEF
The Mobile App Not Downloaded After Enrollment workflow automatically identifies families who have not downloaded the iClassPro Mobile App or your branded app within a specified number of days after their student’s first enrollment. It sends a message encouraging them to download and use the app for easier access to schedules, payments, and communication.
- Overview
- Accessing the Feature
- Step-by-Step Instructions
- Best Practice Recommendations
- Troubleshooting & FAQs
- Related Articles
Interactive Demos for configuring Autopilot workflows can be found in the Education Corner, accessible from the Office Portal's "Welcome" screen.
Overview
The Mobile App Not Downloaded After Enrollment workflow helps promote Mobile App adoption by automatically contacting new families who have enrolled but not yet downloaded the app. It monitors enrollment activity and sends reminders after a configurable waiting period.
- Workflow type: Event-driven
- Trigger: A family’s first-ever enrollment creation
- Purpose: Encourage families to download the Mobile App soon after enrollment.
Accessing the Feature
- From the Office Portal, navigate to AUTOPILOT>WORKFLOWS>"Add a Workflow."
- Locate Mobile App Not Downloaded After Enrollment in the list of workflows.
- The workflow will automatically be copied to your account and will open in the Workflow Editor.
- After configuring the workflow, Save your changes.
- When you are ready, Enable the workflow to begin using it.
NOTE: Only account administrators or staff members who have been granted “Admin Access” permissions can copy or edit Autopilot workflows.
Step-by-Step Instructions
- Open the Mobile App Not Downloaded After Enrollment workflow.
- Review the following workflow details:
- Trigger Type: Event-driven – triggers after the start date of the family’s first enrollment.
-
Communication Template Used: We Have a Mobile App!
- NOTE: This template is located under SETTINGS>SETUP>GENERAL SETTINGS>COMMUNICATION TEMPLATES>"Custom" tab.
- Configure the following options:
-
Wait for Action – Defines how long the System waits after the first enrollment start date before checking for a downloaded app.
-
This value defaults to 3 days.
- NOTE: When the workflow is triggered, the system WILL NOT count any enrollments for classes that have already occurred for the day. However, if the class has not yet met as of the time the workflow is triggered, these enrollments WILL be counted.
-
This value defaults to 3 days.
- Send Communication by Family – Sends one message per family.
- Reply To Email – Defaults to the email address associated with the first enrollment if not provided.
- Send Email / Send to All Emails
- Send SMS / Send to All SMS
- Send Push Notification
-
Wait for Action – Defines how long the System waits after the first enrollment start date before checking for a downloaded app.
- After configuring the workflow, Save your changes.
- When you are ready, Enable the workflow to begin using it.
Additional Options
-
Communication Templates: While staff cannot select a different communication template, the email and SMS versions of the "We Have a Mobile App!” template can be edited under SETTINGS>SETUP>GENERAL SETTINGS>COMMUNICATION TEMPLATES>"Custom" tab.
- NOTE: Unlike other Autopilot communication templates, this template is located on the “Custom” tab.
- Opt-In Compliance: Autopilot always respects individual email and SMS opt-in preferences when sending messages.
- Push notifications: Because the Mobile App is required to receive Push notifications, there is no need to enable and/or customize the “Push Notification” version of this communication template.
Best Practice Recommendations
Configuration Tips
- This workflow is likely to have multiple instances to serve as a regular reminder throughout the student's first month to download the Mobile App. The best practice would be to have this workflow configured to run three times.
- 01 day: “Don’t forget to download our Mobile App!” (SMS)
- 14 days: “Did you know we have a Mobile App? It's a great way to keep up with your child's progress!” (Email)
- 30 days: Email again
- Include both App Store and Google Play links in the communication template for convenience.
- Personalize the message by highlighting how the Mobile App benefits families (e.g., scheduling, payments, class updates).
Operational Tips
- Consider pairing this workflow with First Class Enrollment Follow-Up workflow for a complete post-enrollment communication plan.
Troubleshooting & FAQs
-
Why didn’t the workflow trigger for a newly enrolled family?
- The workflow only checks for the family’s first-ever enrollment. If the family previously had an enrollment, they will not receive this message.
- When the workflow is triggered, the system WILL NOT count any enrollments for classes that have already occurred for the day. However, if the class has not yet met as of the time the workflow is triggered, these enrollments WILL be counted.
-
Can I send a second reminder later?
- You can create a separate custom workflow with a longer “Wait for Action” delay if you want to send an additional message.
-
What if the family downloaded the app after the workflow was scheduled to run?
- The workflow checks app download status at the time it runs. If the app has been downloaded by then, the message will not be sent.