contact_supermetrics
Send feedback, create a support ticket (only when the user authorizes it), submit a sales enquiry, or reply to an existing ticket. For a common problem, first call supermetrics_guide and try the relevant steps before opening a ticket. Only ticket if that does not resolve it or it needs staff action (non-self-serve plan changes or a genuine bug). Cancelling a trial or an online subscription is not a ticket: use the cancel_trial guide. If you ticket, note which guide was tried and what still failed. When you create a support ticket, always set "category" to the option that matches the user's issue (authentication, billing, subscription, data discrepancy, or query help). For product feature requests, you can also point users to the public wishlist at https://wishlist.supermetrics.com, where they can submit and vote on ideas. Before a ticket or sales enquiry about buying or pricing, call supermetrics_guide(mode="pricing_and_purchasing"); standard plans are bought online at https://supermetrics.com/pricing. Only submit a sales enquiry for special needs: many data sources, data source accounts, users, Supermetrics API access (custom connector or API key), or other custom requirements. Only the user's own tickets are accessible, and only post a reply when the user explicitly asks. Before creating a support ticket, first call get_support_tickets to list the user's existing tickets and check whether an open one already covers the same issue. If it does, add to that ticket with type "ticket_reply" instead of creating a duplicate; only create a new ticket when none of the open tickets match.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"type": "<type>"
},
"name": "contact_supermetrics"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | feedback, support, sales, or ticket_reply (post a follow-up to an existing ticket) | |
| ds_id | No | Related data source ID (e.g. 'FA', 'AW') | |
| company | No | Company (required for sales) | |
| country | No | Country (required for sales) | |
| message | No | Detailed description with span IDs (feedback/support/sales), or the reply body (ticket_reply) | |
| subject | No | Brief summary (required for feedback/support/sales) | |
| category | No | Support ticket category (support only). Pick the one that matches the user's issue: category_authentication_issue (login, token or permission errors, reconnecting a data source); category_help_with_the_queries (query or transfer errors; the fallback when nothing else fits); category_data_discrepancy (missing or mismatching data); category_manage_subscription (data sources, destinations, users, trials, plan changes); category_manage_billing (invoices, payments, VAT) | |
| industry | No | Contact's industry. Used when type is 'sales' | |
| lastname | No | Last name (required for sales) | |
| firstname | No | First name (required for sales) | |
| ticket_id | No | Zendesk ticket ID to reply to (ticket_reply) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| error | No | ||
| notes | No | ||
| success | Yes | ||
| business_context | No |