> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Run Internal Requests Across Departments
- URL: https://blog.jestor.com/internal-requests-across-departments/
- Published: 2026-09-17T22:31:24.000Z
- Updated: 2026-09-17T22:31:24.000Z
- Author: Bruno Bannach

**Internal requests across departments** — facilities, IT, HR — share the same shape: someone needs something, someone else has to do it, and both need to know where it stands.

## Why internal service goes unmeasured

External support usually gets a system. Internal requests rarely do, despite comparable volume.

- Requests arriving by message to whoever is nearest
- No standard format, so every request needs follow-up questions
- Requesters with no way to check status
- No data on how long internal service actually takes

## One pipeline or several?

| Approach                         | When it fits                                                |
| -------------------------------- | ----------------------------------------------------------- |
| **One pipeline, category field** | Small teams, where the same people handle most types        |
| **Separate pipelines per area**  | Distinct teams with different phases and SLAs               |
| **One intake, routed**           | Requesters use one form; routing sends it to the right area |

## How to set it up in Jestor

1. Build one request form in **Jestor** with a category field and conditional questions per type.
2. Route submissions to the right pipeline based on the category chosen.
3. Add the native email address so requests can also arrive by email.
4. Enable **SLA** tracking so time per phase is captured automatically.
5. Give requesters permission to see only their own requests.

## Why choose Jestor for internal service desk?

**Jestor** covers Service Desk as a solution area, but the components — forms, boards, SLA, agents, dashboards — are the same ones used everywhere else, so there is no special case to maintain.

An **AI** agent can handle the repetitive requests end to end, classifying, answering, and closing them, which is usually most of the volume in internal service.

## Frequently Asked Questions

### Can one form serve several departments?

Yes, with a category field and conditional routing. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can requesters check their own status?

Yes, with permissions scoped to their records.

### Can AI handle routine requests?

Yes, an agent can answer, classify, and close them.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.