TeamSupport offers a powerful search tool which allows you to find Tickets, KB articles, Customers, and Contacts quickly. You can also perform advanced filters and sorting to better narrow down your search.

Field Definitions

  • Search Bar: Type your word or words into the search bar to return your results.
  • Tickets, KB, Customers, Contacts Buttons: Click the area of TeamSupport where you would like to search. The default is Tickets.
  • Results: Results are displayed with Ticket Number, Ticket Name, Date Created, Date Modified, and Status. You can click on any result, and it will open in a new tab.
  • Switch to Classic Search: This button will allow you to toggle between Classic Search and the New & Improved Advanced Search.
  • Sort By: The default is Relevance. The drop-down menu will display other options by which to sort the results.
  • Filters: Filtering is optional. Add a filter by clicking in the “Add a Filter” box. Once a selection is made, you will have the option to define your search criteria. You may add multiple filters to a single search by clicking again in the “Add a Filter” box. When you add a filter, the results will update automatically.

Boolean for Classic Search

Boolean searches are fully supported as well when more direct search results are required. Boolean searches allow you to combine words and phrases using the words AND, OR, NOT and NEAR (otherwise known as Boolean operators) to limit, widen, or define your search. Noise words, such as “if” and “the”, are ignored in searches.

Search terminology and connector examples:

  • apple and pear: Both words must be present
  • apple or pear: Either word can be present
  • apple w/5 pear: Apple must occur within 5 words of pear
  • apple not w/12 pear: Apple must occur, but not within 12 words of pear
  • apple and not Pear: Only apple must be present
  • name contains smith: The field name must contain smith
  • apple w/5 firstword: Apple must occur in the first five words
  • apple w/5 lastword: Apple must occur in the last five words

If you use more than one connector (and, or, contains, etc.), you should use parentheses to indicate precisely what you want to search for. For example, apple and pear or orange could mean (apple and pear) or orange, or it could mean apple and (pear or orange). For best results, always enclose expressions with connectors in parenthesis.

(apple and pear) or (name contains smith)


Search terms may include the following wildcard characters:

  • *: Matches any number of characters
  • ?: Matches any single character
  • =: Matches any single digit

For example:
appl* would match apple, application, etc.
*cipl * would match principle, participle, etc.
appl? would match apply and apple but not apples.
ap*ed would match applied, approved, etc.
N=== would match N123 but not N1234 or Nabc

Use of the * wildcard character near the beginning of a word will slow searches somewhat.


  • % for Fuzzy searching. Fuzzy searching will find a word even if it is misspelled. Fuzzy searching can be useful when you are searching text that may contain typographical errors (such as emails), or for text that has been scanned using optical character recognition (OCR). There are two ways to add fuzziness to your searches:

ba%nana: Word must begin with ba and have at most one difference between it and banana.
b%%anana: Word must begin with b and have at most two differences between it and banana.


  • # for Phonic searching. Phonic searching looks for a word that sounds like the word you are searching for and begins with the same letter. To search for a word phonically, put a # in front of the word in your search request.

#Smith would also find Smith and Smythe


  • ~ for Stemming. Stemming extends a search to cover grammatical variations on a word. To add stemming selectively, add a ~ at the end of words that you want stemmed in a search.

fish~ would find fish and fishing
applied~ would find applied, applying, applies, and apply


  • & for Synonym searching. Synonym searching finds synonyms of a word that you include in a search request. You can also enable synonym searching selectively by adding the & character after certain words in your request.

&fast would also find quickly

Numeric Range
  • ~~ will search for a numeric range. A numeric range search is a search for any numbers that fall within a range. To add a numeric range component to a search request, enter the upper and lower bounds of the search separated by ~~.A numeric range search includes the upper and lower bounds.

apple w/5 12~~17: This request would find any document containing apple within 5 words of a number between 12 and 17 (upper bound and lower bound).

Regular Expression

  • ## for Regular Expression searching. Regular expression searching provides a way to search for advanced combinations of characters. A regular expression included in a search request must be quoted and must begin with ##.
Examples: Apple and “##199[0-9]” Apple and “##19[0-9]+”

When used in searching, a regular expression must match a single whole word. For example, you could not search for “apple pie” with a regular expression “##app.*ie”. The beginning of line and end of line regular expression markers ^ and $ cannot be used in searches.

Our search uses the TR1 implementation of regular expressions, which provides many capabilities beyond what is described above. For more details on TR1 regular expression capabilities, please see this Microsoft article:


(1) A regular expression must match a single whole word. For example, a search for “##app.*ie” would not find “apple pie”.

(2) Only letters are searchable. Characters that are not indexed as letters are not searchable even using regular expressions, because the index does not contain any information about them.

(3) Because our search index does not store information about line breaks, searches that include begining-of-line or end-of-line regular expression criteria (^ and $) will not work.

(4) No case or other conversion is done on regular expressions, so a regular expression must match the case of the information stored in the index. If an index is case-insensitive, all letters in the regular expression must be lower-case. If a character is not searchable in the index, then it cannot be included as a searchable character in the regular expression. Non-searchable characters in a regular expression are not ignored as they are in other search expressions.


A regular expression is like the * wildcard character in its effect on search speed: the closer to the front of a word the expression is, the more it will slow searching. “appl.*” will be nearly as fast as “apple”, while “.*pple” will be much slower.

Searching for numbers

The = wildcard, which matches a single digit, is faster than regular expressions for matching patterns of numbers. For example, to search for a social security number, you could use “=== ==” instead of the equivalent regular expression.

Need more help with this?
Customer Support

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.