01
It reads and decides
Workflows understand operational text instead of relying on brittle keyword lists.
- Pull notes and classify them with Corei
- Branch on the AI's answer, not a fixed rule
- Understand phrasing like "left VM" without a keyword list
Agentic workflows
Plain English in. A working workflow out.
Explain the MSP automation you want as you would to a service coordinator. Corei reads your boards, statuses and fields, drafts the workflow, simulates it, and tells you what it could not build.
38 triggers · 147 steps · Auto, Approval or Notify
Unable to reach client8 steps
01Read ticket note
02Classify appointment
03Send TimeZest link
04Wait and follow up
38 triggers
Tickets, notes and statuses, inbound email, schedules, Radar anomalies, bookings, quotes signed, and deals won can all start a workflow.
147 steps
Read data, write notes and statuses, message people, wait, branch, and classify with AI — a catalog that grows with every integration you connect.
Every action carries a control: Auto, Approval, or Notify.
How it behaves
It thinks, waits, and follows up.
02
It waits for people
Long-running coordination becomes reliable and visible instead of living in someone's memory.
- Wait for a customer reply or a booking
- Ignore out-of-office auto-replies
- Pick back up the moment something changes
03
It chases politely
Follow-up that would otherwise get forgotten happens on a schedule, every time.
- Delay, remind, repeat, then escalate
- Works in any integration you choose
- Every round is logged on the record
Safe by construction
Nothing runs until a person turns it on.
The agent reads your real boards and fields, drafts the workflow, simulates it against real records, and lists anything it couldn't build — instead of faking a step to look complete.
- Corei always produces a draft; a person activates it
- Anything it couldn't build is listed, not faked
- Start on Notify, move to Approval, then to Auto as trust builds
- The agent drafts, simulates, and shows its work before anything ships
Illustrative example
"The client your tech couldn't reach."
A service manager prompts: "When a tech notes they couldn't reach the client, work out what the ticket needs and send a TimeZest link for that appointment type. Note it and set Waiting on Client. If they don't book, remind every two days, three times, then tell the AM. When they book, set Scheduled."
- 01 · TRIGGER
A note is added to a ticket.
- 02 · AI CLASSIFY
Did the tech fail to reach the client? Understands "left VM" without a keyword list.
- 03 · AI CLASSIFY
What does the ticket need — remote, onsite, or a call? Picks the matching TimeZest appointment type.
- 04 · ACT IN TIMEZEST
Creates the scheduling request; TimeZest emails the client a booking link.
- 05 · UPDATE TICKET
Adds an internal note and sets status to Waiting on Client.
- 06 · UNBOOKED
Chases with a reminder email and note every two days, three rounds.
- 07 · ESCALATE
Notifies the account manager in Teams.
- 08 · BOOKED
Sets status to Scheduled and notes the appointment.
What it replaced
- Scanning notes for "unable to contact"
- Choosing the right appointment type by hand
- Logging into TimeZest for a link
- Remembering to follow up three times
- Updating notes and statuses manually
- Noticing when the client finally booked
Illustrative example for demonstration purposes.
Control
You decide how far it goes.
Corei records the reason, checks permissions, and makes the next action visible.
Notify
The workflow reports what it would have done without changing anything.
Approval
Each sensitive step pauses in an inbox for an authorized person.
Auto
Proven steps execute automatically, with every decision and outcome recorded.
Corei · Agentic workflows