Feature requests

A feature request is an idea on the public roadmap. Customers vote for it, and the team moves it across tracks as work progresses. For fields and response details, see the API reference. Samples on this page use the JSON envelope (--json), which is reproducible across terminals. See Output formats.

File a customer’s request

Use this flow when a customer asks for something and you want it on the roadmap.

Run feature-requests search with the gist of the request and check the matches. Each match shows its admin_url, track and votes_count.
If a match is the same request, run feature-requests add-voter on it. Otherwise run feature-requests create.
Show the request’s admin_url to the person who asked.

The title, the description and comments are public on the roadmap. Never put the customer’s name, email, company or ticket details in them. Those go only in --note, a private note that only the team can see. Write the note with one item per line:

Product and ticket or conversation it came from
Customer name and email
What the customer asked for
Link to the ticket

Required arguments

add-voter, voters, move and comment take one positional argument:

<id> - the feature request’s UUID, or the slug at the end of its admin URL, such as 120-export-roadmap-as-csv.

Search feature requests

This command searches public feature requests by title, description and tags, most relevant first. Run it before filing a request to find a duplicate. Private requests are never returned.

neetoengage feature-requests search --query "export roadmap" --limit 5

Flag	Type	Required	Default	Description
`--limit`	`int`		`0`	Maximum requests to return (default 8, max 15)
`--query`	`string`	Yes		Words to search for

Sample output (--json)

{
  "data": [
    {
      "id": "7c1d4e92-3b58-4f06-a9d1-2e6f8b05c3a7",
      "title": "Export roadmap as CSV",
      "description": "Let admins download the roadmap as a CSV file.",
      "status": "Planned",
      "track": "Planned",
      "votes_count": 14,
      "url": "https://acme.neetoengage.com/feature-requests/120-export-roadmap-as-csv",
      "admin_url": "https://acme.neetoengage.com/admin/feature-requests/120-export-roadmap-as-csv",
      "created_at": "2026-09-02T10:15:30Z"
    }
  ],
  "breadcrumbs": [
    { "label": "Add voter", "command": "neetoengage feature-requests add-voter <id> --customer-email <email> --note <note>" },
    { "label": "Create", "command": "neetoengage feature-requests create --title <title> --description <description> --customer-email <email> --note <note>" }
  ]
}

status is null when the request’s track has no public lane, so rely on track. The command returns one list with no pagination block. For fields and response details, see the API reference.

Create a feature request

This command creates a feature request. The customer becomes its first voter and the note is saved as a private team note. Search first with feature-requests search so you do not file a duplicate.

neetoengage feature-requests create \
  --title "Export roadmap as CSV" \
  --description "Let admins download the roadmap as a CSV file." \
  --customer-email sam@example.com \
  --customer-name "Sam Smith" \
  --note "Support ticket 4821 in NeetoDesk. Sam Smith, sam@example.com. Asked for a CSV export of the roadmap. https://acme.neetodesk.com/tickets/4821"

Flag	Type	Required	Description
`--customer-email`	`string`	Yes	Email address of the customer who asked for it
`--customer-name`	`string`		Full name of the customer who asked for it
`--description`	`string`	Yes	Short description of the request. Shown publicly.
`--note`	`string`	Yes	Private note for the team. Customers never see it.
`--title`	`string`	Yes	Short title of the request. Shown publicly.

Sample output (--json)

{
  "data": {
    "feature_request": {
      "id": "7c1d4e92-3b58-4f06-a9d1-2e6f8b05c3a7",
      "title": "Export roadmap as CSV",
      "url": "https://acme.neetoengage.com/feature-requests/120-export-roadmap-as-csv",
      "admin_url": "https://acme.neetoengage.com/admin/feature-requests/120-export-roadmap-as-csv",
      "status": null,
      "track": "Requested",
      "votes_count": 1,
      "created_at": "2026-09-02T10:15:30Z",
      "tag_number": 120
    }
  },
  "breadcrumbs": [
    { "label": "Voters", "command": "neetoengage feature-requests voters <id>" }
  ]
}

For fields and response details, see the API reference.

Add a voter

This command adds a customer as a voter on an existing feature request and attaches a private note. If the customer already voted, no second vote is added.

neetoengage feature-requests add-voter 120-export-roadmap-as-csv \
  --customer-email oliver@example.com \
  --customer-name "Oliver Smith" \
  --note "Support ticket 4833 in NeetoDesk. Oliver Smith, oliver@example.com. Also wants a CSV export. https://acme.neetodesk.com/tickets/4833"

Flag	Type	Required	Description
`--customer-email`	`string`	Yes	Email address of the customer who asked for it
`--customer-name`	`string`		Full name of the customer who asked for it
`--note`	`string`	Yes	Private note for the team. Customers never see it.

Sample output (--json)

{
  "data": {
    "feature_request": {
      "id": "7c1d4e92-3b58-4f06-a9d1-2e6f8b05c3a7",
      "title": "Export roadmap as CSV",
      "url": "https://acme.neetoengage.com/feature-requests/120-export-roadmap-as-csv",
      "admin_url": "https://acme.neetoengage.com/admin/feature-requests/120-export-roadmap-as-csv",
      "status": null,
      "track": "Requested",
      "votes_count": 2,
      "created_at": "2026-09-02T10:15:30Z"
    },
    "vote_registered": true,
    "already_voted": false
  },
  "breadcrumbs": [
    { "label": "Voters", "command": "neetoengage feature-requests voters 120-export-roadmap-as-csv" }
  ]
}

For fields and response details, see the API reference.

List voters

This command lists the customers who voted for a feature request, newest vote first.

neetoengage feature-requests voters 120-export-roadmap-as-csv --page-size 50

Flag	Type	Required	Default	Description
`--page`	`int`		`0`	Page number
`--page-size`	`int`		`0`	Items per page (max 100)

Sample output (--json)

{
  "data": [
    { "name": "Oliver Smith", "email": "oliver@example.com", "voted_at": "2026-09-03T08:42:11Z" },
    { "name": "Sam Smith", "email": "sam@example.com", "voted_at": "2026-09-02T10:15:30Z" }
  ],
  "pagination": {
    "current_page_number": 1,
    "total_pages": 1,
    "total_records": 2,
    "page_size": 50
  }
}

For fields and response details, see the API reference.

Move a feature request

This command moves a feature request to another track. Run tracks list to find the track ID, and changelogs list to find a changelog to attach. Add --notify-all-voters to email every voter about the move.

neetoengage feature-requests move 120-export-roadmap-as-csv \
  --track-id 5b8e2a64-1f07-4c93-b6d2-9a4e7c310f58 \
  --changelog-id c3a91f70-6d24-4e8b-8f15-2b7d0e49a6c1 \
  --notify-all-voters

Flag	Type	Required	Default	Description
`--changelog-id`	`string`			ID of a changelog to attach to the feature request
`--message`	`string`			HTML body of the status update email. Defaults to the “now live” announcement.
`--notify-all-voters`	`bool`		`false`	Email the status update to every voter
`--track-id`	`string`	Yes		ID of the track to move the feature request to

Sample output (--json)

{
  "data": {
    "feature_request": {
      "id": "7c1d4e92-3b58-4f06-a9d1-2e6f8b05c3a7",
      "title": "Export roadmap as CSV",
      "url": "https://acme.neetoengage.com/feature-requests/120-export-roadmap-as-csv",
      "admin_url": "https://acme.neetoengage.com/admin/feature-requests/120-export-roadmap-as-csv",
      "status": "Done",
      "track": "Done",
      "votes_count": 14,
      "created_at": "2026-09-02T10:15:30Z"
    }
  }
}

To tell voters a feature shipped, move the request to the done track with --notify-all-voters, and pass --changelog-id when there is a changelog. --message replaces the default “now live” email body. For fields and response details, see the API reference.

Comment on a feature request

This command posts a public comment on a feature request. Add --notify-all-voters to email the comment to every voter. Keep customer details out of public comments.

neetoengage feature-requests comment 120-export-roadmap-as-csv \
  --content "We are starting on this next sprint." \
  --notify-all-voters

Flag	Type	Required	Default	Description
`--content`	`string`	Yes		Text of the comment. Shown publicly.
`--notify-all-voters`	`bool`		`false`	Email the comment to every voter

Sample output (--json)

{
  "data": {
    "comment": {
      "id": "e4d27b13-8a60-4f59-9c3e-1d5a0b82f7c6",
      "content": "We are starting on this next sprint.",
      "created_at": "2026-09-10T09:30:00Z"
    },
    "feature_request": {
      "id": "7c1d4e92-3b58-4f06-a9d1-2e6f8b05c3a7",
      "title": "Export roadmap as CSV",
      "url": "https://acme.neetoengage.com/feature-requests/120-export-roadmap-as-csv",
      "admin_url": "https://acme.neetoengage.com/admin/feature-requests/120-export-roadmap-as-csv",
      "status": "Planned",
      "track": "Planned",
      "votes_count": 14,
      "created_at": "2026-09-02T10:15:30Z"
    }
  }
}

For fields and response details, see the API reference.

Getting started

Commands

File a customer’s request

Required arguments

Search feature requests

Create a feature request

Add a voter

List voters

Move a feature request

Comment on a feature request

​File a customer’s request

​Required arguments

​Search feature requests

​Create a feature request

​Add a voter

​List voters

​Move a feature request

​Comment on a feature request

File a customer’s request

Required arguments

Search feature requests

Create a feature request

Add a voter

List voters

Move a feature request

Comment on a feature request