By Muhammad Nadeem, Chief Technology Officer · · 7 min read
What is the right order to set up GoHighLevel?
Set up GoHighLevel in this order: custom fields, pipelines and stages, calendars and channels, then lead capture, then automation, then reporting. The order is the whole point. Fields created after data has been written leave you with two versions of the same information, and automation built before the fields exist has nothing reliable to read.
Why the order matters more than the checklist
Almost every messy GoHighLevel account was set up correctly, just in the wrong sequence. Somebody connected a form on day one because leads were waiting, then added fields to hold what the form collected, then built automation to act on it, then discovered the pipeline stages did not match how the team actually sells.
Each of those steps was reasonable. The result is an account where nobody can safely change anything. Doing the same work in a different order costs no more and avoids all of it.
The checklist, in order
- 1
1. Write down how a lead actually reaches you
Every route, including the ones that currently bypass the CRM: portal enquiries, WhatsApp, a number on a business card, a form somebody built years ago. The routes you forget are where leads go missing.
- 2
2. Custom fields, before anything writes data
Decide what you need to capture and create it now. A field added later does not backfill, so you end up with the same information in a note for old contacts and a field for new ones.
- 3
3. Pipelines and stages that match real decisions
A stage should represent something that actually happened, not a feeling about progress. If two people would disagree about which stage a deal is in, the stage is not real.
- 4
4. Calendars, availability and booking
Configured against real working hours, real time zones and real buffer times. Booking that offers slots nobody can attend is worse than no booking.
- 5
5. Channels
Email sending domain authenticated, phone and messaging connected, WhatsApp where it applies. Test each one by sending and receiving, not by reading the settings screen.
- 6
6. Lead capture, through one server-side endpoint
Every surface posts to your own server, which writes to the CRM. That keeps credentials out of the browser and stops any surface choosing its own pipeline or tags.
- 7
7. Automation, one job at a time
Now that the foundations are stable. Small workflows with explicit names, each safe to change on its own.
- 8
8. Reporting, last
Reporting is a consequence of the first seven steps. Build it first and you will be measuring artefacts of your configuration rather than your business.
The mistakes that are expensive to undo
- Storing phone numbers in local format. GoHighLevel infers the country from the caller's IP when a number is not already international. A server in the United States and a customer in Pakistan produces a silently rewritten number that then cannot receive messages. Normalise to international format before every write.
- Letting the browser choose the destination. If client-side code can pick the location, pipeline, stage or tag set, then anyone can, and your data integrity depends on nobody looking.
- Creating opportunities for newsletter signups. It inflates the pipeline and destroys every conversion number you will later quote.
- Storing free-text enquiries in invented custom fields. Put the message in a note. Only move it to a field once you have read the real field id from the account.
- Leaving the old workflow running beside the new one. This is the single most common cause of customers receiving everything twice.
How to know the setup is actually finished
Submit a real enquiry through each live surface and confirm, in the account, that you get one contact, with the enquiry attached, the source recorded, the phone number in international format, an opportunity where one is appropriate, and exactly one notification.
A configuration that has not been tested end to end is not finished. A passing deployment proves nothing about whether the CRM received anything.