Service Desk & Request Portal

A Service Desk & Request Portal is one system where users submit and track service requests and teams manage the tickets, workflows, and fulfillment behind them. The portal side gives requesters forms and status; the service desk side gives agents queues, assignments, and approvals. In SmartSuite both sides read the same request record, so a request moves from intake to resolution in one flow without a second system in between. The organization gets one queue to manage and one place to measure.

Tickets and service requests are records in the same tables, distinguished by type and handled by the same routing, assignment, and status workflow. An agent sees incidents, requests, and tasks in one queue and works them with the same tools. Reporting covers all of them together, so service performance is measured once rather than per tool.

Submitting a request through the portal creates a record and starts an automation that routes it, requests any approval, and creates the fulfillment tasks for the responsible team. Each task carries its own owner and due date, and the request closes when the tasks complete. Requesters watch each step from the portal while agents work from their queue.

Yes. Each service can have its own routing rules, approval chain, notifications, and escalation steps, defined as automations on the request table. A software access request can require a manager approval while a password reset routes straight to the service desk. Changing an automation changes the workflow for the next request, with no deployment.

HR, finance, facilities, and legal teams can run their own services on the same platform, each with its own forms, approvers, and fulfillment team. Requesters see one portal, filtered by permissions to the services they can use. Each department reports on its own volumes and times from the shared tables.

Response and resolution targets are set by service type, priority, or user group on the request table. Formula fields compute the due date and time remaining for each request, and automations notify the owner or escalate when a target is near or missed. Dashboards show on-time rates by team, so leads can see where commitments slip.

Yes. Knowledge Management articles are linked to services and shown in the portal, so a user can read the fix before opening a ticket. Articles are searchable from the portal and from the request form. Ticket volume for common questions falls, and agents attach the same articles when they resolve a request.

Large organizations run many teams, departments, and locations in one workspace, with permissions deciding who sees which requests. Automations handle routing and escalation at volume, and dashboards give leaders workload and trend views by team. Adding a department means adding its services, forms, and approvers, not another tool.