Feature Requests

Make business hours and holidays available to Super Magic
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.
0
·
Super Magic
Scheduled Skill Execution (Standalone, No Flow Required)
Summary Allow skills to be scheduled to run automatically on a recurring basis — without requiring them to be embedded inside a Flow. Current State Skills can only be triggered manually by a technician or admin in the Super Magic interface. The only path to automation today is embedding logic inside a Flow, which is designed for event-driven ticket actions — not time-based operational sweeps. Requested Behavior From the Skills catalog, allow an admin to set a schedule on any skill (e.g. daily at 6:00 AM CT, weekdays only) The skill runs automatically at the defined time, scoped to the configured workspace Output is delivered to a designated inbox, channel, or member — configurable per skill The run is logged with timestamp, output, and any telemetry the skill produces Manual "run now" remains available alongside the schedule Use Case Our OIT (Overnight Intake Triage) skill sweeps two boards every morning for unhandled overnight threads. Right now a technician has to remember to trigger it. A 6:00 AM scheduled run would surface unhandled threads before the first tech even opens their inbox — with zero manual effort. This pattern applies to any recurring operational skill: shift briefings, stale ticket sweeps, backup review checks, SLA risk scans, etc. Why Not a Flow? Flows are ticket-event-driven. A time-based board sweep has no triggering ticket — it's a proactive operational check. Forcing it into a Flow architecture is the wrong abstraction and adds unnecessary complexity. Priority Justification Scheduled skills turn Super Magic from a reactive tool into a proactive operations layer. The value compounds with every skill that has a natural cadence.
0
·
New Feature
Load More
→