GoHighLevel for home services: step-by-step CRM setup guide

GoHighLevel for home services can run a company's whole sales process, from the first call or form to a completed job, if you build the setup in this order: access, pipeline, fields, lead sources, stage automations, follow-up, phones, AI voice agent, inbox, data migration, dispatch, reporting, then testing. This guide walks through each step with the exact triggers and fields we specified for a real duct cleaning and AC company. Every screen below is an illustration with made-up names, but the settings are the ones we specified.

The company runs AC servicing and duct cleaning crews, plus maintenance, cleaning and pest control, in the US and the UAE. It was leaving Zoho CRM because per-user pricing kept climbing as the team grew. On a slow day one branch gets 20 to 25 leads, from 8 to 10 ad campaigns running at once across Meta and Google, plus calls, WhatsApp and Instagram messages. Leads were getting lost between those channels. They asked us to move everything into one GoHighLevel account and make it work without reps updating cards by hand.

What problems does GoHighLevel solve for a home services company?

Almost never a missing feature in the CRM itself. The owner's list is a list of things that fall through the gaps between people and channels. This one, from the client's own brief, is typical:

• Missed calls, and nobody knows which ones were returned.
• Leads that arrive on WhatsApp or a rep's personal phone and never reach the CRM.
• Slow first replies, so the customer books whoever answered first.
• Quotes sent and never followed up; discounts given without anyone approving them.
• Sales promising a scope that operations finds out about on site.
• Technicians closing jobs without photos or a report, and extra work found on site going unbilled.
• Maintenance contract renewals and planned visits missed because they lived in a spreadsheet.
• Managers chasing people to find out what is happening, and staff saying 'I forgot'.

The test the client set for the new system was simple: at any moment, management should be able to see what business is coming in, who owns it, what is due next, where each customer or job is stuck, and who has to act if something is late. Every step below exists to answer one of those five questions without anyone asking.

What does a finished GoHighLevel setup do?

• Every lead lands in one place. Meta and Google lead forms, calls, website forms, WhatsApp, Messenger and Instagram messages all create or update a card, with the source recorded.
• No call goes unanswered. All sales reps ring at once; if nobody picks up in 10 seconds, an AI voice agent answers, qualifies the caller and alerts the team.
• The pipeline moves itself. Replies, bookings, cancellations, reschedules and passed appointment times move cards between stages.
• Follow-up has an end. Quiet leads get up to 5 logged touches, then go to a recycled list for later campaigns.
• One history per customer: calls with recordings, texts, WhatsApp and email in one thread.
• Won work becomes a job with a technician, a date and a status, and the dashboard shows where everything stands.

Before you start: what access and decisions do you need?

Get admin access first, including the Automations section. On our first call the client's own login could not see Automations, Funnels or the AI tools, because the user had not been given admin rights. Nothing can be quoted or built until that is fixed, so ask for it before the kick-off call.

1. Admin access to the GoHighLevel sub-account, with Automations, AI agents and phone settings visible.
2. A full export of contacts and deals from the old CRM, or admin access so you can export it yourself.
3. Admin access to Meta Business Manager: the Facebook page, the Instagram account and the lead forms.
4. Access to the Google Ads account, and the Google Local Services Ads account if they use it.
5. The WhatsApp Business number and the phone it currently runs on.
6. DNS access for the website domain, to set up the email sending domain.
7. The list of reps who should receive calls, and their working hours.
8. How jobs are dispatched today: what a job needs to contain and how it is tracked.

Then write down the decisions that change the build. We list ours later under 'Questions to settle before you build'. Agree them in writing before you start; changing a stage rule after the automations exist costs more than deciding it on day one.

Step 1: How do you set up users, permissions and pipeline stages?

Start with roles, then the pipeline. Give reps access to contacts, conversations and opportunities; give coordinators calendars and jobs; keep settings and billing with one admin. Then create one opportunity pipeline with these stages, in this order:

1. In Settings, create the users and set each role's permissions. Turn off 'see all opportunities' for reps if you want each rep to work only their own.
2. In Opportunities, create a pipeline (we called it 'Residential sales') and add the seven stages above, with the exact names you will use in workflows.
3. Create a booking calendar for site visits and service slots, with the reps or teams who take bookings, travel buffers and working hours.
4. If you run very different services (AC servicing, pest control, renovation), plan one pipeline per business line, but build and test this one first.

Step 2: Which custom fields does an HVAC or duct cleaning pipeline need?

Only the fields someone will use to decide or act. We added three groups: qualification fields the AI agent and reps fill in, source fields filled automatically, and control fields that keep the follow-up honest.

Use dropdowns wherever the answer is one of a few options. Free-text fields cannot be filtered or reported on, and a status that every rep spells differently is worse than no status.

Step 3: How do you connect Facebook, Google Ads and WhatsApp leads?

This is trigger T1: a new lead from any form creates a contact and a card in Opt-in, with the source filled in. Wire the sources one at a time and test each with a real submission before moving on.

One source you cannot connect: Google Business Profile chat. Google shut it down in July 2024. Calls from the Business Profile listing still reach your number, so they are covered by the phone setup in step 6.

Record the source as a chain, not one word. 'Facebook' tells you nothing when 10 campaigns are live. 'Meta, duct cleaning, north zone, spring offer' tells you which campaign paid for the booked job.

Step 4: How do you build GoHighLevel workflows that move pipeline stages?

Write the trigger list before you open the workflow builder. Ours was short enough to put in the proposal, and it became the test plan too:

How to build T2, as an example of the pattern:

1. Automation > Workflows > Create workflow > Start from scratch. Name it 'T2 · Opt-in to Hot Leads' so the ID matches your list.
2. Add trigger 'Customer replied' (all channels). Add a second trigger 'Call status' with status answered.
3. Add an If/Else: opportunity stage is Opt-in in the Residential sales pipeline. Only the yes branch continues.
4. Action 'Create/update opportunity': move to Hot Leads, keep the owner and value.
5. Action 'Assign to user' with round robin across the sales team, only if the card has no owner.
6. Action 'Add task': 'Call back and book', due in 5 minutes, with an app and text notification to the owner.
7. Publish, then test with a real reply from a test phone and a real answered call.

The other triggers follow the same pattern, with two that need care:

• T4 has no 'appointment time passed' trigger. Start the workflow on 'appointment booked', wait until the appointment start time plus a margin (we used 2 hours), then check the appointment is not cancelled or rescheduled before moving the card. Tell reps that Completed is set by time, so they must move a card back if the job did not happen.
• T6 needs a decision: does a rescheduled appointment go back to Hot Leads or straight to Booked? The client's diagram said Hot Leads; we asked them to confirm, because Booked is usually closer to the truth.
• Keep each workflow to one job. Moving cards and messaging customers in the same workflow is how a customer ends up receiving a 'we miss you' text the day after booking.

Step 5: How do you automate lead follow-up that stops after 5 touches?

Give follow-up a counter. Without one, a quiet lead either gets forgotten after one call or chased forever. With one, every lead gets the same number of attempts, and the ones that never answer move somewhere useful.

1. Create the number field 'Follow-up touch count' (step 2).
2. When a rep moves a card to Manual Follow-up (T7), a workflow creates the first 'Follow-up touch' task and resets the count to 0.
3. Each time the rep completes a touch task (a logged call, text, WhatsApp or email), a workflow adds 1 to the count with a math operation.
4. If the lead replied since the last touch, move the card to Hot Leads and reset the count.
5. If the count is under 5, create the next touch task 2 to 3 days out. If it reaches 5, move the card to Recycled Leads, tag it 'recycled' and close any open tasks.

Recycled does not mean lost. Those contacts go into later reactivation campaigns, for example a seasonal duct cleaning offer. Quotes get their own cadence: the client asked for a message on day 1, a call on day 2, a message on day 3, a call on day 5, a follow-up on day 7 and a final one on day 10, then won, lost or nurture.

Step 6: How do you set up call routing and missed call text back?

Ring everyone, fall back fast, text back every missed call and never leave one without an owner. Speed matters more here than anywhere else: a homeowner with a dusty vent or a broken AC usually calls the next company on the list if nobody picks up.

1. Buy or port a number in GoHighLevel (a local or toll-free US number; in the UAE the number is issued on request and approval can take a while).
2. Set call routing to ring all selected users at the same time. Up to 7 reps can ring on one number.
3. Set the ring timeout to 10 seconds, which is the shortest GoHighLevel allows before the fallback.
4. Set the fallback to the AI voice agent (step 7) instead of voicemail.
5. Turn on call recording, with the recording notice played first.
6. Turn on missed call text-back: 'Sorry we missed you, we'll call back in a few minutes.' In the UAE, use WhatsApp for this instead (step 8).
7. Add a workflow on 'call status: missed' that creates a callback task due in 5 minutes and alerts a manager if it is still open after that.

One problem the client had in their old setup: while one rep was on a call, everyone else saw it as a missed call until it ended, so two people would call the same customer back. Check how your phone setup shows a call that a colleague has already answered, and test it with three reps logged in at once.

Step 7: How do you set up a GoHighLevel AI voice agent?

Give it one job: take the details a rep needs, promise a fast callback, and create the card. Do not let it quote prices or promise dates. A short, honest agent that hands over well beats a long one that tries to close the sale.

1. In AI Agents, create a voice agent. Pick a clear, neutral voice; the per-minute cost depends on the voice you choose.
2. Write the greeting: who you are, that the team is busy, that you will take a few details so the right person calls back in a few minutes, and that the call is recorded.
3. Add the questions, each mapped to a field: number of bedrooms, number of AC units, when the ducts were last cleaned, the service address, and the caller's name and best callback number.
4. Add rules: no prices, no dates, and an emergency path (water leak, burning smell) where it says a person will call back immediately and marks the call urgent.
5. Set the after-call actions: find the contact by phone number or create one; create the card in Opt-in; write the answers to the fields and attach the transcript; tag 'ai-qualified'; create a 'Call back' task due in 5 minutes; notify the sales team.
6. Test it with real calls from different people, accents and phones, including someone who refuses to give an address and someone who is clearly an existing customer.

Running costs are usage-based: roughly USD 0.06 to 0.22 per minute of AI call time depending on the voice, plus AI usage, on top of normal call minutes. Check the current rates in your account. Also check the recording consent rules for every state or country you take calls from, and say the call is recorded in the greeting.

Step 8: How do you put SMS, email and WhatsApp in one inbox?

Put SMS, email, WhatsApp, Facebook and Instagram messages and call recordings in one thread on the contact. Reps then reply from the same place, and the next rep sees the whole history.

• Email: set up a dedicated sending domain or subdomain in GoHighLevel and add the DNS records it gives you, so mail is not sent from a shared domain.
• US texting: register your brand and campaign for A2P 10DLC before you rely on SMS. Unregistered business texts get filtered or blocked by US carriers.
• UAE: business SMS needs a registered sender name, and new registrations are currently restricted by the operators, so WhatsApp is the main channel there.
• WhatsApp: messages a customer starts are cheaper than ones the business starts, and outside the 24-hour reply window you need approved templates.

Step 9: How do you migrate from Zoho CRM to GoHighLevel?

Clean the Zoho data before you import it. Moving duplicates and half-filled records into a new CRM gives you a new CRM with the old problems.

1. Export contacts and deals from Zoho as CSV, with record IDs and owner fields.
2. Normalise phone numbers to one international format (+1 or +971 followed by the number). The same customer typed as 050 123 4567 and +971501234567 becomes two contacts otherwise, and the AI agent will not match a returning caller.
3. Merge duplicates on phone and email. Decide which record wins when they disagree.
4. Map Zoho deal stages to the new pipeline. Old stages that do not fit go to a sensible stage with a tag such as 'imported-from-zoho'.
5. Import a sample of 50 records first, check them with the client, then import the rest.
6. Spot-check 20 random records with the people who know those customers.

Step 10: Can GoHighLevel handle job dispatch for technicians?

Yes, for a basic dispatch module. When a deal is won, a workflow creates a job record (a custom object, or a card in a separate jobs pipeline) that carries the customer, property, scope, price, salesperson and photos, so nobody types them again. The job then moves through its own statuses.

• Statuses: new, coordinator review, ready to schedule, scheduled, technician assigned, accepted, en route, arrived, in progress, completed, customer confirmation, quality check, ready for invoice, closed. Exceptions: on hold, return visit, additional work, material pending.
• Required on the job: job number, customer, property, service, scope, coordinator, technician, date and time slot, priority and value.
• Evidence rule: a job cannot be closed without before and after photos and the technician's notes.
• Extra work found on site (booked for 4 ducts, found 6) creates a new opportunity for sales instead of being done for free or forgotten.

Keep the first version basic and agree the exact fields during discovery. If dispatch needs route optimisation, parts inventory or offline mobile forms, a dedicated field service app (such as Jobber, Housecall Pro or ServiceTitan) connected to the CRM may serve better than more custom objects.

Step 11: What should a home services CRM dashboard show?

Health first, then exceptions. A dashboard with 40 widgets gets opened once. One with four numbers and two charts gets checked every morning.

• Leads by source and campaign, so ad spend is judged on booked jobs, not form fills.
• Pipeline by stage, booked and completed appointments.
• Median first response time, against a 5-minute target.
• An exceptions list: leads outside the response target, quotes with no follow-up, missed calls awaiting a callback, overdue jobs, and the value of quotes nobody has touched.

Step 12: How do you test the setup before go-live?

Test every path in the trigger list with real actions, not by dragging cards around. Run each of these and check the card, the fields, the tasks and the notifications:

1. Submit each Meta form and each Google Ads form. Card in Opt-in, source filled, owner assigned.
2. Reply by text, WhatsApp and email to a new lead. Card moves to Hot Leads.
3. Call the main number with three reps logged in; answer on one. Others stop ringing and do not see a missed call.
4. Call and let it ring out. The AI agent answers, the card appears with the answers, the callback task is due in 5 minutes.
5. Book, cancel and reschedule an appointment. Booked, Cancelled, then back to Hot Leads.
6. Let a booked slot pass. Card moves to Completed.
7. Log five follow-up touches with no reply. Card moves to Recycled Leads with no open tasks.
8. Import 50 Zoho records and call one of those numbers. The agent matches the existing contact.

Then train the team on a normal day's work, not on the menus: where new leads appear, how to log a touch, how to book, what to do when the AI agent creates a card. A short written how-to guide stays useful long after the training call.

After go-live: can GoHighLevel ask for Google reviews after each job?

Yes, and the job record from step 10 is the right place to start it. When a job reaches closed, with the photos and the technician's notes in place, a workflow sends the customer a short text (WhatsApp in the UAE) with a link to your Google review page. Trigger it on the job's closed status, not on the Completed pipeline stage: Completed is set by time (T4), so a visit that fell through on the day could still get a review request.

• Send it once per job, from the business number the customer already knows.
• Skip jobs with a return visit, an open complaint or additional work still pending.
• Point it at the review page for the branch that did the job, if you have more than one listing.

It is not in the hours below. Add it once the dispatch statuses are reliable, because a review request is only as accurate as the status that triggers it.

How long does GoHighLevel setup take and what does it cost?

For this scope we estimated 43 to 48 hours of work, spread over 4 to 5 weeks so the client has time to review each phase and outside approvals can run in the background.

The week-by-week plan: week 1 discovery, users, pipeline, fields and calendar, with the phone number request and WhatsApp connection started; week 2 Zoho data and lead sources; week 3 stage automations, the follow-up sequence and the inbox; week 4 phones, the AI agent, dispatch and the dashboard; week 5 testing, AI tuning, go-live and training.

Our CRM setups start from AED 2,900 (about USD 790). A build at this scope, with the AI voice agent, migration and dispatch, is quoted as a fixed fee after discovery, with platform usage billed separately by GoHighLevel and Meta.

What usually delays a GoHighLevel rollout?

• Phone number approval, especially outside the US, where numbers can be issued on request.
• Meta business verification and the WhatsApp connection.
• AI voice agent tuning: it takes several rounds of real test calls before it handles different callers and accents well.
• Old CRM data: duplicates, missing fields and phone numbers in five different formats.
• Access and feedback: a missing admin login or a slow review is the most common cause of delay of all.

Which questions should you settle before you build?

These are the open points we put to the client. Each one changes a workflow, so get the answers in writing:

1. Ring all reps, or round robin? Does ringing stop for everyone once one rep answers?
2. Should the 10-second timeout change after hours, and should the AI agent answer out of hours or when nobody is logged in?
3. Which existing numbers forward to the new GoHighLevel number, and do Local Services Ads calls go there?
4. Are recordings and transcripts saved to the card, and what consent wording is needed?
5. Does an AI-handled call match an existing contact by phone, or always create a new card?
6. Does an AI-qualified caller stay in Opt-in until a rep calls back, or move straight to Hot Leads?
7. When a cancelled appointment is rescheduled, does it go to Booked or back to Hot Leads?
8. What is the callback target, and how are reps told: app, text or a board alert?
9. Which reps receive calls, and in which hours?
10. Who pays for AI minutes, call minutes and messaging, and is there a monthly cap?

Which house rules keep a CRM like this honest?

Automation only covers what is in the system. The client wrote their own rules for staff, and they are worth copying:

• No lead without an owner, and no open deal without a next action and a date.
• No discount outside a person's approval limit.
• No won deal without a job, and no job without a coordinator and a technician.
• No completed job without photos and a report.
• No customer details kept only in WhatsApp or on a personal phone.
• If it is not in the CRM, it did not happen.

Put a review a month after launch on the calendar: which steps people are skipping, which statuses are wrong, which automations failed. Fix those, then lock the process.