Copilot Feature Gap: No Routing to Legal Resources or Verified Assistance

Open
#14,291 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp

Research direction

No files, tests, or specific entry points are named. Start by locating the Semantic Kernel orchestration entry points used by Copilot and review how external resource links and user guidance are handled. Done requires a scoped implementation plan covering verified legal-resource categories and non-advisory next steps.

Written by the indexing model from the issue text.

Description


Copilot can draft legal documents effectively, but it cannot route civilians to verified legal resources, attorneys, or state‑approved assistance. This creates a workflow gap where users receive high‑quality drafts but no guidance on next steps, leaving them stuck at the moment Copilot could meaningfully help.
Proposal:
Add lightweight “legal workflow support” that does NOT provide legal advice, but DOES provide:

links to state legal aid
links to attorney referral services
links to court self‑help centers
links to government consumer protection offices
links to verified legal information portals
optional “next steps” guidance (non‑advisory)

Why this matters:
This improves access‑to‑justice, reduces user confusion, and aligns with Responsible AI principles. It also prevents misuse by giving users safe, verified pathways instead of leaving them to guess.

Additional context:
I submitted this through the Microsoft Product Feedback Portal as well, but wanted to share it here because Semantic Kernel is central to Copilot’s orchestration


Dominant language
C#
Stars
28.8k
Forks
4.9k
Avg merge
2d 17h
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from microsoft/semantic-kernel

All issues in microsoft/semantic-kernel

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.