Set the Default Naming Convention for New SaaS Sub-Accounts

Sparkforge lets agencies on SaaS Mode control the default naming pattern for new sub-accounts created at checkout. Pick between the buyer's personal name or the business name they entered, and Sparkforge applies the choice on every future sign-up.

Where the setting lives

The control sits in the SaaS Configurator at the agency level under Advanced Settings → Sub-Account Onboarding. It applies to future sign-ups only and does not rename existing sub-accounts.

Naming options

• Company Name — Uses the business name provided at checkout. Example: Acme Dental.
• Customer Name + 's Account — Uses the buyer's personal name with 's Account appended. Example: Jane Smith's Account.

If Company Name is selected but the field is empty at checkout, Sparkforge falls back to Customer Name + 's Account.

How to set the default

1. Open the agency view and go to SaaS Configurator → Advanced Settings → Sub-Account Onboarding.
2. Choose Company Name or Customer Name + 's Account.
3. Click Save. New sub-accounts created through Sparkforge funnels and supported external checkouts will follow your selection.

External checkout integration

If you sell SaaS Mode plans through an external checkout, pass the business name into Sparkforge as subscription metadata so the same naming logic applies.

• Send a non-empty companyName value in the subscription metadata.
• Keep the SaaS Configurator set to Use Company Name.
• If companyName is missing or empty, Sparkforge defaults to Customer Name + 's Account.

Example metadata payload:

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

Behavior at a glance

Admins can update a Location's Friendly Business Name later. Renaming after the fact does not retroactively change confirmations or emails already sent.

Where company name is captured

Sparkforge stores the Company Name from checkout in subscription metadata as companyName. This applies to V2 funnels using the Payments ecosystem (metadata via APIs) and SaaS V1 setups using Stripe (metadata via Stripe).