Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Go High Level

Go High Level artwork

How to Manage Companies in GoHighLevel — B2B CRM Guide

Apr 29, 202620 minAudio
ShareXLinkedInFacebookWhatsAppEmail

🚀 Start your FREE 30-day GoHighLevel trial: https://globalhighlevel.com/trial Learn how to leverage the Companies feature in GoHighLevel to manage business relationships at the enterprise level. This episode covers everything digital marketing agencies need to know about consolidating client interactions and organizing company-wide data in one platform. In this episode you'll learn: • How to create, edit, and save detailed company profiles in GoHighLevel • Setting up and managing custom fields for your specific business needs • Customizing list views and using advanced filters for better organization • Searching and sorting across standard and custom fields efficiently Ready to try GoHighLevel yourself? The link above gets you a FREE 30-day trial - double the standard 14-day trial. See why thousands of agencies run their entire business on one platform.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

Welcome to today's deep dive. Um, before we even get into the heavy lifting, I have a massive welcome for you listening right now. And uh, actually a really special offer to get you started on the right foot. Yeah, right off the bat, we're bringing the value. Exactly. So, everything we're discussing today involves setting up like the ultimate digital marketing agency architecture. And if you want to put these strategies into practice immediately, you can grab a completely free 30-day Go High Level trial. Which is huge, by the way. It really is. That is double the standard trial length, so it gives you a full month of unrestricted access. The link to claim it is waiting for you right down in the show notes. So, you know, definitely click that to follow along. Yeah, it's, I mean, it is the perfect sandbox for building out a truly professional environment. You can test the whole architecture out before you ever have to, um, migrate a single real client over. Right, which is so critical because, well, imagine you're checking into this highly acclaimed five-star luxury hotel. You've seen the premium ads, you're paying a premium rate, and you are expecting a flawless service. Oh, absolutely, the white glove treatment. Exactly. But then you walk through the front doors and the lobby sign is like held up by duct tape. Not a good look. Right. And the receptionist name tag has another hotel's logo just kind of crossed out with a permanent marker. And behind the desk, the back office doors are just wide open, and you can see sensitive customer files scattered all over the floor. Yeah, I mean, the illusion of premium service just instantly evaporates at that point. Completely. Start questioning everything, including whether your credit card is even safe, you know, no matter how nice the actual hotel room might end up being. Exactly. And that exact psychological dynamic, it plays out every single day in the digital world. If you're an agency owner asking clients to trust you with their, um, their brand equity and their ad budget. Which is a huge ask. It is. But then the software platform you give them to log into looks piece together, or worse, unsecured, you lose their trust before they even hit the login button. 100%. So today's mission is really about making your agency look flawlessly professional, completely secure, and hyper-organized. We are walking through the core company settings and the underlying data architecture. Moving from how your agency presents itself to the world to how it, uh, locks down its data. Right, and finally how it organizes the actual businesses you serve. So let's start with the presentation part, the white-labeled fortress. Yeah, building that premium experience starts at the absolute foundation, which is the basic details configuration. The plumbing, basically. Exactly. I mean, it sounds so mundane just typing in your business name, your email, website, URL, your niche, but this data isn't just sitting passively in some database somewhere. Right. These fields actually act as the global variables for your entire system infrastructure. Which is something I think people miss because when the platform sends out a system-generated notification or like auto-populates a calendar invite, it pulls directly from these foundational fields. If you leave the agency email blank, or just put in generic placeholder text to get past the setup screen, your high-ticket clients are suddenly going to receive billing receipts or password reset links from a generic agency XYZ address. Yeah, and it just instantly breaks the immersion. Right. The website URL you input establishes your baseline credibility across all the white-labeled experiences. Yeah. But the real leverage, um, the part where you completely erase the fact that you're using a third-party software provider, that happens when you configure the custom domains. Oh, absolutely. This is where we shift from being a consultant who, you know, just uses tools, to being viewed as a software provider in the eyes of the client. Which is a massive paradigm shift. But the domain setup isn't just one single toggle, right? No, no, there are two distinct domains we need to configure. You have the white-label domain and then the API domain. Right. And they serve completely different functions in the architecture. So the white-label domain is your front-facing portal. Instead of your clients navigating to a generic high-level login screen, they go to a custom subdomain. Like app.youragencyname.com. Exactly. You control the URL, you control the branding. But the API domain, um, I feel like that is arguably even more critical for maintaining that illusion of proprietary software. Yeah, because it handles the engine underneath. Right. Let's explore the mechanics of that API domain, because when your system is firing off SMS campaigns or generating email tracking links, you're sending out thousands of URLs. Thousands. And if you haven't configured the API domain, every single one of those links is going to show a generic software domain. Which is a dead giveaway. Right. Your client looks at the marketing campaign you built for them and they see a URL that completely exposes the underlying tool. Yeah, but by configuring the API domain at both the agency level and the sub-account level, every single tracking link is fully branded to your agency. It's total ownership of the client experience. Exactly. The high-level branding is removed at the cellular level of your marketing campaigns. Which fundamentally changes how the market values your business. Now, alongside the domain, we obviously have the visual branding. Right, the logos and all that. Yeah, and uploading the logo is pretty straightforward. You know, you need a 350 pixel by 180 pixel image, under 2.5 megabytes, and that populates the login screen and the app header. But wait, hold on. I need to push back on something here or ask about the browser icons. The favicons. Oh, the favicon. Yeah. Why isn't there just a single master button in the agency settings to upload my browser tab icon once and just have it populate everywhere? Setting it manually for every single funnel and course just seems like a huge unnecessary time sink. It is, uh, it is a really common point of frustration. I hear that a lot. Uh-huh. But it actually makes sense when you look at the system's architecture. Really? How so? Well, you aren't building a monolithic single-brand website. You're building a vast network of highly varied assets. The platform forces you to set these icons at the asset level, because you might be managing multiple sub-brands or unique courses or distinct client portals all operating under completely different visual identities. Oh, I see. So it sacrifices a little bit of upfront convenience for ultimate granular control. So if I'm building a client portal for a specific fitness coach, I go into the client portal branding settings for that specific asset and upload their distinct icon. If it's a funnel for a dental practice, I go into that specific site's settings. You got it. And a really crucial technical note here, browser caching is incredibly aggressive when it comes to these small icons. Oh, it's the worst. It really is. If you upload the 32x32 pixel square and the old icon is still showing up in your browser tab, do not immediately assume the platform is broken. Right, don't panic. Yeah, just open an incognito window or clear your cache. Nine times out of ten, your browser is just stubbornly holding onto the old image data. That's a great tip. Okay, now, beyond uploading static images, we have the ultimate customization lever custom CSS and JavaScript. Oh, yeah, the fun stuff. Right. This is where an agency can write custom code to completely overhaul the dashboard's user interface. You know, you can inject a third-party live chat widget directly into the app, so your clients can instantly ping your support team, or you can restyle the entire color palette for a dark mode. It is incredibly powerful. But, um, injecting custom code into a constantly evolving SaaS platform requires severe discipline. Severe discipline, I like that. It's true. You have to categorize the platform into two environments: safe zones and danger zones. Okay, lay it out for us. What are the safe zones? The safe zones include the login page, the main sidebar, the header bar, and specific embeddable widgets. These elements have really stable architectural structures. Right, they use stable CSS classes that aren't just going to disappear overnight and update. But what constitutes a danger zone? Anything that relies on dynamic code generation or mobile architecture. For instance, do not, and I mean, do not attempt to force custom CSS onto React pop-ups, like the payment modals. Okay, let's define what that actually means for the non-developers listening. A React pop-up isn't just a static box of HTML sitting on the page, right? No, not at all. It's a dynamic window that the platform's core code generates on the fly based on user actions. Exactly. And because they are dynamic and constantly being optimized by the high-level engineering team, forcing your own static hard-coded styling onto them is incredibly fragile. Because what happens when they update it? Well, when the platform pushes a core update to improve that payment modal, the underlying code changes. Your static CSS clashes with the new architecture, the elements shift off the screen, buttons become unclickable. Oh, man. Yeah, and your clients are suddenly calling you in an absolute panic because they can't process a transaction. Which is exactly what we are trying to avoid. So the same goes for the drag-and-drop builder UI. 100%. Keep your custom code far, far away from the core functionality tools. Right, because a perfectly white-labeled dashboard is completely useless if the walls collapse every time there's a software update. Exactly. Which kind of brings us to the operational backend. Right, the transition from presentation to protection. Yeah, because a beautiful custom-branded front-end doesn't mean much if the back-end is a sieve. Once the visual identity is locked in, the focus has to shift entirely to automation and security. Okay, so let's go back to that basic details tab. There is a section dedicated entirely to feature toggles, and it kind of functions as a switchboard for agency-wide capabilities. Yeah, super powerful. You can activate AI employees for repetitive tasks, or workflow AI. And workflow AI isn't just a basic automation tool. Unlike standard if-then logic where a trigger leads to a static action, workflow AI can actually evaluate the sentiment of a client's reply and route them accordingly. Yeah, you're building a thinking system, not just an autoresponder. Right. It elevates the operational capacity of the agency immensely. But if we pivot over to the advanced settings tab, we find what is arguably the most critical toggle for long-term stability: enhanced account security. The heavy vault doors. Exactly. The platform strongly advocates for enabling this, specifically to disable the auto-generation of legacy API keys and to restrict access to sensitive API endpoints. Let's break down the mechanics of that risk. What exactly makes a legacy API key a vulnerability? Well, a legacy API key is essentially an all-access skeleton key to your entire database. Wow. Okay. Yeah, in older software paradigms, you simply handed this single string of text to a third-party application, and it was granted wide-open permissions to read, write, or delete practically anything in your account. So it didn't differentiate between letting an app update an email address and letting an app wipe your entire CRM. Exactly. It was all or nothing. Modern security uses scoped endpoints. You grant an app permission to do one very specific task and absolutely nothing else. Right. So by enabling enhanced account security, you actively prevent the system from generating those old skeleton keys. Which protects your entire client roster from accidental data leaks caused by poorly secured third-party tools. That is massive. Is there ever a reason not to turn it on? The only scenario where you would leave this disabled is if your agency relies heavily on a very specific, older external software that absolutely requires those legacy APIs to function. Right. Otherwise, locking this down is non-negotiable. Secure the perimeter. And speaking of perimeter security, um, the session timeout feature is another advanced setting that is often totally overlooked. Oh, constantly. You can force the system to automatically log users out after a specific period of inactivity, anywhere from 15 minutes to never. And choosing never is an operational hazard. Especially if your agency operates out of a shared office space or utilizes shared hardware. Right. It's the equivalent of a bank vault that automatically swings shut when motion stops. I love that analogy. Yeah, if an account manager walks away from their desk to grab a coffee, leaving, uh, say a 60-minute session timeout, ensures that a client's entire CRM isn't left exposed on an unlocked screen for anyone to wander past and export. Yeah, it's just fundamental workspace hygiene. Absolutely. And, you know, another crucial element of workspace hygiene involves how the system handles new users, specifically regarding the preloaded example data setting. Oh, yeah. Let's talk about that. By default, the platform tries to be helpful. When a new user is added, the system automatically generates a personal booking calendar for them. Which, I mean, sounds incredibly helpful on the surface. Why would we want to turn that off? Because of how agencies actually scale. If you're deploying a highly customized snapshot for a specific niche, say a chiropractic clinic setup, that snapshot already contains perfectly configured, meticulously routed calendars for specific treatments. Right, you've already built exactly what they need. Exactly. So when the system automatically generates generic personal calendars for every single staff member you add to that sub-account, it creates massive data clutter. Oh, I see. You end up with dozens of ghost calendars that no one uses. Right, which muddies up the reporting and just confuses the client. Okay, so disabling preloaded example data stops that automated creation, keeping your calendar list strictly limited to the assets you intentionally build. Exactly. Keep it clean. So the platform's visual branding is flawless, the security is modernized, the workspace is pristine. Now, how do we handle the actual humans doing business within this system? Ah, the contacts. Right, because as an agency scales, managing contacts without a structural hierarchy becomes an absolute nightmare. It really does. If you are only tracking individual contacts, your CRM is basically a flat spreadsheet. It's a 2D rolodex. You know, you have John, you have Jane, and you have Bob. Just a list of names. Right. But in reality, John is the CEO, Jane is the marketing director, and Bob handles the billing for Acme Corporation. Tracking them individually means you constantly lose context regarding the broader business relationship. And that's where the company object feature totally changes the architecture. It's a shift from a flat B2C consumer list to a true B2B 3D relational database. It allows you to create a primary business entity Acme Corp and group multiple individual contacts underneath that umbrella. And this isn't just about organizing a digital filing cabinet, right? The true power here lies in the data architecture, specifically custom fields. Oh, absolutely. Because you aren't limited to standard data points like a global phone number or a corporate website. You can create highly specific custom fields attached directly to the company object. Things like annual revenue range, industry category, or uh, total employee count. Right. And those fields become the engine for highly sophisticated outcome marketing. If you attach annual revenue to a company profile, you aren't just storing trivia. You are building an advanced filter. Let's walk through a scenario for everyone listening. Imagine your agency wants to launch an aggressively targeted direct mail and digital ad campaign offering a like a premium service package. Okay, I'm with you. You don't want to blast this to every contact in your database. Because you utilize the company object, you can build a filter targeting only SaaS companies with an annual revenue over $5 million. Which is incredibly precise. Right. And the system instantly pulls up every single individual contact associated with the companies that meet that exact criteria. Yeah, it allows you to execute true enterprise-level account-based marketing. Okay, but practically speaking, let's say I have 5,000 individual contacts sitting in my database right now. Okay. I am not going to spend my weekend manually clicking on John's profile, linking him to Acme Corp, and then repeating that process 4,999 times. Manual data entry at that scale just destroys productivity. Yeah, no one wants to do that. And the engineers actually anticipated that friction. In the settings, under the objects menu, there is a specific automation toggle. Automatically create and associate companies from contact business names. Wait, really? So it scans the existing flat data and builds the relational web automatically. Precisely. If John and Jane both have Acme Corp typed into the business name field on their individual contact records, flipping that toggle commands the system to automatically generate the Acme Corp company object. And it links them. Yep, instantly links both contacts to it. It resolves the manual labor bottleneck in like seconds. That is brilliant design. But there are a few operational rules regarding this architecture that are crucial to understand, so you don't break your workflows, right? Right. First, a contact can only be associated with one company at a time. There is no double-dipping, which maintains strict attribution for your reporting. Exactly. Second, if a business goes bankrupt or you lose the account and you delete the company object, it does not delete the individual contacts nested inside it. Oh, that's a relief. Yeah. The structural umbrella is removed, but the contacts remain safely in your database, preventing catastrophic data loss. And third, if you do need to manage associations manually, you are not forced into individual profiles. You can bulk-select contacts directly from the main list view and assign them to a company in one swift action. Right. And beyond the marketing applications we discussed, this relational database creates a single source of truth for the entire agency. Consider the sales department. Oh, yeah. When a sales rep is managing a complex pipeline, they are pitching an isolated individual. They are pitching an organization. Right. And by accessing the company object profile, the sales rep can see every single touch point, every logged email, every recorded phone call made with anyone at that organization. It completely eliminates the risk of a sales rep blindly pitching the marketing director without realizing that a different rep had a tense negotiation with the CEO just yesterday. It provides total transparency. And for account management, it offers a clean, centralized way to organize vendors, strategic partners, or corporate hierarchies. Everyone in your agency is looking at the exact same structurally sound data. We have essentially walked through the blueprint for taking an agency from a disjointed duct-taped software stack to a fully white-labeled, highly secure, and deeply organized enterprise machine. We really have. Which, um, leaves a fascinating implication for you to consider as you build all this out. Okay, let's hear it. If you perfectly configure your custom domains, if you maximize your custom CSS within the safe zones to create a totally unique UI, if you lock down your back-end security protocols and you structure your data into complex automated company hierarchies. Yeah. At what point does your Go High Level instance stop being merely a tool you pay a subscription for and start becoming proprietary intellectual property that adds undeniable valuation to your agency? Wow. That is the ultimate question. When does the infrastructure become your intellectual property in the eyes of the market? It completely changes how you view your tech stack. It really does. It's something to seriously analyze as you construct your environment. Well, that is a wrap on today's deep dive. Thank you so much for joining us and exploring the architecture of a truly professional digital agency setup. That was a great deep dive. Absolutely. And before we sign off, I want to remind you one last time to take advantage of the resources available to you. You really do not want to attempt building this complex architecture on a standard, rushed trial. Definitely not. The link for the free 30-day Go High Level trial is waiting for you in the show notes. That double-length trial gives you a full month to perfect your white-label domains, secure your API endpoints, and structure your company object before you ever pay a dime. Yeah, click the link down there. We highly encourage you to click that link and start building your proprietary environment today. Until next time, keep your data structured, secure your perimeter, and make sure your digital lobby always matches the quality of your service. Have a great one.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Stop Chasing Leads: Auto Follow-Up in Conversation AI

    Oct 6, 202626 minAudio

    Your AI bot can now automatically follow up with inactive contacts - no manual work required. Learn how HighLevel's Conversation AI detects drop-offs, schedules smart reminders, and closes deals on autopilot. Watch this...

    Credit the people on this episode

  2. Knowledge Base Triggers: Control Your Conversation AI Responses

    Oct 6, 202617 minAudio

    Stop letting AI guess when to show offers and pricing. Learn how GoHighLevel's Knowledge Base Triggers deliver the right content at the exact moment your prospects need it - driving more conversions and eliminating...

    Credit the people on this episode

  3. Conversation AI on Mobile: Reply to Customers Instantly (No Desktop Needed)

    Oct 6, 202617 minAudio

    Manage customer conversations from your phone with Conversation AI in the HighLevel mobile app. Learn how to use Autopilot Mode, Suggestive Mode, and control your AI assistant on-the-go across WhatsApp, Facebook,...

    Credit the people on this episode

  4. Voice AI Agent Transfer: Route Calls Without Dropping Them

    Oct 6, 202623 minAudio

    Learn how GoHighLevel's Voice AI Agent Transfer hands off live calls between specialized agents seamlessly - no dial transfers, no restarts. Discover how to route callers to sales, support, billing, or language-specific...

    Credit the people on this episode

  5. Sell Your AI Agents: GoHighLevel Marketplace Launch Guide

    Oct 6, 202620 minAudio

    Turn your Conversation AI and Voice AI templates into revenue streams. Learn how to package, list, and sell your agents on the GoHighLevel Marketplace - complete with workflows, automations, and knowledge bases...

    Credit the people on this episode