A workflow is a piece of your business's ordinary work: answering support mail, moving a booking, following up a lead, renewing a licence. You write it once as a few steps, and every time it starts, it becomes a case that walks through those steps. Agents do the steps you give them, people do the rest, and nothing reaches a customer that you have not allowed.
Find it under Workflows in the portal's menu. The list shows each workflow, whether it is on, how many cases wait for you, and how many of this month's cases your organization has used.
The sheet
A workflow is written on a sheet that reads like a procedure: what starts it, who it serves, then its steps in order. Each part of a sentence you can change is underlined; choose it, and the choices open below it, each with a small drawing.
Booking help
OnStarts when an email reaches support@calmhands.example. It serves your customers.
Understand
An agent reads the email and finds the booking it is about.
Look up a bookingreadsCan't tell which booking: ask the customerMove the booking
An agent moves it to the time the customer asked for.
Move a bookingchangesWaits for your yesReply
An agent tells the customer what changed.
Reply on the case channelchanges
What the agents should know
We are open 9–18 on weekdays. A booking can be moved free of charge up to 24 hours before.
Each step answers four questions:
- Who does it. An agent, you, someone on your team, the customer (the case waits for their answer), or nobody (the case waits until a date).
- What it does, in your own words: "finds the booking the customer writes about".
- When it is done: "it knows the booking".
- What needs your yes. Nothing, money only, or every change. Money always waits for a person's yes.
An agent's step also lists the tools it may use, such as Reply on the case channel, Send an email, Look up in a list, or your own systems (see Tools). An agent never uses a tool its step does not name.
Paths
A step can't always simply go on. Its paths say what happens then: ask the customer, go to another step, hand the case to another workflow and wait for it, follow a rules table, give the case to you, or close it. The agent picks the path and says why; the case keeps both.
A rules table is a short list of "when … then …" rows, such as your cancellation rules. The agent only finds the facts; the first row that matches decides, and the case shows which row it used. Several workflows can share one table.
What the agents should know
Under the steps, write what every agent on this workflow should know: your opening hours, your tone, what you never promise. Keep it to facts and rules; the steps say what to do.
Start one
New workflow offers three ways to start:
- a sentence: describe the work, and CoRoid drafts the steps using the tools your organization has, naming any it is missing;
- the library: ready-made workflows CoRoid keeps, to adapt to your own. They cover support, the website chat, orders and returns, new leads, meetings, invoices and payments, renewals, receipts and new colleagues. Choose how they start (an email, the website chat, a form, a set time or by hand) to see only those;
- an empty sheet.
You can also import a workflow another organization exported (a
coroid.workflow.v1 file). Every new or imported workflow starts as a
draft; nothing runs until you turn it on.
If one of your workflows could help others, suggest it for the library from its Settings. CoRoid reads every suggestion before it goes on the shelf. The copy holds the steps, what the agents should know, the rules tables and the situations as you wrote them, so take out anything private first. Your cases, tool keys and organization never go with it.
Try it before it runs
Try it runs the draft on a made-up message, or on one of the workflow's saved situations ("a customer paid twice"). A try changes and sends nothing: every change is simulated and every reply is shown, not sent. Situations run again after every change, so you see what a change does before your customers do.
Publish, turn on, change
Publish makes the draft the live revision, with a note about what changed. Then turn the workflow on. While it runs you can keep editing the draft; cases that started keep the revision they started on, and new cases take the new one once you publish it. Every revision is kept, and an older one can be restored into the draft.
Pause stops new cases; cases already running finish.
Where to go next
- What starts a case: email, forms, by hand, another workflow, or a set time.
- Tools: what a step can use, and how to connect your own systems.
- Cases and approvals: the case list, the yes, and steps that earn the right to act alone.
- Limits, data and safety: monthly cases, retention, and the rules that always hold.