LLPROBeta

Home / Businesses / SLA Deadline in Business Hours

SLA Deadline in Business Hours

Work out when a support or service SLA is due counting only business hours in an IANA time zone, with holidays, closed days and on-hold periods, and whether a reply met or breached it, with a signed record.

Live

What it does
Work out when a support or service SLA is due counting only business hours in an IANA time zone, with holidays, closed days and on-hold periods, and whether a reply met or breached it, with a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call sla_deadline at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Live: open today. Free

New to this? Start here.

What it does

SLA Deadline in Business Hours is for agents that run support queues or service contracts and need response and resolution deadlines, and breaches, worked the same way every time across time zones and daylight-saving changes. Work out when a support or service response is due when the clock only runs in business hours, and whether a reply or fix time breached it. Send when the clock started (start), the IANA time zone of the business hours, the target (target_minutes or target_hours of business time), and optionally the weekly schedule (default Monday to Friday 09:00-17:00; split shifts and 24-hour days allowed), US federal holidays, your own closed dates and on-hold periods that stop the clock. Get back the due time in local time and UTC, the holidays and closed days skipped, and, if you send check_at (when the reply or fix happened), met or breached with the business minutes used and the margin. Daylight-saving changes are handled through the IANA time zone database. It is one of the Scheduling department tools LLPRO builds for the work agents do across business software (Zendesk, Freshdesk, Servicenow, Jira Service Management, Google Calendar). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that run support queues or service contracts and need response and resolution deadlines, and breaches, worked the same way every time across time zones and daylight-saving changes.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call, schedule up to 28 entries, closed_dates up to 200 entries, paused up to 50 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not know your contract: which tickets the SLA covers, priorities, or whether a weekend or holiday counts are yours to send. Does not include state, local or other countries' holidays (send them as closed_dates), Inauguration Day (5 U.S.C. 6103(c), Washington, D.C. area only), one-off closings by Executive order, or overnight spans that cross midnight (send them as two entries, e.g. 22:00-24:00 and 00:00-06:00). Counts business days only as hours (a 'next business day' SLA is a number of business hours here). Works from 1990 to 2100 and up to 3 years after start. Not legal advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "sla_deadline", "arguments": {"start": "2026-11-20T16:00", "zone": "America/New_York", "target_hours": 4}}}

For agents

Tool sla_deadline on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:khb7dzh27fvupberawcjf53ffy): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): CZ1UD04vxoOdEtBXznAEX5XceJJNONwJn9/H+CLC9Qs=

For agents that search MCP registries for SLA deadline, business hours, response time tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card