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

# Use case examples

> Copy practical prompts for conversations, Evelin drafts, translations, and Help Center proposals.

Complete [Setup](/mcp/connect) and check the connected workspace first. Replace bracketed placeholders with a real customer or conversation. Ask your AI to find the item first if you do not know its ID.

Credits below refer to Protodesk credits. Your AI provider may charge separately for using its assistant.

## Summarize open conversations

**Access:** Read conversations. **Credits:** No Protodesk AI credits. **Changes:** None.

```text theme={null}
List up to five open conversations in Protodesk. Read their latest messages,
summarize each customer's question, and explain which needs attention first.
Show the conversation IDs. Do not update conversations or send messages.
```

**Expected result:** a short list with a summary and suggested next step for each conversation, or an explanation that no matching conversations were found.

## Understand a customer

**Access:** Read customers and read conversations. **Credits:** No Protodesk AI credits. **Changes:** None.

```text theme={null}
Find the Protodesk customer with email [customer email]. Read their recent
conversations and summarize unresolved questions and recurring issues.
Do not edit their profile or change any conversations.
```

**Expected result:** the matching customer's recent support history, with conversation IDs. If several records match, the assistant should ask which one you mean.

## Suggest a reply with Evelin

**Access:** Read conversations and use Evelin. **Credits:** Uses workspace AI credits under the current credit policy. **Changes:** Creates an AI run and, when appropriate, a private draft; sends no message.

```text theme={null}
For Protodesk conversation [conversation ID], use Evelin to suggest a reply
addressing the latest customer question. Wait for the run to finish, then
show the draft, citations, and any review warnings. If Evelin decides no reply
is needed, explain why. Do not send anything.
```

**Expected result:** an Evelin draft for you to review, or the reason a draft was not produced. A reply is not sent as part of generation.

<Accordion title="How Evelin generation works">
  The assistant starts a run, checks its status, and retrieves the result. Reading the status or result does not start a new generation. If a request times out, it should reconcile the existing run rather than start another chargeable run.

  See the detailed [Evelin workflow](/mcp/evelin) for result types, retries, and credit behavior.
</Accordion>

## Translate a draft

**Access:** Read conversations and use Evelin. **Credits:** Uses workspace AI credits. **Changes:** Creates a translation result; leaves the original draft unchanged and sends nothing.

```text theme={null}
For Protodesk conversation [conversation ID], use Evelin to translate this
draft into Indonesian. Preserve names and links. Wait for the result and
show the translation for review. Do not send or edit any message.

Draft: [paste your draft]
```

**Expected result:** translated text for review. You can replace Indonesian with your intended target language.

To translate a stored message instead, provide its message ID and ask Evelin to translate that message without changing it.

## Propose a Help Center update

**Access:** Read Help Center and propose Help Center content. Read access includes draft articles. **Credits:** Proposal submission uses no Protodesk AI credits. **Changes:** Creates a review proposal; does not change the article yet.

```text theme={null}
Read Protodesk Help Center article [article ID] and its current revision.
Propose a clearer introduction while preserving its factual meaning.
Submit the change as a proposal for human review, and show me the review link.
Do not publish or approve anything.
```

**Expected result:** a proposal and a link to review it in Protodesk. Open the review and inspect the change before approving it.

<Accordion title="What approval changes">
  Approving an update applies it to the existing article. If the article is published, approval changes its live content. Approving a new article candidate creates an unpublished draft.

  The MCP authoring tools cannot approve or publish content. See the [Help Center review workflow](/mcp/review-workflow) for revision conflicts and new article sets.
</Accordion>

## Take actions after review

Reading, drafting, and sending are separate capabilities. To assign a conversation, update a customer, or send a reply, approve the corresponding write permission and give the assistant a specific action and target.

Operational writes can change workspace data immediately. For replies, inspect delivery status after sending; queued does not mean delivered. Use [Available tools](/mcp/hosted-tools) to check permissions and [Troubleshooting](/mcp/troubleshooting#a-request-times-out) to handle uncertain outcomes.


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