Name of Feature/Request: Appointment data set for workflows
What financial, time savings, or quality of life improvements will occur from this: To have a workflow data set for Appointments | Frequency: 20-30 times per day | We would like to be able to tailor the notification email via a Workflow which sent from a) specifically from one of our 6 physical locations, b) with specific information about the Sales Consultant working the Appointment, and c) specific to the “Sales Consultation” Appointment Type. We would use this as a follow-up to scheduling a consult which we schedule at present 20-30 times per day for our team of 12 sales consultants
Attempted Solutions So Far: Currently they are sending the emails one at a time manually
Digging deep - Any additional Why behind this request / How was this accomplished before Striven in what system or software: Original Description: Hi there! We are wondering why there isn’t a database for Appointments available in Workflows. Our specific current desire is to construct a workflow that emails specific information to customers who have scheduled an in-home consultation with one of our outside sales team members. We can use Notification and Portal Content for this, but it applies to ALL Appointments when we do make any changes there to customize the information inside the notification. Thanks for your consideration. Dan
The initial merge fields desired here are [[Appointment-Date]] and [[Appointment-Time]]. Rather than modify the Appointment Created-External Notification content, which changes the content for ALL Appointments regardless of type, we would like to be able to tailor the notification email via a Workflow which sent from a) specifically from one of our 6 physical locations, b) with specific information about the Sales Consultant working the Appointment, and c) specific to the “Sales Consultation” Appointment Type. We would use this as a follow-up to scheduling a consult which we schedule at present 20-30 times per day for our team of 12 sales consultants | Previously accomplished: Not currently a feature
StrivenID: 4352048