How do I set up a dispatcher's computer so they only see the tools they actually need?

This page may contain affiliate links from which Blur Studio earns commissions.

Dispatch and front-line office roles benefit from a genuinely simple screen more than almost any other role: under time pressure, every extra icon or bookmark is a half-second of searching that adds up across a busy day, and a cluttered setup makes it easier to click the wrong tool entirely.

Why a bookmark folder is only a partial fix

A dedicated bookmark folder for dispatch tools is the obvious free step, and it genuinely narrows down the choices compared to a dispatcher's full bookmark bar. The limitation is that a bookmark folder is still a list you open and scan through, inside a browser that also has everything else in it, every other tab, every other bookmark folder, visible just one click away. It reduces the clutter without actually removing it from view.

How a dedicated space changes this

WebCatalog's Spaces feature groups a specific set of apps into their own named context, so a dispatcher's whole screen can be set to exactly the tools their role uses: a scheduling or job board, a map, a messaging tool, nothing else. Rather than narrowing a list down, it removes everything that isn't part of that space from view entirely while that space is active. For an individual setup, this is covered once you're past the free Basic plan's single space, with Pro giving unlimited spaces for $5 a month billed annually.

Where this genuinely matters for a role like dispatch is consistency across shifts and across staff. If three different dispatchers work different shifts on the same computer, a shared, standard space (available on the Business plan, $8 per user a month billed annually) means every one of them sees the exact same, deliberately limited set of tools, rather than each building their own slightly different version of "the dispatch screen." Alerts matter here too: see how toget alerts from web apps when the browser is closed.

How to set this up

1. List only the tools dispatch genuinely needs minute to minute, not every tool the role might occasionally touch. The goal is a short, deliberate list, not a comprehensive one.
2. Build the dispatch space with exactly that list, resisting the urge to add "just in case" tools that dilute the focus this is meant to create.
3. If multiple dispatchers share one computer or need the same setup, move to the Business plan for shared spaces, so the standard is set once rather than rebuilt per shift. Rollout to a whole team is covered ingetting every new hire into the same tools in one click.
4. Review the space after the first week of real use, since the first version is rarely exactly right; dispatchers will tell you fast if something essential is missing or something included is never actually used.
5. Keep anything genuinely occasional (a rarely-used report, an admin setting) out of the dispatch space entirely, even if that means a dispatcher has to ask someone else for it. That friction is intentional.

What I'd actually tell you

For a role like dispatch, where speed and reduced decision-making under pressure genuinely matter, a deliberately limited screen is worth setting up properly, and the cost ($5 to $8 a month depending on whether you need shared team spaces) is trivial against the time saved across a busy team over a year. I'd treat the "what belongs on this screen" decision as the real work here, not the technical setup, which takes minutes once you've actually decided.

One thing I couldn't fully confirm in detail: exactly how Business's shared, team-level spaces are configured and kept in sync across multiple logins isn't something WebCatalog documents in full public detail. If you're rolling this out across several dispatchers on the Business plan, confirm the specific sharing mechanics directly with WebCatalog before assuming it works a particular way.

A worked example: a two-person dispatch desk covering 20 field technicians

Say a home-services company runs a two-person dispatch desk coordinating 20 field technicians across a metro area, and each dispatcher's computer, before this setup, had the scheduling tool, the mapping tool, the messaging app, but also inherited bookmarks for payroll, the company's internal wiki, a reporting dashboard, and a handful of other tools nobody on dispatch actually uses minute to minute, just because that's what the computer came preloaded with from a previous role. Under real pressure, during a storm surge with twenty customers calling at once, every one of those extra bookmarks is a half-second of visual noise competing with the three tools that actually matter in that moment. Stripping the dispatch space down to exactly the scheduling tool, the map and the messaging app, with everything else deliberately excluded, didn't add any new capability. What it removed was the small, repeated cost of scanning past things that don't matter, multiplied across dozens of job assignments during the busiest hours of the day, which is exactly when that half-second actually costs something. The phones can be set up withcalls routed to whoever is free.

Common mistakes when building a dispatch space

• Building the space around what dispatch might someday need, not what it needs today. A space with ten "just in case" apps isn't meaningfully better than the cluttered bookmark bar it replaced; the value comes specifically from leaving things out.
• Building the space without asking the actual dispatcher. Whoever's doing the job daily knows which tool actually gets used every ten minutes and which one was only ever touched once during onboarding. Skipping that input means guessing at a list that someone living in the role could have told you directly.
• Never revisiting it after the tools change. A dispatch space built around last year's scheduling tool, after the business has since switched systems, quietly becomes as cluttered and irrelevant as the thing it replaced, just with a smaller initial list.

A practical note on training a new dispatcher

A deliberately limited space has a side benefit worth naming: it doubles as a simple training tool. Handing a brand-new dispatcher a locked-down screen with exactly the three or four apps their job needs is a much clearer starting point than handing them the same unrestricted computer everyone else uses and trying to explain verbally which of the dozen open tabs actually matter. The space itself becomes a kind of job description, showing rather than telling a new hire what their role actually touches day to day, and it means a first week of training spends less time on "which tool is this" and more on the actual judgment calls dispatch requires. For new people, see how toset up work apps on a new hire's computer.

When should you skip this?

If your dispatch role is genuinely varied day to day, needing different tools depending on the job type, a rigid, fixed space might feel more restrictive than helpful. In that case a well-organized bookmark folder, which is easier to add to on the fly, might actually serve a varied role better than a locked-down space built for a narrower, more repetitive job.

How I'd approach this

For a genuinely repetitive dispatch role, WebCatalog's Spaces is a quick, cheap way to build a deliberately simple screen. Where I get involved is when dispatch needs more than a simplified view of existing tools, say, a single screen that actually pulls job status, driver location and customer messages into one dashboard rather than three separate apps sitting in one space. That's a bigger, custom build, and it's worth considering once "fewer apps on screen" has stopped being enough and the real ask is "one screen that shows everything dispatch needs at a glance."