From 622e07cb96a59e3eced9c564297c2849d2fe6461 Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Fri, 19 Sep 2025 15:34:17 +0530 Subject: [PATCH 1/8] Update prompt-suggestions.md --- .../conversations/prompt-suggestions.md | 20 +++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index da4983237bd..727dc284670 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -37,7 +37,7 @@ Suggested actions help users continue conversations with your bot. :::column-end::: -:::row-end::: +:::row-end::: ## Prompt starters @@ -47,7 +47,16 @@ Suggested actions help users continue conversations with your bot. > > * Prompt starters are only supported for one-on-one chat bots. -To enable prompt starters, define the `commands` property in your bot's app manifest. Each command contains a `title` and `description`. The `title` is the prompt and the `description` describes what the users accomplish. When the user selects on a prompt starter, the `title` of the prompt is populated in the compose box. To define `commands` in your app manifest, you can either use **Developer Portal** or add them manually in the app manifest. +To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type` and `prompt`. The `title` field is the text shown in the prompt starter and the `description` describes what the users accomplish. The `type` field indicates whether the bot command is a basic command or a prompt. The `prompt` field defines the text to populate in the compose box, when the command is a prompt type. +When the user selects on a prompt starter, the `title` of the prompt is populated in the compose box. To define `commands` in your app manifest, you can either use **Developer Portal** or add them manually in the app manifest. +The `type ` field determines how the command behaves. +* For `type`:basic, the title will be used to populate the compose box. +* For `type`:prompt, the prompt text will be used to populate the compose box. + +If the command is a prompt, set type to "prompt" and provide the text in the prompt field. +If the command is basic, set type to "basic" and use the title field for the text. + +For agent-based bots, developers must set type to prompt and provide a valid prompt. If prompt is left blank, manifest validation will fail at submission. # [Developer Portal](#tab/developer-portal) @@ -103,18 +112,25 @@ The manifest example code for prompt starters is as follows: { "title":"Help", "description":"Displays this help message" + "type":"basic" }, { "title":"Search Flights", "description":"Search flights from Seattle to Phoenix May 2-5 departing after 3pm" + "type": "prompt", + "prompt": "Search flights from Seattle to Phoenix May 2-5 departing after 3pm. Please show me the best options." }, { "title":"Search Hotels", "description":"Search hotels in Portland tonight" + "type": "prompt", + "prompt": "Search hotels in Portland for tonight. Please show me available options with good ratings." }, { "title":"Best Time to Fly", "description":"Best time to fly to London for a 5 day trip this summer" + "type": "prompt", + "prompt": "What is the best time to fly to London for a 5 day trip? I'm looking for good weather and reasonable prices." } ] } From 57381ee830d4423d6c407625936d60983f4531d2 Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Mon, 22 Sep 2025 08:50:19 +0530 Subject: [PATCH 2/8] Update prompt-suggestions.md --- .../bots/how-to/conversations/prompt-suggestions.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index 727dc284670..739a66350d8 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -48,15 +48,15 @@ Suggested actions help users continue conversations with your bot. > * Prompt starters are only supported for one-on-one chat bots. To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type` and `prompt`. The `title` field is the text shown in the prompt starter and the `description` describes what the users accomplish. The `type` field indicates whether the bot command is a basic command or a prompt. The `prompt` field defines the text to populate in the compose box, when the command is a prompt type. -When the user selects on a prompt starter, the `title` of the prompt is populated in the compose box. To define `commands` in your app manifest, you can either use **Developer Portal** or add them manually in the app manifest. +When the user selects on a prompt starter, the `title` of the prompt is populated in the compose box. The `type ` field determines how the command behaves. -* For `type`:basic, the title will be used to populate the compose box. -* For `type`:prompt, the prompt text will be used to populate the compose box. -If the command is a prompt, set type to "prompt" and provide the text in the prompt field. -If the command is basic, set type to "basic" and use the title field for the text. +* If the `command` is `prompt`, set type to "prompt" and provide the text in the prompt field. +* If the `command` is `basic`, set type to "basic" and use the title field for the text. -For agent-based bots, developers must set type to prompt and provide a valid prompt. If prompt is left blank, manifest validation will fail at submission. +For agent-based bots, set `type` to `prompt` and provide a valid prompt. If `prompt` is left blank, manifest validation will fail at submission. + +To define `commands` in your app manifest, you can either use **Developer Portal** or add them manually in the app manifest. # [Developer Portal](#tab/developer-portal) From fb40dee45725252cca0abf5f02f3a7cf8a1c38ce Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Tue, 23 Sep 2025 14:08:58 +0530 Subject: [PATCH 3/8] Update prompt-suggestions.md --- .../bots/how-to/conversations/prompt-suggestions.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index 739a66350d8..5a6a2fb2760 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -49,7 +49,7 @@ Suggested actions help users continue conversations with your bot. To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type` and `prompt`. The `title` field is the text shown in the prompt starter and the `description` describes what the users accomplish. The `type` field indicates whether the bot command is a basic command or a prompt. The `prompt` field defines the text to populate in the compose box, when the command is a prompt type. When the user selects on a prompt starter, the `title` of the prompt is populated in the compose box. -The `type ` field determines how the command behaves. +The `type` field determines how the command behaves. * If the `command` is `prompt`, set type to "prompt" and provide the text in the prompt field. * If the `command` is `basic`, set type to "basic" and use the title field for the text. @@ -111,24 +111,24 @@ The manifest example code for prompt starters is as follows: "commands":[ { "title":"Help", - "description":"Displays this help message" + "description":"Displays this help message", "type":"basic" }, { "title":"Search Flights", - "description":"Search flights from Seattle to Phoenix May 2-5 departing after 3pm" + "description":"Search flights from Seattle to Phoenix May 2-5 departing after 3pm", "type": "prompt", "prompt": "Search flights from Seattle to Phoenix May 2-5 departing after 3pm. Please show me the best options." }, { "title":"Search Hotels", - "description":"Search hotels in Portland tonight" + "description":"Search hotels in Portland tonight", "type": "prompt", "prompt": "Search hotels in Portland for tonight. Please show me available options with good ratings." }, { "title":"Best Time to Fly", - "description":"Best time to fly to London for a 5 day trip this summer" + "description":"Best time to fly to London for a 5 day trip this summer", "type": "prompt", "prompt": "What is the best time to fly to London for a 5 day trip? I'm looking for good weather and reasonable prices." } From 619ca6a39379d3764b928df7a3c51ca1349f8f6e Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Wed, 24 Sep 2025 17:21:31 +0530 Subject: [PATCH 4/8] Update prompt-suggestions.md --- .../conversations/prompt-suggestions.md | 25 +++++++++++-------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index 5a6a2fb2760..389e0b65f25 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -47,14 +47,19 @@ Suggested actions help users continue conversations with your bot. > > * Prompt starters are only supported for one-on-one chat bots. -To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type` and `prompt`. The `title` field is the text shown in the prompt starter and the `description` describes what the users accomplish. The `type` field indicates whether the bot command is a basic command or a prompt. The `prompt` field defines the text to populate in the compose box, when the command is a prompt type. -When the user selects on a prompt starter, the `title` of the prompt is populated in the compose box. -The `type` field determines how the command behaves. +To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type`, and `prompt`. +- The `title` field is the text shown in the prompt starter. When selected, this text is populated into the compose box. +- The `description` field describes what the users accomplish. +- The `type` field indicates whether the bot command is a basic command or a prompt. + + * If the `command` is `prompt`, set type to "prompt" and provide the text in the prompt field. + * If the `command` is `basic`, set type to "basic" and use the title field for the text. +- The `prompt`field defines the text to populate in the compose box. -* If the `command` is `prompt`, set type to "prompt" and provide the text in the prompt field. -* If the `command` is `basic`, set type to "basic" and use the title field for the text. +[!NOTE] +If you're building an agent, you must set type to "prompt" and provide a valid prompt value. If the prompt field is empty, the app manifest fails validation during submission. -For agent-based bots, set `type` to `prompt` and provide a valid prompt. If `prompt` is left blank, manifest validation will fail at submission. +## Define `commands` in app manifest To define `commands` in your app manifest, you can either use **Developer Portal** or add them manually in the app manifest. @@ -79,7 +84,7 @@ To create prompt starters using Developer Portal: * **Command**: Appears as the prompt for your bot. * **Description**: A brief explanation of the purpose of the command. -1. Select the personal scope and then select **Add**. This defines where the command menu must appear. +1. Select the personal scope and then select **Add**. This step defines where the command menu must appear. :::image type="content" source="~/assets/images/tdp/bot-command.png" alt-text="Screenshot shows how to add a command, description, and scopes for your bot."::: @@ -146,7 +151,7 @@ The manifest example code for prompt starters is as follows: > [!NOTE] > If you remove any commands from your manifest, you must redeploy your app to implement the changes. In general, any changes to the manifest require you to redeploy your app. -The following illustrates an example of prompt suggestions: +The following image illustrates an example of prompt suggestions: # [Desktop](#tab/desktop) @@ -158,7 +163,7 @@ The following illustrates an example of prompt suggestions: --- -Prompt starters reappear in the **View Prompts** flyout above the compose box during a conversation and enables users to review the prompts while interacting with your bot. +Prompt starters reappear in the **View Prompts** flyout above the compose box during a conversation and enable users to review the prompts while interacting with your bot. :::image type="content" source="~/assets/images/bots/prompt-starter-desktop-reappear.png" alt-text="Screenshot that shows the Prompt Starter reappear during the conversation." lightbox="~/assets/images/bots/prompt-starter-desktop-reappear.png"::: @@ -169,7 +174,7 @@ You must handle menu commands in your bot code as you handle any message from us Bots in a group or channel respond only when they're @mentioned in a message. Every message received by a bot when in a group or channel scope contains its name in the message text. Before handling the command being returned, your message parsing must handle the message received by a bot with its name. > [!NOTE] -> Handle the commands in code, they are sent to your bot as a regular message. You must handle them as you would handle any other message from your users. The commands in code insert pre-configured text into the text box. The user must then send that text as they do for any other message. +> Handle the commands in code, they are sent to your bot as a regular message. You must handle them as you would handle any other message from your users. The commands in code insert preconfigured text into the text box. The user must then send that text as they do for any other message. # [C#](#tab/dotnet) From e1766ad207c52161f813eb69c49ee9b0c75ce993 Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Wed, 24 Sep 2025 17:55:56 +0530 Subject: [PATCH 5/8] Update prompt-suggestions.md --- .../bots/how-to/conversations/prompt-suggestions.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index 389e0b65f25..72b2059ca95 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -52,12 +52,13 @@ To enable prompt starters, define the `commands` property in your bot's app mani - The `description` field describes what the users accomplish. - The `type` field indicates whether the bot command is a basic command or a prompt. - * If the `command` is `prompt`, set type to "prompt" and provide the text in the prompt field. - * If the `command` is `basic`, set type to "basic" and use the title field for the text. -- The `prompt`field defines the text to populate in the compose box. + * If the `command` is `prompt`, set type to **prompt** and provide the text in the prompt field. + * If the `command` is `basic`, set type to **basic** and use the title field for the text. +- The `prompt`field defines the text to populate in the compose box, when the command is a prompt type. -[!NOTE] -If you're building an agent, you must set type to "prompt" and provide a valid prompt value. If the prompt field is empty, the app manifest fails validation during submission. +>[!NOTE] +> +>If you're building an agent, you must set `type` to **prompt** and provide a valid prompt value. If the `prompt` field is empty, the app manifest fails validation during submission. ## Define `commands` in app manifest From 52055eb57daf9b28ee461ea216f8c90a5603c051 Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Wed, 1 Oct 2025 08:37:05 +0530 Subject: [PATCH 6/8] Update prompt-suggestions.md Updated as per review comments --- .../bots/how-to/conversations/prompt-suggestions.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index 72b2059ca95..d2bc30feb8a 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -48,12 +48,10 @@ Suggested actions help users continue conversations with your bot. > * Prompt starters are only supported for one-on-one chat bots. To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type`, and `prompt`. -- The `title` field is the text shown in the prompt starter. When selected, this text is populated into the compose box. +- The `title` field is the text shown in the prompt starter. When selected, this text is populated into the compose box. If the `type` is **basic**, this text is also used to populate the compose box. - The `description` field describes what the users accomplish. - The `type` field indicates whether the bot command is a basic command or a prompt. - - * If the `command` is `prompt`, set type to **prompt** and provide the text in the prompt field. - * If the `command` is `basic`, set type to **basic** and use the title field for the text. + Set `type` to **prompt** and provide the text in the prompt field. - The `prompt`field defines the text to populate in the compose box, when the command is a prompt type. >[!NOTE] @@ -175,7 +173,7 @@ You must handle menu commands in your bot code as you handle any message from us Bots in a group or channel respond only when they're @mentioned in a message. Every message received by a bot when in a group or channel scope contains its name in the message text. Before handling the command being returned, your message parsing must handle the message received by a bot with its name. > [!NOTE] -> Handle the commands in code, they are sent to your bot as a regular message. You must handle them as you would handle any other message from your users. The commands in code insert preconfigured text into the text box. The user must then send that text as they do for any other message. +> Handle the commands in code, they're sent to your bot as a regular message. You must handle them as you would handle any other message from your users. The commands in code insert preconfigured text into the text box. The user must then send that text as they do for any other message. # [C#](#tab/dotnet) From 2c4c4862d63a08bbd3edbcf6d287a88e966550d4 Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Fri, 3 Oct 2025 14:26:21 +0530 Subject: [PATCH 7/8] Update prompt-suggestions.md --- .../bots/how-to/conversations/prompt-suggestions.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index d2bc30feb8a..e84c8844d88 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -48,7 +48,7 @@ Suggested actions help users continue conversations with your bot. > * Prompt starters are only supported for one-on-one chat bots. To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type`, and `prompt`. -- The `title` field is the text shown in the prompt starter. When selected, this text is populated into the compose box. If the `type` is **basic**, this text is also used to populate the compose box. +- The `title` field is the text shown in the prompt starter. When selected, this text is populated into the compose box. - The `description` field describes what the users accomplish. - The `type` field indicates whether the bot command is a basic command or a prompt. Set `type` to **prompt** and provide the text in the prompt field. @@ -116,7 +116,6 @@ The manifest example code for prompt starters is as follows: { "title":"Help", "description":"Displays this help message", - "type":"basic" }, { "title":"Search Flights", From 3d603e0ff2d584e55fb3d14d53396cd773fc70c8 Mon Sep 17 00:00:00 2001 From: v-shgarcha Date: Fri, 17 Oct 2025 12:27:53 +0530 Subject: [PATCH 8/8] Update prompt-suggestions.md --- .../how-to/conversations/prompt-suggestions.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md index e84c8844d88..3f786347943 100644 --- a/msteams-platform/bots/how-to/conversations/prompt-suggestions.md +++ b/msteams-platform/bots/how-to/conversations/prompt-suggestions.md @@ -37,7 +37,7 @@ Suggested actions help users continue conversations with your bot. :::column-end::: -:::row-end::: +:::row-end::: ## Prompt starters @@ -47,12 +47,12 @@ Suggested actions help users continue conversations with your bot. > > * Prompt starters are only supported for one-on-one chat bots. -To enable prompt starters, define the `commands` property in your bot's app manifest. Each command now contains four fields, a `title`, `description`, `type`, and `prompt`. -- The `title` field is the text shown in the prompt starter. When selected, this text is populated into the compose box. -- The `description` field describes what the users accomplish. -- The `type` field indicates whether the bot command is a basic command or a prompt. - Set `type` to **prompt** and provide the text in the prompt field. -- The `prompt`field defines the text to populate in the compose box, when the command is a prompt type. +To enable prompt starters, define the `commands` property in your bot's app manifest. Each command contains four fields, `title`, `description`, `type`, and `prompt`. + +* The `title` field is the text shown in the prompt starter. When selected, this text is populated into the compose box. +* The `description` field describes what the users accomplish. +* The `type` field indicates whether the bot command is basic or prompt. Set `type` to **prompt** and provide the text in the prompt field. When selected, the prompt text appears in the compose box instead of the title or description. +* The `prompt`field specifies the text that appears in the compose box for a prompt command. It supports up to 4,000 characters. >[!NOTE] > @@ -60,7 +60,7 @@ To enable prompt starters, define the `commands` property in your bot's app mani ## Define `commands` in app manifest -To define `commands` in your app manifest, you can either use **Developer Portal** or add them manually in the app manifest. +To define `commands` in your app manifest, you can either use **Developer Portal** or add them manually in the app manifest. # [Developer Portal](#tab/developer-portal)