Author Archives: Success Software

1. The Challenge: Flows Run in GMT

Salesforce Flow is one of the most powerful automation tools available to admins. But there’s a hidden complexity that often causes unexpected behavior:

Flows run in Coordinated Universal Time (UTC/GMT), not in the user’s or customer’s local time.

This leads to issues such as:

• Emails firing outside the customer’s business hours
• Tasks being created at the wrong local time
• Lead assignment rules triggering too early or too late
• Scheduled paths running at unexpected hours
• Time‑based logic behaving inconsistently across regions

Admins often discover this only after users complain that “the automation ran at the wrong time.”

To build reliable, global automations, you need a way to make Flows aware of the customer’s local time — not just the org’s or the user’s.

2. How to Make Flows Time‑Zone Aware

The key to solving this problem is giving Flow access to:

• The customer’s local time
• Their time zone
• Their UTC offset
• Whether Daylight Savings Time is currently active

Salesforce does not provide these fields natively, which is why admins often struggle.

The Local Time app solves this by automatically calculating:

• Local Time
• Time Zone Name
• UTC Offset
• DST Adjustments

These fields can be used directly inside Flow — no Apex, no external API calls, no maintenance.

3. Example Automation: “Send Email Only During Business Hours”

This is one of the most common time‑zone‑aware automations.

Goal:

Send an email to a Lead only if their local time is between 9 AM and 5 PM. If it’s outside business hours, delay the email until the next morning.

Step‑by‑Step Flow Setup

Step 1: Trigger the Flow

Use:

• Record‑Triggered Flow
• Object: Lead
• Trigger: When record is updated or created

Step 2: Get the Lead’s Local Time

Use the Local Time field from the app.

Example fields:

• tz__Local_Time__c
• tz__UTC_Offset_F__c
• tz__Timezone_F__c

Step 3: Decision Element

Create a decision like:

Is Local Time Between 9 and 17?

• If Yes → Send email immediately
• If No → Go to a scheduled path

Step 4: Scheduled Path

Set the scheduled path to run at:

• Next 9 AM Local Time

Because you have the customer’s local time, you can calculate the next business hour window.

Step 5: Send the Email

Use an Email Alert or Send Email action.

Result

Your automation now respects the customer’s business hours — regardless of where they are in the world.

4. Example Automation: “Assign Leads Based on Local Time”

This is extremely useful for global SDR teams.

Goal:

Assign Leads to different teams depending on the customer’s local time.

Example Rules

• If Local Time is 8 AM – 12 PM → Morning Team
• If Local Time is 12 PM – 5 PM → Afternoon Team
• If Local Time is 5 PM – 8 AM → After‑Hours Queue

Flow Steps

Step 1: Trigger on Lead Creation

Record‑Triggered Flow on Lead.

Step 2: Decision Element

Branch based on Local Time:

• Morning Window
• Afternoon Window
• After Hours

Step 3: Assignment

Update the Lead Owner or Queue based on the branch.

Result

Leads are routed to the right team at the right time — improving speed‑to‑lead and customer experience.

5. Try the Local Time App

Time‑zone‑aware automation is one of the most impactful improvements you can make to your Salesforce org. It ensures:

• Emails go out at the right time
• Leads are routed intelligently
• Tasks and reminders fire when customers are actually available
• Global teams work more efficiently

The Local Time app gives Flow the missing data it needs — without code, APIs, or maintenance.

Try it free for 30 days and start building smarter, more reliable automations. Follow the steps described in the installation and setup guide.

1. The Silent Problem: Reps Waste Time Guessing Time Zones

Salesforce is built to help teams work smarter, faster, and more efficiently. But there’s a surprisingly common productivity drain that almost every sales and support team experiences — and most admins don’t even realize it’s happening.

Reps spend an enormous amount of time guessing or checking a customer’s local time.

Every day, across thousands of Salesforce orgs, reps:

• Google “current time in Denver”
• Ask teammates “Is Arizona on DST right now?”
• Call prospects too early or too late
• Hesitate to dial because they’re unsure of the time zone
• Waste minutes per call trying to figure out the right moment to reach out

Individually, these moments seem small. But across a team — and across a year — they add up to hours of lost productivity and countless missed opportunities.

The worst part? This problem is completely invisible until you measure it.

2. Why Spreadsheets and Google Searches Don’t Scale

When teams are small, manual time‑zone checking feels manageable. But as soon as you’re working across multiple regions, the cracks start to show.

Problem 1: It’s slow

Even a quick Google search takes 10–20 seconds. Multiply that by 50 calls a day, and a rep loses 15–20 minutes daily just checking time zones.

Problem 2: It’s error‑prone

Reps often miscalculate:

• Daylight Savings Time
• International offsets
• Regions that don’t observe DST (e.g., Arizona, parts of Australia)
• Countries with half‑hour or quarter‑hour offsets

A single mistake can lead to a poorly timed call — and a lost opportunity.

Problem 3: It breaks reporting and automation

If reps don’t know the customer’s local time:

• They can’t prioritize call lists
• They can’t schedule follow‑ups intelligently
• Automations fire at the wrong time
• Managers can’t build accurate dashboards

Salesforce becomes less effective simply because it lacks one key piece of information.

3. How Salesforce Can Automate This

The good news is that Salesforce can handle time zones — it just needs the right data.

With the Local Time app, admins can automatically add:

• A Local Time field
• A Time Zone field
• A UTC Offset field
• A DST‑aware calculation
• A Lightning component showing the current time

This works for:

• Leads
• Contacts
• Accounts
• Cases
• Opportunities

And because it requires no Apex, no external APIs, and no maintenance, it’s one of the simplest improvements an admin can make.

What this unlocks

Once Local Time is available, teams can:

• Sort call lists by local time
• Build “Call Now” dashboards
• Trigger Flows only during business hours
• Route leads based on customer availability
• Improve connect rates
• Reduce after‑hours outreach complaints

It transforms Salesforce from a generic CRM into a time‑zone‑aware productivity engine.

4. The ROI of Fixing This

Time zone guessing seems small, but the impact is huge.

A. Higher connect rates

Calling at the right time can increase connect rates by 30–50%.

B. More calls per rep

Removing manual time‑zone checking saves 15–30 minutes per rep per day.

C. Better customer experience

Customers appreciate calls during reasonable hours — and remember when they’re not.

D. Smarter automation

Flows, assignments, and reminders become more accurate and more effective.

E. Happier reps

Reps love tools that remove friction. Admins love tools that reduce support tickets. Managers love tools that improve performance.

Everyone wins.

5. Try Local Time Free for 30 Days

Time zone guessing is one of the most overlooked productivity killers in Salesforce — but it’s also one of the easiest to fix.

The Local Time app gives your team:

• Instant visibility into customer local time
• Accurate, DST‑aware calculations
• List view support
• Lightning components
• Flow‑ready fields
• Zero maintenance

Install it from the AppExchange and try it free for 30 days. Setup takes less than 5 minutes, and the impact is immediate. Follow the steps described in the installation and setup guide.

1. Why Calling at the Right Time Matters

Sales teams live and die by timing. Even the best script or the most motivated SDR can’t overcome the simple fact that:

• People don’t answer the phone early in the morning
• Lunch hours vary by region
• After‑hours calls feel intrusive
• Connect rates drop dramatically outside business hours

Research consistently shows that calling at the right local time can increase connect rates by 30–50%. But Salesforce doesn’t provide a native way to see a Lead’s or Contact’s local time — which means reps often guess, Google, or simply call blindly.

This wastes time, reduces productivity, and leads to poor customer experiences.

Fortunately, with the Local Time app, admins can give reps a simple, reliable way to prioritize calls based on the customer’s actual local time.

2. How to Add Local Time to List Views

Once the Local Time app is installed, you can make it visible in list views — which is where reps spend most of their day.

Here’s how to set it up.

Step 1: Add Local Time to the List View

• Open Leads → All Open Leads (or any list view)
• Click the gear icon → Select Fields to Display
• Add Local Time to the visible columns
• Save

Now every rep can instantly see the customer’s local time without clicking into the record.

Step 2: Sort by Local Time

This is where the magic happens.

• Click the Local Time column header
• Sort ascending or descending

Reps can now work through leads in the order that makes the most sense — starting with those currently in business hours.

Step 3: Filter by Local Time (Optional)

Admins can create filtered list views such as:

• “Leads in Business Hours (9 AM – 5 PM)”
• “Leads in Morning Hours (8 AM – 11 AM)”
• “Leads in Afternoon Hours (1 PM – 4 PM)”

This helps SDRs focus on the highest‑probability windows.

3. Building a “Call Now” Dashboard

Once Local Time is available on records, you can build dashboards that guide reps toward the best opportunities.

Dashboard Component Ideas

A. Leads by Local Time Hour

A bar chart showing:

• 8 AM
• 9 AM
• 10 AM
• …
• 5 PM

Reps can visually see when most leads are currently reachable.

B. “Call Now” Table

A report sorted by:

• Local Time
• Lead Status
• Phone availability

Columns to include:

• Lead Name
• Company
• Phone
• Local Time
• Time Zone
• Lead Owner

C. Region‑Based Call Windows

Use filters to show:

• US East
• US Central
• US Mountain
• US Pacific
• EMEA
• APAC

This is especially useful for global SDR teams.

4. Real‑World Examples

Example 1: SDR Team Calling Across the US

An SDR team in Chicago needs to call leads across all four US time zones.

Without Local Time:

• They call PST leads too early
• They call EST leads too late
• They waste time checking time zones manually

With Local Time:

• They sort leads by Local Time
• They start with EST, then CST, then MST, then PST
• Connect rates increase
• Reps make more calls in less time

Example 2: Support Team Managing Global Cases

A support team in Europe handles cases from Asia, North America, and Australia.

Without Local Time:

• They reply when customers are offline
• They miss same‑day resolution windows

With Local Time:

• They prioritize cases where the customer is currently online
• They improve SLA compliance
• Customer satisfaction increases

Example 3: Sales Ops Building a Global Outreach Strategy

Sales Ops wants to optimize outreach across regions.

With Local Time:

• They build dashboards showing peak availability
• They schedule campaigns based on customer local hours
• They reduce after‑hours outreach complaints

5. Try Local Time Free for 30 Days

Prioritizing calls by local time is one of the simplest ways to improve connect rates, boost rep productivity, and create a better customer experience.

With the Local Time app, you can:

• Add a Local Time field to Leads, Contacts, Accounts, and Cases
• Sort and filter list views by local time
• Build dashboards that guide reps toward the best opportunities
• Do it all without Apex, external APIs, or maintenance

Install it from the AppExchange and try it free for 30 days — setup takes less than 5 minutes. Follow the steps described in the installation and setup guide.

1. Why Time Zones Are a Hidden Challenge in Salesforce

Salesforce is used by organizations that span continents, languages, and working hours. But despite its global reach, Salesforce’s handling of time zones can create unexpected challenges for admins, including:

• Users in different regions seeing different timestamps
• Workflows firing at the wrong local time
• Reps calling customers outside business hours
• Reports showing inconsistent time-based data
• Daylight Savings Time (DST) causing confusion twice a year

These issues often go unnoticed until a team expands internationally or starts working across multiple time zones. Suddenly, what used to be a simple timestamp becomes a source of frustration for admins and end users.

Time zone management isn’t glamorous, but it’s essential for accurate reporting, smooth automation, and a great customer experience.

2. Common Admin Mistakes

Even experienced admins run into pitfalls when dealing with time zones. Here are the most common ones.

Mistake #1: Relying on the User’s Time Zone

Salesforce stores timestamps in GMT and converts them to the user’s time zone. This means:

• A Lead created at 3 PM EST appears as 12 PM PST
• A Case escalated at 10 AM GMT appears as 2 AM PST

This is correct behavior — but it confuses users who expect to see the customer’s local time, not their own.

Mistake #2: Hardcoding Time Zone Offsets

Admins sometimes create formula fields like:

NOW() - (5/24)

This breaks because:

• DST changes
• Not all regions follow DST
• Offsets vary by country
• International customers don’t fit neatly into US-centric formulas

Mistake #3: Using Area Codes to Guess Time Zones

Phone numbers are unreliable indicators of location:

• People keep old numbers when they move
• Companies use VoIP numbers
• International formats vary widely

Mistake #4: Using State/Country Fields Without Normalization

If “CA” means California and Canada in your org, time zone logic becomes impossible.

3. Best Practices for Global Orgs

Here are the most reliable strategies for managing time zones in Salesforce.

A. Standardize Address Fields

Use:

• State & Country Picklists
• Validation rules
• Data cleanup tools

This ensures you can reliably determine a customer’s region.

B. Normalize Phone Numbers

Use:

• E.164 formatting
• Phone validation apps
• Flow to clean up formatting

This helps with downstream automation.

C. Store Time Zone as a Field

Instead of calculating time zones on the fly, store:

• Time zone name (e.g., “America/Los_Angeles”)
• UTC offset
• Local time

This makes reporting and automation far easier.

D. Use a Dedicated Time Zone Tool

A purpose-built tool (like the Local Time app) handles:

• DST
• International regions
• Edge cases
• Automatic updates

This removes the burden from admins entirely.

4. Tools That Make Time Zone Management Easier

Salesforce doesn’t provide a native “Local Time” field, but several tools can help.

Local Time App (Recommended)

Provides:

• Local Time field for Leads, Contacts, Accounts, Cases
• Lightning component showing current time
• Automatic DST handling
• List view support
• No Apex or external API calls

This is the simplest and most admin-friendly solution.

Dynamic World Clock

Useful for:

• Global sales teams
• Support teams
• Managers scheduling meetings

Meeting Planner Tools

Great for:

• Cross-region collaboration
• Scheduling customer calls
• Avoiding after-hours outreach

5. How to Automate Time Zone Workflows

Once you have reliable time zone data, you can build powerful automations.

A. Flow Example: Send Emails Only During Business Hours

Use Flow to check:

• Local Time field
• Business hours
• Day of week

If the customer is outside business hours, delay the email.

B. Flow Example: Assign Leads Based on Local Time

Route Leads to:

• Morning shift reps
• Afternoon shift reps
• Regional teams

This ensures faster follow-up and better customer experience.

C. Reporting Example: Build a “Global Activity Heatmap”

Group activities by:

• Local hour
• Region
• Team

This helps managers understand when customers are most active.

6. Try the Local Time App

Managing time zones doesn’t have to be complicated. With the right structure and tools, you can eliminate confusion, improve automation accuracy, and give your users a smoother experience.

Start using the App right away by following the steps described in the installation and setup guide.

1. The Problem: Reps Calling Prospects at the Wrong Time

Sales teams today work across multiple regions, time zones, and countries. But Salesforce stores time primarily in the org’s default time zone, which means:

• A rep in New York might call a prospect in California at 6 AM
• A support agent in London might follow up with a customer in Sydney after midnight
• SDRs waste time Googling “current time in ___” dozens of times a day
• Managers struggle to build call lists that respect local business hours

The result is predictable:
lower connect rates, frustrated prospects, and inefficient workflows.

Admins know this is a problem, but Salesforce doesn’t provide a native “Local Time” field for Leads, Contacts, Accounts, or Cases. That’s where the challenge begins.

2. Why Salesforce Doesn’t Provide Local Time Out‑of‑the‑Box

Salesforce is incredibly powerful, but time zone handling has some limitations:

No native Local Time field

Salesforce stores:

• User time zone
• Org time zone
• GMT/UTC timestamps

But it does not calculate the local time of a Lead or Contact based on their address or phone number.

Formula fields can’t reliably calculate time zones
Admins often try:

• IF statements based on State/Country
• Hard‑coded offsets (e.g., PST = -8)
• CASE formulas based on area codes

These break quickly because:

• Daylight Savings Time changes
• Area codes overlap
• International numbers are inconsistent
• Formula fields become unmaintainable

External API calls are expensive and slow

Some admins try:

• Google Time Zone API
• WorldTimeAPI
• Custom Apex integrations

But these require:

• API keys
• Development work
• Ongoing maintenance
• Cost per lookup

For most orgs, that’s overkill.

3. The Admin‑Friendly Solution: Add a Local Time Field

The Local Time app solves this problem with a simple, admin‑friendly approach:

• No Apex required
• No external API calls
• No maintenance
• Works instantly for all standard objects
• Automatically adjusts for Daylight Savings Time

You can add Local Time to:

• Leads
• Contacts
• Accounts
• Cases
• Opportunities

Admins can deploy it in minutes.

4. How It Works

Step 1: Add the Local Time field to your page layout

• Go to Object Manager → Lead (or Contact/Account)
• Open Page Layouts
• Drag the Local Time field into the layout

This instantly displays the correct local time based on the record’s location.

Step 2: Add the Lightning Component

The app includes a clean, modern Lightning component that shows:

• Current local time
• Time zone
• Daylight Savings adjustments
• A world clock view (optional)

Place it anywhere on the page.

Step 3: Add the Local Time column to List Views

This is where the magic happens.

Admins can:

• Add “Local Time” to Lead list views
• Sort by Local Time
• Filter by region
• Build call queues based on business hours

This alone can increase connect rates dramatically.

5. Bonus: How to Prioritize Call Lists by Local Time

Once Local Time is available, admins can build powerful productivity tools.

A. Create a “Call Now” list view

Filter Leads where:

• Local Time is between 9 AM and 5 PM
• Lead Status = Open
• Phone is not blank

Sort by Local Time ascending.

B. Build a “Best Time to Call” dashboard

Use:

• A report grouped by Local Time hour
• A chart showing call windows
• A table of Leads sorted by Local Time

C. Automate call routing

Use Flow to:

• Assign Leads to reps based on local business hours
• Trigger reminders at the right time
• Prevent after‑hours outreach

6. Try the Local Time App Free for 30 Days

If your sales or support teams work across multiple regions, adding a Local Time field is one of the simplest and highest‑impact improvements you can make.

You can install the Local Time app from the AppExchange and try it free for 30 days.
It takes less than 5 minutes to set up and requires no code, no API keys, and no maintenance.

Free Trial:

Start using the App right away by following the steps described in the installation and setup guide.