How to Keep Track of Customer Quotes That Need a Follow-Up

1. Give the quote review a clear owner

Imagine Green Lane Plumbing, a fictional two-person business. Nadia approves quotes and the follow-up policy. Sam checks the task list each working morning; Lena covers absences. If a quote is sent on Tuesday, they want a review task due two days later. That is an example policy, not a promise of the right timing for every business.

HighLevel calls a quote record an Estimate. This recipe starts only when an estimate is sent inside HighLevel; it will not discover quotations sitting in a separate document, inbox or messaging app. Use it initially for customers with one open quote, sent by one responsible person. Agree who checks the list, who approves customer contact and when to escalate an unanswered question.

2. Check access and prepare two simple labels

You need the correct business account, working Estimates, access to workflows and tasks, and an active staff assignee. Ask the administrator to confirm your permissions and current subscription features before buying or changing a plan. Estimate delivery can have email or phone charges; this task-only recipe adds no AI, SMS or WhatsApp step. No API connection or coding is required.

Have the administrator create two new, unused contact labels—HighLevel calls these tags:

• bt-quote-review-enabled: the owner has approved this customer for the process.
• bt-quote-review-open: a review is already on the list.

Confirm that neither label starts any other automation. Apply only the enabled label to a controlled test contact. In the contact’s Tags dropdown, select the label and click Apply. Leave the open label absent. Use an email address you control for the test estimate, and check that unrelated workflows cannot turn the test into a customer message, invoice or payment action.

3. Start a workflow when the quote is sent

Open Automation → Workflows → Create Workflow and start from scratch. Name it Quote review list and keep it in Draft while building. Add the Estimates trigger. Use Add Filters to set Estimate Status → Is → Sent, then save the trigger. Do not choose a broad “is not declined” condition; that would describe a different process.

Open the workflow’s Settings and enable Allow Re-entry for later qualifying events after a run finishes. The next step’s labels control whether a new review is needed; the re-entry switch is not a duplicate-task guarantee. Leave unrelated workflow settings and other automations alone. This procedure contains no automatic estimate-sending, invoicing or customer-message action.

4. Continue only when a review is needed

Add an If / Else action and choose Build My Own. Name the first branch Create a review. Use the contact-tag condition and combine these two requirements with AND:

1. The contact has bt-quote-review-enabled.
2. The contact does not have bt-quote-review-open.

Both must be true. Leave the automatic None branch with no follow-up actions, so an unapproved customer or an already-open review ends there. Save the action. Check the actual tag-condition controls in your account; if you cannot express both requirements, stop and ask the administrator or Kashif for help rather than substituting a different condition.

5. Add the open label and the assigned task

On the Create a review branch, add Add Contact Tag and select bt-quote-review-open. If it needs creating, the action’s tag dropdown supports Add New Tag. Save the action. Next add the contact-related Add Task action—the version with Title, Assign To and Due In, rather than a Project Management task asking for a Space or List.

• Title: Review the customer’s open quote.
• Assign To: the named active reviewer, such as Sam.
• Due In: 2 days for this example.
• Due Time: choose a time the reviewer works, if required.

Check Due Date Preview, including a Friday/weekend example. Choose any weekend option deliberately; do not assume “two days” always means two working days. Use this copyable task description:

Open this customer’s current estimate and conversation. Record the quote number, latest status and any reply. Check whether a follow-up is still appropriate. Ask the owner to approve the next customer message. Record the next action, owner and date, or why no contact is needed. Close the review and remove the open-review label only when the case is resolved.

Save the task action. The contact-related task links to the contact; this recipe does not automatically insert or validate a specific estimate number. Adding a task is not proof that somebody received an alert. The reviewer must check the task list unless notifications have been configured and tested separately.

6. Test the complete route with controlled quotes

Have Nadia review every action before testing: one trigger, the two-condition branch, the open-label action and the task. Use Test Workflow with the controlled contact for a first check, then review Execution Logs. A builder test does not prove that the real Sent event works. Record and close any task that this test created, then remove only the test contact’s open-review label before checking the live trigger. Leave its enabled label in place.

For a short controlled live-trigger test, keep the enabled label on test contacts only, have the owner approve the test estimate, and publish this single workflow. Send the marked test estimate to your own address. Put the workflow back in Draft if anything fails. Record expected and actual results:

1. An eligible sent estimate creates one contact-linked task with the right assignee and previewed due date, and adds the open label.
2. A customer without the enabled label receives no task from this workflow.
3. A repeat send while the open label remains creates no extra review task. Test this even if the repeat send does not generate another enrollment.
4. Opening or accepting the estimate produces no second task under the Sent-only filter. Confirm that any existing task still needs human resolution.
5. After the owner resolves the first case and clears its open label, a genuinely later quote can create a new review.
6. The backup can find the contact, quote, task and conversation, including a Friday/weekend due date.

Keep customer-message and payment actions out of the test. These are checks for you to perform, not results observed by BizThrivers in a customer account. For simultaneous sends, multiple open quotes or another workflow using the same labels, get a separately verified design before extending this starter recipe.

7. Review the list and approve the next action

After the controlled checks pass, Nadia approves the process, assignee, backup and review interval before real customers are added to the enabled group. Add the enabled label before sending an approved quote. Adding the label after an old quote was sent does not replay that event; create a manual task for any existing backlog.

Sam opens Contacts → Tasks each working morning. Use Advanced Filters to select the assignee and inspect Due Today, then Overdue. Open the related customer and check the actual estimate status and conversation before contacting them. A viewed quote, an accepted quote, a booked job and a paid invoice are different outcomes.

If the customer has replied, accepted, declined or asked for time, handle that situation first. Record the decision, finish or reschedule the review, and remove bt-quote-review-open only when the case is resolved. In the contact’s Tags dropdown, deselect that one label and click Apply. Keep the enabled label only if the owner wants later quotes included. Neither a reply nor acceptance automatically closes this task or clears the label.

For a message you will review and send yourself, adapt the free customer enquiry reply templates. Keep it relevant to the quote, respect contact preferences, and have the named owner approve the message. This workflow sends no customer reminders.

8. Fix failures and know how to stop

If a task is missing, compare the actual estimate event with Enrollment History and Execution Logs. Check the business account, enabled label, branch result and assignee. If the open label was added but Add Task failed, check for an existing task before creating one manually. Keep one clear owner and flag; do not repeatedly resend the quote to try to repair the task.

If duplicate reviews appear, pause the workflow, identify which workflow or manual action created each one, and retain the correct review. Reconcile the label with that task before restarting. Assign unresolved work to the backup. Do not bulk-delete tasks or clear every customer’s labels as a shortcut.

To stop future processing, switch Quote review list back to Draft. Review any contacts already in progress with the administrator rather than assuming the status change reverses actions already taken. Remove the enabled label from contacts you are withdrawing, and manually review tasks and open labels already created. Stopping the workflow does not recall quotes, cancel jobs or undo customer messages. Maintain a manual review list until the issue is fixed.

If ownership is the wider problem, use the reply-ownership worksheet alongside this list. Keep quote review separate from any automatic lead-follow-up sequence.

Common questions

Will this send reminder emails or texts to customers?

No. The recipe creates a staff task and a contact label. The owner checks the latest quote and conversation, then approves any customer message. Existing customer-message automations need their own review.

Can one customer have several open quotes?

Not with this starter method. Its open-review label belongs to the contact, so another quote for that customer would be held back too. Ask for a quote-specific setup before using it where several estimates can be open together.

Does accepting a quote or replying close the task automatically?

No. The owner must review the outcome, finish or reschedule the task, and remove the open-review label when the case is resolved. A reply to an estimate is not a reply to a message from this task-only workflow, so Stop on Response is not a task-closing rule.

Does the label guarantee there can never be a duplicate?

No. It is a practical guard for ordinary repeat entries, not a guaranteed lock against simultaneous activity or another workflow adding a task. Test repeat sends and check for other automations before launch. Use a separately verified setup for concurrent or higher-volume quoting.

Has this been tested in a real plumbing business?

This is a documented setup walkthrough with a fictional example. No live customer account or end-to-end HighLevel workflow was configured or tested for this guide.