# Customize Default Naming Conventions for New SaaS Accounts

> Choose how new SaaS sub-accounts are named in GHL Customer Care. Company Name or Customer Name + ’s Account. Includes setup steps, external checkout tips, and FAQs.

- Source: https://docs.ghlcustomercare.com/docs/saas-configurator/saas-mode/customize-default-naming-conventions-for-new-saas-accounts
- Section: SaaS Configurator / Saas Mode
- Reading time: 4 min
- Images: 1, each explained below

---
Discover the new configuration in the SaaS Configurator that lets your agency control how **new** SaaS sub-accounts are named at creation. Choose between the **Customer’s name** or the business **Company Name** to reduce post-onboarding edits and improve clarity across search, reporting, and client communications. This article explains the options, behavior, setup, and external checkout requirements so your team can adopt the best convention for your workflow.

---

**TABLE OF CONTENTS**

-   [What Is the Default Naming Convention for New SaaS Sub-Accounts?](#what-is-the-default-naming-convention-for-new-saas-sub-accounts)
-   [Key Benefits of Default Naming Convention for New SaaS Subscribers](#key-benefits-of-default-naming-convention-for-new-saas-subscribers)
-   [How To Setup Default Naming Convention for New SaaS Subscribers](#how-to-setup-default-naming-convention-for-new-saas-subscribers)
-   [Naming Convention Options](#naming-convention-options) 
-   [External Checkout Integration](#external-checkout-integration)
-   [Behavior & Examples](#behavior-and-examples)
-   [Company name capture](#company-name-capture)
-   [Frequently Asked Questions](#frequently-asked-questions)
-   [Related Articles](#related-articles)

---

# **What Is the Default Naming Convention for New SaaS Sub-Accounts?**

This setting defines the **default naming convention** used when GHL Customer Care creates a **new SaaS sub-account** during checkout. Agencies can pick **Company Name** (the business provided during checkout) or keep the traditional **Customer Name + ’s Account** format. The choice applies to **future** sign-ups and does **not** rename existing accounts.

Note: This option lives in the **SaaS Configurator** at the Agency level and is available to agencies with **SaaS Mode** on the **Agency Pro ($497) plan**. If you’re on Starter or Freelancer, upgrade to **Agency Pro** to access SaaS Configurator features.

---

## **Key Benefits of Default Naming Convention for New SaaS Subscribers**

-   **Improved Clarity:** Sub-account names reflect the operating business rather than only the buyer’s personal name.
    
-   **Enhanced Client Experience:** Reduces manual post-onboarding updates by applying your preferred naming automatically.
    
-   **Operational Efficiency:** Makes accounts easier to search, filter, and recognize for support and success teams.
    
-   **Flexible Options:** Switch between **Company Name** and **Customer Name + ’s Account** to match your internal workflow.
    

---

## **How To Setup Default Naming Convention for New SaaS Subscribers**

1.  In your Agency view, Open **SaaS Configurator** → **Advanced Settings** → **Sub-Account** **Onboarding**.
    
2.  Under **Sub-Account Onboarding**, choose one:
    
    -   **Company Name** (recommended for business-forward clarity), or
        
    -   **Customer Name + ’s Account** (useful if your team searches primarily by owner).
        
3.  Click **Save**. New SaaS sub-accounts created via GHL Customer Care funnels (and supported external checkouts) will now follow your selection.
    

![How To Setup Default Naming Convention for New SaaS Subscribers (image 1 of 1)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155052559942/original/71dxTxR0svvIDdWv2CscYvCvHQPGVKhLOg.jpeg)

**How To Setup Default Naming Convention for New SaaS Subscribers (image 1 of 1)**

This screenshot appears in the "How To Setup Default Naming Convention for New SaaS Subscribers" section of "Customize Default Naming Conventions for New SaaS Accounts". The text alongside this image reads: In your Agency view, Open SaaS Configurator → Advanced Settings → Sub-Account Onboarding. Under Sub-Account Onboarding, choose one: Click Save. New SaaS sub-accounts created via GHL Customer Care funnels (and supported external checkouts) will now follow your selection. This part of the guide covers 2 fields, listed below. Immediately after, the guide continues: Review what each option does so you can align the default with how your team identifies and supports new customers.
- What to choose: In your Agency view, Open SaaS Configurator → Advanced Settings → Sub-Account Onboarding. Under Sub-Account Onboarding, choose one: Click Save. New SaaS sub-accounts created via GHL Customer Care funnels (and supported external checkouts) will now follow your selection.
- Fields: Under Sub-Account Onboarding, choose one:, Company Name (recommended for business-forward clarity), or
- Controls: SaaS Configurator, Advanced Settings, Sub-Account, Onboarding, Sub-Account Onboarding, Company Name, Customer Name + ’s Account, Save
- Next: Review what each option does so you can align the default with how your team identifies and supports new customers.

Example values (illustrative, not read from the screenshot):

- Company Name (recommended for business-forward clarity), or: Northgate Dental

Full procedure:

1. In your Agency view, Open SaaS Configurator → Advanced Settings → Sub-Account Onboarding.
2. Under Sub-Account Onboarding, choose one:
3. Click Save. New SaaS sub-accounts created via GHL Customer Care funnels (and supported external checkouts) will now follow your selection.

---

## **Naming Convention Options** 

Review what each option does so you can align the default with how your team identifies and supports new customers.

|  | **Company Name** | **Customer Name + ’s Account** |
| --- | --- | --- |
| **Uses** | Business name entered at checkout | Customer's personal name |
| **Example** | Acme Dental | Jane Smith’s Account |
| **Best for** | Agencies organizing accounts by business | Agencies organizing accounts by account owner |
| **Fallback** | Customer Name + ’s Account if Company Name is missing | Not applicable |

**Note:** If the Company Name field is not present or is left empty during checkout, GHL Customer Care defaults to Customer Name + ’s Account.

---

## **External Checkout Integration**

You can extend the same naming behavior **beyond** GHL Customer Care funnel checkouts by passing the client’s business name from your external checkout into GHL Customer Care as metadata.

-   Ensure your external checkout sends a **non-empty** `companyName` **subscription metadata** value.
    
-   Keep the SaaS Configurator set to **Use Company Name** to apply the business name when metadata is present.
    
-   If `companyName` is missing or empty, GHL Customer Care falls back to **Customer Name + ’s Account**.
    

**Example metadata payload (illustrative):**

`{ "subscription": { "metadata": { "companyName": "Acme Dental" } } }`

---

## **Behavior & Examples**

These quick examples clarify what you and your clients will see after signup so expectations are aligned.

-   **If “Company Name” is selected and provided at checkout:**
    
    -   _Resulting sub-account:_ **Acme Dental**
        
-   **If “Company Name” is selected but not provided:**
    
    -   _Resulting sub-account:_ **Jane Smith’s Account** _(fallback to customer name)_
        
-   **If “Customer Name + ’s Account” is selected:**
    
    -   _Resulting sub-account:_ **Jane Smith’s Account**
        

**Note:** After Account Creation admins can update the **Location’s Friendly Business Name** later if needed. Changing this later does not retroactively change past confirmations or emails already sent. 

## **Company name capture**

GHL Customer Care captures the Company Name a customer enters at checkout and includes it in the subscription’s metadata as \`companyName\`.

This applies to:

-   V2 funnels using the Payments ecosystem (metadata passed via APIs)
-   SaaS V1 setups using Stripe (metadata passed via Stripe)

---

## **Frequently Asked Questions**

**Q:** **Does this setting affect existing SaaS accounts?**  
No. It applies only to **new** SaaS sign-ups after you save the setting.

**Q:** **What happens if no Company Name is provided during checkout?**  
GHL Customer Care defaults to **Customer Name + ’s Account**.

**Q: Can we change the default later?**  
Yes. Update the option in **SaaS Configurator** at any time. It applies to **future** sign-ups.

**Q:** **How do we enable this for external checkouts?**  
Send a **non-empty** `companyName` in subscription metadata and keep the setting on **Use Company Name**.

**Q:** **Will changing the setting rename previously created accounts?**  
No. There’s no retroactive renaming.

**Q: Does this influence merge fields like** `**{{location.name}}**` **in communications?**  
The initial Location name reflects the chosen convention at creation. Messages using `{{location.name}}` will display that name unless it’s edited later in the Location settings.

**Q:** **Could unusual characters in Company Name cause issues?**  
Use standard alphanumeric characters where possible for best results. If a name is not accepted by your external checkout or looks incorrect, edit the Location name after creation.

---

### **Related Articles**

-   SaaS Configurator: Onboarding
    
-   SaaS Mode – Full Setup Guide & FAQ
    
-   Guide to SaaS Plan Creation, Sales, and Customer Onboarding
    
-   Using Stripe Checkout Pages For SaaS Mode Plans
    
-   [Convert Existing Sub-Account to SaaS Mode Subscription Plan](https://docs.ghlcustomercare.com/docs/saas-configurator/saas-mode/convert-existing-sub-account-to-saas-mode-subscription-plan)

---

Documentation for GHL Customer Care. Support: support@ghlcustomercare.com