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
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 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
Table of Contents
- All Categories
- Getting Started with DeskDirector
- How Searching Works
How Searching Works
Updated
by Niamh Ferns
How Searching Works in DeskDirector
In all products DeskDirector has created, we use full-text search for all list interfaces. Compared to traditional approaches that check whether an item contains or starts with a search term, full-text searching provide better flexibility and an overall cleaner user experience.
For more info regarding this technology, you can check out this Wikipedia page.
How do indexing and tokenisation work?
For each collection, we will mark a few properties as query fields (for example, the name, description, or content). The information within will be tokenised and indexed by the database. When searching, we search based on tokens instead of a full sentence and will search against the tokenised query fields in the DeskDirector database.
Basic tokenisation splits information by spaces, special characters, and new lines. All tokens are case-insensitive.
Input string of text:
The quick brown fox jumped over the lazy dogs, Bob@hotmail.com 123432.
Output tokens:[quick] [brown] [fox] [jumped] [over] [lazy] [dog] [bob@hotmail.com] [123432]How does the system determine the most matched object?
When DeskDirector analyses search terms, it will tokenise the search string. It will match on two different criteria, and ones with the highest ratings will be returned near the top of your results.
- Any token that's exactly matched will give a rating of 2
- Any token that starts with the search term will give a rating of 1.
- A repeat match will increase its total rating.
For example, we have two users with the following names.
Jamison Knight / jknight@example.com from Euro Health CenterJamison Coon / jamison@secondcompany.com from Europtimum
Scenario:
Search term: Euro Jamison will give a rating of 4 for Jamison Knight and a rating of 3 for Jamison Coon. Since Jamison Coon only has a starts-with match with Europtimum, while Jamison Knight has an exact match with Euro.
What kind of terms can we use for different collections?
DeskDirector has put a lot of effort into analysing the important fields that should be included in inside the index. I will summarise them below.
- Company / Account: name, identifier
- Contact: first name, last name, primary email, secondary emails, title, email domain.
- Member / Resource: first name, last name, primary email, secondary emails, identifier
- Ticket: title, initial description, identifier
Frequently Asked Questions
"How many terms can we include in a search?"
Same as many other full-text search implementations. You can include as many terms as you like. You can even type in a full sentence.
"Why can't we add sorting to the search results?"
Sorting of search results will often lead to confusion and unexpected results. For example, if sorting results by text, then higher-rated results could end up on page 2 or 4.
This is also why services like Google don't allow sorting.
"When I search contacts, there are results from different companies. How do I improve accuracy?"
You can add an email as an addition to an existing search term, or you can also add a company filter. That way, only contact from that company will be returned.
"How come there are many false positives?"
Full-text searching is likely to retrieve many documents that are not relevant to the intended search question. Such documents are called false positives. They often appear at the end of search results, where they are partially matched with search terms.