Keep your helpdesk.We plug in. You migrate nothing.

Your helpdesk sends us an event when a ticket arrives or changes. We run the flow and answer back through your helpdesk's API.

Best for: getting tickets in from any helpdesk or form.

// example payload, illustrative
{
  "event": "ticket.created",
  "ticket_id": "48213",
  "channel": "email",
  "customer": { "email": "jane@example.com" },
  "message": "I cancelled and still got charged."
}

You describe the endpoints the agent may call: refund, cancel, change plan, update an order. Each one gets its own permission and autonomy level.

Best for: taking real actions in billing, commerce and your own backend.

# action definition, illustrative
name:     refund_charge
method:   POST
url:      https://billing.example.com/refunds
input:    charge_id, amount
success:  status == "succeeded"
autonomy: 4 up to $50, 3 above

If a system already runs an MCP server, point Pronomy at it. Its tools show up as actions, and you allow or block each one.

Best for: internal tools and anything that already has an MCP server.

// generic MCP config, illustrative
{
  "mcpServers": {
    "orders": {
      "url": "https://mcp.example.com/orders",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}