Draft replies from your editor

This guide shows a typical flow with an assistant in your editor or chat window. You need an API key with conversations:read, help-center:read and conversations:write. See connect an assistant.

The flow

1. Ask for the queue: “List my open Tirver conversations that mention the calendar sync.”
2. The assistant calls list_conversations, then get_conversation for each match.
3. Ask it to check your help center: “Find the article about reconnecting a calendar.”
4. It calls search_articles and quotes what the article says.
5. Ask for a draft: “Draft a reply for the first one, friendly, and link the article.”
6. The assistant calls draft_reply and tells you the draft is saved.

Review and send

The draft is saved as an internal note on the conversation, starting with “Draft reply (from an AI assistant, not sent):”. Open the conversation in Tirver, read the note, then copy it into a reply, change what you like and send it, or ignore it. It is a note, so it is visible to your team only. Nothing reaches the customer before you send a reply yourself.

Good prompts

• Give the tone: “short and warm”, “formal”.
• Ask it to cite the article it used.
• Ask it to flag any conversation it is unsure about instead of drafting.

What the assistant will not do

Through MCP it cannot send a reply, close or assign a conversation, or publish an article. Those stay with your team.