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
Admin Essentials
DeskDirector Features Overview
Logging in to DeskDirector
User Profiles & Profile Pictures
Managing Tickets with DeskDirector
Office Hours
Getting Started with the Solution Library
How Searching Works
Embedding Help Page Media
Get started with the DeskDirector Power Automate Connector
Features
Portal Customization
Forms
Service Catalogue
Service Catalogue Strategy
Service Catalogue Setup: Choose Your Path
Why a Small Service Catalogue Works Better
Service Groups Explained: Controlling What Contacts See
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 Account
Contact Groups: Shared Tickets for Teams
Communication
Email Connectors
Notifications
Email Notifications
Actionable Messages for Emails
Real-Time Chats
Email Template Engine
Surveys
Broadcasts
Generative AI
DeskDirector with Generative AI
Ticket Summary for TECH Portal
Setting up AI Service Providers
Microsoft Foundry for DeskDirector
Knowledge Bases for AI Assistants
Custom Tools for AI Assistants
AI Assistants in DeskDirector
Advanced
Login & Authentication
Contact Groups
Custom Domains
File Storage
Dashboard
Accounts
Contacts
Approvals
Tags
Task Lists
The Learning Center
Portal Deep Linking
Auditing & Analytics
Microsoft Power Automate
Actions
Solutions
Featured Solution: Teams Ticket Discussion
Power Automate Template Gallery
Featured Solution: Ticket Briefing
Power Automate Administration
DeskDirector Power Platform Connector Reference
Power Automate Connector - Setting up your first flow
Microsoft Teams App
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
Contact 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
Integrations
Developer Resources
Getting Started
What is the Toki Iti API
API Versions & Routes
Roles & Scopes
Authorization Options
Querying the API
How to Change an Entity Through the API
API Key Authorization
OAuth Fundamentals
Understanding OAuth for Tokity Integrations: Key Concepts
OAuth Authorization Code Flow: How an App Gets Access to Tokity
OAuth App Registration
How to Register an OAuth App to Integrate with Tokity
Choosing an OAuth App Type: Confidential vs. Public Apps and Client Secrets
OAuth Personal Secrets: What They Are and When to Use Them
OAuth Administration
Configuring OAuth Settings in Tokity
Managing OAuth Authorized Sessions and User Consent
Granting OAuth Admin Consent at the Root Level
API Response Control
Uploading Attachments (Ticket API)
The Prefer Header — Overview
Controlling Returned Data (Ticket API)
Controlling Returned Data (Form Result API)
Controlling Returned Data (Workspace API)
Workspace Ordering
How Workspace Ordering Works
Creating and Reordering Workspace Groups
Adding and Reordering Tickets in a Workspace Group
Data Sync & Notifications
Delta API: Tracking Changes Over Time
Webhooks vs. Events — Differences, When to Use Which
Verifying Webhook and Event Payloads (HMAC Signature)
Ticket Widgets
Ticket Widget: Overview
How the Widget Is Requested
Ticket Widget Anatomy and Styling
Ticket Widget Actions: Leading, Secondary and Primary
Ticket Widget: Progress Type
Ticket Widget: List Type
Ticket Widget: Description Type
Ticket Widget: Form Type
Ticket Widget: Control When a Widget Refreshes
Ticket Widget: Form Results and State Across Steps
Ticket Widget: Error Responses and Debugging
Ticket Widget: Building a Multi-Step Request
Glossary
Security
Troubleshooting
Troubleshooting via Web Developer Tools
Permissions & Access - Common Issues
Contact DeskDirector Support
Troubleshooting DeskDirector Connection Issues
Desktop Portal - Common Issues
Contact Impersonation
Approvals - Common Issues
Microsoft Teams App - Common Issues
Email & Email Delivery - Common Issues
Login & Authentication - Common Issues
DeskDirector Desktop App - Installation Issues
Table of Contents
- All Categories
- Features
- Service Catalogue Strategy
- Service Catalogue Setup: Choose Your Path
Service Catalogue Setup: Choose Your Path
Updated
by Helpdocs Admin
The service catalogue is where contacts choose the kind of request they want to make. How you set it up depends on your time, your team and your customers. This page helps you choose a path and go straight to the right article.
Not sure where to start?
Start with Quick Setup. Move to the Advanced Model when you have time to review the catalogue every month.
Choose your path
Path | Who it suits | Effort | Why use it |
1. Quick Setup | Teams with limited time who want it working soon | Low. One-time setup, little upkeep. | One short, generic catalogue that suits most accounts. |
2. Advanced Model | Teams with a dedicated customer success person and time for a monthly review | Higher. Setup plus a monthly review. | A small catalogue, AI-attached forms and AI sorting of every ticket. The most value from each ticket. |
3. Automated Service Groups | Teams that want a unique catalogue per contact or account, and have automation skills | High at the start, then ongoing upkeep. | Removes manual group creation. Not recommended for most teams. |
4. Contact Groups | Teams whose users share tickets, such as shifts or departments | Low. Decide who belongs to which group. | Shared ticket ownership. Explains the "for me or for a group" question. |
Path 1: Quick Setup
Create one generic service group, assign it at the global level, and organise it into 3 to 5 categories. Keep the total under 25 service types, and under 10 if you can. Spend a little time looking at past tickets first, so you create the service types people really need.
Go to: Quick Setup: Service Groups for Teams With Limited Time
Path 2: Advanced Model
Combine three parts:
- Proactive: a small catalogue of 5 to 10 high-value service types.
- Reactive: AI attaches a predefined or disposable form after the ticket is created, only when needed.
- Automated: AI sets tags, queue, status, category, priority and tier 1 agent, so service types don't have to.
A monthly review keeps all three working.
Go to: Advanced Catalogue Model: Proactive, Reactive and Automated
Related articles:
- 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
Path 3: Automated service groups
Some teams want a different catalogue for each contact or account. Tokity has a rich API, so you can use tags and automation to create and assign the service groups for you.
This is possible, but it is expensive and needs research. Every customer's situation is different, so there is no single right design. We recommend Path 1 or Path 2 instead. If your team finds the manual steps too much, this is usually more work, not less.
Go to: Automate Service Group Creation for Each Contact or Account
Path 4: Contact groups
Contact groups are different from the other three paths. They are not a way to set up the catalogue.
A contact group lets a team share tickets. Think of nurses on different shifts. A nurse on the morning shift creates a ticket, and a nurse on the night shift follows it up. The ticket belongs to the team, not to one person.
This is why the portal asks "for me or for a group" when you create a ticket from the landing page. The answer decides who owns the ticket and which service types you see. The same service type can appear in more than one group, so the portal can't guess.
You can assign a service group to a contact group. This is an extra feature for teams that need services of their own, such as HR. Contact groups are not designed to add service types for individuals.
Go to: Contact Groups: Shared Tickets for Teams
Want to know why?
- Why a Small Service Catalogue Works Better shows real data from service providers, and why short lists and short forms help contacts who are in a hurry.
- Service Groups Explained: Controlling What Contacts See explains how service groups are assigned at global, account and contact level, and why we designed them this way.