Once connected, ask your assistant in plain language. It picks the right tools, so you do not need to know any tool names. Try prompts like these:
File a customer’s request
Say where the request came from. The assistant works through the same steps each time:
- It searches for similar feature requests and shows you each one with its link, track, and vote count.
- It asks whether one of them is a match.
- If you confirm a match, it adds the customer as a voter. If not, it creates a new feature request with a short title and description.
- It writes a private note with the product and the ticket or conversation, the customer’s name and email, what the customer asked for, and a link back.
- It shows you the link to the feature request in the admin.
Customer Oliver Smith (oliver@example.com) wrote in ticket 1042 in NeetoDesk asking for a dark mode. File this in NeetoEngage.
Yes, the second one is the same request. Add Oliver as a voter.
The title and description appear on the public roadmap, so the assistant keeps the customer’s name, email, company, and ticket details out of them. Those go only in the private note, which only your team sees.
Look up votes
Which feature requests has oliver@example.com voted for?
Who voted for the dark mode request?
Tell voters a feature shipped
Mark the dark mode request as done and notify its voters. Attach the “Dark mode” changelog.
The assistant finds the Done track, finds the changelog, and moves the request. Voters get the default “now live” email with a link to the changelog. Ask for a different message if the default does not fit.
Move the bulk export request to In progress and email the voters that work has started.
Post a public comment on the dark mode request saying we are shipping it next week, and email it to everyone who voted.
Public comments are visible to everyone on the roadmap, so do not include customer details in them.
Set up
What is the product name and website in our NeetoEngage settings?
Change the website URL to https://www.example.com.
Ask the assistant to confirm before it creates a request, moves one, or emails voters. Moving a request and commenting with voters notified send email to your customers, and MCP actions affect your live workspace.