microsoft / microsoft/CopilotStudioSamples

Enhancement Request: Custom Chatbot Component with Icon Trigger, Bottom-Left Placement & Closure Button

Open
#290 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
797
Forks
491
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
I'm frustrated by the current implementation of the SharePoint chatbot component, which uses a standard button to open the chat window. Additionally, the chat window appears in a way that blocks the website's navigation, which disrupts user experience.

Describe the solution you'd like
I would like to customize the SharePoint component to improve usability by:

  • Replacing the standard button with an icon (e.g., a chat or comment icon) as the trigger to open the chat.
  • Positioning the chat window in the bottom-left corner of the page so that it does not obstruct the main website navigation.
  • Adding a clear closure button within the chat window to allow users to easily close it.

Describe alternatives you've considered

  • Keeping the standard button but modifying its style: This does not fully address the visual consistency with the rest of the site.
  • Allowing the chat window to open in its default position and be minimized manually: This solution still disrupts navigation, particularly on smaller screens.

Additional context
Integrating these changes would enhance the overall user experience by providing a less intrusive chat option and ensuring that website navigation remains accessible. For reference, many modern chat solutions (like Intercom or Drift) use a similar approach with an icon trigger, bottom-left positioning, and an accessible close function.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the SharePoint chatbot component and its trigger and chat-window entry points. Check how the current button, placement, and close behavior are wired; done means an icon trigger, a bottom-left chat window that does not block navigation, and an accessible close button, including responsive behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.