GETTING STARTED
SearchAssist Overview
SearchAssist Introduction
Onboarding SearchAssist
Build your first App
Glossary
Release Notes
Current Version
Recent Updates
Previous Versions

CONCEPTS
Managing Sources
Introduction
Files
Web Pages
FAQs
Structured Data 
Connectors
Introduction to Connectors
SharePoint Connector
Confluence Connector
Zendesk Connector
ServiceNow Connector
Salesforce Connector
Azure Storage Connector
Google Drive Connector
Dropbox Connector
Oracle Knowledge Connector
Virtual Assistants
Managing Indices
Introduction
Index Fields
Traits
Workbench
Introduction to Workbench
Field Mapping
Entity Extraction
Traits Extraction
Keyword Extraction
Exclude Document
Semantic Meaning
Snippet Extraction
Custom LLM Prompts
Index Settings
Index Languages
Managing Chunks
Chunk Browser
Managing Relevance
Introduction
Weights
Highlighting
Presentable
Synonyms
Stop Words
Search Relevance
Spell Correction
Prefix Search
Personalizing Results
Introduction
Answer Snippets
Introduction
Extractive Model
Generative Model
Enabling Both Models
Simulation and Testing
Debugging
Best Practices and Points to Remember
Troubleshooting Answers
Answer Snippets Support Across Content Sources
Result Ranking
Facets
Business Rules
Introduction
Contextual Rules
NLP Rules
Engagement
Small Talk
Bot Actions
Designing Search Experience
Introduction
Search Interface
Result Templates
Testing
Preview and Test
Debug Tool
Running Experiments
Introduction
Experiments
Analyzing Search Performance
Overview
Dashboard
User Engagement
Search Insights
Result Insights
Answer Insights

ADMINISTRATION
General Settings
Credentials
Channels
Collaboration
Integrations
OpenAI Integration
Azure OpenAI Integration
Billing and Usage
Plan Details
Usage Logs
Order and Invoices

SearchAssist PUBLIC APIs
API Introduction
API List

SearchAssist SDK

HOW TOs
Use Custom Fields to Filter Search Results and Answers
Add Custom Metadata to Ingested Content
Write Painless Scripts
Configure Business Rules for Generative Answers

Spell Correction

Spelling errors in the search query can lead to wrong or irrelevant results. SearchAssist offers a spell correction feature that can identify the misspellings in the user’s query, correct them automatically, and thereby, improve the search results. For example, in the case shown below, incorrect spelling in the user query was automatically corrected and relevant results were displayed. 

To enable or disable this feature, go to the Spell Correction page in Search Settings under the Indices tab and use the slider as shown below. 

Use the other fields to configure the behavior of the feature.

Field  Description
Minimum Character Threshold The minimum number of characters that a word must have in order to be considered for spell correction. This field can take a maximum value of 6. The lower the value of this field, the higher the probability of false corrected values. 
Maximum Typo Edits The maximum number of errors to be corrected for a word. 
Fields for Spell Correction  Indexed fields to be considered for spell correction. This should include fields against which the search runs like page_body, faq_question, faq_answer, etc.

It is not recommended to select fields that contain media files or URLs, like page_image_url, faq_question_vector, etc. 

To add a new field whose values can be used for spell correction, click the Add Field link, select the fields from the list, and click Add.

Spell Correction

Spelling errors in the search query can lead to wrong or irrelevant results. SearchAssist offers a spell correction feature that can identify the misspellings in the user’s query, correct them automatically, and thereby, improve the search results. For example, in the case shown below, incorrect spelling in the user query was automatically corrected and relevant results were displayed. 

To enable or disable this feature, go to the Spell Correction page in Search Settings under the Indices tab and use the slider as shown below. 

Use the other fields to configure the behavior of the feature.

Field  Description
Minimum Character Threshold The minimum number of characters that a word must have in order to be considered for spell correction. This field can take a maximum value of 6. The lower the value of this field, the higher the probability of false corrected values. 
Maximum Typo Edits The maximum number of errors to be corrected for a word. 
Fields for Spell Correction  Indexed fields to be considered for spell correction. This should include fields against which the search runs like page_body, faq_question, faq_answer, etc.

It is not recommended to select fields that contain media files or URLs, like page_image_url, faq_question_vector, etc. 

To add a new field whose values can be used for spell correction, click the Add Field link, select the fields from the list, and click Add.