Support tickets

The 3 MCP tools in Support tickets, granted with the support scope under Organisation.

To let an assistant use these tools, grant Organisation on the consent screen, or just Support tickets under its Fine-tune. The scope is support. Read tools work with Read only or Read & write access; write tools only with Read & write.

Your assistant doesn't see these tools straight away. It finds them with search_tools or describe_tools, and runs one with use_tool, passing its name and arguments. Most assistants do this for you: just ask for what you want.

What your assistant is told about this group

Tickets for Subcontext's own support team: file one (written from the conversation, with the page and an account check attached), list them and read the replies.

The descriptions below are the ones your assistant reads, so they're written for it. When a connection covers more than one organisation, the assistant passes org (the organisation's slug, from list_orgs) to say which one.

create_support_ticket

Write File a support ticket with Subcontext

File a support ticket with Subcontext's own support team, for problems you can't fix with the tools (a bug, something only Subcontext can change, an account question). Write it yourself from the conversation: never ask the person to fill in a form. Include what they were trying to do, what went wrong, what you checked (diagnose_account, logs) and what you tried. The page, this conversation and an account check are attached automatically.

Arguments

FieldTypeDescription
title required string One line, e.g. "WhatsApp replies not arriving for Sales Bot"
summary required string What they need, what happened, what you checked and tried
category string One of: "channels", "billing", "integrations", "crm", "insurance", "agents", "account", "bug", "question", "other"
severity string urgent: customers can't be served at all; high: an important part is broken One of: "low", "normal", "high", "urgent"
org string Organisation slug: required when this authorization covers more than one organisation (see list_orgs)

list_support_tickets

Read List support tickets

Support tickets filed with Subcontext's team: yours, or everyone's in the organisation for owners and managers, newest activity first, with status and when a reply is expected.

Arguments

FieldTypeDescription
open_only boolean
org string Organisation slug: required when this authorization covers more than one organisation (see list_orgs)

get_support_ticket

Read Read a support ticket

One support ticket with its conversation with Subcontext's team, by id or reference (SUP-1042).

Arguments

FieldTypeDescription
id required string
org string Organisation slug: required when this authorization covers more than one organisation (see list_orgs)

Stuck, or something missing?

Get in touch and a person on the team will help.

Contact us