By the Onsites AI team · Last updated · 4-minute read
Follow-the-sun support gets sold as an enterprise concept with an enterprise structure — three regional shifts, three managers, a war room. Small teams run it with one shared queue, three honest clocks, and a handoff note. The buyer in Rotterdam does not care whether their 3 pm question is answered from Shanghai by a colleague whose morning it is; they care that it was answered in ninety minutes, that the answer read their thread, and that the next reply is as informed as the first. This guide builds follow-the-sun at small scale: how a desk of three to ten covers global buyers without night shifts, the handoff discipline that makes the desk feel like one continuous team, the channel-hours honesty that keeps clocks legible, and the memory that makes it all work while you sleep (the thread-is-the-record principle carries it).
Not three regional shifts: one desk whose coverage follows the team's morning. The structure: teammates in two or three time zones — the Shanghai hire, the Berlin office, the Chicago founder — sharing one queue, one set of channels, one playbook. The coverage shape: each teammate owns their own workday, the queue holds everything, and the handoffs (the morning list) carry what arrived overnight — the desk's honest promise is a first response within one business day, delivered every day, in every zone. What it is not: nobody answers from bed; nobody owns a "night shift" they never agreed to; the widget outside published hours shows its hours (the channel guide's staffing arithmetic). The small-team form of follow-the-sun is not exotic: it is a shared inbox plus people who trust each other's handoffs — which is precisely why the writing matters more than the structure.
One discipline carries follow-the-sun: the handoff. Three lines, every morning: the overnight threads that need a decision (order #1041's tracking question, the EISU-4821 delay), the promises falling due (the €12,400 quote's 14-day validity, today), the emotional temperatures that rose overnight (the buyer who wrote twice) — one screen, written for a reader whose morning is just starting. Same thread, never reopened: the handoff moves ownership, not location — the buyer's thread carries its whole history, and the Shanghai morning reads the Berlin afternoon's promises without reconstructing them (the thread memory). The drafts wait ready: the copilot drafts overnight replies grounded in the handbook, and the next morning reviews them in minutes — the desk's overnight questions are drafted by the copilot at credit prices before the human wakes, and the morning's work becomes approval, not archaeology. The escalation's clock travels: "L2 replies by Thursday noon" survives the handoff because clocks are written on threads, not held in heads.
Follow-the-sun fails or succeeds at the channel expectations. Chat: the widget publishes its hours — the desk staffs chat during its combined working day (Shanghai morning through Chicago evening is nearly continuous) and hides the widget outside them; a chat ghosted by a "still there?" message at 3 am desk-time is a conversion loss and a trust leak. Email and the async channels: the desk's promise — first response within one business day, delivered every calendar day — is the publishable clock that follow-the-sun makes real at small scale. IM channels (WhatsApp, WeChat, LINE): the most dangerous clocks, because buyers treat them as always-on; the desk's honest pattern is hours published in the away-reply plus the thread-queue treatment (the WeChat guide's shape) — nobody carries the desk on a personal phone all night. The published hours are confidence: buyers forgive clocks they can read; what they do not forgive is discovering the clock after waiting in silence. The desk that publishes "Shanghai until 6 pm CET, Berlin until midnight CET, back at 8 am Chicago" turns time zones from an apology into a promise.
Follow-the-sun's failure mode at scale is handoff loss — three shifts, three sets of notes, the buyer's story retold thrice. Small teams win structurally because the memory is shared, not passed. One thread, one account, same system: the Shanghai morning reads the same thread Berlin wrote at midnight — accounts, orders, promises; nothing is retyped (the conversation-linked accounts carry it). One playbook, one voice: the handbook and templates are shared; the buyer hears one desk regardless of whose morning it is, and the weekly card reads threads across zones so the quality is the team's, not the shift's. One escalation path: the clock that escalates overnight ("one business day") works across zones because the desk wrote it once — the specialist in Berlin wakes to escalations with clocks already set (the matrix's writing). Three people with one memory outrun three shifts with three handovers; the small-team version of follow-the-sun is a design advantage disguised as a constraint.
One desk's follow-the-sun week, concretely. The team: Mia (Shanghai), Jonas (Berlin), the founder (Chicago). Monday 9 am Shanghai: Mia reads the overnight list — four threads, one with a promise due (the Rotterdam quote's validity); she handles three, drafts the fourth's answer for Jonas's morning (copilot-reviewed), sends the quote-extension before Shanghai lunch. Jonas's 9 am Berlin: the handoff list shows the overnight WhatsApp (the Chicago buyer's sizing question) — answered in six minutes from the thread; the EISU-4821 delay note goes to the depot thread with its own clock. Chicago 8 am: the founder reads the overnight escalations — two, both carrying clocks Berlin set; one is a billing edge (the founder's own call), one a refund-past-the-ladder (decided and noted in the handbook). Tuesday's Shanghai morning: an empty handoff list — the first in a month. The buyer-visible shape: first responses inside each zone's day, promises kept on dates, the desk's voice continuous across twelve time zones. The costs: zero extra software, a handful of written rituals, and the discipline of the three-line morning list — which is the entire price of follow-the-sun at small scale.
Can a small team really do follow-the-sun support?
Yes — one shared queue plus teammates in two or three time zones. Each person owns their own workday, the handoff is a three-line morning list, and the desk's promise becomes first response within one business day, every calendar day. No night shifts, no regional structure.
How do handoffs work without losing context?
Same thread, never reopened: the handoff moves ownership, not location. Every morning the oncoming teammate reads a three-line list (threads needing decisions, promises due today, emotions that rose overnight) and picks up threads that carry their full history.
What do we publish for channel hours?
Chat: staffed hours only, widget hidden outside them. Email and async: first response within one business day, delivered every day. IM channels: hours in the away-reply — buyers forgive clocks they can read; what they don't forgive is an always-on channel answered from bed.
Why do small teams do this better than big ones?
One memory. Big desks hand off through notes and shift systems; small desks share one thread store, one handbook, one escalation path — the Shanghai morning reads the same account Berlin wrote at midnight, with nothing retyped.
What does follow-the-sun cost?
Configuration and discipline: assignment rules that escalate on clocks, the copilot drafting overnight replies for morning review, and the three-line handoff ritual. Zero extra software, and the payback is coverage your buyers read as one continuous team.