Requests and the employee portal
Employees file requests from the portal or by email, on a form you design for each kind of request. Agents work every request from one shared queue.
A form for each kind of request
Each request type has its own form. A laptop request asks for the model and cost center, and an access request asks for the system and the reason.
- Text, long text, select, multi-select, checkbox, date and file fields, each optional or required
- The request type decides which team receives the request
- Each type also sets whether approval is needed and whether the request can be confidential
- The REST API can create requests too, including their field values
The employee portal
The portal lists your teams and the requests each one handles. Employees pick a type, set the urgency and review the request before they submit it. Afterwards they follow it from the same portal, reply to the agent and confirm the resolution.
- Suggested knowledge base articles before a request is filed
- Email intake: each email a member sends to your workspace's address becomes a request
- With Evee turned on, employees can ask a question first and get an answer that cites articles
The agent queue
Agents open a request beside the list without losing their place in it. They filter by team, status, priority, assignee, SLA risk and more, and saved views keep the filters each person uses.
- Bulk changes to status, assignee, team or tags
- Export the filtered queue to CSV
- Keyboard shortcuts: J and K to move, Enter to open, X to select, R to reply and N for an internal note
- At-risk and breached requests are marked in the list
Replies, notes and history
Public replies go to the requester, and internal notes stay with the desk. The request's history shows every status change with who made it and when, and the audit log keeps the same record.
- @mentions and watchers
- Attachments scanned for malware before they are stored
- Macros and knowledge base links from the reply composer
- Time logged against a request, with a note
More in Requests and portal
Confidential requests
A request type can be always confidential or let the requester choose. A confidential request opens only for the team it is routed to and the people on it: the requester, assignee, watchers and approvers. You can grant access to other people or teams.
Change requests
A request type can collect change details such as the risk, the maintenance window and the rollback plan, and classify each change as standard, normal or emergency. The Changes calendar lists scheduled windows and flags overlaps.
Links and merging
Link requests as related, blocking or duplicates, and merge two requests into one. When the two requesters differ, the merged conversation is kept as internal notes.
Slack and Microsoft Teams
Post request updates to a channel. In Slack, replies in a request's thread are added to the request as comments. Confidential requests are never posted.
Teams and routing
Limit a role to the teams it serves. New requests can be assigned round-robin or to the least busy agent, passing over agents who are busy or offline.
Included in every plan.See pricing →
Questions about Requests and portal
- Do employees who file requests need a paid seat?
- No. Requesters are free and unlimited. You pay for agents, the people who work requests, and the first 3 agents are free.
- Can employees send requests by email?
- Yes. Each workspace gets its own address. Forward your support mailbox to it, and each email from an active member of your workspace becomes a request. Replies to a request's emails are added to that request.
- Can HR requests be kept away from the IT team?
- Yes. Set the HR request types to always confidential and route them to the HR team. Only that team, the requester and the people on the request can open them.
- Can we bring our existing tickets?
- Yes. Import a CSV export from any tool, or connect Zendesk, Freshdesk or Jira Service Management and bring over tickets with their conversations, dates and requesters. The migration page has the details.
- Is there a mobile app?
- Not a native one. EvenTier runs in a phone browser, where the queue switches to a list, so agents can reply and approvers can decide from their phones.
Documentation
- Request lifecycleHow a request is created, triaged, worked, and closed. Covers the seven states, custom fields, watchers, links, attachments, and the audit history.
- Requests by emailForward your support mailbox to your workspace's email address, and each email from a member becomes a request. Replies by email continue the same request.
- Teams & routingSet up several teams, limit roles to certain teams, and assign new requests automatically by workload or in turn. Assignment looks at who is online, and service level agreement (SLA) rules can escalate work to another team.
- MacrosReusable reply templates that fill in details such as the requester's name. Insert them from the agent reply composer to keep answers consistent.
- IntegrationsPost request updates to Slack and Microsoft Teams, send signed webhooks, store attachments in S3-compatible storage with ClamAV scanning, and use the REST API.
Related
- ApprovalsOne approver or an ordered chain, with delegation
- SLAsResponse and resolution targets on business hours
- AutomationsIf and Else rules on a drag-and-drop canvas
- Knowledge baseReviewed articles that answer questions before a ticket
- Internal IT help deskIntake, routing, SLAs, approvals, assets, and audit for the team that fields hardware and access requests.
- Employee request managementOne portal for IT, HR, finance, and facilities requests, with per-department forms, routing, approvals, and SLAs.
Try it with your own data
Create a workspace and set it up with your own teams, request types and settings.



