When the history can't answer, it asks one question
Do enterprise refunds always go through Priya, or only above $1K? When past decisions went different ways, org.run shows the right person the evidence and asks one specific question where they already work. The answer becomes a rule, with the answer as its source.
org.run
Direct message
SlackToday
org.runApp10:12
Quick one, Priya. Two enterprise refunds went different ways last month.
$720 refund, HarborlineWent to you
$640 refund, BayfieldHandled by supportDo enterprise refunds always go through you, or only above $1K?
Priya10:14
Only above $1K
org.runApp10:14
Got it. Writing that down.
Enterprise refunds over $1K go through Priya.
How it works
From a gap in the history to a rule it can run
- 01
It finds the gap
Two refunds, same size, same tier, routed to different people. Or a pattern it sees every week that nothing explains. Those are the only things it asks about.
- 02
It picks the person
The question goes to whoever made those decisions or owns the rule, not to a channel. One person, one question.
- 03
It asks with the evidence
The two decisions that disagree, side by side, and a question you can answer in one tap or a short reply, in Slack, Teams or the app.
- 04
The answer becomes a rule
Only above $1K becomes a rule with its scope set and the answer as its source. The rule it was unsure about is corrected, and it stops asking.
Where it asks
A question, not a meeting
Questions arrive where you already answer things, and they wait until you have a moment.
Slack and Teams
A DM with the two decisions that disagree and one-tap answers. Most questions end here, in the time it takes to read them.
The org.run web app
Every open question in one place, with the decisions behind it and the rule it will create or change when you answer.
Week-one onboarding
A short, structured interview with a few key people in the first week: who approves what, which customers are exceptions, what it must never do.
Off your plate
Stop explaining the same thing twice
Every unanswered question about how you work comes back as an interruption. org.run asks once, writes it down and does not ask again.
- Sitting through interviews about how you work
- Filling in a questionnaire about your process
- Answering why this customer is the exception, again
- Explaining the unwritten rule to each new hire
- Being pinged for every edge case
- Reconstructing why a decision went that way
- Settling which of two habits is the real rule
- Writing the rule down after you answered
Built to ask less
Rare, specific and worth answering
Specific, not open-ended
Never tell me about your refund process. Always one question with a yes, a no or a number for an answer.
Evidence attached
The two decisions that disagree, with dates, amounts and who decided, so you can answer at a glance without opening anything.
Routed to the right person
The question goes to whoever made the decisions or owns the rule. Priya gets the refund question. The on-call engineer gets the deploy one.
Rare and batched
Questions are held and sent a few at a time, and only when the history genuinely can't tell it. Most of what it needs it learns from your approvals, edits and rejections.
Week-one onboarding interview
A short structured interview with a few key people covers the big decision rights and the hard stops, so the first runs start on firm ground.
Answers become rules
Each answer becomes a plain-language rule, with the answer and who gave it as its source. Read and edit it later like any other rule.
See Rules and SOPsQuestions about interviews
Rarely. It asks only when past decisions disagree or a pattern has nothing to explain it, and it batches questions rather than sending them one at a time. Most of what it needs it learns from your approvals, edits and rejections.
No. There is a short structured interview with a few key people in week one, covering decision rights and hard stops. Everything else it learns from your history or asks about one question at a time.
Pass it on. You can send the question to someone else from the message itself, and the rule records who answered.
It becomes a rule with your answer as its source, and you as the owner unless you name someone else. You can read and edit it in Rules and SOPs at any time.
Yes. Nothing breaks. Until it is answered, anything that depends on it stops for a person instead of being handled alone.
Early access
Answer once and it writes it down
Connect your tools and see the first questions org.run has for you in week one.
Scoped, auditable and reversible from day one. Your data stays yours.