Texting hours
How DogBot holds each text until it’s within texting hours where the person lives, which state law it starts from, and how to change or reset the hours for one state or all of them.
Nobody wants a text from a business at 11:40 PM, and several states limit the hours a business may text. DogBot accepts every text you send and holds it until it’s within texting hours where the person lives, then sends the texts that waited in order at your pace. Every state starts at the hours its law allows, and you can change one state or all of them.
The law DogBot starts from
Federal rules allow business texts from 8 AM to 9 PM in the person’s own time. Six states set hours of their own, and where a state’s hours are narrower than the federal ones, DogBot uses the state’s. Every other state, DC, Puerto Rico and the other territories start at the federal hours.
| Where the person lives | Texting hours | Law | Read on |
|---|---|---|---|
| Anywhere the table doesn’t name | 8 AM to 9 PM | 47 C.F.R. § 64.1200(c)(1) | October 28, 2026 |
| Florida | 8 AM to 8 PM | Fla. Stat. § 501.616(6)(a) | October 28, 2026 |
| Maryland | 8 AM to 8 PM | Md. Code Ann., Com. Law § 14-4502 | November 6, 2026 |
| Oklahoma | 8 AM to 8 PM | Okla. Stat. tit. 15, § 775C.4 | October 28, 2026 |
| Oregon | 8 AM to 8 PM | Or. Rev. Stat. § 646.563, as amended by Or. Laws 2025, ch. 580 (HB 3865) | November 6, 2026 |
| Pennsylvania | 9 AM to 7 PM, and none on Sunday | 73 Pa. Stat. § 2245(a)(1), as amended by Act 47 of 2026 (SB 992) | November 6, 2026 |
| Virginia | 8 AM to 9 PM | Va. Code Ann. § 59.1-511 | November 6, 2026 |
The read-on date is the day DogBot last read each law. Settings → Texting hours shows the same law and citation beside every state.
Where the person lives
DogBot reads the hours for each text in the person’s own time, and it finds their state in this order:
- The contact’s
state, when you’ve set it on the contact in the dashboard, with the API or in an import. - The area code of their number. A number from 305 is in Florida.
- Neither. Group chats, email addresses and numbers from outside the US use the hours for people with no known state, which start at the federal 8 AM to 9 PM, in your account’s
time_zone.
Some states have two time zones. When the area code is in the person’s state and keeps one zone, DogBot uses that zone. Otherwise a text waits until it’s within the hours in every zone the state has. Kim moved to Florida and kept her Austin number, so her contact says FL and her area code says Texas. Florida has Eastern and Central time, so a text to her goes between 9 AM and 8 PM Eastern, the hours Florida law allows in both.
What a held text says
Dana’s account is in New York. Her booking app sends a reminder to a Florida client at 10:40 PM. DogBot answers 201 with the text queued and a hold:
{
"state": "queued",
"hold": {
"reason": "texting_hours",
"until": "2026-11-14T13:00:00.000Z",
"rule": "state_law",
"state": "FL",
"description": "Florida law allows business texts from 8 AM to 8 PM where this person lives. It goes at 8:00 AM tomorrow."
}
}rule says whose hours held the text, state is the person’s state (null when DogBot doesn’t know it), and until is when the hours open. The description is set in your account’s time zone:
rule | It means | An example description |
|---|---|---|
state_law | The person’s state has hours of its own, and you haven’t changed them. | "Florida law allows business texts from 8 AM to 8 PM where this person lives. It goes at 8:00 AM tomorrow." |
federal_law | The person’s state has no hours of its own, or DogBot doesn’t know their state. | "Federal law allows business texts from 8 AM to 9 PM where this person lives. It goes at 9:00 AM tomorrow." |
yours | You changed the hours for the person’s state, or for people with no known state. | "Your texting hours for California hold this text. It goes at 10:00 AM tomorrow." |
At 8:00 AM the reminder goes, with the other texts that waited, one after another at your pace. Nothing about the text changes while it waits, and you don’t need to send it again. A text whose send_at falls outside texting hours does the same: it becomes queued at its send_at and waits for the hours to open.
Change the hours
In the dashboard it’s Settings → Texting hours. Change on a state’s row sets that state’s hours, and Set hours for every state sets them all at once. Hours for every state never take a state past its law unless you tick Use these hours even where they’re wider than the law. Without the tick, a state whose law allows less gets the hours its law allows, and a state whose law shares no hour with yours keeps its law. The dialog and the message after you save name those states. Your hours can be narrower or wider than the law. Where they’re wider, that state’s row says so, the message after you save names those states, and the settings carry a warning. You’re responsible for texting within the hours the laws that apply to you allow.
With the API, send the places that change. place is a state’s two-letter code, or OTHER for people with no known state. Hours are whole hours in the person’s own time: start_hour from 0 to 23, end_hour from 1 to 24 (24 is midnight), and sundays says whether texts may go on Sunday. Sam’s office answers texts from 9 AM to 6 PM, Monday to Saturday, so he sets Florida to match:
/v1/settingscurl -X PATCH "https://getdogbot.com/api/v1/settings" \
-H "Authorization: Bearer $DOGBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"texting_hours": {
"places": [
{
"place": "FL",
"hours": {
"start_hour": 9,
"end_hour": 18,
"sundays": false
}
}
]
}
}'To set every state and people with no known state at once, send all. Each place gets the narrower of all and its law, so 9 AM to 8 PM sets Texas and Florida to 9 AM to 8 PM and leaves Pennsylvania at its law of 9 AM to 7 PM with no Sunday texts. A place whose law shares no hour with all keeps its law, or goes back to it if you’d set its own hours, since no text could go there in those hours. Evening hours of 7 PM to 9 PM leave Pennsylvania at 9 AM to 7 PM, and the answer lists it in texting_hours.kept_at_law and says so in warnings. Set that place on its own in places if you want something else. To set every place to the hours as you send them, even where they’re wider than its law, add "allow_wider": true. When you send all and places together, all is applied first and places changes the ones it names, exactly as sent:
/v1/settingscurl -X PATCH "https://getdogbot.com/api/v1/settings" \
-H "Authorization: Bearer $DOGBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"texting_hours": {
"all": {
"start_hour": 9,
"end_hour": 20,
"sundays": true
}
}
}'The answer lists every place you changed in texting_hours.custom, with wider_than_law on each. Hours equal to a place’s law are kept as no change, so that place isn’t listed:
{
"texting_hours": {
"custom": [
{
"place": "FL",
"start_hour": 9,
"end_hour": 18,
"sundays": false,
"wider_than_law": false
}
]
}
}The change applies at once. Texts that were waiting get a new hold.until, and texts now within their hours go on the Mac’s next check-in.
| You got | It means | Do next |
|---|---|---|
200 with your texting_hours | Saved. | Read a waiting text with GET /v1/messages?state=queued and check its hold.until. |
400 on texting_hours.all.end_hour | The hours end before they start. | Send an end_hour later than the start_hour. Use 24 for midnight. |
400 with "Name each place once." | The same place is in places twice. | Send each place once. |
200 with texting_hours.kept_at_law | all and those places’ law have no hour in common, so they keep their law. A warning names them. | Set those places in places if their law isn’t what you want, or add "allow_wider": true. |
Reset to the law
Reset to the law on a state’s row puts that state back, and Reset every state to the law puts them all back. With the API, send null as a place’s hours:
/v1/settingscurl -X PATCH "https://getdogbot.com/api/v1/settings" \
-H "Authorization: Bearer $DOGBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"texting_hours": {
"places": [
{
"place": "FL",
"hours": null
}
]
}
}'Or send "all": null to put every place back at once:
/v1/settingscurl -X PATCH "https://getdogbot.com/api/v1/settings" \
-H "Authorization: Bearer $DOGBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"texting_hours": {
"all": null
}
}'What texting hours don’t cover
- Texts you type yourself. A text you send by hand in Messages goes when you send it. Texting hours only hold the texts DogBot sends.
- Other holds come first. DogBot shows one hold at a time. A paused account or a Mac that’s away shows
pausedordevice_offlineovernight, andtexting_hoursonly once those clear. - Expiry keeps running. A text with an
expires_atan hour away, sent at 10:00 PM, expires before the morning and never goes. Give night-time texts an expiry that reaches past the morning, or leave it at the 24-hour default. - The daily limits count by your own day. "Today" for the daily limits always uses your account’s
time_zone, wherever the people you text live.