Managing Default Values

Understanding Default Values

The SAFE Billing Platform’s default value system transforms repetitive data entry into efficient, accurate operations. By capturing and reusing common field values, defaults reduce errors, save time, and ensure consistency across your records.

Default values work throughout the platform wherever you create or edit records - customers, features, numbers, and more. This powerful system adapts to your business needs, supporting multiple operational scenarios from single-brand businesses to complex multi-brand operations.

How Default Values Work

The Concept of Defaults

When you create new records in the platform, many fields come pre-populated with sensible values. These aren’t random - they’re carefully managed defaults that you control. The system remembers your preferences and applies them intelligently, eliminating repetitive typing while maintaining flexibility to override values when needed.

Think of defaults as templates for your data entry. Just as document templates provide starting points for letters or reports, default values provide starting points for customer records, service configurations, and billing settings.

Types of Default Values

The platform supports several types of defaults to match your operational needs.

Default sets can be shared across multiple users, so your whole team can work from the same configurations. If a user saves their own default set with the same name as a shared one, their personal version takes priority.

System Defaults provide baseline values when no other defaults apply. These ensure new records always have sensible starting values, even if you haven’t configured specific defaults.

Named Default Sets let you save multiple configurations for different scenarios. Create sets like “Residential Customers”, “Business Accounts”, or “International Clients”, each with appropriate preset values.

The Special “New” Default automatically loads whenever you create records. This ensures your most common values appear without any extra steps, maximising efficiency for routine operations.

The Special “Import” Default works the same way but for bulk imports. When the platform processes a bulk import file in Insert mode, it looks for a default set named “Import” for that record type (e.g. customer, number, feature). If one exists, those values apply to every new record where the import file does not provide a value. Create an Import default set the same way as any other: fill in the fields, then Default Values > Save with the name “Import”.

Partial Defaults save only specific field groups rather than entire records. Create focused defaults like “UK Billing Address” or “Standard Payment Terms” that you can combine as needed.

What each set stores

Saving a default is two choices: which set of fields to store, chosen from the Save submenu, and what to call the result. The sets available depend on the record type:

Record type	Sets offered
Customer	All, New, New + Service Charges
Number	All, New, New + Tariff + Discount Plans, New + Tariff + Discount Plans + Service Charges, Service Charges
Service	All, New, Service Charges, New + Service Charges

All covers every field that can be stored, and is the set to use for a default you will load onto an existing record. New covers the fields that make sense on a new record, leaving out anything that identifies one particular record: a number’s Carrier Reference and a service’s Provider Reference, for instance, are offered under All only, so a reference belonging to one record is never stamped onto a batch of new ones by a default that loads automatically.

The sets naming service charges also store the feature slots on the add form, so a record and its recurring and one-off charges can be set up together from a single stored default. On a service those slots are the only place its charges are entered, so a service default that does not include them cannot describe the service’s pricing at all.

A default saved from an existing record keeps whatever feature slots are already stored under that name. The slots only exist on the add form, so an edit form does not offer them, and it no longer clears them either.

Creating and Saving Defaults

Saving Your First Default Set

Creating default sets is intuitive and happens within your normal workflow:

1. Begin Normal Data Entry: Start adding or editing any record type - customer, number, service or feature. Enter the values you want to save as defaults.

2. Access Default Menu: Look for Default Values > Save in the menu bar. This appears on all add and edit screens where defaults are supported.

3. Choose Which Fields to Save: The Save submenu lists the sets of fields you can store, named for the job they do. Every record type offers All and New, with further sets covering charges and tariffs. See What each set stores above.

4. Name Your Default Set: Enter a descriptive name that clearly identifies the purpose:

   • “Standard UK Business Customer”
   • “Pay-As-You-Go Mobile Account”
   • “International Wholesale Partner”

5. Save and Confirm: The system confirms successful saving and the defaults become immediately available.

Strategic Default Creation

Plan your defaults strategically to maximise their value:

Analyse Common Patterns: Review your existing records to identify frequently-used value combinations. If 80% of new customers use the same payment terms and billing cycle, those values deserve a default set.

Consider Operational Workflows: Create defaults matching your business processes. If different teams handle different customer types, create appropriate defaults for each team’s typical scenarios.

Plan for Growth: Design defaults that scale with your business. Use naming conventions that remain clear as you add more sets. Consider hierarchical naming like “UK-Business-Standard” and “UK-Business-Premium”.

Managing Multiple Default Sets

As your default library grows, organisation becomes crucial:

Naming Conventions: Adopt consistent naming that indicates:

• Geographic region (UK, EU, International)
• Customer type (Business, Residential, Wholesale)
• Service level (Standard, Premium, Enterprise)
• Special conditions (Promotional, Legacy, Trial)

Regular Reviews: Schedule quarterly reviews of your default sets:

• Remove obsolete sets no longer used
• Update sets reflecting changed business rules
• Consolidate similar sets causing confusion
• Document which teams use which sets

Access Control: Consider who needs which defaults:

• Customer service might need retail defaults
• Account management might need business defaults
• Finance might need special payment term defaults

Using Default Values

Loading Defaults During Data Entry

The platform makes using defaults seamless:

Automatic Loading: If you’ve saved a “New” default set, it loads automatically when creating records. Fields populate instantly, ready for review or modification.

Manual Selection: For other default sets:

1. Click Default Values > Load in the menu bar
2. Choose from your saved sets
3. Selected values populate immediately
4. Override individual fields as needed

Combining Defaults: Load multiple partial defaults sequentially:

1. Load “UK Address Standards” for location fields
2. Load “Enterprise Payment Terms” for billing fields
3. Load “Premium Service Package” for features Each load preserves previous values unless explicitly overwritten.

Defaults give you a head start, but always review the populated fields before saving. A quick check catches any values that don’t suit the specific record you’re creating.