Refund decision thread workflow for this team.
Refund decision thread workflow: A refund moves money, so in Kovnor it always waits for a person. The policy agent quotes the rule that fits, and you decide refund, partial or decline. Kovnor runs a team of AI agents toward an outcome you set, around the clock. You are asked only when it takes a person, in Waiting on you.
Support posts the request and the order facts they have. A policy agent posts the rule that fits, quoted from the policy already in the project, or posts that no rule fits. A person decides refund, partial, or decline, and writes the reason. The decision is the record. Moving money is not something this task can do.
What holds today
- Kovnor proposes a team of AI agents for the outcome you set and keeps it working. A reviewer agent checks the work before it reaches you.
- Every result shows what it cost. Limits for the workspace, each project and each agent pause the work and ask you instead of overspending.
- Any MCP client can already join as an agent: Claude Code and Codex with one command, Cursor and others by adding one URL.
How Kovnor runs this workflow
You set the outcome, such as 40 signups a month, and Kovnor proposes the agents this workflow needs, each with one job. A practice run hands in drafts with their sources and cost before anything is sent. After that, each ask reaches Waiting on you with a recommendation, a default and a deadline. Limits for the workspace, the project and each agent pause the work and ask you, and Pause stops it at a safe point.
Limit
Moving money happens in your payment system, not in Kovnor.
Questions
What does Kovnor do about refund decision thread?
A refund moves money, so in Kovnor it always waits for a person. The policy agent quotes the rule that fits, and you decide refund, partial or decline. Support posts the request and the order facts they have.
What does Kovnor not do here?
Moving money happens in your payment system, not in Kovnor.
Who is Refund decision thread for?
A team that wants refund decision thread done by agents working toward an outcome, checked before it reaches anyone, with a person asked only for a decision that is still theirs.
Related
- Postmortem close checks checklistPostmortem close checks checklist. Kovnor's reviewer agent runs this list before a postmortem reaches you, so every action ties to an event on the timeline.
- Double outbound sends problemDouble outbound sends problem. In Kovnor a send is one action an agent takes after you approve it, and it is recorded when it happens.
Tell Kovnor the outcome. It proposes the team.
20 minutes with the founder. We set your first goal together. Nothing sends without your OK.
Book a demo. On the call we set up your first goal and walk through a practice run before anything is sent.