HighLevel Setup Checklist: CRM, Pipeline, Calendar & Workflows

The rule

Do not automate a broken process.

Build one working customer path first. A clean pipeline, a working calendar, a reliable lead source, and one tested workflow are more valuable than dozens of automations nobody has validated end-to-end.

Step 1

1. Foundation

Set the account basics before automating anything.

Confirm business name, address, timezone, and contact information.Add the users who actually need access and review their permissions.Connect the primary sending email/domain configuration you plan to use.Connect the phone setup you plan to use before building call or SMS automations.Define the one primary sales or service process this location needs to run first.

Step 2

2. Pipeline + opportunities

A clean pipeline gives the rest of the system somewhere to put leads and deals.

Create the primary pipeline for the sales or service process.Create stages that represent real operational handoffs, not every tiny activity.Define what qualifies an opportunity to move into each stage.Create one test contact and one test opportunity.Move the test opportunity through every stage and verify the process makes sense.

Step 3

3. Calendar + scheduling

Booking should work before follow-up automation starts driving people toward it.

Create the booking calendar that matches the real appointment type.Set duration, availability, buffers, timezone, and meeting location.Connect external calendars needed for availability and conflict checking.Confirm the correct team member or assignment logic is attached.Complete a test booking from the public booking page and verify confirmations.

Step 4

4. Lead capture

Make sure every new lead enters with enough information to route and follow up.

Choose the first lead source to operationalize: form, survey, chat, inbound call, import, or integration.Create or verify required contact fields and custom fields.Map the lead source to the correct contact and opportunity fields.Submit a real test lead through the same public path a customer will use.Confirm the contact and opportunity are created or updated as intended.

Step 5

5. First workflow

Automate one complete path before building a library of disconnected workflows.

Choose one trigger with a clear business outcome.Add the immediate customer response or internal notification.Add only the delays, branches, and actions required for that outcome.Define the stop condition so contacts do not keep receiving messages after conversion.Run the workflow with a test contact and verify every action in order.

Step 6

6. Reporting + ownership

Someone should be able to tell whether the setup is working without opening every record.

Decide who owns new leads, appointments, open opportunities, and failed follow-up.Define the small KPI set the team will review consistently.Confirm opportunity values and statuses are populated consistently enough to report on.Create a simple daily or weekly operating review around the pipeline.Document the owner for future workflow, calendar, and pipeline changes.

Step 7

7. Launch test

The setup is not finished until the full customer path works.

Submit a new lead using an address and phone number not already in the CRM.Verify contact creation, opportunity creation, assignment, and source attribution.Verify the first email/SMS/notification arrives correctly.Book the appointment or complete the intended conversion action.Confirm the workflow stops or changes state correctly after conversion.Fix failures before adding more automations.

Minimum viable HighLevel

If these seven things work, you have something real.

Lead enters→Contact updates→Opportunity appears→Owner is assigned→Follow-up fires→Appointment converts→Automation stops or advances

Common setup mistakes

What to avoid while checking the boxes.

Too many pipeline stages

Stages should represent meaningful business states. If nobody makes a different decision because of a stage, it may not need to exist.

Automation before ownership

A workflow can send messages, but it cannot fix a team that does not know who owns the lead after the message sends.

No stop conditions

Follow-up sequences should know when someone booked, replied, purchased, or otherwise converted.

No real-world test

Previewing a workflow is not the same as sending a lead through the actual public path and checking every downstream action.

Official HighLevel setup references

This checklist is SkillMerchant's recommended implementation order. Product-specific setup facts were checked against HighLevel's current official documentation.

Pipelines & opportunities ↗Workflows ↗Calendar setup ↗Calendar sync & conflicts ↗