Editar

Compartir a través de

Send and receive messages

  • Artículo

Conversational bots communicate with users through messaging, enabling seamless interactions. It can simulate real life conversations with users through text or voice interactions. You must ensure that bot conversations are interactive, dynamic, adaptive, and user friendly.

Message content

Messages interaction between your bot and user can include different types of message content that:

Content type From user to bot From bot to user
Rich text and emojis ✔️ ✔️
Pictures ✔️ ✔️
Adaptive Cards ❌ ✔️

Use rich text message and emojis

Your Teams bot can send rich text and emojis. Teams supports emojis through UTF-16, like U+1F600 for a grinning face.

Use picture messages

To make bot message pop, the user can add pictures as attachments:

  • Pictures can be up to 1024 × 1024 pixels and 1 MB in PNG, JPEG, or GIF format. Animated GIFs aren't supported.

  • You can specify the height and width of each image using XML. In Markdown, the image size defaults to 256×256. For example:

    • ✔️: <img src="http://aka.ms/Fo983c" alt="Duck on a rock" height="150" width="223"></img>.
    • ❌: ![Duck on a rock](http://aka.ms/Fo983c).

For more information on attachments, see add media attachments to messages.

Use Adaptive Cards

A conversational bot can include Adaptive Cards that simplify business workflows. Adaptive Cards offer rich customizable text, speech, images, buttons, and input fields. You can author Adaptive Cards in a bot and shown in multiple apps such as Teams, your website, and so on.

For more information, see:

The following code shows an example of sending a simple Adaptive Card:

Example: Send a simple Adaptive Card 
{
    "type": "AdaptiveCard",
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.5",
    "body": [
    {
        "items": [
        {
            "size": "large",
            "text": " Simple Adaptivecard Example with a Textbox",
            "type": "TextBlock",
            "weight": "bolder",
            "wrap": true
        },
        ],
        "spacing": "extraLarge",
        "type": "Container",
        "verticalContentAlignment": "center"
    }
    ]
}

Send and receive messages

Sending and receiving messages is the core functionality of a bot. It enables a bot to:

In a chat, each message is an Activity object of type messageType: message. When someone sends a message, Microsoft Teams posts it to your bot. Teams sends a JSON object to your bot's messaging endpoint, and it allows only one endpoint for messaging. Your bot then checks the message to figure out its type and responds accordingly.

Basic conversations are managed through the Bot Framework connector, which is a single REST API. This API enables your bot talk to Teams and other channels. The Bot Builder SDK offers the following features:

  • Easy access to the Bot Framework connector.
  • Tools to manage conversation flow and state.
  • Simple ways to add cognitive services, like natural language processing (NLP).

Your bot gets messages from Teams using the Text property and can send back single or multiple responses to users.

For more information, see user attribution for bot messages.

The following table lists the activity that your bot can receive and take action on:

Message type Payload object Scope
Receive a message activity Message activity All
Receive edit message activity Message edit activity All
Receive undelete message activity Message undelete activity All
Receive soft delete message activity Message soft delete activity All

Receive a message activity

To receive a text message, use the Text property of an Activity object. In the bot's activity handler, use the turn context object's Activity to read a single message request.

The following code shows an example of receiving a message activity:


protected override async Task OnMessageActivityAsync(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)
{
  // Sends an activity to the sender of the incoming activity.
  await turnContext.SendActivityAsync(MessageFactory.Text($"Echo: {turnContext.Activity.Text}"), cancellationToken);
}

Receive a read receipt

The Read receipts setting in Teams allow the sender of a chat message to be notified when their message was read by the recipient in one-on-one and group chats. After the recipient reads the message, the Seen appears next to the message. You also have the option to configure your bot to receive read receipt events through the Read receipts setting. The read receipt event helps you enhance user experience in the following ways:

  • You can configure your bot to send a follow-up message if your app user hasn't read the message in the personal chat.

  • You can create a feedback loop using read receipts to tune your bot’s experience.

Note

  • Read receipts are supported only in user to bot chat scenarios.
  • Read receipts for bots doesn’t support team, channel, and group chat scopes.
  • If an admin or user disables the Read receipts setting, the bot doesn't receive the read receipt event.

To receive read receipts events for your bot, ensure the following:

  • Add the RSC ChatMessageReadReceipt.Read.Chat permission in the app manifest, as follows:
    
"webApplicationInfo": {
    
     "id": "38f0ca43-1c38-4c39-8097e-47f62c686500",
     "resource": ""
},
"authorization": {
    "permissions": {
    "orgwide": [],
     "resourceSpecific": [
        {
        "name": "ChatMessageReadReceipt.Read.Chat",
        "type": "Application"
        }
        ]
     }
 }

You can also add RSC permissions through Graph API. For more information, see consentedPermissionSet.

  • Override the method OnTeamsReadReceiptAsync with IsMessageRead handler.

    The IsMessageRead helper method is useful to determine if the message is read by the recipients. If the compareMessageId is less than or equal to the LastReadMessageId, then the message has been read. Override the OnTeamsReadReceiptAsync method to receive read receipts with IsMessageRead helper method:

    
protected override async Task OnTeamsReadReceiptAsync(ReadReceiptInfo readReceiptInfo, ITurnContext<IEventActivity> turnContext, CancellationToken cancellationToken) 
{
    var lastReadMessageId = readReceiptInfo.LastReadMessageId;
   if (IsMessageRead("{id of the message that you care}", LastReadMessageId))
   {
        await turnContext.SendActivityAsync(MessageFactory.Text("User read the bot's message"), cancellationToken);    
    }
}

    The following example shows a read receipts event request that a bot receives:

    {
    "name": "application/vnd.microsoft.readReceipt",
    "type": "event",
    "timestamp": "2023-08-16T17:23:11.1366686Z",
    "id": "f:b4783e72-9d7b-2ed9-ccef-ab446c873007",
    "channelId": "msteams",
    "serviceUrl": "https://smba.trafficmanager.net/amer/",
    "from": {
        "id": "29:1-8Iuh70W9pRqV8tQK8o2nVjxz33RRGDKLf4Bh7gKnrzN8s7e4vCyrFwjkPbTCX_Co8c4aXwWvq3RBLr-WkkVMw",
        "aadObjectId": "5b649834-7412-4cce-9e69-176e95a394f5"
    },
    "conversation": {
        "conversationType": "personal",
        "tenantId": "6babcaad-604b-40ac-a9d7-9fd97c0b779f",
        "id": "a:1xlimp68NSUxEqK0ap2rXuwC9ITauHgV2M4RaDPkeRhV8qMaFn-RyilMZ62YiVdqs8pp43yQaRKvv_U2S2gOS5nM-y_pOxVe4BW1qMGPtqD0Bv3pw-nJXF0zhDlZHMZ1Z"
    },
    "recipient": {
        "id": "28:9901a8b6-4fef-428b-80b1-ddb59361adeb",
        "name": "Test Bot"
    },
    "channelData": {
        "tenant": {
            "id": "6babcaad-604b-40ac-a9d7-9fd97c0b779f"
        }
    },
    "value": {
        "lastReadMessageId": "1692206589131"
    }
}

  • Read receipt admin setting or user setting is turned on for the tenant for the bot to receive the read receipt events. The admin or the user must enable or disable the read receipt setting.

After the bot is enabled in a user to bot chat scenario, the bot promptly receives a read receipt event when the user reads the bot's message. You can track the user engagement by counting the number of events and you can also send a context aware message.

Receive edit message activity

When you edit a message, the bot gets a notification of the edit message activity.

To get an edit message activity notification in a bot, you can override OnTeamsMessageEditAsync handler.

The following is an example of an edit message activity notification using OnTeamsMessageEditAsync when a sent message is edited:


protected override async Task OnTeamsMessageEditAsync(ITurnContext<IMessageUpdateActivity> turnContext, CancellationToken cancellationToken) 
{ 
var replyActivity = MessageFactory.Text("message is updated"); 
await turnContext.SendActivityAsync(replyActivity, cancellationToken); 
}

Send a message

To send a text message, specify the string you want to send as an activity. In the bot's activity handler, use the turn context object's SendActivityAsync method to send a single message response. Use the object's SendActivitiesAsync method to send multiple responses.

The following code shows an example of sending a message when a user is added to a conversation:


protected override async Task OnMembersAddedAsync(IList<ChannelAccount> membersAdded, ITurnContext<IConversationUpdateActivity> turnContext, CancellationToken cancellationToken)
{
  // Sends an activity to the sender of the incoming activity.
  await turnContext.SendActivityAsync(MessageFactory.Text($"Hello and welcome!"), cancellationToken);
}

Note

  • Message splitting occurs when a text message and an attachment are sent in the same activity payload. Teams splits this activity into two separate activities, one with a text message and the other with an attachment. As the activity is split, you do not receive the message ID in response, which is used to update or delete the message proactively. It is recommended to send separate activities instead of depending on message splitting.
  • Messages sent can be localized to provide personalization. For more information, see localize your app.

Messages sent between users and bots include internal channel data within the message. This data allows the bot to communicate properly on that channel. The Bot Builder SDK allows you to modify the message structure.

Receive undelete message activity

When you undelete a message, the bot gets a notification of the undelete message activity.

To get an undelete message activity notification in a bot, you can override OnTeamsMessageUndeleteAsync handler.

The following is an example of an undelete message activity notification using OnTeamsMessageUndeleteAsync when a deleted message is restored:


protected override async Task OnTeamsMessageUndeleteAsync(ITurnContext<IMessageUpdateActivity> turnContext, CancellationToken cancellationToken)
{ 
var replyActivity = MessageFactory.Text("message is undeleted"); 
await turnContext.SendActivityAsync(replyActivity, cancellationToken); 
}

Receive soft delete message activity

When you soft delete a message, the bot gets a notification of the soft delete message activity.

To get a soft delete message activity notification in a bot, you can override OnTeamsMessageSoftDeleteAsync handler.

The following example shows a soft delete message activity notification using OnTeamsMessageSoftDeleteAsync when a message is soft deleted:


protected override async Task OnTeamsMessageSoftDeleteAsync(ITurnContext<IMessageDeleteActivity> turnContext, CancellationToken cancellationToken) 
{ 
var replyActivity = MessageFactory.Text("message is soft deleted"); 
await turnContext.SendActivityAsync(replyActivity, cancellationToken); 
}

Update and delete messages sent from bot

Important

The code samples in this section are based on version 4.6 and later versions of the Bot Framework SDK. If you are looking for documentation for earlier versions, see the bots - v3 SDK section in the Legacy SDKs folder of the documentation.

Your bot can dynamically update messages after sending them instead of having them as static snapshots of data. Messages can also be deleted using the Bot Framework's DeleteActivity method.

Note

A bot can't update or delete messages sent by the user in Microsoft Teams.

Update messages

You can use dynamic message updates for scenarios, such as poll updates, modifying available actions after a button press, or any other asynchronous state change.

It is not necessary for the new message to match the original in type. For example, if the original message contains an attachment, the new message can be a simple text message.

To update an existing message, pass a new Activity object with the existing activity ID to the UpdateActivityAsync method of the TurnContext class.

// Send initial message
var response = await turnContext.SendActivityAsync(MessageFactory.Attachment(card.ToAttachment()), cancellationToken);
var activityId = response.Id; // Fetch activity id.

// MessageFactory.Text(): Specifies the type of text data in a message attachment.
var newActivity = MessageFactory.Text("The new text for the activity");
newActivity.Id = activityId;

// UpdateActivityAsync(): A method that can participate in update activity events for the current turn.
await turnContext.UpdateActivityAsync(newActivity, cancellationToken);

Now that you have updated messages, update the existing card on button selection for incoming activities.

Update cards

To update the existing card on button selection, you can use ReplyToId of incoming activity.

To update existing card on a button selection, pass a new Activity object with updated card and ReplyToId as activity ID to the UpdateActivityAsync method of the TurnContext class.

// Returns a message activity that contains an attachment.
var activity = MessageFactory.Attachment(card.ToAttachment());
activity.Id = turnContext.Activity.ReplyToId;

// A method that can participate in update activity events for the current turn.
await turnContext.UpdateActivityAsync(activity, cancellationToken);

Now that you have updated cards, you can delete messages using the Bot Framework.

Delete messages

In the Bot Framework, every message has its unique activity identifier. Messages can be deleted using the Bot Framework's DeleteActivity method.

To delete a message, pass that activity's ID to the DeleteActivityAsync method of the TurnContext class.

foreach (var activityId in _list)
{
    // When overridden in a derived class, deletes an existing activity in the conversation.
    await turnContext.DeleteActivityAsync(activityId, cancellationToken);
}

Send suggested actions

The suggested actions enable your bot to present buttons that the user can select to provide input. Suggested actions enhance user experience by enabling the user to answer a question or make a choice with selection of a button, rather than typing a response with a keyboard. When the user selects a button, it remains visible and accessible in the rich cards, but not for the suggested actions. This prevents the user from selection of stale buttons within a conversation.

To add suggested actions to a message, set the suggestedActions property of an activity object to specify the list of card action objects that represent the buttons to be presented to the user. For more information, see sugestedActions.

The following is an example for implementation and experience of suggested actions:

"suggestedActions": {
    "actions": [
      {
        "type": "imBack",
        "title": "Action 1",
        "value": "Action 1"
      },
      {
        "type": "imBack",
        "title": "Action 2",
        "value": "Action 2"
      }
    ],
    "to": [<list of recepientIds>]
  }

The following illustrates an example of suggested actions:

Bot suggested actions

Note

  • SuggestedActions are only supported for one-on-one chat bots with both text based messages and Adaptive Cards.
  • SuggestedActions aren't supported for chat bots with attachments for any conversation type.
  • imBack is the only supported action type and Teams display up to six suggested actions.

Send messages in Teams channel data

The channelData object contains Teams-specific information and is a definitive source for team and channel IDs. Optionally, you can cache and use these IDs as keys for local storage. The TeamsActivityHandler in the SDK pulls out important information from the channelData object to make it accessible. However, you can always access the original data from the turnContext object.

The channelData object isn't included in messages in personal conversations, as these take place outside of a channel.

A typical channelData object in an activity sent to your bot contains the following information:

  • eventType: Teams event type passed only in cases of conversation events in your Teams bot.
  • tenant.id: Microsoft Entra tenant ID passed in all contexts.
  • team: Passed only in channel contexts, not in personal chat.
    • id: GUID for the channel.
    • name: Name of the team passed only in cases of team rename events.
  • channel: Passed only in channel contexts, when the bot is mentioned or for events in channels in teams, where the bot is added.
  • channelData.teamsTeamId: Deprecated. This property is only included for backward compatibility.
  • channelData.teamsChannelId: Deprecated. This property is only included for backward compatibility.

The following code shows an example of channelData object (channelCreated event):

"channelData": {
    "eventType": "channelCreated",
    "tenant": {
        "id": "72f988bf-86f1-41af-91ab-2d7cd011db47"
    },
    "channel": {
        "id": "19:693ecdb923ac4458a5c23661b505fc84@thread.skype",
        "name": "My New Channel"
    },
    "team": {
        "id": "19:693ecdb923ac4458a5c23661b505fc84@thread.skype"
    }
}

Teams channel data

The channelData object contains Teams-specific information and is a definitive source for team and channel IDs. Optionally, you can cache and use these IDs as keys for local storage. The TeamsActivityHandler in the SDK pulls out important information from the channelData object to make it accessible. However, you can always access the original data from the turnContext object.

The channelData object isn't included in messages in personal conversations, as these take place outside of a channel.

A typical channelData object in an activity sent to your bot contains the following information:

  • eventType: Teams event type passed only in cases of channel modification events.
  • tenant.id: Microsoft Entra tenant ID passed in all contexts.
  • team: Passed only in channel contexts, not in personal chat.
    • id: GUID for the channel.
    • name: Name of the team passed only in cases of (how-to/conversations/subscribe-to-conversation-events.md#team-renamed).
  • channel: Passed only in channel contexts, when the bot is mentioned or for events in channels in teams, where the bot is added.
  • channelData.teamsTeamId: Deprecated. This property is only included for backward compatibility.
  • channelData.teamsChannelId: Deprecated. This property is only included for backward compatibility.

Example channelData object

The following code shows an example of channelData object (channelCreated event):

"channelData": {
    "eventType": "channelCreated",
    "tenant": {
        "id": "72f988bf-86f1-41af-91ab-2d7cd011db47"
    },
    "channel": {
        "id": "19:693ecdb923ac4458a5c23661b505fc84@thread.skype",
        "name": "My New Channel"
    },
    "team": {
        "id": "19:693ecdb923ac4458a5c23661b505fc84@thread.skype"
    }
}

Status codes from bot conversational APIs

Ensure to handle these errors appropriately in your Teams app. The following table lists the error codes and the descriptions under which the errors are generated:

Status code Error code and message values Description Retry request Developer action
400 Code: Bad Argument
Message: *scenario specific		 Invalid request payload provided by the bot. See error message for specific details. No Reevaluate request payload for errors. Check returned error message for details.
401 Code: BotNotRegistered
Message: No registration found for this bot.		 The registration for this bot wasn't found. No Verify the bot ID and password. Ensure the bot ID (Microsoft Entra ID) is registered in the Teams Developer Portal or via Azure bot channel registration in Azure with 'Teams' channel enabled.
403 Code: BotDisabledByAdmin
Message: The tenant admin disabled this bot		 Admin blocked interactions between user and the bot app. Admin needs to allow the app for the user inside of app policies. For more information, see app policies. No Stop posting to conversation until interaction with bot is explicitly initiated by a user in the conversation indicating that the bot is no longer blocked.
403 Code: BotNotInConversationRoster
Message: The bot isn't part of the conversation roster.		 The bot isn't part of the conversation. App needs to be reinstalled in conversation. No Before attempting to send another conversation request, wait for an installationUpdate event, which indicates that the bot is added again.
403 Code: ConversationBlockedByUser
Message: User blocked the conversation with the bot.		 User blocked the bot in personal chat or a channel through moderation settings. No Delete the conversation from cache. Stop attempting to post to conversations until interaction with bot is explicitly initiated by a user in the conversation, indicating that the bot is no longer blocked.
403 Code: ForbiddenOperationException
Message: Bot isn't installed in user's personal scope		 Proactive message is sent by a bot, which isn't installed in a personal scope. No Before attempting to send another conversation request, install the app in personal scope.
403 Code: InvalidBotApiHost
Message: Invalid bot api host. For GCC tenants, call https://smba.infra.gcc.teams.microsoft.com.		 The bot called the public API endpoint for a conversation that belongs to a GCC tenant. No Update the service URL for the conversation to https://smba.infra.gcc.teams.microsoft.com and retry the request.
403 Code: NotEnoughPermissions
Message: *scenario specific		 Bot doesn't have required permissions to perform the requested action. No Determine the required action from the error message.
404 Code: ActivityNotFoundInConversation
Message: Conversation not found.		 The message ID provided couldn't be found in the conversation. Message doesn't exist or it is deleted. No Check if message ID sent is an expected value. Remove the ID if it was cached.
404 Code: ConversationNotFound
Message: Conversation not found.		 Conversation wasn't found as it doesn't exist or is deleted. No Check if conversation ID sent is an expected value. Remove the ID if it was cached.
412 Code: PreconditionFailed
Message: Precondition failed, please try again.		 A precondition failed on one of our dependencies due to multiple concurrent operations on the same conversation. Yes Retry with exponential backoff.
413 Code: MessageSizeTooBig
Message: Message size too large.		 The size of the incoming request was too large. For more information, see format your bot messages. No Reduce the payload size.
429 Code: Throttled
Message: Too many requests. Also returns when to retry after.		 Too many requests sent by the bot. For more information, see rate limit. Yes Retry using Retry-After header to determine backoff time.
500 Code: ServiceError
Message: *various		 Internal server error. No Report the issue in developer community.
502 Code: ServiceError
Message: *various		 Service dependency issue. Yes Retry with exponential backoff. If the issue persists, report the issue in developer community.
503 Service is unavailable. Yes Retry with exponential backoff. If the issue persists, report the issue in developer community.
504 Gateway Timeout. Yes Retry with exponential backoff. If the issue persists, report the issue in developer community.

Status codes retry guidance

The general retry guidance for each status code is listed in the following table, bot must avoid retrying status codes that aren't specified:

Status code Retry strategy
403 Retry by calling the GCC API https://smba.infra.gcc.teams.microsoft.com for InvalidBotApiHost.
412 Retry using exponential backoff.
429 Retry using Retry-After header to determine the wait time in seconds and in between requests, if available. Otherwise, retry using exponential backoff with thread ID, if possible.
502 Retry using exponential backoff.
503 Retry using exponential backoff.
504 Retry using exponential backoff.

Request headers of the bot

The current outgoing requests to the bot don't contain in the header or URL any information that helps bots route the traffic without unpacking the entire payload. The activities are sent to the bot through a URL similar to https://<your_domain>/api/messages. Requests are received to show the conversation ID and tenant ID in the headers.

Request header fields

Two non-standard request header fields are added to all the requests sent to bots, for both asynchronous flow and synchronous flow. The following table provides the request header fields and their values:

Field key Value
x-ms-conversation-id The conversation ID corresponding to the request activity if applicable and confirmed or verified.
x-ms-tenant-id The tenant ID corresponding to the conversation in the request activity.

If the tenant or conversation ID isn't present in the activity or wasn't validated on the service side, the value is empty.

Image shows header fields.

Receive conversation messages with RSC

With the resource-specific consent (RSC) permissions model, conversation owners can allow a bot to receive all user messages in standard channels and chats without needing to be @mentioned. They can give consent during the app installation or upgrade process after the app updates are published. Originally made for Microsoft Teams Graph APIs, the RSC model is now expanded to include bot scenarios. You can enable this by adding the ChannelMessage.Read.Group or ChatMessage.Read.Chat permission strings in your app manifest (formerly known as the Teams app manifest).

Note

Bots that receive all conversation messages with RSC are supported in Government Community Cloud (GCC), GCC-High, and Department of Defense (DOD) environments.

Ensure that the services needing access to all Teams message data use the Graph APIs to get access to archived data in channels and chats. A bot must use the ChannelMessage.Read.Group and ChatMessage.Read.Chat RSC permission appropriately to create engaging experience for users so it can get approved by the Microsoft Teams Store. Additionally, the app description must explain how the bot uses the data it reads. Here are some tips to help you use the RSC permissions correctly for your bot:

  • A bot mustn't use the ChannelMessage.Read.Group and ChatMessage.Read.Chat RSC permissions to pull a large amount of customer data.
  • A bot must be able to get all chat messages using ChatMessage.Read.Chat only after they've been re-installed or newly installed into a chat.
  • If your app uses the ChatMessage.Read.Chat RSC permission for Graph scenarios, ensure that you test the app using the steps in upload a custom app in a conversation and adjust it before the feature is generally available.

If your app uses RSC permissions to receive all channel or chat message, you can:

Receive all channel or chat messages

The ChannelMessage.Read.Group and ChatMessage.Read.Chat RSC permissions are available for bots. With user consent and app installation, these permissions:

  • Enable a specified graph application access all messages in channels and chats.
  • Enable a bot to get all messages without needing to be @mentioned by defining in its app manifest to receive all conversation messages in the relevant contexts where these permissions apply.

If these RSC permissions are defined for a bot in its app manifest, it can receive all messages from a channel or a chat where it's installed. To receive all channel or chat messages, you must:

Update app manifest

For your bot to receive all conversation messages, the relevant RSC permission strings must be specified in the authorization.permissions.resourceSpecific property of your app manifest. For more information, see app manifest.

Screenshot shows the changes to be made in the app manifest.

The following code provides an example of the app manifest:

  • webApplicationInfo.id: Your Microsoft Entra app ID. The app ID can be the same as your bot ID.
  • webApplicationInfo.resource: Any string. The resource field has no operation in RSC, but must be added with a value to avoid error response.
  • authorization.permissions.resourceSpecific: RSC permissions for your app with either or both ChannelMessage.Read.Group and ChatMessage.Read.Chat specified. For more information, see resource-specific permissions.

The following code provides an example of the app manifest version 1.12 or later:

{
    "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.12/MicrosoftTeams.schema.json",
    "manifestVersion": "1.12",
    "version": "1.0.0",
    "id": "8239c8f3-ed78-4512-933e-babfd28856f1",
    "packageName": "com.contoso.rscechobot",
    "developer": {
        "name": "Contoso",
        "websiteUrl": "https://www.contoso.com",
        "privacyUrl": "https://www.contoso.com/privacy",
        "termsOfUseUrl": "https://www.contoso.com/tos"
    },
    "icons": {
        "color": "color.png",
        "outline": "outline.png"
    },
    "name": {
        "short": "RscEchoBot",
        "full": "Echo bot with RSC configured for all conversation messages"
    },
    "description": {
        "short": "Echo bot with RSC configured for all channel and chat messages",
        "full": "Echo bot configured with all channel and chat messages RSC permission in manifest"
    },
    "accentColor": "#FFFFFF",
    "staticTabs": [
        {
            "entityId": "conversations",
            "scopes": [
                "personal"
            ]
        },
        {
            "entityId": "about",
            "scopes": [
                "personal"
            ]
        }
    ],
    "webApplicationInfo": {
        "id": "07338883-af76-47b3-86e4-2603c50be638",
        "resource": "https://AnyString"
    },
    "authorization": {
        "permissions": {
            "resourceSpecific": [
                {
                    "type": "Application",
                    "name": "ChannelMessage.Read.Group"
                },
                {
                    "type": "Application",
                    "name": "ChatMessage.Read.Chat"
                }
            ]
        }
    },
    "bots": [
        {
            "botId": "07338883-af76-47b3-86e4-2603c50be638",
            "scopes": [
                "personal",
                "team",
                "groupchat"
            ],
            "supportsFiles": false,
            "isNotificationOnly": false
        }
    ],
    "permissions": [
        "identity",
        "messageTeamMembers"
    ],
    "validDomains": []
}

Upload a custom app in a conversation

The following steps guide you to upload and validate bot that receives all channel messages in a Team without being @mentioned:

  1. Select or create a team.

  2. Select ●●● from the left pane. The dropdown menu appears.

  3. Select Manage team from the dropdown menu.

    Screenshot shows the managing team option in Teams application.

  4. Select Apps. Multiple apps appear.

  5. Select Upload a custom app from the lower right corner.

    Screenshot shows the upload a custom app option.

  6. Select Open.

    Screenshot shows the open dialog box to select the app package.

  7. Select Add from the app details pop-up, to add the bot to your selected team.

    Screenshot shows the add button to add a bot to a team.

  8. Select a channel and enter a message in the channel for your bot.

    The bot receives the message without being @mentioned.

    Screenshot shows a bot receiving message in a channel.

Receive only at-mentioned messages

To enable you bots to get only those channel or chat messages where your bot is @mentioned, you must filter the messages. Use the following code snippet to enable your bot to receive only those message where it's @mentioned:

    // When ChannelMessage.Read.Group or ChatMessage.Read.Chat RSC is in the app manifest, this method is called even when bot is not @mentioned.
    // This code snippet allows the bot to ignore all messages that do not @mention the bot.
    protected override async Task OnMessageActivityAsync(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)
    {
            // Ignore the message if bot was not mentioned. 
            // Remove this if block to process all messages received by the bot.
            if (!turnContext.Activity.GetMentions().Any(mention => mention.Mentioned.Id.Equals(turnContext.Activity.Recipient.Id, StringComparison.OrdinalIgnoreCase)))
            {
                return;
            }
            // Sends an activity to the sender of the incoming activity.
            await turnContext.SendActivityAsync(MessageFactory.Text("Using RSC the bot can receive messages across channels or chats in team without being @mentioned."));
    }

If you want your bot to receive all messages, then you don't need to filter the @mention messages.

Step-by-step guide

Follow the step-by-step guide to create a Teams conversation bot.

Next step

Channel and group chat conversations with a bot

See also

Conversation events in your Teams bot