Flow and role map
Intake, qualification, decisions, assignments, escalations and closure criteria are explicit.
ITSM & Service Management
Frame the processes before building or extending the tool.
This page covers flows, roles, SLAs, escalations, changes, problems, assets and operating rules. The Service Desk page separately describes a portal, focused ticketing or platform extension.
What framing makes verifiable
Operational decisions before development.
An ITSM workflow can be technically correct and still be unusable. Priority, impact, urgency, SLA, ownership, escalation, categories, change and CMDB must match real team practices and become testable rules.
Rules matrix
Priorities, commitments, approvals, exceptions and required data become verifiable.
Views and acceptance criteria
Agent, manager and user journeys are tested with the indicators that actually matter.
From framing to tool
A custom Service Desk has its own operational scope.
The dedicated page describes portal, queues, prioritisation, SLAs, escalations, knowledge, assets, reporting and integration options. It complements the ITSM framing shown here.
Areas to frame
From the priority process to a coherent ITSM cockpit.
These areas can feed one focused component, several coherent modules or an extension around the current platform. They are not a promise to replace everything.
Incidents & requests
Portal, forms, prioritisation, queues, assignment, escalations, SLAs and user communications.
Service catalogue
Guided requests, required data, eligibility rules, approvals and associated commitments.
Problems & causes
Recurrence, analysis, known errors, corrective actions and links to incidents.
Changes
Standard / normal, risk, impact, approvals, calendar, tasks, rollback and review.
Assets & configuration
Equipment, configuration items, users, sites and services with the right level of relationship and upkeep.
Knowledge
Articles, procedures, known solutions, search and diagnostic assistance with appropriate rights.
Automation
Routing, reminders, enrichment, synchronisation, notifications and checks before human action.
Reporting & SLAs
Backlog, age, volumes, SLA/OLA, reopenings, escalations, trends and recurring causes.
Flow examples
Concrete, actionable ITSM processes.
The model is not fixed. These examples show the level of operational precision GE2Smart can build into a tool.
Detection→Qualification→Mobilisation→Communication→Recovery→Review
Roles, timestamps, communication and evidence gathered in one place.
Request→Eligibility→Approval→Execution→Control
Approvals remain human where they need to be; the rest can be automated.
Submission→Risk→Approval→Planning→Execution→Closure
Governance depends on actual risk, not one identical form for every change.
Already have an ITSM tool?
The right project is not always to replace the platform.
A specific need may be addressed with a peripheral application, portal, automation, cockpit or integration rather than a complete redesign.
Examples
- Business portal connected to ticketing
- More operational backlog / SLA cockpit
- Specific approval workflow
- Synchronisation with directory, CMDB or business tool
- Knowledge assistant with sources and permissions
- AI preparation or enrichment of tickets
Possible around platforms such as ServiceNow, EasyVista or Jira Service Management, subject to available APIs and rights.
AI & IT operationsA copilot can help support teams.
A copilot can help support teams.
It must not invent reality.
GE2Smart favours controllable uses: find a procedure, summarise history, suggest classification, prepare an answer, identify similar tickets or suggest the next action.
A document-based answer should be traceable to a known knowledge base.
The copilot must not expose more than the user is allowed to see.
Sensitive changes and operational decisions remain explicitly approved.
When your IT team needs fewer workarounds.
Custom work becomes especially useful when the real process spills beyond the standard tool.
Your Service Desk still relies on emails and spreadsheets
You need structure without launching a heavy ITSM programme.
Your ITSM platform is too generic for a critical process
A focused extension may avoid costly, fragile customisation.
Reporting exists but does not help managers act
A cockpit can put backlog, SLA risk and priorities back into operational context.
You want automation without losing governance
Repetitive tasks can be automated while necessary approvals remain in place.
Illustrative ITSM scenarios
From ticket to management, four starting points.
These scenarios are not customer references. Final scope depends on your organisation, existing platform, volumes and security requirements.
IT · Service DeskITSM / Service Desk
ITSM request and incident portal
Guided intake, routing, queues, priorities, SLAs, knowledge and a complete history.
View the related solutionIT operations · ITSMITSM workflow
Major incident coordination
Detection, qualification, mobilisation, communication, recovery and review with roles and timestamps.
View the related solutionIT operations · ChangeITSM workflow
Change approval workflow
Risk, impact, approvals, calendar, tasks, rollback and review in a proportionate flow.
View the related solutionIT · Service ManagementAI business copilot
ITSM knowledge copilot
Search authorised knowledge, summarise history and prepare a response without bypassing permissions.
View the related solutionLet’s discuss Service ManagementShow us the current flow.
Show us the current flow.
We will discuss process before code.
A ticket export, workflow diagram or a few screenshots are enough to start the diagnostic.
Start the ITSM diagnostic →