Salesforce Foundational Configuration: Business Hours, Custom Domains, & State Picklists

A VectorFormed Technical Guide

By VectorFormed LLC

‍

# 1. Executive Overview & Business Value

‍

Quick Summary: Standardize Salesforce foundational settings to ensure scalable Revenue Operations, data integrity, and automation accuracy.

Day 1 org initialization sets the technical foundation for scalable Revenue Operations (RevOps). Implementing custom domains, standardizing address data structures, and establishing organizational business hours directly influence security, data integrity, and automation accuracy. Failure to standardize state and country picklists prior to data ingestion results in downstream data silos and broken routing logic. Configuring business hours and holidays immediately ensures that Case SLAs, Entitlement Processes, Lead Assignment rules, and Scheduled Flows execute precisely against actual operating hours, protecting service metrics and system ROI.

‍

# 2. Architecture & Prerequisites

• Required Licenses/Editions: Enterprise, Unlimited, or Performance Edition (Sales Cloud / Service Cloud)
• Required User Permissions: Customize Application, Modify All Data
• Objects & Relationships: Lead, Account, Contact, Case (specifically standard Address fields)
• Pre-configuration Checklist:
  
  • Fresh Org Environment: Execute these steps prior to importing legacy data or integrating external marketing platforms to avoid mass data-mapping dependencies.
  • Approved Naming Convention: Obtain compliance/infosec approval for the custom domain nomenclature.
  • Operational Schedule: Procure the finalized corporate holiday and operating hours schedule.

‍

# 3. The Build Blueprint: Step-by-Step Configuration

Phase 1: Establishing Operational Business Hours & Holidays

• Navigate to Setup > Company Settings > Business Hours.
• Select the Default Business Hours record.
• Update the Time Zone to accurately reflect headquarters operations (e.g., Eastern Standard Time (America/New_York)).
• Modify the operational days and hours to match organizational operating hours. Click Save.
• Navigate to Setup > Company Settings > Holidays.
• Click New to configure non-working days (e.g., Christmas). Define the date parameters and associate the Holiday with the established Business Hours to ensure SLA timers and automations pause appropriately on these days.

‍

Phase 2: Custom Domain Deployment (My Domain)

• Navigate to Setup > Company Settings > My Domain.
• In the My Domain Details section, input the approved organizational domain syntax (e.g., vectorformed).
• Click Check Availability.
• Upon receiving the availability confirmation, click Save.
• Wait for the automated Salesforce provisioning email indicating readiness.
• Refresh the interface, click Deploy to Users, and enforce the new login policy. The URL structure will transition from the standard generic instance (or Dev Ed) to the custom organization URL.

‍

Phase 3: State and Country/Territory Picklist Enforcement

• Navigate to Setup > Data > State and Country/Territory Picklists.
• Scan for Data: Execute the data scan to validate that zero existing records will be orphaned or impacted by the schema change (mandatory if configuring an existing org).
• Configure States and Countries: Define the operational territory. For US-centric operations, navigate to the country configuration, select United States, and set it as the Default country.
• Restrict Access: If operating strictly domestically, deactivate international options to restrict the UI exclusively to the US and its respective states. Update state/province values to utilize standard abbreviations if preferred by RevOps.
• Save configurations and click Enable to deploy picklist standardization across all standard address fields.

‍

# 4. Logic, Automation, & Formulas

# 4. Logic, Automation, & Formulas

The configuration of Business Hours inherently controls how declarative automations calculate time. Scheduled Flows implicitly respect organizational time zones, but Lead Assignment rules, SLA timers, and Entitlement Processes must be explicitly associated with the designated Business Hours record to inherit holiday pause logic.

Recommended Practice: SLA Business Hours Formula When building SLA validation or elapsed time reporting, standard datetime subtraction includes weekends. To ensure custom formula fields respect the operating hours established in Phase 1, utilize the following logic to skip weekends on a standard 48-hour SLA calculation:

Recommended Practice: Salesforce Formula

‍

/* Data Type: Date/Time */

/* Object: Case */

/* Description: Calculates target resolution date skipping weekends */

CASE(

  MOD( DATEVALUE(CreatedDate) - DATE( 1900, 1, 7 ), 7 ),

  4, CreatedDate + 2 + 2, /* If created Thursday, add 4 days to skip weekend */

  5, CreatedDate + 2 + 2, /* If created Friday, add 4 days to skip weekend */

  6, CreatedDate + 2 + 1, /* If created Saturday, add 3 days to skip Sunday */

  CreatedDate + 2 /* Default: add 2 days */

)

‍

# 5. Testing & QA Validation Protocol

• Domain Resolution: Terminate current sessions and authenticate via the new custom domain URL to verify login policies function as intended.
• Data Integrity Check (Leads): Navigate to the Lead object. Attempt to create a new Lead. Verify that the Country field defaults to United States and that the State field renders as a restricted picklist rather than a free-text field.
• SLA & Automation Verification: Trigger a test case or scheduled flow designed to execute on a recognized Holiday (e.g., Christmas). Verify that the system pauses the escalation rules or defers the automation until the next operational business hour.

‍

# 6. Edge Cases & Maintenance

• Retroactive Picklist Enablement: Enabling State/Country picklists after data exists requires complex data mapping. This breaks external integrations (like Web-to-Lead or HubSpot) that push non-standardized text strings (e.g., "US", "USA", "United States"). External integration payloads must be updated to push standard ISO codes prior to enablement.
• Holiday Drift: Static holidays remain consistent, but floating holidays (e.g., Thanksgiving) require manual administrative updates annually. Failure to update the Holidays object will result in false SLA breaches on days the business is closed.
• My Domain API Disruptions: Altering a custom domain later in the organization's lifecycle breaks hardcoded API endpoints, Managed Packages, and external webhooks. Establish the permanent nomenclature immediately upon deployment and treat it as immutable.

‍