Enterprise service management in banking:
IT workflows and audit readiness

ITSM for regulated industries: what enterprise service management means in banking

ITSM for regulated industries is IT service management run as an evidence trail: every incident, change and request is logged, approved and timestamped so a bank can meet reporting deadlines and answer auditors. Enterprise service management extends that discipline beyond IT to HR, finance and facilities, with AI-powered ITSM and IT workflow automation handling the routine work and incident and change management controlling the rest.

For a bank, the record matters as much as the fix. When systems fail, the incident ticket shows when the problem was detected and classified, which starts the regulatory reporting clock. When an auditor asks who approved a production change, the change record answers. Freshservice, the IT service management software from Freshworks used as the example on this page, covers incident, problem, change and release management, IT asset management, alert management and Freddy AI for agents and employees.

Why banks treat internal IT as a regulated process

• Incident reporting: EU and US supervisors set deadlines measured in hours from when a bank identifies a serious incident.
• Asset inventories: EU rules require financial firms to identify and document all information and ICT assets and keep the inventory current.
• Change control: who approved a change, and when, is a standard audit test.
• Third parties: outages increasingly start at cloud, telecoms and hosting suppliers, which the bank must still record and report.
• Access: joiner, mover and leaver requests leave a trail of who was given access to what.

Audit readiness in banking IT: the reporting clocks and the cost of failure

The EU's Digital Operational Resilience Act (DORA) has applied to banks, insurers and investment firms since 17 January 2025, and its reporting clock is short. The figures below describe the sector and its rules, not Freshservice.

Incident and change management: how Freshservice handles outages and approvals

A serious outage in a bank rarely arrives as one alert. A failing database triggers alerts from every monitoring tool that depends on it, and engineers lose minutes sorting duplicates while the reporting clock runs. Freshservice's alert management, on its Growth, Pro and Enterprise plans, takes alerts from monitoring tools through ready-made integrations or webhooks and opens or resolves incidents by rule. On Pro and Enterprise, Freshservice's automated grouping uses Freddy, its machine-learning engine, to attach related alerts to the open incident; Freshworks states that this reduces alert noise by up to 50%. On-call alerts escalate through Microsoft Teams, Slack, WhatsApp, SMS, phone and email.

Change management carries the approval trail. Freshservice's problem, change and release management sit on its Pro and Enterprise plans, and admin audit logs on Enterprise. Freshworks closed its acquisition of FireHydrant, an incident-management company, on 5 January 2026, and says it will connect FireHydrant's incident response with Freshservice's service and asset records.

The audit point is simple. DORA's four-hour clock runs from the moment an incident is classified as major, and the US 36-hour clock from the moment a bank determines a notification incident has occurred. A bank that records classification as a timestamped step in the incident ticket can show a supervisor exactly when each clock started.

Sources: Freshservice Support, alert management (updated 9 Dec 2025), automated grouping (24 May 2024); Freshservice ITOM; FireHydrant acquisition; all read 1 Oct 2026.

AI-powered ITSM: what the Freshservice Benchmark Report 2025 measures

AI-powered ITSM claims are only as useful as the data behind them. The Freshservice Benchmark Report 2025, published by Freshworks on 12 August 2025, draws on more than 187 million tickets from 10,743 organisations in 118 countries; Freshworks bases its KPI benchmarks on 10,551 of those teams. It reports that Freddy AI Copilot users cut average ticket resolution time by 76.6% and improved first response time by 41.1%, and that Freddy AI Agent deflected 65.7% of tickets, saving an estimated 431,270 agent hours a year.

Two cautions apply before a bank uses those numbers in a business case. They are averages across all Freshservice customers, not a banking cohort, and the report publishes no financial-services breakdown. And they are vendor-reported. A bank's own baseline, measured before rollout, is the figure an auditor or board will accept.

One named financial institution gives a narrower view. On Freshworks' Freddy AI page, Fox Communities Credit Union, a Wisconsin credit union, says Freshservice's Freddy AI virtual bot deflects 65% of its IT tickets and that Freddy AI Copilot saves it 200 hours a month.

Source: Freshservice Freddy AI, read 1 Oct 2026. Freshworks-reported.

IT workflow automation: internal requests, approvals and the audit trail

IT workflow automation takes the repetitive employee requests out of the IT queue — password resets, software access, onboarding — while keeping the approval record a bank needs. Freshservice's AI Agent Studio lists password resets, software access approvals and onboarding workflows among its typical uses, and builds agents that answer questions, open incidents and take action through connected apps. Freddy AI Agent works in Microsoft Teams, Slack, the support portal, email and Microsoft 365 Copilot. It is part of the Enterprise plan, with 1,200 sessions a year, a session being one employee's interactions within 24 hours; AI Agent Studio is being offered on Growth, Pro and Enterprise as a promotion until 31 December 2026.

In a bank, the automation needs limits. A password reset should require identity verification and exclude privileged and administrator accounts, and requests that change access should still route through an approval step, so the audit trail shows who authorised each grant.

Where AI processing happens is the next question a data-protection officer will ask. Freshworks' Freddy AI FAQs state that Freddy AI uses Microsoft Azure OpenAI for certain features, that customer data is never used to train third-party models, and that data hosted in the US or EU stays in its region; data hosted elsewhere may be sent to Azure OpenAI in another region to generate a response, without being stored there. Data from consenting customers does train Freshworks' own models, so the consent setting belongs on the bank's checklist.

Sources: Freshservice Support, AI Agent Studio (updated 29 Sep 2026), Freddy AI Agent (27 Jan 2026), Freddy AI data and safety FAQs; all read 1 Oct 2026.

Certifications and audit evidence: PinkVERIFY, ISO 27001 and SOC 2

Two kinds of evidence answer different audit questions. Process certification shows the workflows follow a recognised framework: Freshservice is PinkVERIFY-certified across six ITSM processes — incident, change, problem, asset, request fulfilment and service catalogue management — an assessment of ITIL alignment by Pink Elephant, first announced by Freshworks in December 2019. Freshworks also describes Freshservice as a Gold Accredited Tool Vendor with certification across 14 ITIL practices. Neither is a regulatory certification; they tell an auditor the process design is standard.

Security attestation shows the vendor itself is audited. Freshworks, which makes Freshservice, lists ISO/IEC 27001:2022, ISO/IEC 27701:2019 and a SOC 3 report in the Freshworks Trust Center, with SOC 1 Type 2 and SOC 2 Type 2 reports available on request within one business day.

The third piece is the bank's own inventory. DORA's Article 8 requires financial firms to identify and document all information and ICT assets, map the critical ones and update inventories after every major change. Freshservice's unified IT asset management discovers assets across on-premises, cloud and hybrid environments and maps dependencies, with discovery added from Device42, which Freshworks acquired in June 2024.

Sources: PinkVERIFY announcement (23 Dec 2019); Freshservice ITSM; Freshworks Trust Center; DORA Article 8; Freshservice ITAM; all read 1 Oct 2026.

For a bank's vendor-risk team, that means the AI data terms that apply to Freshservice do not automatically extend to the discovery and incident tools now being joined to it. Each needs its own review of data handling, hosting and sub-processors before it touches production systems.

Enterprise service management beyond IT: HR, finance and facilities on one platform

Enterprise service management puts non-IT teams on the same workflows. A new starter's laptop, system access, building pass and payroll set-up become one onboarding request with tasks for IT, facilities and HR; a leaver's access removal follows the same path in reverse. For audit purposes, that turns joiner, mover and leaver controls from a set of emails into a single record with approvals and timestamps.

Tata Consumer Products, the Indian food and beverage group, gives an enterprise example. Freshworks reports that it uses Freshservice for its IT and finance teams, cutting incident resolution time by 73%, from 15 hours to 4, reviewing incidents 87% faster with Freddy AI Copilot, and running change management 137.5% faster in its HR department through automated workflows. Its distributor support runs separately on Freshdesk, Freshworks' customer service product.

Source: Tata Consumer Products customer story, read 1 Oct 2026. Freshworks-reported.

Freshservice pricing: where the audit controls sit

Freshservice is priced per agent per month, and the controls a bank's auditors look for rise with the plan. Cllimber's profile of Freshservice IT service management for financial services sets out which controls sit in which tier.

Prices are per agent per month in US dollars, billed annually. Additional ITAM asset units and advanced asset functions are sold separately. Check Freshworks' site for current pricing.

Source: Freshservice pricing (US), read 1 Oct 2026.

Pre-audit checklist: what to verify in a Freshservice deployment

• Incident timestamps: detection and classification recorded as separate, timestamped steps in every major incident
• Change trail: approvals recorded on every production change, and audit logs switched on
• Inventory coverage: discovery running across on-premises, cloud and remote sites, with critical assets mapped to business services
• Automation limits: AI-driven password resets verified and excluded from privileged accounts
• Vendor evidence: ISO 27001 certificate and SOC 1 and SOC 2 Type 2 reports from the Freshworks Trust Center on file
• Own baseline: resolution and deflection measured before rollout, so vendor benchmarks are not the only evidence
• Acquired tools: separate data-handling review for Device42 and FireHydrant