To set up an internal ticketing system, give IT, HR and facilities one address each, forward those addresses into a help desk, and let rules send every request to the right team. Then add the login employees already use, a form that asks what each team needs to know, and answers to the questions you get every week.
Below is the order we'd do it in, for a company where requests reach IT, HR and facilities by email and by someone stopping at a desk. The examples use Cayzu, and our internal help desk software page covers what Cayzu does for IT teams.
Decide what counts as a ticket
Start on paper. A ticket is any request where someone is waiting on someone else, and where you'd want a record later. A password reset counts. So do a new starter's laptop, a broken chair, a payroll question and a lost badge.
A quick "is the second-floor printer working?" in the hallway doesn't have to be a ticket. But if the answer is "no, I'll fix it," it should become one, so the fix has an owner and a date.
Write down the requests each team gets most often. You'll use that list three more times: for the forms, the rules and the knowledge base.
Give each team one address
Employees need one obvious place per team: helpdesk@ for IT, hr@ for HR, facilities@ for the building. Forward each one to Cayzu and every email to it becomes a ticket, with the subject as the title and the sender as the requester. Replies go back from the same address, so nothing looks different to the person who asked.
The portal is the second way in. Employees sign in, send a request through a form, and check where it stands without emailing to ask.
If those addresses are a shared Gmail inbox today, you don't have to give the address up. We cover what changes in switching from Gmail to a help desk.
Make a group for IT, HR and facilities
A group is a team that tickets go to, instead of a person. Make a group each for IT, HR and facilities, add the right people, and write a rule that sends each address to its group. If the usual IT person is out, the other one sees the ticket. One person can sit in two groups, which helps when the office manager covers facilities and some of HR.
HR needs one more step, because most HR tickets are private. Groups don't keep tickets private on their own. By default, agents can see and open tickets in every group. On every plan, the ticket access scope setting can limit an agent to their own groups' tickets, so someone in IT can't open an HR case. Private notes help too: your team can talk about a case on the ticket, and the employee never sees it. Our HR help desk software page goes through the HR side in more detail.
If one person covers IT and HR anyway, that may not matter to you. Decide whether it does before HR's first ticket arrives.
Let employees sign in with their work login
If the help desk needs its own password, people will just email you instead. Single sign-on lets employees in with the login they already use, and the setup depends on where that login lives.
If your directory is Active Directory on your own servers, Cayzu connects to it with a short script on a web server of yours, usually IIS. You'll need someone who can put a script on a server, so line them up first. The Active Directory page covers what happens when people join and leave.
If you sign in through Microsoft Entra, Okta or Google Workspace, Cayzu's SAML 2.0 single sign-on has been tested with all three. You choose whether it's for your agents or for the employees using the portal. Single sign-on is on Pro and Enterprise.
Build a request form for each team
A form asks up front for what people forget to say. With custom ticket fields, each team gets its own form. For example:
- IT: which device, what's wrong, and how many people it affects.
- HR: the type of request, and the dates for a leave request.
- Facilities: the floor or room, and what's broken.
Fields can be dropdowns, checkboxes, numbers or text, and each one can be required or optional. Keep each form to five or six questions, and only require the ones you can't work without.
One limit. Fields show on the portal form and the web widget, not in an email, so a ticket sent to helpdesk@ arrives with empty fields until someone fills them in. Custom fields and multiple forms are on Pro.
Set assignment rules and response times
Rules sort tickets before anyone reads them. If it came through hr@, send it to HR. If the facilities form says "Leak," set the priority to urgent. A rule can look at who sent the ticket, which address it came to, what the subject says or what they picked on the form. Then it sends the ticket to the right team and sets how urgent it is. We'd start with one rule per address and add more when you catch yourself sorting by hand.
Turn on the auto-reply too. Every employee gets a ticket number back, and the "did anyone see my email?" follow-ups stop.
Then put a clock on it. SLAs set a response and a resolution target for each priority. Set your business hours so the clock only runs while you're open. Our guide to help desk SLAs covers business hours and holidays in more detail.
A common starting point is one business hour for urgent, four for high, one business day for normal and two for low. Start loose and tighten the ones you beat. SLAs and business hours are on Pro and Enterprise.
Write answers to the ten questions you get most
Go back to your list from the first step. The questions that come in every week belong in the knowledge base: how to connect to the VPN, how to book time off, where to report a broken light. Employees search it in the portal before they send a request, and your team can answer with a link instead of a paragraph.
Private articles stay agent-only. That's where your team's own steps go, like how to set up a new starter's accounts.
Tell employees how to ask
Send one short message, from someone people listen to. Say where each kind of request goes, how to sign in, and what happens next. Something like this:
Starting Monday, send IT requests to helpdesk@, HR questions to hr@, and anything about the building to facilities@. You can also use the help portal with your usual login. You'll get a ticket number back right away, and you can check on your request in the portal.
Then hold the line, kindly. When someone asks in the hallway or in a chat message, help if it's quick, and ask them to send it in so it's on record. It'll feel stiff for a while, but it's the only way hallway requests show up in the numbers.
Check the numbers after a month
A month gives you enough tickets to learn from. In Cayzu's reports, start with first response time, past-due tickets and the SLA report, which shows which tickets met their targets and which missed.
Then read the tickets. A question that came in five times needs an article. A ticket you still move by hand is a rule you haven't written. Tighten the targets you beat easily, and loosen the ones nobody could hit.
What it costs, and when you don't need one yet
Cayzu has no free plan. You pay for agents, the people who answer tickets. Employees who send requests cost nothing. Plans run $19 to $65 per agent per month billed yearly, or $24 to $79 billed monthly. Standard covers the addresses, groups, rules, portal and knowledge base. Pro adds single sign-on, custom forms and SLAs, which is most of this setup. Keeping HR tickets private doesn't need a bigger plan, because the ticket access scope setting is on every plan.
If IT is one person and the requests are a handful a week, you may not need any of this yet. A shared inbox will do. You need it the first time a request gets lost between two people, or HR needs a place IT can't read.
If you'd like to try this setup with your own requests, Cayzu's 15-day free trial has every feature, roles included, and needs no card.