AI Agent
Handle repeating requests with your knowledge, policies, flows and customer state. Answer the question, confirm an approved action, or hand off the reason and work so far.
Pronomy handles recurring product questions, cancellations and refunds.
It uses your knowledge, policies, flows and customer state to answer or take approved actions.
When a person is needed, it hands off the reason and work so far.
Real product interface · example refund workflow. Instructions change only after approval; publishing is separate.
Explore the workflow →SKELARGenesis
UMAEF
Grant funding
AWS ActivateMission Possible
Startup & accelerator support
Free your team from repetitive requests. Keep judgment-heavy work with people.
Handle repeating requests with your knowledge, policies, flows and customer state. Answer the question, confirm an approved action, or hand off the reason and work so far.
Check the work. Improve what comes next.
Judge human and AI conversations by one agreed quality standard. Tone, a correct and complete response, required actions and tags, and reply and follow-up timing combine into one result—so your team knows what needs attention.
We set it up together from your flows, policies and agreed criteria.
Find why customers keep asking, so your team can fix the guide, product or process behind the repeat requests.
Your instructions, your voice, your quality standard. See how the pieces fit together.

How do I change what it says?
Tell Pronomy what you want the agent to do differently. See the proposed instructions beside the steps that stay the same, then approve or decline.
Your request becomes a proposal you can inspect.
This refund example changes reply instructions. Routing and actions stay unchanged; nothing is published.
Explore AI Agent →
When should a person take over?
Build the steps, conditions and actions for a recurring request. In this delivery flow, the agent explains available tracking or passes missing tracking to a person.
Handle the expected path. Keep exceptions human.
Shown: the tracking and handoff steps from the delivery Canvas.
Explore the flow builder →
Can it sound like our team?
Choose a starting tone, then add voice instructions and examples. Agent settings also give your team a place to manage languages and escalation rules.
Set the style instead of correcting every answer.
Shown: Friendly tone selected. Add brand-specific instructions in Agent settings.
Explore Agent settings →
Was that actually a good answer?
Evaluate tone, response completeness, required actions and tags, and reply timing. See the criteria behind the result—not just a single score.
Check what was said against what happened.
In this example, the cancellation claim is checked against the recorded renewal result.
Explore Scorecards →
Why do customers keep asking?
Follow recurring questions to the conversations behind them. Separate the evidence from a working hypothesis, then turn it into a concrete improvement.
Fix the source of repeat requests.
Here, questions about skipping a box point to a hard-to-find account control. The proposed change has not been measured.
Explore Analytics →An answer, a follow-up, an action or a person. Choose a request to see the difference.
Scripted examples, not customer results. Actions depend on your connected tools and approved flows. Scores are illustrative.
Zendesk, Intercom and Slack are native integrations. Connect other systems through APIs, webhooks or MCP when the required access is available. We check each workflow’s permissions with you.
With a monthly volume commitment agreed with you.
Pay as you go. No monthly volume commitment.
No seat fees. Scale also includes Analytics and Scorecards for AI conversations.
"I'm not going to sell you a chatbot. I'm going to take the five questions your team answers a thousand times a week, and actually solve them."
Oleksii Liaskovskyi, founder. Start with one recurring request your team knows well. We can work through where the software helps and where a person should stay involved.
