Service Level Objectives
The following definitions govern how support tickets are classified within the Patchworks platform. Severity levels determine response prioritisation and are based on the operational impact to the platform itself.
Service Level Objectives: Priority Definitions
Urgent: Platform is down or critically impaired
The Patchworks platform is unavailable, unresponsive, or experiencing a failure that prevents normal operation. No workaround is possible, and business operations are at a standstill.
Examples
- Platform UI completely inaccessible
- Core API returning 5xx errors
- All scheduled flows have stopped executing
- Authentication service failure preventing login
High: Core platform functionality severely degraded
A significant platform function is impaired, but the platform remains partially operational. The issue causes measurable business impact, and no reasonable workaround exists.
Examples
- Flow execution engine intermittently dropping runs
- Platform logging and monitoring unavailable, preventing error visibility
- Connector version management and virtual environments non-functional
- Data throughput severely throttled
Normal: Platform issue with a workaround or limited impact
A platform feature or function is not behaving as documented but a workaround exists, or the impact is limited to non-critical workflows. Includes requests for guided support on platform capabilities.
Examples
- UI bug causing incorrect display of flow history or run logs
- Connector behaving inconsistently with documented spec
- Intermittent slowness affecting flow execution
- Request for guidance on platform configuration or feature use
Low: General enquiry, feedback, or minor inconvenience
No operational impact. The request relates to product questions, documentation feedback, feature suggestions, or cosmetic/UX issues that do not impair platform use.
Examples
- Request for clarification on platform documentation
- Feature request or product feedback
- Cosmetic UI issue with no functional impact
- General “how do I…” questions about the platform
Basic Ticket State Flow
Acknowledged: Patchworks will communicate receipt of the initial request for support.
- Assigned: Patchworks will communicate that a Ticket has been assigned and severity prioritised. This marks the beginning of investigation/resolution planning.
- Resolved: Patchworks will communicate when a Resolution is available. Patchworks will provide the necessary instructions, guidance, and/or software or documentation updates required to implement this Resolution. (Resolution may be any of the following: fixed, won’t fix, incomplete, workaround, duplicate or cannot reproduce).
- Fixed: Where applicable, Patchworks will communicate when a permanent fix is available. Supplier will provide the necessary instructions, guidance, and/or software or documentation updates required to implement the fix. A fix may be made available in conjunction with a scheduled software release cadence.
- Closed: Problem has been resolved and, where applicable, a fix has been implemented and communicated to the Customer or End User who has accepted the resolution. No further action is required.
Ticket Response Times
Ticket Times are an objective and may vary if Customer has purchased Advanced or Hyper Support. Resolution times will not apply to Customer-created data issues, third-party-created issues, or misuse of the Patchworks Services by any unapproved modification to Patchworks code.
Awaiting Prioritisation
- Priority assigned within 30 minutes.
Example: All tickets
Urgent
- Response time: Immediate response time
- Resolution time: within 8 hours
- Complete time: within 24 hours
Example: Platform UI completely inaccessible or all scheduled flows have stopped executing
High
- Initial response time: < 90 minutes
- Resolution time: within 16 hours
- Complete time: within 72 hours/ as per monthly plan
Example: Flow execution engine intermittently dropping runs
Normal
- Initial response time: < 4 hours
- Resolution time: within 5 working days
- Complete time: within 15 days / as per monthly plan
Example: Connector behaving inconsistently with documented spec
Low
- Initial response time: < 5 business days
- Resolution time: within a commercially reasonable time
- Complete time: within a commercially reasonable time
Example: Feature request or product feedback
Communication Channels
* Availability is subject to chosen support tier
Urgent:
- Ticket: follow-up only
- Email*: follow-up only
- Phone*: yes
High:
- Ticket: follow-up only
- Email*: yes/ follow up only
- Phone*: yes
Normal:
- Ticket: follow up only
- Email*: yes
- Phone*: yes
Low:
- Ticket: yes
- Email*: yes
- Phone*: no/ batch only
Uptime:
These Service Level Objectives apply to all services delivered directly to Customers of Patchworks.
Availability
Patchworks services have a guaranteed 99.9% uptime. Uptime is exclusive of service outages attributed to:
- Scheduled maintenance of which Customer has notice.
- Failures by the Customer, the Customer’s third-party providers, suppliers or any factors beyond Patchworks reasonable control.
- Internet connectivity issues (Customer cannot connect to the internet).
Patchworks will use reasonable endeavours to ensure that the integration is up and running at all times.
