delete_canned_reply

Remove a saved support reply from a project's picker. Replies already sent with it are untouched.

Purpose

Take a snippet out of the picker for good. Messages that were sent using it are ordinary messages on their threads and are not affected — a snippet is a template, not a link.

Confirm before calling

There is no undo and no soft delete. Confirm the target canned_reply_id with a human — read it back with get_canned_reply so they see the text they are losing. The tool is annotated destructive so a client can prompt for confirmation.

Emits support.canned_reply.deleted with a snapshot of the snippet taken before it went. Idempotent in the only sense a delete can be: a second call for the same id is RESOURCE_NOT_FOUND, indistinguishable from an id that never existed.

Required ability

support-canned-reply:delete

Input schema

{
  "type": "object",
  "required": ["project_id", "canned_reply_id"],
  "properties": {
    "project_id": {
      "type": "string",
      "description": "UUID of the project the snippet belongs to."
    },
    "canned_reply_id": {
      "type": "string",
      "description": "UUID of the saved reply to remove."
    }
  }
}

Output shape

{
  "data": {
    "canned_reply_id": "5d2f8a71-3c9e-4b06-a8f4-1e7c9d2b6a35",
    "deleted": true
  }
}

The id is echoed as sent. Nothing else about the snippet is returned, so read it first if the text matters.

Example prompts

"Delete saved reply 5d2f8a71-3c9e-4b06-a8f4-1e7c9d2b6a35 from project 7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13 — the refund terms changed."

"Remove the 'Black Friday' snippet now the sale is over."

"Clear out every saved reply that mentions the old bot name." (list, confirm the set with the creator, then delete each)

Failure modes

  • VALIDATION_FAILED — the token's owner is on the project's team but their role lacks the support permission on it.
  • RESOURCE_NOT_FOUNDproject_id names a project the token cannot see, or canned_reply_id is unknown, already deleted, or belongs to another project.
  • AUTHENTICATION_REQUIRED — no authenticated user on the request.
  • TOKEN_MISSING_ABILITY — token lacks support-canned-reply:delete.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request