To automate quarterly business reviews in HighLevel, use a qualifying opportunity-stage change to begin a review cycle, apply the correct timing rule, check eligibility, create preparation work, and send a tested booking invitation. A client moved into a custom “Onboarding Complete” stage on January 15, for example, could receive an invitation 90 days later if the intended rule is “90 days after onboarding,” not “the first day of the next calendar quarter.”
HighLevel documents the workflow trigger, wait, task, message, and calendar-link building blocks. The reviewed documentation does not establish a turnkey QBR template. Booking, attendance, completion, and follow-up therefore need separate tracking and exception handling.
Core sequence: opportunity-stage event, cycle and eligibility checks, timing rule, preparation task, tested invitation with a booking link, then booking and completion tracking.
Automate the repeatable handoffs, but define the QBR cycle, its owner, and its completion states before the workflow runs.
The reliable way to automate a QBR in HighLevel
A QBR cycle is the business process for one review period associated with an opportunity. A stage transition can initiate that process, but it does not prove that the client booked, attended, or completed a meeting. Keep the invitation, appointment, preparation task, and completed review distinguishable in your operating records.
HighLevel’s Pipeline Stage Changed trigger is opportunity-based and supports pipeline and stage filters. “Onboarding Complete” is an example custom stage name, not a confirmed HighLevel default. The original HighLevel QBR article presents a useful high-level pattern, but it is not a complete production build with duplicate prevention, booking confirmation, or exception handling.
Before building the workflow, decide what one QBR cycle means. A proposed business record could contain one row per opportunity and review period:
{
"qbr_cycle_id": "illustrative-opp-1042-review-2026-q2",
"opportunity_id": "opp_illustrative_1042",
"review_period": "2026-Q2",
"review_due_at": "2026-04-15T09:00:00-04:00",
"status": "eligible",
"preparation_task_reference": null,
"invitation_sent_at": null,
"booking_reference": null
}
This is an illustrative business record, not a set of native HighLevel fields. Its declared grain is one QBR cycle per opportunity and review period. Invitation attempts, bookings, tasks, and completed reviews should be separate records or clearly separate states. Do not deduplicate on contact ID alone, because one contact can have multiple opportunities and review cycles.
If the cycle record is held outside HighLevel, verify the integration route, identifiers, permissions, rate limits, and concurrency behavior available to your account. The reviewed documentation does not establish a specific public API or export path for a transactional QBR ledger. For broader record-design decisions, see CRM systems and process design.
Choose the review clock before building the workflow
A fixed 90-day wait measures elapsed time. It does not automatically mean three calendar months, the next calendar quarter, a fiscal quarter, or a contract anniversary. HighLevel’s Wait action supports fixed waits as well as other timing options, but the business must define the date rule first.
Use a fixed Wait
Choose a fixed 90-day delay when the rule is “invite 90 days after onboarding completion.” Define the task due interval and communication timing separately.
Define the target date
For fiscal-quarter, contract-anniversary, or client-specific timing, define the target date and verify the account’s date-based configuration. Do not assume 90 days will align.
Use appointment-based timing only when a later action should be anchored to an appointment that has actually been booked. For a client-specific date, confirm the date, time zone, and account behavior before scheduling communication.
Build the opportunity-triggered workflow
Configure the workflow around an opportunity and an explicit cycle decision, not a contact name alone. The sequence below combines documented HighLevel actions with operational checks that your team must define.
HighLevel’s Add Task action supports a title, description, selected-user assignment, due interval, due time, and weekend exclusion. A practical task might be “Prepare QBR for [Contact Name]” with a checklist for the reporting period, approved metrics, open actions, and meeting owner.
For communication, Send Email supports message configuration and test sending. Merge fields may be blank when the trigger does not provide the required data. Send SMS supports personalized messages, URLs, and a test-phone-number function. Valid contact data, sender configuration, permissions, and applicable communication requirements still matter.
Choose the booking link deliberately. A reusable calendar link is a shareable calendar URL. A generated one-time booking link is a separate workflow action that creates a unique link for a subsequent communication. These options are not interchangeable. Verify the calendar, host, duration, availability, and time zone.
Prevent duplicate invitations and wrong-cycle enrollments
A qualifying stage regression can trigger the stage-change workflow again. A stage name alone cannot tell you whether the event represents a new QBR cycle, a correction, or a duplicate. Review HighLevel’s Allow Re-entry and Allow Multiple Opportunities settings before launch. Multiple opportunities matter when one contact has separate qualifying engagements.
Define a cycle-level uniqueness rule. If the business defines one cycle per opportunity and review period, a proposed external key is UNIQUE(opportunity_id, review_period). If the cycle is defined by a scheduled date instead, the key might be UNIQUE(opportunity_id, scheduled_review_date). These are design examples, not native HighLevel constraints.
When concurrent writes are possible in an external system, use a database-enforced unique index or transactional upsert. A lookup-then-create check alone can race. Verify the external system’s API, authentication, identifiers, and permissions before designing that integration.
Before enabling re-entry, decide what a returning stage event means. If it is a new cycle, establish its new review period. If it is a correction or uncertain duplicate, hold it for the QBR operations owner rather than sending automatically.
One workflow enrollment is not necessarily one QBR. Keep the cycle, invitation attempt, booking, preparation task, and completed review distinguishable so a second message or a canceled appointment does not overwrite the history of the cycle.
Add readiness checks and a human exception path
Before the invitation step, define a gate for a usable email or phone number, an active eligible opportunity, an assigned preparation owner, an available calendar, and an unclaimed cycle. If any check fails, create internal work for a named owner instead of attempting the client message.
- Missing contact channel: hold the invitation and assign an owner to confirm current details and communication preferences.
- Duplicate or uncertain cycle: stop the send and have the QBR operations owner classify the event as new, corrected, or duplicate.
- No booking after the chosen interval: create a follow-up task or use one approved follow-up message, with an owner responsible for the next step.
- Cancellation or reschedule: route the appointment change to a defined rescheduling process and update the cycle status.
- Failed or skipped action: have the workflow owner inspect execution history and assign recovery work. The reviewed documentation supports log review, not automatic retries for this QBR sequence.
HighLevel’s workflow guidance covers execution-history review, including skipped steps and errors. Use that history to diagnose a run, then follow the team’s escalation process.
Keep AI optional and bounded in QBR preparation
AI is not needed to decide whether a stage qualifies, when a review is due, whether contact details exist, or whether a cycle is a duplicate. These decisions have explicit rules and should remain deterministic.
A bounded, hypothetical use is drafting an internal preparation brief from approved, period-labeled account metrics and notes. Require structured output containing the reporting period, source references, highlights, and unknowns. Check each value against approved records, reject unsupported claims, and have the assigned QBR owner approve the brief before client use. Do not let an AI summary determine eligibility or trigger a client message.
Test the workflow and measure the operational result
Test a representative opportunity through the actual published configuration. Confirm the pipeline and stage filter, timing, task assignment, rendered message, and booking link. Review execution history after launch for failures, skipped steps, and unexpected re-enrollments.
Measure the process in separate stages: eligible QBR cycles, invitations sent, bookings made, reviews completed, and overdue preparation tasks. Define the reporting period and denominator before comparing results. Workflow activation or a sent invitation is not evidence of a booking or completed review.
- Run a test enrollment and confirm the intended opportunity and stage qualify.
- Check the timing rule, time zone, task assignee, and due interval.
- Test message personalization and verify the selected reusable or one-time booking link.
- Review re-entry and multiple-opportunity settings against the cycle definition.
- Confirm the exception owner and inspect execution history after the test run.
For teams that need help configuring the workflow and validating account-specific behavior, see HighLevel setup and implementation support.
