Work follows your plan. You see every step.
A request arrives. An AI employee replies, gathers the details and prepares the next action. When approval is needed, CRAIM waits for your decision, then continues.
01 · Build
Set the order of work from request to result
Choose what starts the work, who handles each step and when to pause. For example: a new request, an AI reply, a manager’s approval and a task for the next call.
02 · People
Bring in a person when a decision matters
Add an approval or a task for a manager at the right point. CRAIM keeps the context, waits for completion and moves to the next step.
03 · Runs
See the full work history step by step
See what has been done, how long each step took and whose decision is needed. If something fails, the history shows where it happened and why.
- 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
No - Wait
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
CRAIM keeps the result of each step and continues from the right place. Rules, deadlines and responsibilities stay in one process.
Keeps the rules for work already started
A run executes the graph that was published when it started. Editing the process never rewrites what is already in flight.
Respects your working hours
A wait is counted in your working hours and survives a restart. Nobody receives a message at three in the morning.
Chooses the next step
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.
Before you set up a process.
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.