Skip to content
Ramp Remote

Follow the Sun Support: How the Model Works and How to Build It

Follow the sun support explained: how regional shifts hand off tickets for 24/7 coverage, what staffing and handoffs you need, and how to start small.

By Ramp RemoteUpdated

Follow the Sun Support: How the Model Works and How to Build It

Follow the sun support is a way to cover customers around the clock by passing open work between teams in different time zones. When one team’s day ends, the next team’s day begins, and they pick up the same queue. No one works overnight, and customers never wait for a local office to open. This guide covers how the model works, what it takes to run, where it breaks, and how a US company can build it without opening offices on three continents.

Ramp Remote
Add Philippines-Based Support Capacity
Ramp Remote recruits vetted offshore professionals from the Philippines for support roles, with centralized HR and payroll services.

TL;DR

  • Follow the sun support means regional teams hand open cases to each other at shift end, so someone is always on duty in daylight. Salesforce describes it as a handoff framework for exactly this reason.
  • Most companies split the 24-hour day between two or three time zones, with a short overlap for handoffs.
  • The staffing is the easy part. Handoff notes, queue ownership, shared tools and escalation rules decide whether it works.
  • You do not need 24/7/365 coverage. Many businesses are better served by an 18-hour or 16-hour window.
  • A US team can add a daytime-in-Asia shift through a managed offshore team in the Philippines, starting with a few support hires.

What follow the sun support means

The name says it all: as the sun moves across the globe, support responsibility moves with it. Zendesk defines the model as a global workflow in which offices in different time zones handle issues and pass them between one another. The goal is round-the-clock service without making any single group work through the night.

HubSpot frames the value in customer terms: customers get help regardless of where they are or what time it is, and no single customer-service department has to staff late shifts.

You will also see it called a 24/7 support model. The two are related but not identical. Follow the sun is one way to deliver 24/7 coverage, and it is a specific one: coverage comes from teams in different regions taking turns, not from one team working in rotating night shifts.

How it differs from on-call and night shifts

Salesforce separates the model from 24/7 on-call staffing and weekend rotations. Follow the sun is structured and process-driven. It depends on knowledge management, clear handoff protocols and customer-service software, rather than on someone being reachable by phone at 3 a.m.

That difference matters for cost and retention. Night shifts at home are hard to hire for and hard to keep. A shift that happens during someone’s normal working day is neither.

It also does not require an office on every continent. Zendesk notes that the idea is a method of satisfying customers regardless of time or location, not a mandate to open sites everywhere. It also mentions that some companies stagger agents’ hours with mobile access to cover different time zones.

How the model provides 24/7 coverage

The mechanics are simple. You divide the day into regional shifts. Salesforce says organizations commonly use two or three major time zones, so a team is active as another team’s day ends. Open cases move to the next region instead of waiting for the next business day.

A typical three-region layout looks like this:

Region shift Covers Hands off to
Asia-Pacific team Roughly the US evening and overnight Europe or the US East team
Europe team (optional) US early morning US team
US team US business hours Asia-Pacific team

The three-region version is the classic one. Zendesk gives an example of 24/7/365 coverage using teams in Colorado, California and Beijing with staggered start times and daily handoffs designed to meet service-level agreements.

For many US companies, two regions are enough. A US team plus an Asia-Pacific team covers the hours when your customers are asleep and your own people are offline. You skip the European leg and its extra handoff.

You may not need 24/7/365

Full coverage is a business decision, not a badge. Zendesk points out that some businesses need 24/7/365 support while others reach their goals with a shorter daily window. Its example is Prezi, whose teams in San Francisco and Budapest provide 18 hours of coverage a day.

Before you design shifts, answer three questions:

  1. When do your customers actually contact you? Pull ticket timestamps for the last 90 days and chart them by hour.
  2. What is the cost of a delayed answer? A missed payment alert is different from a question about a size chart.
  3. Which channels need live coverage? Chat and phone are time-critical. Email and tickets often are not.

If 90 percent of volume lands in 18 hours, an 18-hour model costs less and carries one fewer handoff risk than full coverage.

What the model requires: staffing, handoffs and tools

The consistent lesson across the vendor guides is that staffing alone does not create dependable coverage. Soon’s operational view is that handoffs, overlap and explicit ownership are the fragile points. Here is what to put in place.

Regional staffing

Each region needs enough people to handle its window’s volume, plus cover for sick days and leave. One agent per shift is a single point of failure. Plan at least two people per region for any window you promise to cover, then scale by ticket volume.

A shared system of record

Salesforce lists a shared CRM or help desk, standardized case fields and templates, escalation flags and knowledge management among the core requirements. Every team must see the same customer history. If one region keeps notes in a spreadsheet, the model fails at the first handoff.

A written handoff

The outgoing team records what was tried, what is pending and any urgent context. The incoming team reviews it and takes ownership. Zendesk describes a daily handoff in which open and pending matters move to the next team, with private comments on support tickets preserving context. It reports that Zuora uses this same approach.

A workable handoff note has five lines:

  • Customer and issue in one sentence
  • What has been tried
  • What the customer was told, and when
  • What is pending, and from whom
  • The next action and its deadline

Overlap

Both Salesforce and Soon suggest a brief overlap, typically 30 to 60 minutes, as a starting point. Use it for a live walk through the hardest open cases, not for chat. If time zones leave no natural overlap, stretch one team’s start or end by an hour and rotate who does it.

Keeping ownership and quality consistent

The common failure is a ticket that bounces between regions and belongs to nobody. Three habits prevent it.

One site owns a case at a time. Lucidchart’s explanation is that work is owned and worked by one site at a time and handed to the next as shifts end. Documenting the work keeps the next team from repeating it.

One leader owns overall performance. Dialpad advises naming a leader or team accountable for the whole operation, even though work moves between regions. Without that person, each region optimizes its own queue.

Measure at the boundaries. Dialpad also points to quality-assurance scorecards, clear metrics and unified communications as ways to bridge cultural and communication gaps. In practice, track these by shift:

  • First response time and time to resolution
  • Tickets reopened within 48 hours
  • Cases handed off versus cases closed in the same shift
  • Customer satisfaction by region

If reopen rates jump on tickets that crossed a handoff, your notes are the problem, not your people.

Benefits and limits to plan for

The benefits are well documented in vendor guidance. Dialpad lists 24/7 customer support, faster response times, global coverage and flexible scheduling. LiveChat adds that continuous handoffs remove downtime between geographic workdays, so teams keep resolving issues rather than wait until morning. Gladly notes that it spares employees routine late-night work.

The same sources flag what to design around: communication silos and uneven service across regions. Both are process problems, and the sections above address them directly. Treat the first 60 days as a tuning period. Review every handoff that led to a customer complaint and fix the template, not the person.

Building a follow the sun team without three offices

The traditional version assumed a company owned sites in the Americas, Europe and Asia. Today you can add one region at a time. The simplest first step for a US business is an Asia-Pacific shift that covers your overnight hours, staffed in the Philippines.

Philippine support agent replying to a customer case

The practical reasoning is easy to follow. A team working a normal daytime in Manila is working through the US evening and night. The exact gap changes when US clocks change, so confirm your overlap twice a year. Your customers get answers while your US team sleeps, and your Manila team works a normal day.

A sensible rollout:

  1. Weeks 1 to 2: Audit ticket volume by hour and pick the window to cover.
  2. Weeks 2 to 4: Write the handoff template, escalation rules and a first set of help-center articles. Our guide to managing staff in the Philippines in the first 90 days covers onboarding in more detail.
  3. Weeks 4 to 8: Start with two support hires on tier-one tickets, with a US lead reviewing every handoff.
  4. Weeks 8 to 12: Widen the scope to billing questions, order issues or account checks as quality holds.

If you want the management side in depth, see our practical guide to offshore team management. If you are weighing a different region, nearshore versus offshore by workstream lays out the trade-offs.

Our perspective

We see companies get this wrong in one consistent way: they treat follow the sun as a hiring problem. Hire people in another time zone, the thinking goes, and coverage follows. It does not. Coverage follows from ownership, notes and a shared system.

That is why we think the best entry point is small. Add a dedicated, full-time offshore support team that works your overnight, writes handoffs as part of the job, and reports to someone on your side. The people are vetted, employed and managed for you, with payroll, compliance and equipment included in one monthly price, so you spend your time on the playbook, not on paperwork.

Our model is designed for this: you meet and select candidates, see the cost up front, and have a relationship manager on an ongoing basis. Start with the shift your customers feel most, prove the handoff, then grow.

Josh

What a managed offshore support hire costs

Our published rate for a Customer Support Specialist starts from $1,400 per month per person. That is a monthly fee per full-time hire covering salary, compliance, equipment, support and onboarding, and the exact quote depends on the role. A Virtual Assistant also starts from $1,400, an Operations Coordinator from $1,500, and a Data Analyst, useful for reporting on shift metrics, from $1,600. Our pricing page explains what a quote includes.

If you are ready to add an overnight support shift, browse our offshore roles and see how your first offshore hire works.

Ramp Remote

Support leads often pair a support hire with an executive assistant or a virtual assistant who handles the admin around the queue: reporting, scheduling and knowledge-base upkeep.

Where follow the sun fits by business type

The model suits businesses whose customers expect fast answers at any hour. Three common cases:

In each case, the first hires should be the ones doing repeatable, well-documented work. Complex escalations stay with your senior US staff until the playbook proves itself.

FAQ

What does follow the sun support mean?

It means customer support is passed between teams in different time zones so that one team is always working its normal daytime hours. At each shift end, the outgoing team hands open cases to the next. Salesforce describes it as geographically distributed teams handing off open cases or tasks so work continues in the next time zone.

Do I need three time zones to follow the sun?

No. Two regions can cover most of the day, and many companies use two or three. Zendesk’s Prezi example shows two teams in San Francisco and Budapest delivering 18 hours a day. Pick the number of regions your ticket data justifies.

How long should the handoff overlap be?

A common starting point is 30 to 60 minutes, according to Soon. Use it to review open cases live and confirm ownership. Adjust once you see how many handoffs generate follow-up questions.

What is the biggest risk of the model?

Handoffs. Dialpad lists communication silos and inconsistent service across regions as the main limits. A standard note template, a single accountable leader and scorecards by shift reduce both.

Sources

Good people, more possible.