Skip to content

Employee request management

Employee request management for every department

Employees submit every request from one branded portal. Each team keeps its own request types, forms, approvals, and service level agreements (SLAs). Requests go to the department that owns them, and requesters can follow the status from submission to resolution.

How employee request management works

Each department publishes its own request types, forms, and approvals. Every request goes to the team that owns it. All teams share one portal, one audit log, and one subscription.

One portal for every department

IT, HR, finance, and facilities each publish their own request types in one branded portal. An employee chooses the service they need and fills in that team's form. Requests from the portal and the REST API go into the same queue.

  • Custom request types per department, with per-type fields and validation
  • Branded portal with your colors, logo, and banner
  • REST API requests go into the same queue

Forms and routing

Each request type has its own fields, validation, and routing. When a form is submitted, automation rules read the request type and its content and assign the request to the team that owns it. No one has to dispatch requests by hand.

  • Per-type fields and required-field validation at intake
  • Keyword automation rules assign requests on submission
  • Team queues with workload-aware assignment to the least busy agent

Permissions and confidentiality

Custom roles are built from 24 permission keys, and each agent can be limited to their own team's queue. Set a request type to always confidential and its requests are visible only to the team they are routed to, the requester, the assignee, approvers, and people who have been granted access.

  • Custom roles built from 24 permission keys
  • Per-agent team scoping and always-confidential request types for HR
  • Internal notes hidden from requesters, and every change recorded in the audit log

Approvals and reassignment between teams

Purchases, access changes, and policy exceptions go to a named approver before work starts, and approvers can delegate while they are out of office. When a request needs another team, reassign it; the request keeps its history and comments. The approval workflows page describes approvals in full.

  • Approval requirements set per request type, with out-of-office delegation
  • Reassignment across teams keeps the request's history and thread
  • Approval decisions trigger automation rules

Request tracking and notifications

Requesters see the status of each request in the portal and receive a notification on every change. Watchers let managers and other stakeholders follow a request without being copied on email.

  • Request status visible to the requester in the portal
  • Watchers and notifications on status changes
  • Public replies and internal notes kept separate

Audit history and reporting

Every status change is recorded with who made it, when, and the previous status. Per-team SLA and resolution reports show each department how its queue is performing.

  • Full status history with the user who made each change
  • Per-team SLA and resolution reporting
  • Backlog and mean time to resolution reports

Frequently asked questions

Do employees need a paid seat?

No. Requesters are unlimited and free. Every employee can submit and track requests. You pay only for agents, the people who resolve them.

Can each department have its own forms?

Yes. Request types are defined in your workspace, each with its own custom fields, required-field validation, and approval requirements. An HR onboarding form can ask for different information than an IT access request.

Can HR requests be hidden from other teams?

Yes. You can limit each agent to their own team's queue. A request type set to always confidential keeps its requests visible only to the team they are routed to, the requester, the assignee, approvers, and people who have been granted access.

Where do employees submit requests?

In the branded employee portal, or from any system connected to the REST API. Both create the same kind of request and follow the same routing rules.

Get notified when signup opens.

EvenTier is in private early access. Leave your work email and we will let you know when you can create a workspace.

No card. We use your email only for your early-access invite and launch news. Privacy Policy