MCP PROMPT · COMMS

/inbox-triage

Triage unread customer conversations across channels.

01 · The flow

What the agent does, in order.

  1. 01 Call list_conversations with filter "unread" (or recent, depending on the user's request).
  2. 02 For each conversation, call get_conversation_messages to read the latest exchange.
  3. 03 Categorise: needs reply, needs ticket, can be closed without action.
  4. 04 For "needs reply": draft a response with the user, then call send_whatsapp_message (or send_message for SMS/email).
  5. 05 For "needs ticket": call create_ticket with category + priority + a link back to the conversation.
  6. 06 Summarise: X replied, Y tickets created, Z closed without action.
02 · Tools called

4 typed tools in sequence.

  • list_conversations
  • get_conversation_messages
  • send_whatsapp_message
  • create_ticket

Every tool ships with MCP annotations (title, readOnlyHint, destructiveHint, openWorldHint, idempotentHint). Clients can gate destructive calls before invoking. Full catalog: /server-card.json.

Try this in your agent.

Connect FavCRM to Cursor, Claude, ChatGPT, or any MCP client. Type /inbox-triage in chat. Agent runs the steps in order.

Verified .