How Orme OS turns a sales call into an approved recap and follow-up
A brief before the meeting, a recap with the commitments after it, record changes proposed with their evidence, and follow-ups that chase only what was agreed. The meeting loop in Orme OS, step by step.
On this page7
Short answer
Before a meeting, Orme OS prepares a brief a day ahead and refreshes it an hour before. After the call, it matches the transcript to the meeting, drafts a recap with the commitments made, proposes record changes with their evidence and drafts the follow-up email. The deal owner approves, and a follow-up agent tracks only accepted commitments and unanswered threads.
What does Orme OS prepare before a meeting?
#A meeting brief, 24 hours before the meeting and refreshed an hour before it. The brief draws on the deal's emails, earlier calls and the record, and every line in it points to its source, so the seller can open the message or the call excerpt it came from instead of taking a summary on trust.
Where does the call transcript come from?
#From tools a team already uses. Orme OS is built to take transcripts from Zoom and Fireflies, or from a transcript file uploaded by hand, and to match each one to the meeting on the calendar. It does not put a bot of its own into the call.
What is in the recap?
#A short summary, the commitments made on the call, proposed changes to the record, and a draft of the follow-up email to the buyer. The commitments and record changes are proposals, each shown with the lines of the call they came from. Nothing in the recap is saved or sent until the deal owner accepts it.
What happens when the deal owner approves the recap?
#Observed facts, such as the meeting taking place and who attended, are already on the record with their source. Accepted commitments and record changes are written with the approved recap as their source. The follow-up email goes out once the deal owner approves the message itself.
How does follow-up work after the call?
#A follow-up agent watches two things only: commitments someone accepted, and threads that are waiting on a reply. When a due date passes or a thread goes quiet, it raises a nudge. It has no other reason to contact a buyer, so follow-up stays tied to what the buyer agreed to.
Why does this matter for the forecast?
#An accepted buyer commitment with a due date still ahead is one of the conditions for a deal to count as commit in Orme OS. Deals move in the forecast on what the buyer agreed to, and the evidence for it is one click away from the number.