Skip to main content

Quiet hours for global customers

Send Review Requests in Customer Timezones

When customers are spread across continents, a request that leaves your office at 10am lands in someone’s inbox at 2am. From Pro, an automation can send only during working hours, skip weekends and use each recipient’s timezone. The settings take a minute; agreeing them as a team, and checking they hold, is what this page is for.

  • One agreed sending window for every automation
  • What to check for contacts with no known timezone
  • A quarterly look at what actually went out when

The problem, solved

The overnight request problem, and the settings that fix it

  • Customers get our requests at night

    A message that arrives at 2am is buried under the morning’s mail before anyone reads it.

  • Saturday requests feel intrusive

    For business customers especially, a weekend ask reads as a system nobody is watching.

  • Reminders ignore the window too

    Teams set quiet hours on the first email and forget the follow-ups.

  • Every teammate picks different hours

    One automation sends from 8am, another from 11am, a third at any hour.

  • Nobody checks what actually went out

    Settings drift and no one notices until a customer replies at midnight asking why.

Flip the switch to see how StoryProof handles each one.

Team checklist

Agree the window, apply it everywhere, check it holds

Run through this once as a team, then repeat the last group every quarter.

Agree as a team
Apply in StoryProof
Test
Every quarter

Ticks are stored in this browser only.

In StoryProof

How the settings fit together

  • You will need
  • StoryProof on Pro or above
  • Contacts with email addresses
  • An agreed sending window
  1. 1

    Open each request automation

    Start with the ones that send most, such as follow-ups after a request.

  2. 2

    Set quiet hours

    Working hours only, weekends skipped if agreed, and each recipient’s timezone.

  3. 3

    Keep waits sensible

    Waits before a reminder still apply alongside quiet hours. If a send must land on a particular day, a wait can also run until a set weekday and time.

  4. 4

    Test with a teammate abroad, then publish

    Changes do not run until published. Tests send for real, so only use your own team’s contacts.

What happens next: Add the quiet hours check to the template your team uses when creating any new automation.

Before you start

What quiet hours do not cover

  • Public holidays

    StoryProof is not described as knowing holidays in each country. Pause or adjust automations by hand around the big ones.

  • Unknown timezones

    This page does not say how a contact’s timezone is determined. Check the automation’s settings for that and for the fallback.

  • The right moment is separate

    Quiet hours decide the clock time, not whether the customer is ready to be asked. The blog post on when to ask covers that.

  • Per automation, not global

    Quiet hours are set for each automation, so a new automation needs them set too.

FAQ

Questions people ask

Short answers to what usually comes up next.

Will a request triggered at midnight be lost?

This page does not state whether a send that falls outside the window is held or dropped. Start a test on your own contact late in the evening and read the log to see what your automation does.

Can different automations use different hours?

Yes, quiet hours are set per automation. Most teams still agree one default so customers get a consistent experience.

Who should own these settings?

One named person, with a backup. Give only them a role that edits automations, so the agreed window is not changed by accident.

Is there a frequency limit as well?

Yes, the same settings can cap how often one person hears from you. That is a separate decision from the time window.

Still have a question? Ask the StoryProof team or book a demo.

Ask customers during their working day

Set quiet hours once per automation and let each request arrive on the customer’s clock.

Last updated 2026-11-18.