Business Profile
Business profile verification is the process of confirming that all foundational business information in the GHL sub-account is accurate: business name, phone number, physical address, operating hours, and timezone. This data feeds into nearly every other system component, from caller ID to email signatures to booking widgets. Getting it wrong here creates compounding errors downstream.
Why This Matters
Every automated message, every email footer, every calendar booking page, and every review request pulls business information from the sub-account profile. If the timezone is wrong, appointment reminders go out at 3am. If the business name has a typo, every automated email looks unprofessional. If the address is the owner’s home instead of the business location, Google integrations and local SEO efforts point to the wrong place.
These are not hypothetical problems. They are the most common source of “something is broken” tickets in the first month of an engagement. The client does not realize the issue is bad data in their profile. They think the system is malfunctioning. You spend 30 minutes troubleshooting a workflow only to discover the timezone was set to UTC instead of Eastern.
Business profile data also matters for compliance. LC Phone requires accurate business information for identity validation. A2P messaging registration checks the business name and address against public records. If your profile data does not match what is on file with the business registry, you will hit roadblocks when setting up the Phone Number in the next step.
How to Think About It
Treat the business profile as the single source of truth for the client’s identity within the system. Every field should be verified, not assumed. Do not copy data from your CRM contact record without confirming it with the client. Business names change. Addresses change. Hours change. The quick start call is the moment to get it right.
Go through each field methodically. Business name exactly as it should appear publicly. Primary phone number — which may not be the number you are about to purchase. Physical address, including suite numbers. Operating hours for each day of the week. Timezone matching the business location, not the owner’s personal location if they are in a different area.
This step feels tedious, and it is. That is precisely why it gets skipped or rushed, and why it causes so many problems. Spend the three minutes. Verify every field. Move on with confidence that the foundation is solid.
Common Mistakes
Using the agency’s timezone instead of the client’s. This is the most common error, especially for agencies serving clients across multiple timezones. If you are in California and your client is in New York, make sure the sub-account is set to Eastern, not Pacific. Every scheduled message, every workflow delay, every calendar availability slot depends on this setting.
Copying the business name with inconsistent formatting. “Bob’s HVAC” vs “Bob’s HVAC LLC” vs “Bobs HVAC” — these all look close enough until they show up in different places. Confirm the exact legal name and the exact DBA (doing business as) name, and use whatever the client prefers for public-facing materials.
Skipping the address for service-area businesses. Some businesses do not have a physical storefront. They still need an address in the system for compliance and integration purposes. Confirm what address the client uses for their Google Business Profile and match it.
Not verifying hours of operation. Operating hours affect when automated messages are sent. If the client’s hours say they are open until 5pm but they actually close at 3pm on Fridays, after-hours workflows will not trigger correctly. Go day by day.
Assuming the information from the sales process is still current. Data captured during the sales call or demo can be weeks or months old by the time onboarding starts. The client may have moved, changed their phone number, or updated their business name. Always verify, never assume.
Tools Involved
Business profile settings live in the GHL sub-account under Settings > Business Profile. This is the same data that populates custom values used in templates and automations. The information here also feeds into the Phone Number setup process, particularly for LC Phone identity validation. If you are using GHL MCP for bulk management, the Locations API can read and update business profile fields programmatically.
Where This Fits
Business profile verification sits at sequence position 12, running in parallel with Mobile App and Team Members. It depends on Sub-Account Access being confirmed first, because you will be in the sub-account settings while verifying. It is a prerequisite for Phone Number purchase at sequence 13, because identity validation requires accurate business information. It also supports the connection steps: GBP Connection and Reputation Setup both work better when the business profile matches the client’s Google Business Profile data.
Common Questions
What if the client has multiple locations? Each location should have its own sub-account with its own business profile. Do not try to manage multiple locations in a single sub-account. The profile data needs to be specific to each physical location for integrations and compliance to work correctly.
Should I update the business profile if the client rebrands later? Yes. Any time the business name, address, or phone number changes, the sub-account profile must be updated. Downstream systems pull from this data, so an outdated profile means outdated automations. Build this into your ongoing client management process.
Does the business profile affect SEO or online presence directly? Not directly. The sub-account profile is internal to GHL. However, it feeds into outbound communications, calendar booking pages, and reputation management tools, all of which affect the client’s public-facing presence. Consistency between the GHL profile and the client’s Google Business Profile, website, and directory listings is important for local SEO.