IT fixed Slack requests. HR is still digging through DMs.

In most companies running Foqal, IT is in good shape. Requests come in through #it-help, land with the right person, and get closed. When leadership asks what the team handled last month, IT has an answer.

Walk over to HR and the picture changes.

Benefits questions arrive by DM. Someone posts about their leave in a public channel because nobody told them where else to go. Finance has a help channel that one person checks between meetings. Legal gets pinged directly and keeps track in their heads.

The work gets done. Most of the time anyway. But often, none of it shows up anywhere. That's invisible work, and it's happening one department over from a setup that already solved it.

Every team that handles requests has a queue, whether they call it that or not

A queue is the place where a team's requests wait for someone to own them. Service teams have worked this way for decades. Requests come in, get sorted, get assigned, and get worked.

In Slack, the queue is usually a channel. Slack's own guidance recommends dedicated triage channels and suggests making them public, so the whole company can see what's pending and what's been resolved.

For IT, that's great advice. For HR, it's a nonstarter.

Why the second team waits

An employee's question about medical leave can't sit in a channel the whole company reads. A performance issue can't land where the IT team can see it. So HR does the reasonable thing and keeps everything in DMs. That keeps it private. It also means nothing is tracked.

Foqal queues remove that tradeoff. Each queue has its own members, and only those members can see its requests. That includes Foqal admins. IT sees IT's work, and HR sees HR's. Sensitive requests stay private, and the record still exists.

What adding a team looks like

For employees, nothing changes. They keep asking in Slack or Microsoft Teams, wherever they already ask.

Behind the scenes, HR gets its own queue. Their channels route into it, and so does email sent to their team address. Direct messages get sorted too. Your company has one Foqal bot, so Foqal reads each DM, works out whether it's an IT question or an HR one, and sends it to the right team. Nobody has to know the org chart to get help.

Some work belongs to more than one team. Onboarding needs IT for the laptop and HR for everything else. Offboarding needs someone to actually shut off access. You can build a queue with people from both teams, so they share that work without sharing everything else.

The second team usually asks for it

It rarely starts with a sales pitch. Someone on another team sees how IT handles requests and asks how to get the same thing. Funnel started by rethinking how support worked and now runs six internal teams on Foqal, from Finance to Security. DonorsChoose runs Customer Support, HR, and IT on the same platform. Different companies, same progression. One team proves it works, and the next one wants in.

"Won't more teams make it messier?"

Usually it's the opposite.

Each team sets its own rules. HR can spread requests evenly across its generalists. IT can keep on-call agents in rotation while managers watch without getting assigned. When a request lands with the wrong team, they transfer it, and ownership moves with it. Nobody forwards a screenshot and hopes someone picks it up.

Cost stays predictable too. Foqal prices per agent, so adding HR means paying for HR's agents. The employees asking questions don't count.

Where to start

Pick the team closest to breaking. It's usually HR or Finance, the team with the most DMs and the least visibility.

Give them one queue and one channel. Check back in two weeks.

Your IT team already proved this works. Let the next team see it.

Ready to set up your next team? Start with our Queues guide, or reach out to your Foqal contact and we'll help you plan the rollout.