Create the Interactive Appointment Reminder Flow for Customer Outreach in the New Agentforce Builder
Create an appointment reminder flow that triggers the notification flow you created.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Field Service and Foundations. Also available with Einstein 1 Field Service Edition or Agentforce 1 Field Service Edition. |
| User Permissions Needed | |
|---|---|
| To open, edit, or create a flow in Flow Builder: | Manage Flow |
The Field Service: Collect Service Appointments for Reminders flow is a Schedule-Triggered flow. Before you begin, review the Schedule-Triggered Flow Considerations.
- In Setup, find and select Flows.
- Open the Field Service: Collect Service Appointments for Reminders flow.
- Click Save As New Flow.
- Enter a label. The API name is populated for you.
-
Connect the notification flow.
- At the end of the flow, under the Yes path of the Does Contact Have Mobile Phone Number? Decision element, add a Subflow element.
- Select the notification flow that you created.
- Select to include the input values.
- For operationType, enter AppointmentReminder.
- Determine if you want to send a second reminder. For sendSecondReminder, select True or False.
- For serviceAppointmentId, select Triggering ServiceAppointment > Service Appointment ID.
- Save and activate the flow.
You might see this warning after saving the flow:
Warning: For a schedule-triggered flow, specify the default workflow user in your org’s process automation settings.
Explanation: The Field Service: Collect Service Appointments for Reminders flow is a Schedule-Triggered flow that runs daily at 7:00 AM. Scheduled flows aren’t run by the logged-in user. Instead, the org’s Default Workflow User runs them. If that setting is empty, the flow has no user context to run under, which can cause it to fail or behave unpredictably at runtime.
Solution: From Setup, go to Process Automation Settings. Set the Default Workflow User to an active user, typically an admin or a dedicated integration or automation user.
