Processes
The team's playbook, running itself
A process is a graph: an event starts a chain, AI employees and people work as steps, conditions split the path, waits hold it. CRAIM runs it and records every step.
01 · Build
Build the chain from five kinds of step
Trigger, participant, condition, action and wait. There is nothing else to learn: those five describe almost any sales or support playbook you already run on paper.
02 · People
A person is a step, not the end of the automation
Ordinary automation can hand a lead to a human and stop there. Here a person stands in the graph beside the AI: the process waits for their work and carries on by itself.
03 · Runs
Every run is visible step by step
Which node passed, which branch a condition took, how long a step held, and where the process stands right now. If it broke, you see the step and the error — not “run failed”.
- Trigger
New enquiry
A message on any connected channel
- Participant · AI
AI employee · Sales
Answers, qualifies the need, fills in the record
- Condition
Did the customer reply?
Checked against the thread for the life of the run
- NoWait
Hold for 2 days
Counted in your working hours
- Participant · Person
Rep approves the quote
The process waits for their decision, then continues
- Action
Create a task and move the stage
Owner, due date and pipeline stage
What a process does beyond sending messages
Every step runs on the server, records its result and retries on failure. A process survives a service restart without losing the place it stopped at.
Freezes its version at the start
A run executes the graph that was published when it started. Editing the process never rewrites what is already in flight.
Holds a wait properly
A wait is counted in your working hours and survives a restart. Nobody receives a message at three in the morning.
Splits on the customer's reply
A condition looks at whether the customer replied and how a call ended, then sends the run down its branch.
Creates tasks and moves the pipeline
An action changes the deal stage, assigns a task to an owner, sends a message or places a call.
What processes cannot do yet. Straight away
Conditions currently check two things: whether the customer replied and how a call ended. There is no arbitrary branching on deal fields. You cannot describe a process in words either — the graph is built by hand in the editor. Runs start from a single event; there is no batch run across a list.
That is what is in the code today. When the rest lands, it will be described here rather than in a “coming soon” section.