SalesTouch Docs
All MCP tools
Submits feedbackFeedback

Submit feedback

feedback_submit

Submit a concrete SalesTouch bug report, feature request, or general feedback to the product team.

When to use it

Send a concrete SalesTouch bug report, feature request, or useful general feedback directly to the product team.

Required scopes
salestouch:use
Execution
Synchronous MCP tool call

Requirements

Choose bug, feature_request, or general_feedback.
Submit one ticket per distinct issue and include enough context to act on it.
Avoid speculative or duplicate reports.

Example

Ask your agent

Submit this SalesTouch feature request: add a dry-run preview before starting a LinkedIn outreach workflow.

Tool arguments
{
  "type": "feature_request",
  "message": "Add a dry-run preview before starting a LinkedIn outreach workflow so I can verify the selected leads and final copy."
}
MCP response envelope
{
  "content": [
    {
      "type": "text",
      "text": "{\n  \"data\": { ... },\n  \"meta\": null\n}"
    }
  ],
  "isError": false
}

Expected: A confirmation containing the new PostHog Conversations ticket id and creation time.

Parameters

typerequired
string

Feedback category: bug, feature_request, or general_feedback.

messagerequired
string

Concrete feedback with enough context for the SalesTouch product team.

Aliases are shown independently because MCP clients send a flat JSON object. Use one alias from each required group, not every alias.

Common errors

invalid_input

Use a supported type and provide a non-empty message within the published limit.

feedback_unavailable

Try again after SalesTouch restores its PostHog Conversations configuration.

feedback_rate_limited

Wait before submitting another feedback ticket.

feedback_submission_failed

Do not retry automatically because the delivery result may be ambiguous.

On this page