Need to provide guidance to send a welcome message to user in response to agentInstanceCreated event

[Sunil-Garg]

Description

We dont have any guidance published in our samples and our docs for how an agent can send a proactive message to the user in Teams when the instance is created.

Expected behavior

No response

SDK Version

1.0.0

Language/Runtime

all

OS

all

How to Reproduce

Just create an instance from teams store. The expectation is that the agent shall send a welcome message to the user as a 1:1 chat in teams.

Output

No response

Screenshots

No response

Code of Conduct

• I agree to follow the Microsoft Open Source Code of Conduct.

[github-actions]

[AUTO-TRIAGE] Team Assistant Triage

This issue has been automatically analyzed and triaged.

AI Decision Reasoning: Type: Classified as 'documentation' because the issue highlights the lack of guidance or samples in the documentation for a specific use case.
Priority: Assigned P3 because it is a minor issue that does not affect functionality but improves user understanding and experience.
Copilot: The issue involves updating documentation to provide guidance on sending a proactive message in response to an event. This is a well-scoped documentation task with clear requirements, which is within Copilot's capabilities.
Assignment: Issue is suitable for Copilot automated fix. The issue involves updating documentation to provide guidance on sending a proactive message in response to an event. This is a well-scoped documentation task with clear requirements, which is within Copilot's capabilities.
Labels: Applied labels documentation, P3 based on issue type and priority

Labels and assignee have been applied based on this analysis.

[github-actions]

[AUTO-TRIAGE] Results

Classification: documentation
Priority: P3
Confidence: 95.0%

Recommended Assignee: @copilot

Analysis:
type rationale: Classified as 'documentation' because the issue highlights the lack of guidance or samples in the documentation for a specific use case.

priority rationale: Assigned P3 because it is a minor issue that does not affect functionality but improves user understanding and experience.

copilot rationale: The issue involves updating documentation to provide guidance on sending a proactive message in response to an event. This is a well-scoped documentation task with clear requirements, which is within Copilot's capabilities.

assignment rationale: Issue is suitable for Copilot automated fix. The issue involves updating documentation to provide guidance on sending a proactive message in response to an event. This is a well-scoped documentation task with clear requirements, which is within Copilot's capabilities.

labels rationale: Applied labels documentation, P3 based on issue type and priority

[OK] This issue appears to be Copilot-fixable!

[SUGGESTION] Suggested Approach

1. Add a new section in the docs directory titled Proactive Messaging in Teams and provide step-by-step guidance on how to send a welcome message using the Microsoft Bot Framework SDK. Include sample code snippets for handling the agentInstanceCreated event and sending a proactive Teams message.
2. Update the autoTriage/requirements.txt file to include the botbuilder Python package for Teams bot development, if not already included. This will ensure developers have the necessary dependencies to implement proactive messaging functionality.
3. Create a sample implementation in the src directory, such as src/Samples/ProactiveMessaging.cs, demonstrating how to handle the agentInstanceCreated event and send a welcome message using the Microsoft Bot Framework. Reference the Bot Framework's TeamsActivityHandler class for handling Teams-specific events.
4. Add a unit test in src/Tests/Microsoft.Agents.A365.DevTools.Cli.Tests/Services to verify that the welcome message is sent correctly when the agentInstanceCreated event is triggered. Mock the Teams API to simulate sending the message and validate the behavior.
5. Update the README file to include a link to the new documentation section and briefly explain the proactive messaging feature. Highlight its importance in improving user experience when interacting with the agent in Teams.

---

Generated by TeamAssistant Auto-Triage powered by GitHub Models

[github-actions]

SLA Escalation Alert

This P1 issue has exceeded its SLA threshold.

Metric	Value
Priority	P1
SLA Threshold	48 hours
Time Since Update	63.1 hours
Current Assignees	None

Action: Adding Tech Lead @sellakumaran as assignee for immediate attention.

cc: @ajmfehr

---

Generated by AutoTriage SLA Escalation

[github-actions]

SLA Escalation Alert

This P1 issue has exceeded its SLA threshold.

Metric	Value
Priority	P1
SLA Threshold	48 hours
Time Since Update	48.2 hours
Current Assignees	@sellakumaran

Action: This issue is already assigned to a Tech Lead but remains unresolved.

Escalating to Engineering Manager @ajmfehr for visibility.

Tech Leads: @sellakumaran

---

Generated by AutoTriage SLA Escalation

[github-actions]

SLA Escalation Alert

This P1 issue has exceeded its SLA threshold.

Metric	Value
Priority	P1
SLA Threshold	48 hours
Time Since Update	72.0 hours
Current Assignees	@sellakumaran

Action: This issue is already assigned to a Tech Lead but remains unresolved.

Escalating to Engineering Manager @ajmfehr for visibility.

Tech Leads: @sellakumaran

---

Generated by AutoTriage SLA Escalation

[github-actions]

SLA Escalation Alert

This P1 issue has exceeded its SLA threshold.

Metric	Value
Priority	P1
SLA Threshold	48 hours
Time Since Update	72.0 hours
Current Assignees	@sellakumaran

Action: This issue is already assigned to a Tech Lead but remains unresolved.

Escalating to Engineering Manager @ajmfehr for visibility.

Tech Leads: @sellakumaran

---

Generated by AutoTriage SLA Escalation

[github-actions]

SLA Escalation Alert

This P1 issue has exceeded its SLA threshold.

Metric	Value
Priority	P1
SLA Threshold	48 hours
Time Since Update	71.9 hours
Current Assignees	@sellakumaran

Action: This issue is already assigned to a Tech Lead but remains unresolved.

Escalating to Engineering Manager @ajmfehr for visibility.

Tech Leads: @sellakumaran

---

Generated by AutoTriage SLA Escalation