Skip down to the research record

2 defaults that set HubSpot SMS quiet hours for prospects

Quota Forecast Editorial Team · Published · 12 min read

HubSpot holds SMS messages during quiet hours, set by two defaults: the contact's time zone, or a US fallback when the record has none.

Key takeaways

  • HubSpot holds SMS messages sent between 8PM and 8AM in the contact's local time zone, and defers them until the window ends.
  • A contact with a time zone on the record follows the window for that zone.
  • A contact with no time zone falls under the US default, 8PM US/Eastern to 8AM US/Pacific.
  • Check the SMS message editor before you schedule, and move any send that falls inside a closed window.

Near the end of a quarter, revenue teams tend to send more text messages to prospects. A deal needs a nudge, a proposal needs a reply, and someone wants a batch of follow-ups queued in HubSpot before the books close. The schedule looks right when you build it. Then a message goes out at a time you did not expect, or a few of them seem to go nowhere, and nobody is sure why.

Quiet hours are often the reason. One default ties the window to each contact's own time zone. The other covers contacts whose time zone is missing. If you know both defaults, you can predict when a text will actually go out before you schedule it, instead of checking the results afterward.

This guide is written for the revenue leader who schedules prospect texts in HubSpot, or who reviews them before they go out. This guide does not assume you administer HubSpot. It assumes you need a clear picture of how the two defaults work and a habit of checking them before a batch is set.

This post follows one example case from start to finish. A prospect named Jordan has a HubSpot contact record with a Pacific time zone. A rep schedules a follow-up text to Jordan for just after 8PM Pacific, in the last weeks before quarter close. The question is simple: will that text go out at 8PM, and what should change before anyone presses schedule?

What quiet hours mean in HubSpot

HubSpot's help article on quiet hours describes them as the period from 8PM to 8AM in a contact's local time zone, when SMS laws in some places require that the contact not be texted. The quiet hours article gives that definition. HubSpot's guide to creating and sending SMS messages states the same default: SMS messages are not sent from HubSpot from 8PM to 8AM in a contact's time zone.

Two points matter for planning. First, the window is measured in the contact's local time, not in yours. A schedule set by your own clock tells you nothing about the window until you check it against the contact's zone. Second, the window exists because of legal requirements in some places. That makes it a rule tied to where the person is, not to how your team's calendar looks.

For Jordan, the window is 8PM to 8AM Pacific. A text scheduled for just after 8PM Pacific falls inside it. If the rep built the batch on an Eastern clock, that same moment would read as 11PM, which is late at night rather than an ordinary evening. The gap between your clock and the contact's clock is where many surprises start, and it gets wider when a single batch contains prospects in several zones.

Quarter close makes this worse. Reps tend to finish calls and queue follow-ups in the evening, after the day's meetings, and that is exactly the stretch when the window is closed for many contacts. A text that felt timely at the end of a long day can be held until morning without anyone noticing.

Default one: each contact's time zone sets the window

The first default is the simpler of the two. HubSpot applies the 8PM to 8AM window in each contact's own time zone. That means two contacts scheduled at the same moment can get different results. One can be inside its window while the other is outside it. The send time you set is the same for both; the outcome is not.

This matters for batches. When you enroll a list of prospects spread across regions, a single scheduled time in your own zone is not a single send time for everyone. Some recipients fall inside quiet hours and others do not. A batch that looks correct on your calendar can split across zones, and you will only see the split if you look at it from the recipients' side.

For Jordan, the Pacific zone is the whole story under this default. The question is never what time it is where the rep sits. It is what time it is in Pacific time for Jordan. Just after 8PM Pacific is inside Jordan's window, so the text is held. If the same batch had been scheduled for a time inside the 8AM to 8PM stretch in Pacific time, the window would not apply to that send.

There is a practical point here too. This default only works when the contact has a time zone on the record. Without one, HubSpot has no zone to apply, and the second default takes over. That rule can produce results that look wrong if you assume the contact's own zone is being used. For a wider look at time zone errors, read time zone checks before you trust a deal close date.

Default two: the fallback when a contact has no time zone

The second default covers recipients with no time zone information. HubSpot's quiet hours article says that when timezone information is not available for a recipient, their quiet hours are set to the default for recipients in the United States. That default runs from 8PM US/Eastern to 8AM US/Pacific.

Read that window closely. It begins at 8PM Eastern and ends at 8AM Pacific. Eastern time runs ahead of Pacific time, so 8PM Eastern happens before 8PM Pacific on the same day. A contact who is in the Pacific zone but has no time zone on the record can therefore be held earlier in the evening than their own zone would hold them.

Now picture the same contact with a gap in the record. If Jordan's record had lost its Pacific time zone, perhaps because the contact was imported without one, a text sent before 8PM Pacific would be allowed under Jordan's own Pacific window. Under the fallback, though, the window has already opened, because 8PM Eastern arrives before 8PM Pacific. The message is held either way, but for a different reason than the rep expected, and the change is easy to miss unless someone checks which window applied.

This is also why the fallback deserves a look in every batch. A contact with no time zone on the record falls under the US default window instead. Scanning the batch for records without a zone is a cheap way to find these cases before they matter.

The lesson is to fill in time zones on every record you plan to text. The fallback is HubSpot's assumption for missing data, not a reading of where the prospect actually is. A rule that is close enough for some contacts can be wrong for others. If you can complete the time zone before the batch, the first default does the work and the fallback never comes into play.

How deferral works for single texts and workflows

HubSpot's quiet hours article says that SMS messages sent during quiet hours are automatically deferred until quiet hours are complete. In practice, the message waits until the window closes instead of going out while the window is still closed.

That wait changes how you read a message that looks late. A text whose scheduled time falls during quiet hours is not necessarily a failed send. It may simply be waiting for the window to end. Before you assume a problem, compare the scheduled time against the contact's zone, and then compare it against the window that applies to that contact.

The restriction applies to both individual SMS messages and SMS messages sent through workflows. That matters if your team sends prospect texts from a workflow. A workflow step timed for the evening is held just like a single text you send by hand, so enrollment timing belongs in the plan, not in an afterthought.

For Jordan, deferral means the 8PM text does not vanish. It waits. The send time on your screen is not the time Jordan receives it. If the message was written for a same-evening reply, it may arrive after the window has closed and read as a stale nudge. A line like "can we talk tonight" does not work when the text lands the next morning. Write the message for when it will actually arrive, not for when it was queued.

The practical lesson is that deferral protects the window but does not fix the message. Decide the arrival time before you schedule, and write the text so it still makes sense if it lands later than you planned. For message length, see SMS length limits before a follow-up.

Check the window in the SMS message editor before you schedule

HubSpot's quiet hours article notes that you can review whether your contacts will be affected by quiet hour sending restrictions in the SMS message editor. Treat that review as a required step, not an optional check. Open the editor for the batch before you schedule it, and look at which contacts the restriction touches.

For Jordan, the check is specific. Find Jordan in the batch and confirm whether the 8PM send will be affected. If the editor shows that it will, you have a decision to make before the batch leaves your hands. Moving the time is the cleanest fix, because it avoids sending a message you already know will be held.

When many contacts in one batch are affected, resist the urge to schedule the whole batch for a single time and accept the result. A large affected group is usually a sign that the batch was built around one clock. Pull the affected contacts out, check their time zones, and rebuild the send with a time that suits their zone. The extra step takes a few minutes, and it keeps the batch from arriving in a cluster during the wrong hours.

Also check the sending setup. HubSpot's guide to creating and sending SMS messages asks you to have a US-based phone number that starts with +1 and contains 11 digits. That is a setup requirement, not a quiet hours rule, but a batch that fails for a setup reason can be mistaken for a timing problem. Confirm the sending number before you blame the window.

A plan for the last stretch of the quarter

Start with the arrival time, not the queue time. Decide when a prospect should actually receive a message, check that the time falls inside the contact's allowed hours, and only then set the schedule. This reverses the usual habit of picking a time that feels good on your calendar and hoping the window agrees.

Split batches by time zone when the list spans regions. A single batch can be fine for one group and held for another. Separate batches let you choose a send time that works for each group, and they make the editor review simpler because each batch has fewer zones to reason about.

Think in sequences, not single messages. Many prospect texts are part of a short run of touches: an initial note, a reminder, and a last check before a deadline. Each touch has its own arrival time, and a quiet-hours deferral on one touch can push it past the next. Lay out the whole run on paper, mark the window for each contact, and confirm that each touch still lands in a sensible order. A reminder that arrives before the original note is worse than no reminder at all.

Clean up records before the batch goes out. A missing time zone is the quiet way a contact drops into the fallback window. Before the final push of the quarter, check the prospects you plan to text for a time zone on the record. The fallback is a safety net, not a plan. For timing around the record freeze, see quarter cutoff dates before freezing your record.

For Jordan, the fix is concrete. Move the text from just after 8PM Pacific to a time inside Jordan's day, the 8AM to 8PM stretch in Pacific time, so the message lands while the window is open. If the deadline needs a same-day reply, say so in the message and set a deadline Jordan can meet after the window opens.

Get legal or compliance input on the rules that apply where your prospects are. HubSpot's quiet hours article ties the window to SMS laws in some places, and this post does not cover what those laws require. Ask the people who own that question, and treat their answer as the rule for your team rather than a guess from a blog post.

Checklist before you schedule the batch

Run through these five checks before you press schedule:

  1. Confirm every prospect in the batch has a time zone on the record, so the first default applies rather than the fallback.
  2. Open the SMS message editor and review which contacts the quiet hour restrictions affect.
  3. Look at any workflow that includes an SMS step and check its timing against the same windows.
  4. Confirm the sending number is a US-based number that starts with +1 and contains 11 digits.
  5. For any message with a deadline, schedule it for a time when the recipient's window is open, and write the text for its arrival time.

Where Jordan ends up

By the end of the check, Jordan's text is no longer the 8PM message on the schedule. Jordan's record has a Pacific time zone, the send has moved into a daytime slot in Pacific time, and the message has been written to make sense when it arrives. The batch goes out with fewer surprises, and the rep can explain the timing if a manager asks about it.

None of this needs a special tool. It needs reading the window the way the contact's phone will. Start from the contact's clock, confirm the time zone on the record, check the editor before the batch leaves, and write each message for the moment it will actually arrive. Do those four things near the end of a quarter, when the pressure is highest, and the texts will go out at the times you planned.

Next step for today

Open one batch you have already queued and compare each send time with the time zone on every record it includes. If a record has no zone, fix it before the batch goes out.

Related guides: Bulk-edit sales records: 4 checks before saving changes · Calendar availability: 4 tools for forecast call timing · Check 6 caption settings before the weekly sales call.

Frequently asked questions

Does HubSpot send SMS messages during quiet hours?

No, HubSpot holds SMS messages sent during quiet hours and sends them once the quiet hours are complete.

Which window applies when a contact has no time zone?

The US default applies, which runs from 8PM US/Eastern to 8AM US/Pacific.

Does the restriction cover workflows as well as single texts?

Yes, it applies to both individual SMS messages and SMS messages sent through workflows.

Sources