When a mortgage broker receives an enquiry—whether a new application, a follow-up to an existing case, or a request from someone checking on a partner's submission—the response must be swift, accurate, and routed to the right adviser. Delays create frustration; misrouted calls waste time; lost context leads to repeated questioning. GoHighLevel's pipeline and call-handling workflow system can organize this chaos, but only if you design the intake and callback process with the right boundaries, data capture, and automation triggers in place. This guide walks through building an enquiry-to-callback workflow that tracks lead source, applicant identity, existing records, adviser availability, and caller preference, so your team knows what to do the moment someone calls or submits a form.

Why the Mortgage Broker Enquiry Workflow Matters

A mortgage broker handles multiple roles: sourcing new clients, nurturing applications mid-process, managing withdrawals and resubmissions, and coordinating with lenders and advisers. An unorganized enquiry intake creates friction at every stage. A caller might reach the wrong adviser; an existing application might be duplicated instead of updated; a request for a callback might vanish into a notes field; sensitive details might be stored in unsecured text messages. The workflow you build acts as a guard rail: it captures what you need to know, flags what needs human judgment, and hands the right information to the right person.

The workflow is administrative. It does not provide mortgage advice, assess eligibility, or make lending decisions. Its sole job is to identify who is calling, why they are calling, where their record lives, and which adviser should call them back—and to do that consistently, every time.

Structuring the Pipeline for Enquiry States

Begin by defining your pipeline stages. A pipeline represents your overall enquiry process; stages are the steps a lead moves through. For a mortgage broker, the stages should reflect the administrative journey of an enquiry, not the application approval process.

A typical enquiry pipeline might include:

Stage Meaning Entry Point
New Enquiry First contact, unqualified source or intent unknown Form submission, inbound call logged, import
Existing Application Review Caller references an active case number Call workflow or manual classification
Adviser Assignment Pending Caller identity and intent confirmed; adviser selection in progress Manual move after verification
Callback Scheduled Callback agreed and calendar invite sent Workflow or manual task creation
Callback Completed Adviser spoke to caller; outcome recorded Call log or manual update
Duplicate / Merged Enquiry matched to existing contact; record consolidated Manual merge or deduplication workflow

These stages are fluid. A caller might move from New Enquiry to Existing Application Review in one workflow step if their application number is verified. Another might stay in Adviser Assignment Pending if no adviser is free that day. The pipeline is a way to see at a glance where every enquiry stands and what must happen next.

Capturing the Right Contact and Opportunity Data

Every enquiry creates two records in GoHighLevel: a Contact record (the person) and an Opportunity record (the enquiry itself). The contact holds persistent information—name, phone, email, address. The opportunity holds the enquiry context—which pipeline stage, which adviser, what was discussed, what callback action is needed.

When designing your contact form, capture the minimum required to route the call:

  • Full name (and confirm spelling)
  • Phone number (and confirm which number to call back)
  • Email address
  • Reason for enquiry (new application, existing case, general question)
  • If existing case: application reference number or adviser name
  • Preferred callback time or date
  • Preferred contact method (phone, email, SMS)

Do not ask for financial details, property information, or employment history on the enquiry form. Those belong in the adviser conversation, in a secure environment, after identity is confirmed. The enquiry form is a gate; it asks only: who are you, why are you here, and how should we reach you?

When a form is submitted, GoHighLevel can automatically create an opportunity in the New Enquiry stage. This ensures no enquiry is lost and establishes a record trail. The contact's information flows into the Contact record; the enquiry context (reason, callback preference, timestamp) flows into the Opportunity.

Detecting Duplicate and Partner Enquiries

A common friction point: the same caller submits a form twice, or a partner submits an enquiry for their spouse's application. Without careful handling, you create two opportunity records for one person or lose track of the relationship.

Before creating or updating a record, demonstrate the proposed contact-matching process using controlled examples. Inspect what happens when an existing contact has another enquiry or a corrected callback number.

  • Merge the new contact into the existing record (consolidating the contact history).
  • Apply a tag such as "Duplicate Enquiry" to flag that this person has contacted you more than once.
  • Create an opportunity on the existing contact, avoiding a duplicate contact creation.

If the enquiry is from a partner (spouse, co-applicant), the workflow can ask: "Is this enquiry about your own application or someone else's?" A follow-up workflow step can then determine whether to create a linked contact record (if the partner is a new contact) or to tag the existing contact as "Primary Applicant – Co-applicant Contacted" (if the partner calls on behalf of an existing case).

For example: Sarah submits a form asking about her husband Mark's mortgage application. The form asks "Is this enquiry for you or someone else?" Sarah selects "Someone else." The workflow then checks: is there an existing contact named Mark with the phone number Sarah provided as his number? If yes, the workflow creates an opportunity on Mark's record and applies tags "Co-applicant Contacted" and "Callback Requested by Sarah." If no, the workflow creates a new contact for Mark (using available information) and a contact relationship linking Sarah as the reporter.

Matching New Enquiries to Existing Applications

When a caller says, "I'm calling about my application with reference number XYZ," or "I was speaking to adviser Jane," the enquiry belongs to an existing application, not a new lead. The workflow must find and link that record.

Store application reference numbers and adviser assignments in custom fields on the Contact record. When an enquiry arrives mentioning a reference number or adviser name, use a workflow to search the Contact database for that reference number or adviser. If a match is found, create the opportunity on that contact rather than generating a duplicate.

Here is an illustrative workflow sequence:

  1. Form submitted with fields: name, phone, reason ("I'm calling about an existing application"), application reference number.
  2. Workflow searches Contact records for a contact with Application Reference = the number provided.
  3. If found: Create opportunity on that contact, move to "Existing Application Review" stage, tag with "Existing Caller – Verify Identity."
  4. If not found: Create new contact and opportunity, tag with "Reference Not Matched – Manual Review Required."

The manual review step is crucial. If a reference number does not match any record, it may be misremembered, mistyped, or from a different broker. Do not assume; flag it for manual verification by your team.

Automating the Call Details Trigger

When an adviser speaks to a caller, the call is logged in GoHighLevel's phone system. You can configure a workflow that automatically captures call details—direction, duration, status, disposition—and creates follow-up actions without manual intervention.

The Call Details workflow trigger, described in GoHighLevel's support documentation on workflow triggers, evaluates incoming or outgoing calls against conditions you specify. For a mortgage broker enquiry workflow, the key conditions are:

  • Call Direction: Incoming (caller reaches you) or Outgoing (adviser calls back).
  • Call Status: Completed (call connected), No Answer (call went unanswered), Voicemail (caller left a message), Busy (line engaged).
  • Custom Disposition: A classification assigned after the call, such as "Follow Up Required," "Callback Requested," "Callback Completed," or "Application Advice Declined."

Build separate workflows for different call scenarios. For example:

Scenario 1: Incoming Missed Call (No Answer or Voicemail)

  • Trigger: Call Direction = Incoming; Call Status = No Answer or Voicemail.
  • Actions: Tag contact "Missed Call – Callback Pending." Create a task for the assigned adviser: "Return missed call to [contact name] at [number]." Send an SMS to the contact: "Thanks for calling. An adviser will call you back shortly."

Scenario 2: Completed Call with Callback Disposition

  • Trigger: Call Direction = Incoming or Outgoing; Custom Disposition = "Callback Requested."
  • Actions: Move opportunity to "Callback Scheduled" stage. Create a task for the assigned adviser with the callback time agreed during the call. Send a calendar invite to the adviser. Send a confirmation SMS or email to the contact with the callback time.

Scenario 3: Outgoing Call Completed (Adviser Calling Back)

  • Trigger: Call Direction = Outgoing; Call Status = Completed; Custom Disposition = "Callback Completed."
  • Actions: Move opportunity to "Callback Completed" stage. Apply a tag with the date of callback. Remove any pending "Callback Required" tasks. Send an internal note to your manager noting the callback was completed (for reporting purposes).

These automations eliminate manual task creation and status updates. Once an adviser logs a call disposition—"Callback Requested" or "Callback Completed"—the workflow engine moves the opportunity forward and assigns the next action automatically.

Handling Adviser Unavailability and Reassignment

When a caller asks for a callback "as soon as possible" but their adviser is on holiday or has a full calendar, the workflow must not leave the enquiry stranded. Instead, it should escalate to a backup or queue the call for the next available adviser.

Design your workflow to check adviser availability before assigning the callback. For example:

  1. Enquiry arrives with a named adviser.
  2. Workflow checks: is that adviser active and not on leave? (Store leave dates in a custom field or use an integration to a calendar system.)
  3. If yes, create a task for that adviser with the callback deadline.
  4. If no, use a workflow rule to assign the callback to an alternative adviser (based on team or rotation), or move the opportunity to a shared queue. Tag the opportunity "Reassigned – Original Adviser Unavailable" so your team knows why the caller is not hearing from their preferred contact.

A callback should never be assigned to an adviser who cannot fulfil it. If adviser Jane is the stated contact but is away, let the caller know via SMS: "We received your callback request for Jane. She is currently unavailable, but adviser Tom will call you back on [date/time]. Thank you for your patience." This sets expectation and prevents frustration.

Recording Contact Preference and Secure Communication

Callers often specify how they want to be contacted: "Call me on my mobile, not my work phone" or "Email me; don't leave voicemails." Record this preference on the contact record and reference it when scheduling callbacks.

Add a custom field to your Contact record: "Preferred Callback Method" with options Phone, Email, SMS. Add another field: "Do Not Call" times or "Do Not Leave Voicemail." During workflow actions—creating a callback task, sending a reminder—reference these preferences.

For sensitive communications, avoid unencrypted SMS or email if the subject is financial or personal. Use GoHighLevel's secure messaging or advise the adviser to confirm the contact's identity before discussing specifics. The enquiry workflow does not store sensitive data; the call itself is where advice and detailed information are shared. Your job in the workflow is to get the right person talking to the right adviser.

Secure Boundaries and Verification Requirements

A configured workflow is not evidence of a contractual or regulatory commitment. Confirm relevant privacy, processing and identity-verification requirements with the supplier and the responsible business team.

When an adviser is about to speak to a caller about an existing application, the workflow should remind the adviser to verify the caller's identity. Create a task or send a message to the adviser: "Before discussing this application, confirm the caller's date of birth, postcode, or another detail from the existing record." This is a manual step—the adviser completes it—but the workflow ensures it is not skipped.

For new enquiries, no sensitive data should be discussed during the initial intake call. The workflow and intake form are designed to collect contact details and intent only. Once the contact is routed to an adviser and identity is verified in a scheduled callback (ideally via a secure phone line or after confirmation), the adviser can discuss financial details, property specifics, and eligibility.

Do not rely on the workflow to enforce data security. Document your procedures: advisers must confirm identity before discussing sensitive details; personal information must not be stored in notes without encryption; calls about applications must be recorded with the contact's consent (check local regulations); and all communications must comply with your firm's data privacy policy and applicable financial regulations.

Building the Intake Form and Import Process

The entry point for most enquiries is either an online form (website, landing page) or a phone call. For forms, GoHighLevel's form builder is the starting point. You can embed a form on your website or landing page; when submitted, the form data creates a contact and can trigger a workflow.

A practical enquiry form structure:

  • Step 1 (Contact Details): Full name, phone number, email address, postcode.
  • Step 2 (Enquiry Type): "Is this a new application, an enquiry about an existing application, or a general question?" Radio buttons or dropdown.
  • Step 3 (Conditional Fields): If existing application, ask for application reference number or adviser name. If new application, ask for property type or approximate loan amount (optional; no sensitive data).
  • Step 4 (Callback Preference): Preferred callback date/time window, preferred method (phone/email/SMS), any do-not-contact hours.
  • Step 5 (Consent): Checkbox: "I consent to be contacted about my enquiry by the selected method."

After form submission, the workflow automatically creates a contact record and an opportunity in the New Enquiry stage. If the form mentioned an existing application reference or adviser name, the workflow searches for a matching contact and moves the opportunity to the Existing Application Review stage instead.

For bulk uploads (e.g., enquiries from a partner broker or a list of lapsed clients), use GoHighLevel's CSV import feature. Map columns from your spreadsheet to Contact and Opportunity fields. You can specify which pipeline and stage opportunities should land in. Review the documentation at https://help.gohighlevel.com/support/solutions/articles/155000005062-getting-started-setup-pipelines-and-opportunities for import mechanics.

Sample Workflow: New Enquiry to Callback Assigned

Here is an illustrative workflow demonstrating the complete journey from form submission to callback assignment, including handling of a duplicate enquiry and an unavailable adviser.

Scenario Setup: A contact named Alex submits an enquiry form stating this is an existing application (reference XYZ123). The form also captures Alex's phone number, email, preferred callback time (Wednesday 2 pm), and confirms consent.

Workflow Trigger: Form Submitted (Enquiry Form).

Workflow Steps:

  1. Create/Update Contact: Form fields populate a contact record. Phone and email are used to search for duplicates. If a contact with the same phone number exists and was created in the last 30 days, the workflow tags this record "Duplicate Enquiry – Do Not Create New Contact." If no duplicate, a new contact is created.
  2. Search for Existing Application: The form included an application reference (XYZ123). The workflow queries the database for a contact with Application Reference field = XYZ123. If found, update the existing contact's record to note a new enquiry and move to the next step. If not found, tag this opportunity "Reference Not Matched – Review Required" and notify your team lead for manual investigation.
  3. Assign Adviser: The matched contact record includes an Assigned Adviser field (let us say "Jane"). Workflow checks Jane's calendar (or a custom Leave field). If Jane's Leave field = "01/10 – 07/10" (she is away), the workflow triggers a reassignment rule: assign the callback to Tom (the backup adviser for Jane's portfolio). If Jane is available, proceed with assigning to Jane.
  4. Create Callback Task: A task is created for the assigned adviser (Jane or Tom) with details: "Callback to Alex – Reference XYZ123 – Preferred time: Wed 2 pm – Confirm identity before discussing application details." The task due date is set to Wednesday.
  5. Send Confirmation to Caller: An SMS or email is sent to Alex: "Thanks for your enquiry, Alex. We received your request for a callback regarding application XYZ123. [If Jane] Adviser Jane will call you Wednesday around 2 pm. [If Tom] Your adviser Jane is currently unavailable. Adviser Tom will call you Wednesday around 2 pm. You can also reach us at [support number] if you need to reschedule."
  6. Move Opportunity Stage: The opportunity is moved to "Adviser Assignment Pending" (if awaiting confirmation) or "Callback Scheduled" (if adviser and time are confirmed).

Outcome: Alex receives a confirmation message; the assigned adviser has a task with clear instructions; your team knows the reference number was matched and the adviser was available. If the adviser later logs a call with disposition "Callback Completed," a separate workflow updates the opportunity stage to "Callback Completed" and removes the task. If the adviser marks disposition "Callback Requested – Reschedule," the workflow creates a new task for a future callback attempt.

Testing the Workflow: Three Scenarios

Before publishing your workflow, test it with realistic scenarios. Here are three test cases designed to validate the workflow's behavior when common edge cases occur.

Test Case 1: Duplicate Enquiry

A contact named Sarah submits an enquiry form on Monday with phone 07700123456 and email sarah@email.com. The workflow creates an opportunity. On Friday, the same person submits the form again with identical details. Expected outcome: the workflow detects the duplicate contact (phone and email match), does not create a second contact, and either merges the new enquiry into the existing opportunity or creates a second opportunity on the existing contact with a "Duplicate" tag. Your team sees one contact record with two enquiries, not two separate contacts. Verify this by checking the contact record: how many opportunities are shown? Is the duplicate flagged?

Test Case 2: Partner Enquiry (Existing Application)

Mark is an existing contact with an active application (reference APP5678, adviser assigned: Jane). Mark's spouse Sarah submits an enquiry form. The form asks, "Is this enquiry for you or someone else?" Sarah selects "Someone else – my spouse" and provides Mark's name and the application reference. Expected outcome: the workflow finds the existing contact Mark (by reference number), does not create a new contact for Sarah, and creates an opportunity on Mark's record with tags "Co-applicant Contacted – Sarah" and "Callback Requested." The adviser (Jane) sees that the application was contacted, the person calling was the co-applicant, and a callback is expected. Verify by navigating to Mark's contact record and checking that Sarah's enquiry appears as an opportunity linked to Mark, not as a separate contact.

Test Case 3: Unavailable Adviser

Alex submits an enquiry for an existing application (reference APP9999). The application record shows Assigned Adviser = Jane. You have set Jane's Leave field to "Today – 10/10." Expected outcome: the workflow checks Jane's availability, discovers she is on leave, and reassigns the callback to Tom (the backup adviser). A task is created for Tom. Alex receives a message: "Your adviser Jane is currently unavailable. Adviser Tom will call you back on [date]. If you need to reach us urgently, call [support number]." Verify by checking the opportunity record: is the assigned adviser field now Tom? Does the task show Tom as the assignee? Does the message sent to Alex mention Tom?

Monitoring and Reporting on the Enquiry Workflow

After the workflow is live, track key metrics to ensure it is working as intended:

  • Duplicate Detection Rate: How many enquiries are flagged as duplicates? This tells you whether your duplicate check is working and whether you have repeat enquiries (which might indicate a communication issue or caller confusion).
  • Reference Match Rate: Of all enquiries citing an existing application, how many are successfully matched to a contact record? A low match rate suggests reference numbers are being misremembered or mistyped; you may need to improve your intake form guidance or follow up with manual review more often.
  • Adviser Reassignment Rate: When advisers are unavailable, how often is a callback reassigned to a backup? This shows whether your leave fields are being kept current and whether your reassignment rules are fair (no adviser is over-assigned while others are underutilized).
  • Callback Completion Rate: Of all opportunities that reach "Callback Scheduled" stage, what percentage move to "Callback Completed" within 24 hours? This reflects adviser responsiveness and whether tasks are being followed up.
  • Workflow Failure or Skip Rate: GoHighLevel logs every action. Check the Execution Logs in your workflow settings. Are any steps being skipped (e.g., a task not being created, a message not being sent)? A failure usually indicates a misconfiguration (e.g., the Assigned Adviser field is empty, so no task can be assigned).

Review these metrics weekly. If duplicate detection is very high, investigate why; perhaps your intake form is being submitted multiple times by one contact, or a bot is submitting spam. If adviser reassignment is very high, double-check that leave dates are accurate. If callback completion is low, discuss with your team: are advisers receiving the tasks? Are they completing the calls but not logging the disposition?

Integrations and Extensions

GoHighLevel's workflow system is flexible. You can expand the enquiry workflow by integrating with other tools:

  • Calendar Integration: Connect Google Calendar or Outlook to check adviser availability and automatically book callback slots. When a caller requests a callback for Wednesday 2 pm, the workflow checks the adviser's calendar and blocks off 30 minutes.
  • SMS Gateway: GoHighLevel has a built-in SMS feature. Use it to send confirmation messages, reminders, and updates. Ensure the SMS complies with local regulations (e.g., recipients can opt out).
  • Email: Send forms, confirmations, and reminders via email. Use templates with dynamic fields (e.g., "Hi [Contact Name], your callback is scheduled for [Date Time]").
  • Reporting and Analytics: Export enquiry data to analyze callback times, adviser performance, and drop-off rates. GoHighLevel allows custom reporting on pipeline stages and workflow execution.

Do not over-engineer. Start with the core workflow: form submission, duplicate check, application matching, adviser assignment, callback task, confirmation message. Once this is stable, add integrations.

Official sources and related guides

This independent Sysevo guide uses the following official documentation. The workflow and trial scenarios are evaluation proposals, not reported customer results or a hands-on benchmark.

Compare the same requirements with the relevant Sysevo product, Voice Agents and CRM. Review Sysevo plans and pricing or book a demo to discuss the proposed setup. Sysevo sells its own business software and is not affiliated with the competitors discussed here.