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

# Examples

> Prompts to try once your assistant is connected to NeetoDesk.

Once [connected](/mcp/connect), ask your assistant in plain language. It picks the right [tools](/mcp/tools), so you do not need to know any tool names. Try prompts like these:

## Triage a queue

> List open tickets in my workspace.

> Show me all open tickets assigned to me, newest first.

> Which of our open tickets are marked high priority?

An OAuth connection answers these within your own permissions, so "assigned to me" and "our
tickets" mean what they would mean in the web app. See
[Authentication](/mcp/authentication).

## Read a ticket

> Show me ticket #42 with its full description.

> List all comments on ticket #42.

> Summarize the conversation on ticket #42 and tell me what the customer is still waiting for.

Tickets can be named by number or by UUID, so `#42` is enough.

## Search

> Find tickets mentioning "refund not received".

> Search our tickets for anything about failed card payments in the last week.

Search covers ticket subjects and the text of their comments, and returns the most recent
matches with a snippet of the text that matched.

## Reply and draft

> Draft a reply on ticket #42 thanking the customer for their patience and asking for their
> order number.

> Add an internal note on ticket #42 saying the payments team is investigating.

A draft is saved on the ticket for you to review and send from NeetoDesk. A reply is published
on the ticket where the customer reads it, and a note stays internal. Neither is emailed to the
customer by the assistant.

## Create and update

> Create a ticket for [customer@example.com](mailto:customer@example.com) with subject "Login issue" and description
> "Customer cannot reset their password."

> Update ticket #42 to resolved and set its priority to low.

> Assign ticket #42 to [oliver.smith@example.com](mailto:oliver.smith@example.com).

## Attach a file

> Attach the image at [https://example.com/printer-error.png](https://example.com/printer-error.png) to ticket #42.

That address is fetched and stored in one step, so it works in any assistant. The address has to
be reachable without a login.

> File a ticket for [customer@example.com](mailto:customer@example.com) about the jammed printer and attach
> \~/Desktop/printer.png.

A file on your own machine takes an extra step: the assistant reserves the upload, sends the
bytes itself, then attaches the result. That needs an assistant that can make an HTTP request of
its own, which a terminal-based one can and a chat-only one cannot. If yours cannot, upload the
file with [`neetodesk attachments upload`](/cli-reference/attachments) and give the assistant the
`signed_id` it prints.

## People

> List the team members in my workspace.

> Invite [sam.smith@example.com](mailto:sam.smith@example.com) to the workspace as an Agent.

> Create a customer for [sam.smith@example.com](mailto:sam.smith@example.com) named Sam Smith.

## Reports

> How many tickets changed status in the last 7 days?

> Show me agent response-time reports for this month.

> Which group had the fastest average resolution time over the last 30 days?

> Summarize our customer satisfaction survey results for July.

## Forms

> List the enabled web forms in my workspace.

## Chain requests together

The tools compose, so a single request can span several of them:

> Find every open ticket about refunds, summarize what each customer is asking for, and draft a
> holding reply on the oldest one.

> Compare this month's agent performance against last month and tell me who improved most.

<Tip>
  Ask the assistant to confirm before it posts a reply, changes a ticket's status, or deactivates a team member. MCP actions affect your live workspace.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.