When recruitment departments use GoHighLevel to handle initial candidate enquiries, the system must capture and organize information that separates administrative intake from screening decisions. This guide walks through the practical workflow for recording where candidates found the role, confirming contact permission, identifying available callback windows, assigning recruiter ownership, and maintaining a source record that stays accurate as a recruiter reviews applications. The goal is to equip your team to move enquiries forward consistently while preserving the distinction between what GoHighLevel records and what a human recruiter decides about fit.

Why Intake Structure Matters in Recruitment

Recruitment intake differs from general sales lead capture. A sales pipeline tracks opportunities to close; a recruitment pipeline tracks people who have applied and the next administrative steps. When a candidate enquires—whether through a job board, career site form, email, or phone—you need to know: who they are, how they asked to be contacted, when they are available, and which recruiter will handle them. Recording this information correctly avoids missed follow-ups, duplicate contact attempts, and confusion about who owns each candidate.

GoHighLevel's pipeline and opportunity structure can model this workflow, but only if your team configures it deliberately. A candidate record is a contact; their application for a specific role is an opportunity. The pipeline stage reflects where they stand administratively: newly arrived, callback scheduled, awaiting interview confirmation, hired, or withdrawn. Automations can help move candidates through these stages based on call outcomes and form submissions, reducing manual data entry and ensuring no one is overlooked.

Setting Up Your Recruitment Pipeline

Start by defining the stages that reflect your actual intake and scheduling process. This is not the same as a sales funnel. A typical recruitment intake pipeline might include: New Enquiry, Contact Permission Confirmed, Callback Scheduled, Awaiting Interview, Offer Extended, Hired, or Not Pursued. Each stage represents a distinct administrative checkpoint, not a qualification judgment.

To create this pipeline in GoHighLevel, navigate to Opportunities, select Pipelines, and click Create New Pipeline. Name it something clear like "Recruitment Intake 2026" and add your stages in order. According to the GoHighLevel pipeline setup guide, you define stages that match your actual workflow; recruitment intake is no exception. Save the pipeline and confirm your team understands what each stage means before data starts flowing in.

The contact record holds the candidate's name, email, phone number, and any notes from the initial conversation. The opportunity record—linked to that contact—holds the application itself: which role they applied for, when they applied, what stage they are in, and who owns their follow-up. This separation allows one candidate to apply for multiple roles without duplicating contact records.

Recording Enquiry Source and Channel

Know where each enquiry came from. Did the candidate find the role on a job board, your career site, a referral, social media, or a recruiter's direct message? GoHighLevel lets you capture this by using custom fields or tags. When you add an opportunity manually or import bulk candidates, include a field that records the source: "LinkedIn Job Post," "Indeed," "Referral from Employee," "Career Site Form," or "Phone Enquiry."

If candidates submit applications through a form on your career site or LinkedIn, use a workflow to automate opportunity creation. Set the trigger to "Form Submitted" and configure the action to create an opportunity in your Recruitment Intake pipeline at the "New Enquiry" stage. In the form mapping, ensure the source field is captured. This way, every candidate who submits a form automatically generates an opportunity record without manual entry, and the source is recorded from the form data.

For phone enquiries, create opportunities manually as the call ends. Note the source as "Phone Enquiry – [Caller Name]" so your team knows a recruiter spoke to the candidate live. For referrals, record the referrer's name in a custom field; this helps you thank internal advocates and track which recruitment channels yield the best candidates.

Tracking source is not about automated ranking or scoring. It is administrative housekeeping. Your recruiter will decide whether to pursue a candidate based on qualifications, fit, and timing. Source data helps you understand which channels generate your best applications and where to invest recruitment marketing spend.

Permission to Contact: Capture and Compliance

Before you schedule a callback or send follow-up messages, confirm that the candidate has given permission to be contacted. This is especially important if you are calling prospects who have not yet applied but might be interested in roles.

Create a custom field on your contact record called "Permission to Contact" with options: "Confirmed – Phone," "Confirmed – Email," "Confirmed – SMS," "Not Confirmed," or "Declined." When a candidate submits an online application, assume they have given permission via the channel they used. When a recruiter has a phone conversation, ask explicitly: "Is it okay if we call you again to discuss this role?" Document the answer in the field.

If you send bulk invitations or nurture sequences to candidates, check the Permission to Contact field before enrollment. Create a workflow that applies a tag—"Opt In"—only to contacts where Permission to Contact is "Confirmed – Email." Then configure your email workflow to enroll only tagged contacts. This is a simple guard against sending unsolicited messages.

If a candidate replies "Please do not contact me," update the field to "Declined" and ensure no further outbound calls or messages are sent. Document the date and method of their decline. This protects your reputation and helps you stay compliant with local employment advertising regulations.

Capture Available Callback Times

Recruitment moves fast when candidates are available when you call. Create custom fields to record the times candidates prefer to be contacted. Examples: "Best Time to Call," "Time Zone," "Availability Window," or "Do Not Call Before" and "Do Not Call After."

If a candidate applies online, ask these questions in the application form: "What time of day is best to reach you?" and "What is your time zone?" Populate the opportunity record with the answers. If you speak to a candidate on the phone, ask: "When should I call you back to discuss next steps?" Record the specific window: "Tuesday to Thursday, 9am–12pm ET" or "Anytime after 5pm."

This information prevents missed calls and shows the candidate that your process is organized. When a recruiter is ready to call, they check the availability window and call during those hours. If the candidate does not pick up during that window, a callback task can be created automatically using a workflow triggered by a missed call or voicemail status.

According to the Call Details workflow trigger documentation, GoHighLevel can detect missed calls, voicemails, and busy signals automatically. Configure a workflow so that when an incoming call has a status of "no-answer" or "voicemail," a task is created for the assigned recruiter: "Call [Candidate Name] again—preferred time [availability window]." This removes the manual step of reviewing call logs and ensures follow-ups happen.

Assigning Recruiter Ownership

Every opportunity must have an owner: the person responsible for the next contact. When an opportunity is created—manually, by import, or by workflow automation—assign it to a specific team member. In GoHighLevel, the "Assigned To" field on an opportunity record designates ownership.

If opportunities arrive through a form, configure the workflow to assign them to a default recruiter or to a recruiter based on a rule. For example, if the form includes a field for the position level (graduate, mid-level, senior), you might assign graduate roles to your junior recruiter and senior roles to your senior recruiter. Set up a conditional action in the Create/Update Opportunity workflow: "If Position = Graduate, assign to [Junior Recruiter]; if Position = Senior, assign to [Senior Recruiter]."

If opportunities are imported in bulk or created manually, assign them during creation. Do not leave opportunities unassigned; this creates ambiguity and delays follow-up. Establish a rule: "By end of business day, all new opportunities are assigned or moved to Not Pursued."

Ownership clarity also matters for reporting. At the end of each week, pull a report of opportunities by assigned recruiter to see who has how many active candidates, who has completed the most callbacks, and where bottlenecks exist. This helps you balance workload and ensure no candidate is forgotten.

Creating the Source Record

Maintain a single source of truth for each candidate's enquiry. This record should include: contact name and phone, role applied for, date of enquiry, source channel, permission to contact, availability window, assigned recruiter, current pipeline stage, and any notes from conversations. In GoHighLevel, this is the combination of the contact record and the opportunity record.

Before you import or create opportunities, set up custom fields on the contact and opportunity to hold all this information. Here is an illustrative list of fields you might add:

Field Name Record Type Purpose
Enquiry Source Opportunity Where the candidate found the role (job board, referral, etc.)
Permission to Contact Contact Which channels candidate approved (phone, email, SMS)
Best Time to Call Contact Preferred callback window and time zone
Role Applied For Opportunity Job title and internal reference number
Date of Enquiry Opportunity When candidate submitted application or called
Assigned Recruiter Opportunity Recruiter responsible for follow-up
Last Contact Date Opportunity When recruiter last spoke to or emailed candidate
Call Notes Opportunity Summary of last conversation (recruiter-entered)

When you import candidates from a job board or career site export, map these fields during import. GoHighLevel allows you to upload a CSV file and match columns to fields in your system. Ensure every candidate record has at minimum: name, email, phone, enquiry source, and date of enquiry. The recruiter will add availability and permission details during the first call.

Using Forms and Workflows for Intake Automation

If candidates apply through your own form—on your career site or landing page in GoHighLevel—automations can handle routine tasks. Set up a form with these fields: First Name, Last Name, Email, Phone, Role Interested In, Best Time to Call, and Time Zone. When the form is submitted, trigger a workflow to create an opportunity in your Recruitment Intake pipeline at the "New Enquiry" stage.

Configure the Create/Update Opportunity action to populate fields automatically from the form submission. Set the opportunity value to blank (this is not a revenue deal); set the status to Open; and assign the opportunity to your default recruiter or to a recruiter based on role type. Then add a second action to send a confirmation email to the candidate: "Thanks for applying! We have received your application for [Role] and will contact you on [Best Time to Call]. If you have any questions, reply to this email."

This workflow confirms receipt to the candidate, generates an opportunity record without manual entry, and alerts the assigned recruiter that a new candidate is waiting. The recruiter checks the "Best Time to Call" field and rings the candidate during that window. If the call results in voicemail or a busy signal, a second workflow—triggered by the Call Details outcome—creates a callback task.

Another useful workflow responds to inbound calls. When a candidate calls your main recruitment line and leaves a voicemail, the Call Details trigger fires and can create a task or send an internal notification. If you have a dedicated recruitment phone number, add the Call Details trigger configured for that number with a status filter for voicemail or no-answer. The action creates a task: "Voicemail from [Contact Name]—follow up within 2 hours." This ensures urgent inbound enquiries do not slip through the cracks.

What Stays With the Recruiter: Judgment and Qualification

GoHighLevel records facts and administrative steps. What it does not do—and should not do—is make hiring decisions. Questions about whether a candidate meets the job requirements, whether their experience is genuine or inflated, or whether they are a good cultural fit belong to the recruiter, not the system.

Distinguish between intake facts and recruiter assessment. Intake facts are: "Candidate submitted application on 15 March through Indeed," "Candidate prefers calls between 9am and 5pm GMT," "Candidate gave permission to call," and "Candidate last called back on 17 March and left voicemail." Recruiter assessment is: "Candidate claims five years of experience but CV shows only two years," "During first call, candidate was unclear about SQL skills despite listing it prominently," or "Candidate said they were available immediately but then mentioned a three-month notice period."

Record a candidate’s statement as self-reported at intake. Keep verification of qualifications and any hiring assessment with the responsible recruiter.

When a recruiter speaks to a candidate, they listen for: availability (can they start in the timeframe you need?), work authorization (do they need visa sponsorship?), and general interest (are they seriously considering the role or just exploring?). These are facts the recruiter should enter into Call Notes so the hiring manager can review them. But the recruiter should not screen for technical skills or soft skills over the phone. That belongs to the formal interview stage, after the candidate has been scheduled.

Handling Different Enquiry Channels

Recruitment enquiries arrive through different channels, and each requires slightly different handling. Structure your intake to accommodate all of them.

For online applications through your career site or job board: Candidates fill a form with their details and preferred contact method. GoHighLevel captures this, creates an opportunity automatically via workflow, and your team receives a notification. The assigned recruiter then contacts the candidate at their preferred time.

For phone enquiries: A candidate calls your main line and speaks to a recruiter or receptionist. The call is logged (see Call Details trigger documentation for automatic logging). The person who took the call should ask: name, email, phone, role interested in, best time to callback, and permission to call back. If it is a recruiter, they might have a short initial conversation about availability and interest. Create the opportunity record immediately after the call, including a note about the conversation. If the candidate reaches voicemail, the workflow triggers a callback task.

For email enquiries: A candidate emails your recruitment inbox with their CV and a message. Forward the email to GoHighLevel by creating a contact and opportunity manually or by configuring email-to-CRM capture. Record the source as "Email Enquiry," note their message in Call Notes, and ask them to confirm the best time to call. Treat email enquiries the same way you treat form submissions: schedule a callback within one business day.

For referrals: An employee or external contact refers a candidate they know. Create a contact record and ask the referrer for the candidate's contact details, role they are interested in, and preferred contact method. Record the referrer's name in a custom field. Referrals often have higher engagement, so prioritize callbacks within the same day if possible.

A Sample Enquiry Record

Here is what a completed enquiry record might look like in GoHighLevel after initial intake:

Contact Record:
Name: Sarah Chen
Email: sarah.chen@email.com
Phone: +44 7700 900123
Permission to Contact: Confirmed – Phone
Best Time to Call: Tuesday–Thursday, 10am–12pm GMT
Time Zone: GMT

Opportunity Record:
Contact: Sarah Chen
Pipeline: Recruitment Intake 2026
Stage: New Enquiry
Role Applied For: Senior Software Engineer
Date of Enquiry: 16 March 2026
Enquiry Source: LinkedIn Job Post
Assigned Recruiter: James Park
Status: Open
Call Notes: [Empty until first call]
Last Contact Date: [Null until first contact]

When James calls Sarah on Thursday morning at 10:30am GMT, he updates the Call Notes with: "Spoke to Sarah—confirmed 8 years Java experience, currently employed at MidSize Tech, available to start in 6 weeks, interested in flexible working. Strong fit for role. Suggested interview process. Sarah agreed to receive calendar invite. Sent invite same day."

James then moves the opportunity to "Callback Scheduled" or "Awaiting Interview Confirmation," depending on your pipeline stages. He updates Last Contact Date to the date of the call. This record now tells any team member (hiring manager, HR, another recruiter) exactly where Sarah stands and what has been discussed.

Handling Call Outcomes and Follow-Up

Not every call attempt succeeds. A candidate might not answer, might answer but not be available to talk, or might explicitly decline interest. Record the outcome and trigger the right follow-up.

Configure your Call Details workflow trigger to detect common call outcomes. For an incoming call with status "no-answer," create a task: "Follow up with [Contact Name]—retry within 48 hours." For a "voicemail" status, create a task: "Voicemail received from [Contact Name]—call back during preferred window." For a "busy" signal, create a task: "Line was busy—retry in 30 minutes if within preferred window, else schedule retry for next availability window."

If a candidate picks up and says "Now is not a good time," the recruiter should ask: "When would be better?" and record the new callback time. Update the "Best Time to Call" field and create a task with that time. Do not call a candidate multiple times outside their stated availability window; this damages your reputation and wastes time.

If a candidate explicitly says they are not interested, update the opportunity stage to "Not Pursued" and record the reason in Call Notes: "Candidate declined interest—prefers to stay in current role." Move on. If they later re-apply for a different role, treat the new application as a fresh enquiry but reference the earlier interaction in notes.

Reporting and Quality Checks

Track how your intake process is performing. Run weekly reports to see: how many new enquiries arrived, which sources generated the most candidates, how many enquiries resulted in scheduled calls, average time from enquiry to first contact, and how many candidates moved to the interview stage.

Check that all opportunities have an assigned recruiter and are in an appropriate pipeline stage. If you find opportunities stuck in "New Enquiry" for more than five business days without a note, that is a signal the assigned recruiter has not acted. Escalate or reassign.

Audit a random sample of call records each month. Listen to or read summaries of calls; confirm that recruiters are recording outcomes accurately, asking for permission to contact, and respecting availability windows. This quality check ensures consistency and identifies where recruiters need coaching.

Frequently Asked Questions

Q: Can I import candidates from my existing ATS into GoHighLevel?
A: Yes. Export a CSV file from your ATS with columns for name, email, phone, role applied for, enquiry source, and enquiry date. In GoHighLevel, go to Opportunities, click Import, select Opportunities, upload your file, and map columns to fields. This creates all candidates as opportunities in your Recruitment Intake pipeline at the "New Enquiry" stage in one batch.

Q: What if a candidate applies for multiple roles?
A: Create one contact record for the candidate. Create a separate opportunity for each role they apply for. Both opportunities link to the same contact, so if you update their phone number or permission settings, it applies to all their opportunities. The assigned recruiter for each role is independent, so different recruiters can own different applications from the same candidate.

Q: Can I use GoHighLevel to schedule interviews automatically?
A: GoHighLevel has a scheduling feature where candidates can book time slots. You can send a candidate a link to your calendar, and they pick a time. This is useful for initial call scheduling. For formal interviews, most recruitment teams use a dedicated scheduling tool or calendar; GoHighLevel is handling intake and initial contact, not the full interview process.

Q: How do I handle candidates who apply offline, like by post or at a job fair?
A: Create their contact record manually and add a note: "Applied in person at Career Fair, 14 March." Confirm their phone number and email, ask for permission to contact, and create an opportunity. Treat it like any other enquiry from that point forward.

Q: What should I do if a candidate's number is disconnected or email bounces?
A: Update the opportunity stage to "Not Pursued – Contact Invalid" and record the reason in Call Notes. Try one alternative contact method if you have it (e.g., their LinkedIn profile or referrer's details). If you have no way to reach them, do not spend more time; mark them as not pursued.

Conclusion

GoHighLevel can manage recruitment intake efficiently when you use its pipeline, opportunity, and contact structure deliberately. Capture enquiry source, permission to contact, available callback times, and recruiter ownership consistently. Use forms and workflows to automate routine tasks—creating opportunities, sending confirmations, and generating callback tasks—so your team spends time talking to candidates rather than data entry. Keep assessments and hiring decisions with the recruiter; GoHighLevel is the administrative home for facts and scheduling. Review your process weekly, audit call records, and adjust as needed. When intake is organized, your hiring team can move candidates through the next stages faster and candidates have a better experience.

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.