Configure Default Naming for New SaaS Accounts

This guide explains how to set a default naming convention for new sub-accounts created through your SaaS offering. By defining this upfront, you can ensure new accounts are named consistently, improving clarity for your team and reducing manual adjustments after a client signs up.

Understanding the Default Naming Convention

The default naming convention determines how a new sub-account is automatically named during the sign-up process. You can choose to have the account named after the client's business or after the primary contact person. This setting is applied to all new accounts created after it is configured and does not change the names of existing accounts.

Note: This feature is part of the SaaS Configurator and is available on the Agency Pro plan.

Benefits of Setting a Default Naming Convention

• Improved Clarity: Account names that reflect the client's business are easier to identify at a glance.
• Streamlined Onboarding: Automatically applying your preferred format saves time by eliminating the need to manually rename accounts.
• Better Organization: Consistent naming makes it simpler to search for and filter accounts within your CRM.
• Flexibility: You can switch between the two naming options to suit your agency's workflow.

How to Set the Default Naming Convention

Follow these steps to configure the naming convention for new SaaS accounts.

1. Navigate to the SaaS Configurator and open the Advanced Settings section.
2. Select Sub-Account Onboarding.
3. Under the naming options, choose one of the following:
   • Company Name: Recommended for using the client's business name.
   • Customer Name + 's Account: Uses the primary contact's name followed by "'s Account".
4. Click Save to apply your selection.

This setting will take effect for all new sub-accounts created through your CRM's funnels or supported external checkout systems.

Naming Convention Options

Review the two available options to decide which best fits your needs.

• Company Name: The sub-account will be named using the business name provided by the client during checkout. For example: Global Solutions Inc.
• Customer Name + 's Account: The sub-account will be named using the customer's personal name. For example: Alex Johnson's Account

Important: If the Company Name field is left blank during checkout, the system will automatically default to the Customer Name + 's Account format.

Using with External Checkout Systems

To apply the same naming behavior when using an external checkout system, you must pass the client's business name as metadata. Ensure your checkout process sends a value for the companyName field within the subscription metadata. The SaaS Configurator must be set to Company Name for this to work. If the companyName value is missing or empty, the system will fall back to the customer's name.

Behavior and Examples

Here are examples of what to expect based on your configuration and the information provided at checkout.

• If Company Name is selected and provided: The resulting account name will be the company name (e.g., Sunrise Marketing).
• If Company Name is selected but not provided: The resulting account name will fall back to the customer's name (e.g., Sam Lee's Account).
• If Customer Name + 's Account is selected: The resulting account name will always be the customer's name (e.g., Sam Lee's Account).

You can update a location's friendly business name manually after account creation if needed. This change will not affect any confirmation emails or communications that were already sent.

Frequently Asked Questions

Does this setting rename existing accounts?

No. This configuration only applies to new sub-accounts created after the setting is saved.

What if a client doesn't provide a company name?

The system will automatically use the Customer Name + 's Account format as a fallback.

Can I change the default later?

Yes. You can update the selection in the SaaS Configurator at any time. The new setting will apply to future sign-ups.

How does this work with merge fields in emails?

The initial location name, used in merge fields like {{location.name}}, will reflect the chosen convention at the time of creation. If you change the location name later, the merge field will update accordingly.