Getting Started with DeskDirector
DeskDirector Portals
Browser Support
What is the DeskDirector Admin Portal?
What is the DeskDirector TECH Portal?
What is the DeskDirector Client Portal?
Desktop Portal
Managing Your Account
Pricing & Subscription Plans
Deskdirector - Sign up walk through
Managing your DeskDirector Subscription
Admin Essentials
Release Notes
Permissions & Feature Configuration (ConnectWise/Autotask Partners)
Automatic Contact Creation
The Developer Corner
DeskDirector Features Overview
Logging in to DeskDirector
Desktop Portal Version Differences
Managing Tickets with DeskDirector
User Profiles & Profile Pictures
Office Hours
How Searching Works
Embedding Help Page Media
Get started with the DeskDirector Power Automate Connector
Featured Solution: Teams Ticket Discussion
Features
Portal Customization
Service Catalogue
Service Catalogue Strategy
Service Catalogue Setup: Choose Your Path
Why a Small Service Catalogue Works Better
Quick Setup: Service Groups for Teams With Limited Time
Advanced Catalogue Model: Proactive, Reactive and Automated
Build a Small, High-Value Service Catalogue
Capture Requests the Catalogue Misses With Inline Forms
Use AI Categorisation Instead of Setup-Only Service Types
Monthly Service Catalogue Review Checklist
Automate Service Group Creation for Each Contact or Company
Contact Groups: Shared Tickets for Teams
Forms
Communication
Actionable Messages for Emails
Real-Time Chats
Notifications
Email Notifications
Email Template Engine
Surveys
Broadcasts
Generative AI
Ticket Summary for TECH Portal
DeskDirector with Generative AI
Setting up AI Service Providers
AI Assistants in DeskDirector
Custom Tools for AI Assistants
Knowledge Bases for AI Assistants
Set up Microsoft Foundry Agent Service with DeskDirector Portals
Advanced
Login & Authentication
Contact Groups
Accounts and Companies
Contacts
Approvals
Task Lists
The Learning Center
Tags
Custom Domains
File Storage
Portal Deep Linking
Service Dashboard
Auditing and Analytics
Integrations
ConnectWise
ConnectWise Custom Menu Item for DeskDirector Tech Portal
ConnectWise
ConnectWise Quotes & Invoices
ConnectBooster
ConnectWise - Avoid Aggressive Notifications
AutoTask
Switching or Merging PSAs
QuoteWerks
Wise-Pay
TimeZest
BiggerBrains
OneNote Notebooks
Integrations - Frequently Asked Questions
IT Glue
Microsoft Teams App
Featured Solution: Ticket Briefing
Introducing the DeskDirector for Microsoft Team App
Installing the Microsoft Teams App (Client Mode)
Installing the Microsoft Teams App (TECH Mode)
Setting up Tags for Teams Discussions (TECH Portal)
Branding the DeskDirector Teams App
DeskDirector Teams App Notifications
User Groups Integration with Microsoft Teams
Setting up Content Security Policy (CSP)
Advanced topic: Setting up Tech & Client Mode in the same tenancy
Integrating Microsoft Teams with DeskDirector Tech Portal
Smart Alerts for TECH Users
Microsoft Power Automate
Actions
Solutions
Power Automate Administration
Power Automate Connector - Setting up your first flow
DeskDirector Power Platform Connector Reference
Troubleshooting
Troubleshooting via Web Developer Tools
Diagnose Entities Tool
Troubleshooting DeskDirector Connection Issues
Permissions & Access - Common Issues
Tickets & Chats - Common Issues
ConnectWise Audit Trail - Exporting API Logs
Contact DeskDirector Support
Desktop Portal - Common Issues
Contact Impersonation
DeskDirector Desktop App - Installation Issues
Login & Authentication - Common Issues
Approvals - Common Issues
Email & Email Delivery - Common Issues
PSA Entity Syncing - Common Issues
PSA Integration - Common Issues
ConnectWise Integration - Common Issues
Autotask Integration - Common Issues
Microsoft Teams App - Common Issues
Security
Glossary
Archived
- All Categories
- Features
- Service Catalogue Strategy
- Quick Setup: Service Groups for Teams With Limited Time
Quick Setup: Service Groups for Teams With Limited Time
Updated
by Jason He
You don't need a complex setup to get a useful service catalogue. This article shows a quick way to set one up that works for most companies and takes little effort to maintain.
The short version
- Create one generic service group and assign it at the global level.
- Use 3 to 5 categories to organise your service types.
- Put about 5 service types in each category.
- Keep the total under 25. Under 10 is even better.
- Spend a little time looking at past tickets before you create anything.
Why keep it short
Contacts are often in a hurry when they ask for help. A short list is quick to scan, and a quick choice leads to a created ticket. A long list slows people down, and they may pick the wrong type or send an email instead.
For more detail, see Why a Small Service Catalogue Works Better.
Step 1: Look at your history first
Even a quick setup works better when it reflects what your customers really ask for. Set aside a short time to study your past tickets.
Look at the last 3 months of tickets and ask:
- What is requested most often? Examples: password resets, new user requests, software requests.
- What needs attention quickly? Examples: urgent issues, outages, security concerns.
- What do customers struggle to describe? These requests may need a clear service type name.
Don't try to cover everything. Pick the requests that are most common or most important. You can always add more later.
Step 2: Choose 3 to 5 categories
A category groups related service types. It keeps the first screen short, because contacts see the categories first and open only the one they need.
Choose categories that match how your customers think about their problems. Here is an example:
Category | Example service types |
Get Help | Urgent issue, Computer problem, Printer problem, Email or spam problem, Something else |
New or Changed Access | New user, Remove user, Change access, Password or account help |
Software and Equipment | Install software, Request new equipment, Software licence question |
Questions and Changes | General question, Report a problem with a service, Request a change |
These names are examples. Use words your customers already use, and avoid internal terms they won't recognise.
Step 3: Create the service types
For each category, create about 5 service types. Follow these rules:
- Use clear, plain names. "Printer problem" is better than "Peripheral incident".
- Include a general option. "Something else" gives contacts a safe choice when nothing fits.
- Keep forms short. Ask only what you need to start the work. You can collect more details after the ticket is created.
- Skip the form if you can. A subject and description is often enough.
How many is too many?
Total service types | Result |
Under 10 | Best. Easy to scan at a glance. |
10 to 25 | Good. Categories keep it manageable. |
Over 25 | Possible, but the experience gets worse. Contacts take longer to find what they need. |
You can go over these numbers. Just be aware that each extra service type makes the catalogue harder to use.
Step 4: Create one service group
- Create a service group, for example "Standard Catalogue".
- Add your service types to it.
- Assign the service group at the global level.
Every company and contact now sees the same list. There is nothing more to set up for each customer.
Step 5: Adjust over time
A quick setup is a good starting point, not the end. Once a month, or every few months, do a short check:
- Which service types are never used? Remove them.
- Which requests keep coming in without a matching service type? Add one.
- Is any form too long? Cut the questions you don't need.
For a more detailed routine, see Monthly Service Catalogue Review Checklist.
When this setup is not enough
This setup works well for most teams. Consider a more detailed approach if:
- A few companies need very different services from the rest.
- You have a dedicated customer success person and time to review each month.
In that case, see Service Catalogue Setup: Choose Your Path for other options.