Business Hours

Tell TicketCord when your team is available, what to say outside those hours, and whether tickets may still be opened

Business hours give your server a weekly schedule, a timezone, and a holiday list. Outside those hours the bot either blocks new tickets with a closed notice, or lets them through and posts a notice in the ticket so both the user and staff know a reply may take longer.

The same schedule can pause SLA timers, hold auto-close and reminders until you open, and decide when the AI answers on its own. It is for teams that do not staff support around the clock and want to set expectations instead of leaving people waiting.

Business hours is an Enterprise feature. On lower plans the Business hours block shows an Enterprise badge instead of its settings, and if the bot owner's plan is not Enterprise the bot ignores any saved schedule and creates tickets at all hours. Upgrade your plan to use it.

Go to General → Business hours

Setting up

Open the Business hours settings

Go to General → Business hours. Turn on the Business hours card.

Set the timezone

In the Time zone card, leave Use this browser's time zone on to use the time zone of the browser you are configuring from (the detected zone is shown), or turn it off and pick any named time zone from the Time zone list. Schedules use named time zones, so daylight saving changes are handled for you.

Fill in the weekly schedule

Under Opening times, turn on each day you offer support and set its From and To times in 24-hour HH:MM format. Days you turn off are closed all day. A range that ends before it starts, such as 22:00 to 06:00, runs overnight into the next day, and the page says when it closes. A range that opens and closes at the same time keeps that day closed.

Write the after-hours message

Under After-hours message, design the message in the container editor (new setups start with one container holding the default title and text). If you save it with every container empty, the default container is saved instead.

A message saved in the older style shows a Title and a Message field instead, with Switch to the new style to move it to containers. New messages always use containers; only a message already saved in the older style keeps the older fields.

Decide whether to Show the next opening time and whether to Let members open tickets after hours.

Add holidays

Under Holidays, enter a Name and Date, turn on Every year for dates that repeat, and click Add holiday. Holidays close the whole day regardless of the weekly schedule.

Save

Click Save changes on the bar at the bottom of the page, or press Ctrl/Cmd + S. The schedule applies to the next ticket request immediately.

Settings

SettingAllowed valuesDefault
Business hours (card switch)on or offoff
Use this browser's time zoneon or offon
Time zone (shown when the browser option is off)any named time zone from the list, for example Europe/Berlinthe time zone of the browser that first sets up business hours
Opening times → day switchon or off per dayMonday to Friday on, Saturday and Sunday off
Opening times → From / ToHH:MM, 24-hour, one range per day, overnight allowed09:00 to 17:00
Title (older-style message)1 to 100 charactersWe're Currently Closed
Message (older-style message)1 to 500 charactersThank you for contacting us! We're currently outside of business hours, but you can still create a ticket and we'll get back to you during our next business day.
After-hours message containersas many containers as fit in 4,000 characters of text and 40 components (each container, block of text, and divider line counts as one); supports {title}, {description}, and {nextOpenTime}one orange container containing the default title and description
Show the next opening timeon or offon
Let members open tickets after hourson or offon
Holidays → Name1 to 100 charactersnone
Holidays → DateYYYY-MM-DDnone
Holidays → Every yearon or offoff

Let members open tickets after hours is on by default. A freshly enabled schedule therefore only adds a notice; it does not stop anyone from opening a ticket until you turn that switch off.

Worked example: a European weekday team

A team in Berlin that works office hours, offers a shorter Friday, and closes on public holidays would choose the values below. These are one example team's choices, not the defaults: the defaults are in the Settings table above (Monday to Friday, 09:00 to 17:00, in the time zone of the browser that first sets up business hours). This team would:

  • turn Use this browser's time zone off and set Time zone to Europe/Berlin;
  • set Monday to Thursday 09:00 to 18:00 and Friday 09:00 to 15:00;
  • leave Saturday and Sunday disabled;
  • add 2026-12-25 "Christmas Day" and 2026-01-01 "New Year's Day" as recurring holidays.

With Let members open tickets after hours on and Show the next opening time on, a user opening a ticket at 20:00 on Friday gets their ticket plus a notice saying the team is back Monday at 09:00, shown in the user's own local time.

What happens outside hours

The bot checks the schedule every time someone tries to open a ticket from a panel button, dropdown, modal, or a ModMail DM.

With Let members open tickets after hours on

  1. The ticket is created normally, with the welcome message you configured.
  2. A separate notice is posted in the ticket: your After-hours message containers. For a message saved in the older style, it is a bold clock line with your Title (or "Outside Business Hours" if empty) and your Message (or "This ticket was created outside of business hours. Staff may not respond until the next business day.").
  3. The staff ping set on the button or menu that opened the ticket (or the ping from New ticket defaults, which ModMail tickets use) is skipped for that ticket, so nobody is woken up. Staff can still see and answer it. Thread tickets are the exception: the bot still mentions your staff roles at the top of each new thread at any hour, because that is how Discord adds them to the thread. If you do not want that mention after hours, use ticket channels instead of threads. Role pings from Sorting rules and Tone alerts are sent at any hour.
  4. The ticket is otherwise a normal ticket: it counts toward limits, can be claimed, and follows your close settings.

With Let members open tickets after hours off

  1. No ticket or channel is created.
  2. The user sees an error card with code TC018. The heading is "Ticket creation is not available outside of business hours." When your after-hours message uses containers, its first line of content is used as the heading instead.
  3. When Show the next opening time is on, the card also says We'll be back: followed by a Discord timestamp of the next opening, rendered in each viewer's local time.
  4. ModMail users who DM the bot outside hours receive "We're currently outside of business hours. Please try again later." and no ticket is opened.

The next-opening placeholder

In an after-hours message built with containers you can place {nextOpenTime} anywhere in the content. It becomes a Discord timestamp when Show the next opening time is on.

If you leave the placeholder out, the bot appends a block instead: We'll be back: with the timestamp, Our Hours: with your weekly schedule, and a note that times are shown in the viewer's local timezone.

If the next opening cannot be worked out (for example every day is disabled), the placeholder is removed silently.

What else uses the schedule

FeatureBehaviour
SLA ManagementWith Pause outside business hours on (Staff → Response targets), SLA timers pause while you are closed, including holidays
AI answersWhen staff are around set to Outside hours (AI assistant → Atlas → Answer questions in tickets) makes Atlas answer only when your team is closed, so staff handle tickets during the day and the AI covers nights. The option shows while business hours are on
ModMailDMs outside hours follow Let members open tickets after hours as described above
Auto-close, reminders and Auto-unclaimWith Pause on closed days on (the default), they wait while you are closed and run once you open. See Pause on closed days
ModMail remindersNot paused by Pause on closed days

Pause on closed days

While the schedule says you are closed (outside opening times, on days you turned off, and on holidays), auto-close and the inactivity reminders before it wait, and Auto-unclaim releases no claims. Once you open, they run as usual.

Go to Closing tickets → Auto-close and reminders
  • The switch is the Pause on closed days card in Closing tickets → Auto-close and reminders. It is on by default and shows on Enterprise, the plan with business hours.
  • It only pauses while the Business hours card is on; with business hours off, the card says so and links here.
  • Quiet time keeps counting while you are closed. A ticket that reaches its auto-close or reminder time overnight is closed or reminded once you open, so several can happen at once at opening time. Auto-close handles up to 10 tickets per server at a time, the longest quiet first, so a big pile can take a while to clear.
  • Tickets that came due while you were closed close when you open, the same way as any other auto-close, with whatever DMs your closing settings send. Only a ticket your schedule would have let auto-close more than an hour earlier (for example when many are waiting and later batches take that long, or the bot was offline after you opened) closes without a close DM, transcript copy or feedback request to its creator. Everything else about that close stays the same.
  • ModMail reminders are not paused.
  • If the schedule cannot be read, nothing is paused.
SettingAllowed valuesDefault
Pause on closed days (card switch)on or offon

Limits and gotchas

  • One schedule and one timezone per server. Different teams in different timezones need to agree on one schedule.
  • One time range per day. Split shifts (morning and evening with a lunch gap) are not supported; enable the whole span instead.
  • Holidays are always full-day closures. Use the weekly schedule for shortened days.
  • Up to 200 holidays per server. Remove past one-off dates to make room.
  • The start time is inclusive and the end time is exclusive: with 09:00 to 17:00, a ticket at 17:00 exactly is outside hours.
  • The schedule is stored in the timezone you pick, but users always see the next opening time in their own timezone thanks to Discord timestamps.
  • If the bot cannot evaluate the schedule for any reason, it errs on the side of creating the ticket rather than blocking users.

A saved time zone never changes by itself. With Use this browser's time zone on, someone who opens the page from a browser in another time zone sees Opening times use with your saved zone, and the zone only changes if they click Use with their own zone and save. Teams spread across regions can turn the option off and pick the zone explicitly.

Troubleshooting

SymptomCauseFix
Tickets are still created outside hoursLet members open tickets after hours is on (the default), or the bot owner's plan is not EnterpriseTurn the switch off to block, and confirm the plan on Plan & billing
Users get TC018 during working hoursThe time zone is wrong, or the day is turned off or listed as a holidayCheck Time zone and the day's switch under Opening times; remove stale one-off holidays
Users see TC018 with no next opening timeShow the next opening time is off, or every day is turned off so no opening existsTurn the switch on and turn on at least one day
The after-hours notice shows the default text, not mineThe message is in the older style and its Title or Message is empty, or the containers have no contentFill in Title and Message, or add content to the containers
Tickets auto-close or get reminders at nightPause on closed days is off, the Business hours card is off, or the bot owner's plan is not EnterpriseTurn on Pause on closed days in Closing tickets → Auto-close and reminders and the Business hours card
SLA timers keep running at nightPause outside business hours in Staff → Response targets is offTurn it on; see SLA Management
Staff were not pinged for an off-hours ticketThe button, menu or ModMail staff ping is skipped on purpose for tickets created outside hours (a thread ticket still mentions your staff roles at the top)Expected. Use the notice in the ticket or check the queue in the morning
Staff were pinged for an off-hours thread ticketA new thread ticket always mentions your staff roles at the top, at any hour, because that is how Discord adds them to the threadExpected for thread tickets. If you do not want that mention after hours, use ticket channels instead of threads
The next opening time is a day lateAn overnight range such as 22:00 to 06:00 belongs to the day it starts onEnable the range on the evening day, not the morning day

Common questions

Can users still open tickets when we are closed? Yes by default. Let members open tickets after hours is on unless you turn it off, and the ticket gets an after-hours notice. Turn the switch off to block tickets with a TC018 message instead.

Do business hours affect ModMail? Yes. Outside hours, a DM either opens a ticket with the after-hours notice (Let members open tickets after hours on) or gets "We're currently outside of business hours. Please try again later." (switch off).

Can I set different hours for different ticket categories or priorities? No. There is one schedule per server. Use SLA Management targets per priority if you need urgent tickets treated differently.

How do I handle daylight saving time? Nothing to do. Pick a named timezone such as Europe/London and the schedule follows local time through the change.

Why does the next opening time look different for different users? It is a Discord timestamp, so Discord renders it in each viewer's own timezone. The underlying moment is the same.

Can I close for lunch? Not with a gap. Each day has a single range. Keep the range continuous, or make a holiday for a whole day off.

What does the user see when tickets are blocked? An error card with code TC018, your after-hours heading, and, if enabled, the next opening time. Nothing is created and staff are not notified.

Does the schedule stop auto-close timers overnight? It holds the closes, not the clock. With Pause on closed days on (the default) in Closing tickets → Auto-close and reminders, no ticket is auto-closed and no reminder is posted while you are closed, but quiet time keeps counting, so tickets that went quiet overnight can be closed or reminded right when you open. SLA timers are different: with Pause outside business hours on in Staff → Response targets, the time you are closed does not count at all.

Why did many tickets close at once when we opened? Pause on closed days waits until you open before closing quiet tickets or sending reminders. Every ticket that passed its auto-close or reminder time while you were closed is handled after you open, up to 10 auto-closes per server at a time. Those closes work like any other auto-close; only a ticket your schedule would have let auto-close more than an hour earlier closes without DMing its creator. Turn Pause on closed days off if you prefer tickets to close at any hour.

Last updated on

On this page