Configure Default Naming for New SaaS Sub-Accounts

As an agency, you can now define a default naming convention for all new SaaS sub-accounts created through your CRM. This setting allows you to automatically name accounts using either the customer's business name or the customer's personal name, streamlining onboarding and improving organization.

Understanding the Default Naming Convention

This configuration determines the name automatically assigned to a new SaaS sub-account when it is created through a checkout process. You can select to use the business's Company Name (entered during checkout) or the traditional format of Customer Name + ’s Account. This setting only applies to new accounts created after it is configured and does not rename existing accounts.

Note: This feature is part of the SaaS Configurator and is available to agencies on the Agency Pro plan with SaaS Mode enabled.

Benefits of Configuring a Default Naming Convention

• Improved Clarity: Account names that reflect the actual business are easier to identify.
• Streamlined Onboarding: Reduces the need for manual renaming after a client signs up.
• Operational Efficiency: Makes searching for and managing client accounts faster for your team.
• Flexibility: You can switch between naming options to suit your agency's workflow.

How to Set Up the Default Naming Convention

To configure this setting, follow these steps:

1. Navigate to your Agency view and open the SaaS Configurator.
2. Go to Advanced Settings and select Sub-Account Onboarding.
3. Under the Sub-Account Onboarding section, choose one of the following options:
   • Company Name: Recommended for clear identification of the business.
   • Customer Name + ’s Account: Useful if your team primarily searches for accounts by the owner's name.
4. Click Save.

Your selection will now be applied to all new SaaS sub-accounts created through your CRM's funnels and supported external checkout systems.

Naming Convention Options

Review the two available options to choose the best fit for your agency.

• Company Name: The sub-account is named using the business name provided during checkout. For example: Acme Dental.
• Customer Name + ’s Account: The sub-account is named using the customer's personal name with "'s Account" appended. For example: Jane Smith’s Account.

Note: If the Company Name field is not available or is left blank during checkout, the system will default to the Customer Name + ’s Account format.

Integration with External Checkouts

To apply the same naming behavior for clients signing up through an external checkout system, you must pass the business name as metadata. Ensure your external checkout sends a non-empty companyName value within the subscription metadata. The SaaS Configurator must be set to Use Company Name for this to take effect. If the companyName metadata is missing or empty, the system will fall back to the Customer Name + ’s Account format.

Behavior and Examples

The following examples illustrate the outcome based on your configuration and the information provided at checkout.

• If Company Name is selected and provided: The resulting sub-account name is Acme Dental.
• If Company Name is selected but not provided: The resulting sub-account name is Jane Smith’s Account (fallback behavior).
• If Customer Name + ’s Account is selected: The resulting sub-account name is Jane Smith’s Account.

Note: After an account is created, an admin can update the Location's Friendly Business Name later if needed. This change does not retroactively alter any confirmation emails that were already sent.

Frequently Asked Questions

Does this setting rename existing SaaS accounts?
No. It only applies to new accounts created after the setting is saved.

What happens if no Company Name is provided during checkout?
The system defaults to the Customer Name + ’s Account format.

Can I change the default naming convention later?
Yes. You can update the selection in the SaaS Configurator at any time. The change will apply to future sign-ups.

How do I use this with an external checkout?
Send a non-empty companyName value in the subscription metadata and ensure the setting is configured to use the Company Name.

Will changing the setting rename previously created accounts?
No. There is no retroactive renaming of accounts.

Does this affect merge fields like {{location.name}} in automated messages?
Yes, the initial value for the location name will reflect the chosen convention. This value is used in merge fields unless it is later edited in the Location settings.