Keep your helpdesk.We plug in. You migrate nothing.
Your team keeps working where it works. Pronomy reads tickets from your helpdesk and acts in your billing, store and CRM through their APIs. Connect your existing tools through native integrations, APIs, webhooks and MCP.
Access is not one switch.
For each flow, we agree what the agent can read, what it may change and what needs a person. A tool name in a list is not permission to use every feature.
| Access | Example | Confirm before rollout |
|---|---|---|
| Read | Tickets, account details, charges or order state. | Which records are needed, how identity is verified, and which endpoint provides them. |
| Change | Reply to a ticket, refund a charge, update an order. | The exact action, required permission and reliable confirmation of its result. |
| Ask a human | An exception, a disputed charge or an action above the agreed limit. | Who approves, where the request goes, and what context follows it. |
Examples, not a list of granted permissions. Zendesk, Intercom and Slack have native integrations. Other connections depend on the available interfaces and the flow we configure with you. See a refund workflow →
Webhook. API. MCP.Pick whatever your stack already speaks.
These are connection methods, not a guarantee that every action is available. We check the endpoints, permissions and result handling for your flow before rollout.
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>" } } } }
Snippets are illustrative, not our API reference. Field names and URLs are examples. We share the real setup details during onboarding.
Your tools. Connected.Helpdesk, billing, knowledge and your own systems.
"Native" means a dedicated integration. Other systems require a connection through their own interfaces. The actions available depend on your plan, permissions and the endpoints the system exposes.
Helpdesks where tickets live
Billing & commerce where actions happen
Knowledge what the agent reads
Chat & internal where your team talks
Not on the list? Let's check.
Tell us what you need it to do. An API, webhook or MCP server is a starting point; we'll check the specific action and access. Email us the tool and workflow.
Product names are trademarks of their owners. Non-native listings identify systems to assess through their interfaces, not prebuilt connectors or guaranteed support for every action. No partnership or endorsement is implied.
It reads what your team reads.And it tells you where the docs are thin.
Answers come from your sources, not from the open internet. When a question has no good source, the agent says so and hands off. It would rather fetch a person than invent a refund policy. With Analytics, those gaps become a list of docs to write.
- Website URLsHelp center, FAQ, pricing and policy pages
- Static documentsPolicies, playbooks and internal guides you upload
- Predefined responsesYour macros and approved wording, used as-is when required
- Past conversationsHow your best agents actually solved it
- Notion · ConfluenceInternal wikis where the real rules live
- Google DriveDocs and sheets your team keeps up to date
- MongoDBStructured product data, such as plans and feature flags

Morrow Club demo workspace. These four sources are present, but have not been indexed.
No helpdesk yet?Put the agent on your site.
Add Pronomy as a chat widget on your website. Same flows, same actions, same scorecards. When a conversation needs a person, it goes to your team (in Slack, for example) with the full story.
- Says it's an AI assistant, clearly, from the first message
- Replies in the customer's language
- A human is always one message away
The connector is the easy part.Your rules deserve more attention.
Often that's all it takes to connect a helpdesk or an API. You can do it yourself, or we do it for you, free.
Takes longer. Here's why.
- Your policies live in people's heads. "We refund within 14 days" usually comes with five unwritten exceptions.
- Permissions are real decisions. Which refunds can the AI do alone? Which need a person? You decide that, not us.
- "Correct" needs a definition. Scorecards can only grade what you've written down.
- Trust is earned. Shadow mode first, then one live flow, then more.
So we don't hand you an empty form. We read your tickets, docs and policies and pre-fill a draft of your flows for you to confirm. Onboarding is free.
Data and access commitments.
- DPA available before we touch any data
- Your customer data is never used to train models
- Role-based access, human approval for risky actions, full audit log
Questions worth asking.Before another system gets access.
Do we have to switch helpdesks?
What's the difference between "native" and "via API"?
Who does the technical setup?
Will this mess with the setup we already have?
Can the agent act in our own internal admin panel?
What happens if one of our systems is down?
Which channels do you cover?
If part of your stack is a webhook nobody wants to touch, send us the documentation. I’ll tell you honestly whether we can plug in and what the setup would take.