-
Email or online ticketing support
-
Yes
-
Support response times
-
According to the signed SLAs
-
User can manage status and priority of support tickets
-
Yes
-
Online ticketing support accessibility
-
WCAG 2.2 AA
-
Phone support
-
Yes
-
Phone support availability
-
24 hours, 7 days a week
-
Web chat support
-
Yes, at an extra cost
-
Web chat support availability
-
24 hours, 7 days a week
-
Web chat support accessibility standard
-
WCAG 2.2 AA
-
Web chat accessibility testing
-
We deliver web chat through the ServiceNow Service Portal (Virtual Agent/Live Chat) and verify accessibility in two ways: (1) baseline assurance via vendor Accessibility Conformance Reports (WCAG 2.1 AA / Section 508), and (2) our own assistive‑technology (AT) testing on the buyer‑branded portal prior to go‑live. Our AT testing combines keyboard‑only navigation with screen readers (NVDA, JAWS, VoiceOver), high‑contrast/zoom (200–400%), and, where relevant, Dragon speech input. Moderated sessions follow task‑based scenarios: launching chat from the portal and via deep links; confirming predictable focus; reading bot and agent messages in order (ARIA live‑region announcements); composing/sending messages and handling errors; uploading/downloading attachments; minimising/restoring the chat window; escalating to a human agent; ending chat and exporting a transcript. We check that tab order is logical, roles/names/states are exposed programmatically, and that text reflows without loss of content or functionality. Findings are logged against WCAG 2.1 success criteria, remediated in the theme/widgets (e.g., focus management, landmark structure, contrast tokens, ARIA attributes), and retested before release. This approach has consistently cleared blocker issues and confirmed an operable, perceivable, and robust chat experience for assistive‑technology users.
-
Support levels
-
L2 — Functional/Technical Engineering
Handles complex configuration and enhancements, defect analysis and fixes, Power Platform flows/apps, data remediation, and integration troubleshooting. Owns regression testing for Microsoft “One Version” updates and prepares release notes and runbooks.
L3 — Solution Architecture & Release Management
Defines environment strategy and ALM, governs “One Version” cadence, designs/assures integrations, performance tunes at scale, sets guardrails (security, data, compliance), chairs change advisory, and maintains the product/roadmap backlog.
Service management (included)
A named Platform Manager / Technical Account Manager (TAM) provides governance, service reviews, KPI reporting, risk/issue management, and stakeholder communications. Cloud/Application Support Engineers deliver day‑to‑day execution across L2/L3.
Hours and SLAs
Standard coverage is Business Hours (UK) with optional 24×7 for P1/P2. Typical SLAs (tailored at Call‑Off): P1 response 30 minutes / engineering ≤2 hours; P2 response 30 minutes / engineering ≤4 hours; P3/P4 triaged same business day. Monthly reports cover SLA attainment, incident trends, change success rate, and improvement actions.
Ticketing and escalation
Incidents/requests via the agreed online portal (ServiceNow or Jira Service Management). Major Incidents follow an expedited workflow with bridge calls and PIRs.
Onboarding and knowledge
Structured transition, documentation handover (as‑built, runbooks, ALM), access model (RBAC), and knowledge transfer ensure continuity and self‑sufficiency.
-
AI chatbot
-
Yes