SLA Deadline Calculator

Overview

You send the instant the clock started, the priority, and the policy that governs it — business hours per weekday, the weekend, the holidays, and the target minutes per priority. We walk working time forward and return the deadline in UTC and in the policy's own timezone, together with the escalation instants and the pauses that were actually applied. A BUSINESS target consumes only time inside your windows, so evenings, weekends and holidays cost nothing; a CALENDAR target is plain elapsed time for a 24x7 commitment. Pauses suspend the clock for their overlap with working time only, which is why pausing over a weekend consumes nothing. Send asOf as well and we also report how much of the target has been used, what is left, and whether it has been breached. Weekend, holiday and next-working-day questions are answered by the same calendar engine as the time skills, so two answers can never disagree about whether a date is a working day. The clock is never read: every instant is yours.

Every support tool computes SLA deadlines, and most of them get the edges wrong: a ticket opened at 16:50 on the Friday before a public holiday, a lunch gap that should not count, a pause taken over a weekend, a clock walked in local time straight through a daylight-saving transition. Getting those right needs a walk over declared working time, not an addition of hours, and it needs the same weekend and holiday definition the rest of the platform uses.

When to use it

Scope

Non-goals

• Does not read the clock — start, asOf and every pause are inputs
• Does not know your holidays: a holiday is whatever you send
• Does not escalate, notify, assign or store anything
• Does not decide priority — you send the one to apply
• Does not count business days on its own: day classification is the time pack's calendar engine

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"business.sla_deadline","input":{"start":"2026-03-02T08:00:00Z","priority":"P2","slaPolicy":{"timezone":"Europe/Brussels","targets":{"P2":{"durationMinutes":480}},"businessHours":{"MONDAY":[{"from":"09:00","to":"17:00"}],"TUESDAY":[{"from":"09:00","to":"17:00"}],"WEDNESDAY":[{"from":"09:00","to":"17:00"}],"THURSDAY":[{"from":"09:00","to":"17:00"}],"FRIDAY":[{"from":"09:00","to":"17:00"}]}}}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("business.sla_deadline", {"start":"2026-03-02T08:00:00Z","priority":"P2","slaPolicy":{"escalations":[{"atPercent":0.75,"name":"notify-lead"}],"businessHours":{"MONDAY":[{"from":"09:00","to":"17:00"}],"TUESDAY":[{"from":"09:00","to":"17:00"}],"WEDNESDAY":[{"from":"09:00","to":"17:00"}],"THURSDAY":[{"from":"09:00","to":"17:00"}],"FRIDAY":[{"from":"09:00","to":"17:00"}]},"timezone":"Europe/Brussels","targets":{"P2":{"durationMinutes":480},"P1":{"durationMinutes":120}}}});

Errors

Other limits

Limitations

• Does not read the clock — start, asOf and every pause are inputs
• Does not know your holidays: a holiday is whatever you send
• Does not escalate, notify, assign or store anything
• Does not decide priority — you send the one to apply
• Does not count business days on its own: day classification is the time pack's calendar engine
• Counting whole business days between two dates — that is time.business_days_between
• Adding business days to a date — that is time.add_business_days
• Deciding which priority a ticket deserves
• Watching a clock and firing the escalation for you

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "business.sla_deadline",
  "input": {
    "start": "2026-03-02T08:00:00Z",
    "priority": "P2",
    "slaPolicy": {
      "escalations": [
        {
          "atPercent": 0.75,
          "name": "notify-lead"
        }
      ],
      "businessHours": {
        "MONDAY": [
          {
            "from": "09:00",
            "to": "17:00"
          }
        ],
        "TUESDAY": [
          {
            "from": "09:00",
            "to": "17:00"
          }
        ],
        "WEDNESDAY": [
          {
            "from": "09:00",
            "to": "17:00"
          }
        ],
        "THURSDAY": [
          {
            "from": "09:00",
            "to": "17:00"
          }
        ],
        "FRIDAY": [
          {
            "from": "09:00",
            "to": "17:00"
          }
        ]
      },
      "timezone": "Europe/Brussels",
      "targets": {
        "P2": {
          "durationMinutes": 480
        },
        "P1": {
          "durationMinutes": 120
        }
      }
    }
  }
}

Examples

{
  "start": "2026-03-02T08:00:00Z",
  "priority": "P2",
  "slaPolicy": {
    "escalations": [
      {
        "atPercent": 0.75,
        "name": "notify-lead"
      }
    ],
    "businessHours": {
      "MONDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "TUESDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "WEDNESDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "THURSDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "FRIDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ]
    },
    "timezone": "Europe/Brussels",
    "targets": {
      "P2": {
        "durationMinutes": 480
      },
      "P1": {
        "durationMinutes": 120
      }
    }
  }
}

{
  "deadline": "2026-03-02T16:00:00Z",
  "timezone": "Europe/Brussels",
  "durationMinutes": 480,
  "pauses": [],
  "clock": "BUSINESS",
  "escalationsAt": [
    {
      "name": "notify-lead",
      "atPercent": 0.75,
      "at": "2026-03-02T14:00:00Z",
      "atLocal": "2026-03-02T15:00:00+01:00"
    }
  ],
  "deadlineLocal": "2026-03-02T17:00:00+01:00",
  "workingMinutesConsumed": 480
}

{
  "priority": "P1",
  "start": "2026-03-06T15:00:00Z",
  "slaPolicy": {
    "businessHours": {
      "MONDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "TUESDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "WEDNESDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "THURSDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ],
      "FRIDAY": [
        {
          "from": "09:00",
          "to": "17:00"
        }
      ]
    },
    "timezone": "Europe/Brussels",
    "targets": {
      "P1": {
        "clock": "BUSINESS",
        "durationMinutes": 480
      }
    },
    "holidays": [
      "2026-03-09"
    ]
  },
  "pauses": [
    {
      "from": "2026-03-07T00:00:00Z",
      "to": "2026-03-08T00:00:00Z",
      "reason": "waiting on customer"
    }
  ],
  "asOf": "2026-03-10T09:00:00Z"
}

{
  "durationMinutes": 480,
  "timezone": "Europe/Brussels",
  "breached": false,
  "pauses": [
    {
      "from": "2026-03-07T00:00:00Z",
      "to": "2026-03-08T00:00:00Z",
      "reason": "waiting on customer",
      "effectiveMinutes": 0
    }
  ],
  "deadlineLocal": "2026-03-10T16:00:00+01:00",
  "remainingMinutes": 360,
  "deadline": "2026-03-10T15:00:00Z",
  "workingMinutesConsumed": 120,
  "clock": "BUSINESS",
  "escalationsAt": [],
  "consumedPercent": 0.25
}

Recommended use cases

• Set a due date on a ticket at creation, from the priority and the support calendar
• Show a customer when their case is due, in their own timezone
• Compute escalation instants once, so the reminder job has nothing to guess
• Report how much of an SLA is spent at a point in time, and whether it is breached

Avoid for

• Counting whole business days between two dates — that is time.business_days_between
• Adding business days to a date — that is time.add_business_days
• Deciding which priority a ticket deserves
• Watching a clock and firing the escalation for you

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags