Thread already knows when you are open. Business hours, time zones, holidays and custom closures can be configured at workspace, team and client level, and they are already respected by SLA timers, the Triage Agent's after-hours handling, and Messenger's after-hours experience.

Super Magic cannot see any of it. It also has no reliable sense of the current date and time, which makes any date-sensitive instruction in a skill or intent unpredictable.

What this would unlock

Stop a skill from running on holidays or outside business hours, without maintaining a separate holiday list in every flow and every skill

Prevent work being scheduled on a day the team is closed

Let customer-facing replies set the right expectation, such as noting that a request will be picked up when the office reopens

Make date-based rules dependable, for example checking whether a requested start date gives enough notice

What we would like

Super Magic should be able to ask Thread whether you are currently open, and get back the hours, holidays and closures that apply to the relevant client.

Two things would make this dependable. Thread should work out which hours apply, client first, then team, then workspace, rather than leaving the agent to figure it out. And it should return a clear yes or no on whether you are open right now, along with the current local date and time, rather than raw hours for the agent to calculate against.

Today the only workaround is hard-coding holiday dates into flow filters, which means maintaining the same calendar in multiple places even though Thread already stores it once.