Self-Service Portal
The Self-Service Portal is where your users meet ServiceCore. It gives employees, customers and external contacts a single, branded place to raise incidents and service requests, track what they've already opened, search the knowledge base and pull self-service answers before a ticket is ever created. The interface is dynamic and role-aware: menus, buttons, fields and actions are configured by an admin and shown, hidden or simplified to single-button flows per user, so each audience sees only what is relevant to them.
Built for the way self-service portal should work
The Self-Service Portal is where your users meet ServiceCore. It gives employees, customers and external contacts a single, branded place to raise incidents and service requests, track what they've already opened, search the knowledge base and pull self-service answers before a ticket is ever created. The interface is dynamic and role-aware: menus, buttons, fields and actions are configured by an admin and shown, hidden or simplified to single-button flows per user, so each audience sees only what is relevant to them.
Every request the portal collects flows straight into ServiceCore's shared data model rather than a separate inbox. A request raised here becomes the same record an agent works in Request Management or Incident Management, so there is no re-keying and no lost context. Users build records through dynamic forms tied to the Service Catalog: they browse or search only the catalog items they're entitled to, fill in the category, priority, description, attachments and any custom fields in one structured form, and the platform applies catalog-based SLAs, approval routing and rules-based assignment the moment the record is created.
Because the portal sits on top of the same model as the rest of the suite, it surfaces work from many modules in one place. Users follow live status on their own records, add notes and reopen items, and review threaded correspondence with the support team — and anyone added to the share list sees the record too. The portal also presents approvals routed from Request Management or Change Enablement, knowledge articles and suggested solutions from the Knowledge Base, assigned assets from Asset Management and the CMDB (with accept/reject of custody and the ability to log a fault directly against an asset), plus scheduled announcements for outages and maintenance.
The portal ships in two forms: the configurable classic end-user portal and Flexy Advanced Portal, a React-based single-page experience built for speed, deeper customization and full mobile responsiveness. Either way the experience is brandable and feels like part of your organization, and it works as the user-facing front door to ServiceCore's 29 modules without any of the back-office complexity reaching the end user.
- Modern self-service portal
- Request & ticket intake
- Live status tracking
- Knowledge search
- Suggested solutions
- Mobile-friendly
What you can do with it
Dynamic Role-Aware UI
Menus, fields, buttons and actions are admin-configured and shown, hidden or simplified per user, so each audience only sees the catalog items and actions it is entitled to.
Catalog-Driven Intake
Users raise incidents and service requests through dynamic forms bound to entitled Service Catalog items, capturing category, priority, attachments and custom fields in one structured record.
Live Status Tracking
End users list their own records, follow status, dates and category, add notes, reopen items and review threaded correspondence with the support team in the same place.
Knowledge & Suggested Solutions
Search of entitled Knowledge Base articles with automatic in-context suggestions that help users resolve issues themselves before a ticket is opened.
Portal Approvals & Assets
Approvals routed from Request Management or Change Enablement are actioned with full context, while assigned assets from the CMDB can be accepted, rejected or used to log a fault directly.
Announcements & Mobile Portal
Scheduled outage and maintenance announcements appear as planned pop-ups, and the React-based Flexy Advanced Portal delivers a fast, fully responsive single-page experience.
Why teams adopt it
Higher Deflection
Knowledge search and suggested solutions resolve routine questions before they become tickets, reducing inbound volume on the service desk.
Cleaner Intake
Structured catalog forms capture the right details up front, so agents stop chasing missing information and first-contact quality improves.
Fewer Status Calls
Self-service status tracking and shared records keep users informed without phone calls or follow-up emails to the team.
Consistent Branded Experience
A mobile-friendly, brandable portal makes ServiceCore feel like part of your organization rather than a bolted-on tool.
Where it fits
Employee IT Requests
Staff browse their entitled catalog, raise an access or hardware request, see the SLA and approval applied automatically, and track it to delivery.
Self-Service Resolution
A user searches the knowledge base for a password or VPN issue, applies a suggested solution, and never needs to open a ticket.
Asset Custody & Fault Logging
An employee reviews assets assigned to them in the CMDB, accepts custody of a new laptop, and logs a fault against an existing device directly.
Approvals On The Move
A manager receives an approval routed from Request Management, reviews the record details and attachments in the mobile portal, and approves or rejects on the spot.
Common questions
Everything raised in the portal lands on ServiceCore's shared data model, so a request becomes the same record agents work in Request Management or Incident Management — no re-keying. Forms are tied to the Service Catalog, approvals come from Request Management and Change Enablement, knowledge and suggested solutions come from the Knowledge Base, and assets come from Asset Management and the CMDB, all surfaced in one user-facing view.
Part of these solutions
See Self-Service Portal in action.
Book a demo and we'll show self-service portal working alongside the rest of the platform — on one shared data model.