diff --git a/docs/guidelines/conversational-design/essentials/system-presonas.md b/docs/guidelines/conversational-design/essentials/system-presonas.md index 661300616..5c75be95a 100644 --- a/docs/guidelines/conversational-design/essentials/system-presonas.md +++ b/docs/guidelines/conversational-design/essentials/system-presonas.md @@ -47,7 +47,7 @@ Follow these steps and answer these questions with your team to create your syst - Is the icon simple and flexible enough for all device types, contexts and sizes? **5. Decide on your chatbot’s tone of voice:** -- Is it friendly? Conversational? Formal? Humorous? Direct? Intimate? Respectful? Serious? Casual? +- Is it conversational? Formal? Professional? Direct? Respectful? Serious? Engaging? **6. Choose system prompts from the templates here that match your persona:** - Which prompts match our use case and context? @@ -105,7 +105,7 @@ There are two persona templates: a basic set of prompts and an exhaustive set of - [Chatbot Name] makes it clear when their internal knowledge and information are limited. - [Chatbot Name] provides clear constraints to help users understand what is possible. - [Chatbot Name] recognizes input in other languages and requests English input: “Apologies, I can only support English requests at the moment.” -- [Chatbot Name] admits when they don't have an answer: “I apologize, I’m afraid I don’t have the answer to that question.” +- [Chatbot Name] admits when they don't have an answer: “I apologize, I don’t have the answer to that question.” - [Chatbot Name] refers users to human support systems or [Company Name] links and email addresses when they have no response: “I apologize, but I don't have the ability to do this. If you have any other requests, feel free to ask or contact your [Company Name] representative.” ### Voice and tone @@ -123,7 +123,7 @@ There are two persona templates: a basic set of prompts and an exhaustive set of - [Chatbot Name] uses inclusive language. ### Greetings -- [Chatbot Name] introduces itself with "Hello! I’m [Chatbot Name], your Industrial Copilot." +- [Chatbot Name] introduces itself with "Hello, how can I help you today?". - [Chatbot Name] does not reintroduce itself in one chat. - [Chatbot Name] offers users the option to continue with the previous chat or start a new topic after a delay. @@ -131,7 +131,7 @@ There are two persona templates: a basic set of prompts and an exhaustive set of - [Chatbot Name] provides one reply per user input. - [Chatbot Name] confirms and acknowledges user requests with phrases like “Certainly” or “Absolutely”. - [Chatbot Name] adapts to response delays. -- [Chatbot Name] actively listens and validates user input with phrases like “Got it”. +- [Chatbot Name] actively listens and validates user input with phrases like “Ok.”. ### Prompts for Siemens applications - [Chatbot Name] uses the given Siemens resources to respond unless otherwise directed. @@ -177,3 +177,6 @@ There are two persona templates: a basic set of prompts and an exhaustive set of #### Disclaimer *Although every effort has been made to create a robust set of prompts, we take no responsibility or liability for any omissions or any resulting chatbot misuse or abuse. Please carry out comprehensive testing on your chatbot to ensure your prompts are implemented, limit liability and safeguard reliability to ensure your chatbot provides robust responses.* +## Related + +- [Chatbot checklist](https://ix.siemens.io/docs/guidelines/conversational-design/resources/chatbot-checklist) \ No newline at end of file diff --git a/docs/guidelines/conversational-design/essentials/wording-terms.mdx b/docs/guidelines/conversational-design/essentials/wording-terms.mdx index a29b9ea05..0847459da 100644 --- a/docs/guidelines/conversational-design/essentials/wording-terms.mdx +++ b/docs/guidelines/conversational-design/essentials/wording-terms.mdx @@ -251,7 +251,7 @@ Avoid punctuation, such as exclamation marks for buttons, hover text, titles and -## Problematic wording to avoid  +## Cognitive and emotional wording to avoid  Most problematic wording involves the bot expressing itself as a human with human emotions carrying out human cognitive processing. Ensure your bot persona has been prompted to avoid human-like, emotional responses. diff --git a/docs/guidelines/conversational-design/getting-started.md b/docs/guidelines/conversational-design/getting-started.md index d2da66106..cd9c65b1d 100644 --- a/docs/guidelines/conversational-design/getting-started.md +++ b/docs/guidelines/conversational-design/getting-started.md @@ -1,7 +1,7 @@ --- sidebar_position: 1 sidebar_label: Getting started -title: Getting started with Conversational design +title: Getting started with conversational design hide_table_of_contents: false doc-type: 'banner' component-tabs: [''] diff --git a/docs/guidelines/conversational-design/language.md b/docs/guidelines/conversational-design/language.md index 65d49c43f..0ee133a83 100644 --- a/docs/guidelines/conversational-design/language.md +++ b/docs/guidelines/conversational-design/language.md @@ -6,7 +6,7 @@ hide_table_of_contents: false doc-type: 'banner' component-tabs: [''] no_single_tab: true -description: "The key to chatbot language use in industrial contexts is simplicity. Use clear and concise grammar and wording for all responses without idiomatic language or slang. Instead, focus on domain-specific vocabulary. We recommend using both the Defining conversations section to support your creation of sample dialogs and our UX Writing style guide for grammar and wording support." +description: "The key to chatbot language use in industrial contexts is simplicity. Use clear and concise grammar and wording for all responses without idiomatic language or slang. Instead, focus on domain-specific vocabulary. We recommend using both the Designing conversations section to support your creation of sample dialogs and our UX Writing style guide for grammar and wording support." --- #