A moving company has embedded a taskflow called “Mover’s quote” on their website.
“Request a quote” is the first task in the taskflow that processes online requests for quotes. This task is a published form and can be completed by any member of the public.
A customer visits a page on the website to get a quote and the first task is displayed. The customer completes the questions. One of the questions is a link to an inventory that the customer needs to complete for quoting purposes. (A Google sheet template has been created for this purpose.) The customer needs to complete this sheet, copy the unique link to their sheet and paste the link in the dedicated field.
The Mover is notified of the new request. They click on the link in the notification email to access the taskflow.
This link takes the person to the “Quote” task. When this form was created in the Designer, we specified that the customer’s details from the “Request a quote” task need to be pulled into the “Quote” form. Dynamic field tags were used to pull-in the detail.
After the quote is completed, a notification email containing the link to the next task - “Review quote” - is sent to the customer. The customer clicks the link and is taken to the “Review quote” form. This task is also a published form and therefor the customer does not need to login to view it.
The customer reviews the quote. The Movers might not be available to move on the date the customer requested in the first task. In the earlier “Quote” task, the Mover had the option to propose two alternative dates.
These two dates are included in the “Review quote” task (first two lines in the image below). In the context of the taskflow, in order to ‘know’ which date the customer chooses, the customer is asked to confirm the date in the field “Please confirm the date of your move” (last field in the image below). The field is pre-filled-in with the date the Movers indicated.
Conditions were set for the last two emails: if the quote is accepted the Mover is notified via the “Accepted” email. If it is rejected, the “Rejected” email will be sent to the Mover.