Workflow Builder & Scheduler
Lay out how a job gets done, then let it run on its own.
- Build it visually
- No code required
- Runs on events or a schedule
What a workflow looks like
Each box is one piece of work, and the lines show what happens next. A load offer comes in on the left, two things happen at once, and anything that costs money waits for a person before it goes out.
- Starts here
- Agent
- System lookup
- Decision
- Person approves
Lay out the process once
A workflow is a picture of how a job should get done. You lay out the steps; Emulon runs them in order, every time, without anyone chasing them.
It starts by itself
An email arrives, a call ends, your TMS changes a status, or the clock hits 7 AM. The work begins on its own — nobody has to spot it first.
It handles the exceptions
No two loads are the same. A workflow can take a different path depending on the customer, the price, or the problem, and do several things at once.
It keeps going when something breaks
If a system is slow or down, the workflow waits and tries again. If it still cannot finish, a person hears about it with the full story.
You can change it safely
Saving a change creates a new version. Loads already moving finish the old way, so nothing in progress gets disturbed.
How you build one
Four steps, and no code at any point.
Choose what starts it
Pick the moment the work should begin — an email or a call coming in, a status changing in your TMS, or a time of day.
Add the steps
Drag in the agents and systems that should do the work, in the order you want it done.
Decide where a person steps in
Mark the steps that need someone to approve first — anything involving money, a commitment, or a message to a customer.
Try it, then turn it on
Run it against a load that already happened to see what it would have done. When it looks right, switch it on.
The pieces you build with
No code, no scripting. You pick from the same short list every time.
Any of these can begin the work, and one workflow can use more than one.
Each box on the canvas is one piece of work.
One workflow can cover very different loads.
Some work runs on the clock
The routine jobs that slip when the day gets busy. Set the time and Emulon handles them — in your local time, only during the hours you choose.
When something goes wrong
Systems go down and people stop answering. What matters is what happens next.
Why it matters
This is the layer that turns a set of agents into an operation that runs.
The process stops living in people
How your team covers a load becomes something you can see and edit, instead of knowledge held by your three most senior reps.
Nothing falls through
When a step fails you see it, with what went in and what went wrong — instead of a load quietly slipping off someone's list.
The next one is quicker
The same agents and steps get reused, so your second and third workflow take a fraction of the effort of the first.
See it run on your freight
Bring one process that costs your team too much time. We will show you the same workflow running on Emulon, with the execution trace open.