Microsoft Teams App

​

Overview

​

Installation

1. Upload the app manifest file (requires a user with permission to submit apps).
2. Admin approval and publishing (performed by a Microsoft Teams administrator).

​

Step 1: Upload the App Manifest File

1

Open Microsoft Teams

• Open the Microsoft Teams app.
• Click on the Apps button on the left sidebar.

2

Go to Manage your apps

• In the Apps menu, scroll down and select “Manage your apps”.

3

Upload the App

• Click on “Upload an app” at the top of the page.

4

Submit the app

• In the Honeydew app, go to Settings → Microsoft Teams (requires admin permissions) and click Download Microsoft Teams app package to download the manifest package zip file.
• Select “Submit an app to your org” to send it for IT admin approval and upload the app manifest file.

If your organization uses a single-tenant dedicated deployment and Microsoft Teams is not available in your Honeydew settings, contact Honeydew support at support@honeydew.ai.

5

Confirm Submission

• A confirmation message will appear: “Request submitted to your admin”.
• Click “View your requests” to check the status of your submission.

​

Step 2: Admin Approval & Publishing

1

Open Microsoft Teams Admin Center

• Go to the Microsoft Teams Admin Center.
• Sign in with an admin account.

2

Navigate to Manage Apps

• In the left sidebar, expand “Teams Apps” and click “Manage apps”.

3

Find the Honeydew App

• Use the search bar to find Honeydew.
• The app will be listed under Pending Approval.

4

Select the App

• Click on Honeydew to open its details page.

5

Publish the App

• Click “Publish” to approve and deploy the app to your organization.

• A confirmation message will appear—click “Publish” again to finalize.

6

Verify App Availability

• Once published, the app will be available in Microsoft Teams for users in the organization.

​

Configuration

​

Authentication Methods

​

Configuration Steps

1. Send honeydew-config to the bot and click Configure Settings (or Edit Configuration) to open the form.
2. Fill in the following details:
   • Authentication Mode: Choose OAuth Only, Hybrid, or API Key Only (see above).
   • API Key (Optional): Leave blank to use OAuth. Enter your API key to use API Key authentication.
   • API Secret (Optional): Required only if API Key is set. Leave blank for OAuth.
   • Workspace: The Honeydew workspace the bot connects to (required).
   • Agent (Optional): Leave blank to enable agent routing. Enter a specific agent name to use that agent for all conversations.
   • API Key Channels: Used only in Hybrid mode. Comma-separated channel IDs that use API key authentication; all other channels use OAuth.
3. Click Save. A confirmation message appears showing the updated settings.

​

Prerequisites

​

Usage

​

Direct Conversations

​

Conversations in a Channel

​

Logout (OAuth Mode Only)

​

Agent routing

• Single match: routes to that agent automatically.
• Multiple matches: asks which agent to use.
• No match: replies that no configured agent fits the question.

​

What the router considers

• description and AI context — the primary signals. The description frontmatter field and the agent’s AI context (the Markdown body) are equally weighted: both should precisely describe what data, topics, or business area the agent covers, from the user’s perspective.
• sample_questions — example questions the agent is designed to answer. These are the most direct routing hint: the closer a user’s question resembles a sample question, the more confidently the router picks that agent.
• domain — the domain the agent is connected to, which provides additional topical scope.

​

Writing effective agent metadata

---
description: Analyzes sales pipeline, deal stages, and revenue forecasts for the sales team
sample_questions:
  - What is the current pipeline value by stage?
  - Which deals are at risk of slipping this quarter?
  - Show me revenue forecast vs. actuals for Q2
---

This agent covers sales performance analysis: pipeline health,
deal progression, win/loss trends, and revenue forecasting.
Use it for questions about the sales team's targets and actuals.

​

Tips

• Write description from the user’s perspective, not the data model’s. “Analyzes sales pipeline” is more useful than “accesses the orders domain.”
• Make sample_questions representative of what real users will ask, not just technically valid queries.
• When two agents cover adjacent topics, make their descriptions distinct enough to avoid ambiguous routing. The router will surface both as choices when it cannot differentiate between them.

​

Useful Tips

1. Treat it as a conversation: Sometimes AI will need additional context to answer well. Use follow-up questions to narrow down the data.
2. Ask detailed questions: The more context you provide in your question, the better the bot can understand and provide accurate answers.
3. Ask for possible values before asking to filter: If you asked for data with filter and the bot returned nothing, a common root cause is that the database values don’t match you filter. When that happens, instead first ask for the values in that category and then ask for the filtering as a follow-up question - when the bot sees the data first, it can construct much smarter filtering.
4. Provide hints: If you get an unexpected or incomplete answer, ask again, and provide some additional information or context, or point out what was missing in the previous answer.
5. Break very complex questions into few steps: If your question is very complex, ask it in steps and gradually make a journey through the data by adding context.

​

Support