web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Making Copilot underst...
Copilot Studio
Suggested Answer

Making Copilot understand which info is for internal use and what info is for client.

(0) ShareShare
ReportReport
Posted on by 8
I'm having the following issue:

Our Copilot has a hard time understanding which info is for client and which info is for the user of the bot (the colleague).
I played around with the mainprompt (Instructions in overviewpage), explicitly stating that some of the articles in the knowlegde base are only relevant for the colleague/user not the client that the user is helping.

The articles itself also each have it stating in the first alinea if it is not relevant for clients and the info may not be shared with that client. Also the same for the knowlegde description of that article.

When trying out the following question, 'what should I do if client can't log into "(client relevant program)"?' or "what should client do if it can't log into "(client relevant program)"?'

The bot might come with a semi-correct answer, based on the client-relevant website, which is also linked to the knowlegde base (and has some instructions for clients in how to go about this issue). But as last step it might say that client could call the IT-desk including number if nothing else works, a number that may not be shared with clients. The IT-desk number is only for internal use, and is only named it the articles that specificly states that the info may not be shared with clients and is not relevant to clients.

How to go about this issue? Or issues like this?

Relevant info: The copilot is in Dutch, so it wont have all the options in Copilot studio as an English-based model.
Categories:
I have the same question (0)
  • Suggested answer
    Artur Stepniak Profile Picture
    1,539 Moderator on at
    Hello,
     
    the best way to achieve that kind of functionality is to switch the knowledge base datasource. I'd suggest you to use Dataverse or SP list and perform a ODATA filter query to filter out any content related to internal department. Otherwise, the agent won't know what's exactly related to the client and what's not as it's probably not stated directly in the docs itself. You could also think about separate agents to avoid the need to complicate the design.
     
    In case of any other questions, let me know. If the answer helped you, mark it, so that others can benefit from it.
     
    Best regards,
     
    Artur Stepniak

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 837

#2
Vish WR Profile Picture

Vish WR 294

#3
Haque Profile Picture

Haque 256

Last 30 days Overall leaderboard