Keep in mind, that fallbacks will be displayed in addition to the answer. If you want to provide the user with a standard answer if no document or information can be found, use the tonality instead. Additionally, the fallback functionality doesn’t require or use any permissions. If you have different user groups for your use case, separation based on user groups won’t be possible. Therefore, fallbacks should be generalistic.
How to Set Up Fallbacks
You will need the following information to add a fallback:- Fallback Name: will be displayed to the user
- Description: a description of the fallback strategy. Will be accessable to the user via a mouseover.
- Example questions: a list of example questions.
The selection of a fallback is based on similarity of the user question and example questions. The list of example questions should therefore include at least five similar questions. This also means, that if you have multiple fallback strategies with similar example questions, the selection process will reliable.
- Further information: Fill out at least one of:
- Contact name or additional information (free text input): Might be a description or explenation or a name of a contact person.
- Contact email address: up to one email address. Clickable in the user interface via mailto.
- Link / URL: a link to an additional website
Example: Jobrad in HR
In the following you will find an example for Jobrad, in an HR use case:| Field | Input |
|---|---|
| Name | Fallback Jobrad |
| Description | In case of question about the Jobrad this fallback should be used. |
| Example Question | ”How can I apply for a Jobrad?”, “What information do I need to apply for a Jobrad?”, “Who can I contact about a Jobrad?”, “How can I get a Jobrad?”, “How can I get a Jobrad?”, “What is a Jobrad?”, “Give me information about a Jobrad?”, “Jobrad?” |
| Further information: Contact name | Contact you individual contact person of HR. |
| Further information: URL | https://www.jobrad.org/ |