> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap & Updates

> Where feature requests go — post an idea, vote on someone else's, and see what shipped

**Roadmap & Updates** is Neo's public feedback board. It is where feature requests belong: you post an idea, other MSPs vote on it, and the team works from what the votes say.

Click **Roadmap & Updates** at the bottom of the dashboard's left-hand menu — the same group as Documentation and Discord. That link signs you straight in, so there is no second password. The board also lives at [feedback.neoagent.io](https://feedback.neoagent.io), but going there directly means signing in again.

## What goes where

A feature request and a support issue are different things, and they go to different places.

| You want to say                                 | Where it goes                                                                   |
| ----------------------------------------------- | ------------------------------------------------------------------------------- |
| "Neo can't do X yet — please build it"          | **Roadmap & Updates.** Post it, and other MSPs can vote                         |
| "Neo does X, but it's doing it wrong"           | **Support.** Ask your Neo Support Agent, or your support chat                   |
| "This is broken and it's blocking us right now" | **Support**, and say it's blocking                                              |
| "What shipped recently?"                        | The [changelog](https://feedback.neoagent.io/changelog), also on the same board |

A support ticket is for something that is broken. Putting a feature request in one hides it from the people who would vote for it, so it belongs on the board instead.

<Note>
  If something is both — a missing feature that is also blocking live work today — do both. Post the request on the board so it gets votes, and raise the blockage with support so someone looks at it now.
</Note>

## Asking the Neo Support Agent for a feature

When you ask your [Neo Support Agent](/chat-agents/neo-support-agent) for something Neo cannot do yet, it will:

1. Tell you plainly that Neo can't do it today, and explain the limit.
2. Point you at Roadmap & Updates, and suggest you search the board first — someone may have asked already.
3. Offer you a short write-up you can paste straight into the post.

It will **not** open a support ticket for a feature request. If it does open a support ticket for you — because something is broken or blocking — it will call it a support ticket, not a feature request.

## Writing a post other MSPs will vote for

The people reading your post are other MSPs deciding whether they have the same problem. Write it for them:

* **What you were trying to do.** The job, not the screen.
* **What happens instead.** Including the part you have to do by hand.
* **Why it matters to your team.** How often it bites, and who it costs.

Keep it short and keep it in plain words. You do not need to name settings, fields or workflow numbers — if the team needs that detail, they will ask.

<Note>
  **Search before you post.** A vote and a comment on an existing request carry further than a second copy of it, because the votes stay on one post instead of splitting across two.
</Note>

## What happens to your post

The team reads the board and works from it. When a request ships, it appears in the [changelog](https://feedback.neoagent.io/changelog), and everyone who voted on the post is notified — so you find out without having to check back.