Workflows
Your procedures, run by AI agents
Write how your team handles support, orders or bookings as a list of steps. AI agents run each case. A person approves what matters.
- Starts by itself
- An email, a form on your site, a schedule or a person starts a case.
- 100 cases a month on Free
- On Professional, 1,000 a month for each agent slot.
- Payments always wait
- No workflow spends money without a person's yes.
Write it the way you would explain it
A workflow is a numbered list of steps in plain sentences. Each step says what the agent does and which tools it may use.
- Add an “If…” path for each exception: ask the customer, hand it to a person or go to another step.
- Tell the agents what they should know, such as prices, opening hours or your tone.
- Try it with a made-up message before you publish.
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.
Cases start where your work arrives
Each email, form entry or scheduled start becomes a case. It runs from the first step until it closes.
- Forward your support address to the workflow's own email address.
- Put a form on your site, or start a case every day, week or month.
- Start one by hand in the portal, from the CoRoid MCP server or from another workflow.
An email arrives
Someone sends a form
You start it
Another workflow
At a set time
A case
It walks through the steps, one customer or one date at a time.
Tools that fit your business
A step uses tools to look things up and to get things done.
- Built-in tools reply by email, read your help pages, look up your lists and file a work request.
- Connect business apps such as Stripe, HubSpot, Zapier or Make.
- A tool is missing? CoRoid can build it for you as a task.
CoRoid's own
- Reply on the case channelchanges
- Ask the customerchanges
- Help pagesreads
Business apps
- Gmail: Send email (Zapier)changes
- Stripe: Create a refundmoney
- HubSpot: Find a contactreads
Your MCP servers
- find_orderreads
- cancel_orderchanges
Your own APIs
- Find a bookingreads
- Move a bookingchanges
Lists
- Look up in Partnersreads
- Add to Leadschanges
Money waits
A tool that moves money always waits for a person's yes, whatever the step says.
You decide what needs a yes
Choose which steps wait for a person. A step that spends money always does.
- Approve, edit or answer instead, in the portal or through MCP.
- After 20 approvals in a row without a change, CoRoid suggests that the step acts alone.
- Even then, 1 case in 10 still asks, so you keep seeing its work.
Your yeses to “Move a booking” in Move the booking
20 in a row, none edited
Offered
It may run by itself from now on.
An owner turns it on
Runs by itself
About 1 in 10 of its changes still asks you, at random.
Back to counting
An edit or a no to one, or a change to the step, and it asks every time again.
Always asks: anything that moves money, anything for a sender whose address isn't verified, and anything while the Mandate is paused.
Every case on one page
See what arrived, what each step did and what waits for you.
- The list of cases opens on the ones that need you.
- A reply to the same email joins its case.
- A situation that no path covers is flagged, so you can add the path.
Anna wants to move her massage
Waits for youAnna wrote
Can I move my massage on Thursday to Friday afternoon?
- Understand: found booking B-4711, Thursday 14:00.
Move the booking
Prepared: move Anna's massage to Friday 15:30.
ApproveInstead…Take over- After your yes, the booking moves and Reply tells Anna.
Built for public forms and inboxes
Anyone can write to a form or an email address. Every workflow has limits, so floods and tricks do not reach your data or your bill.
- Flood limits
- Each workflow and each organization has a daily cap. Each sender has a limit per 10 minutes.
- Screened text
- Customer text is checked for prompt injection. Flagged text waits for a person.
- Unknown senders
- A reply to a sender whose address is not verified waits for your yes.
- Honest replies
- Replies say that AI helped write them. This is on by default.
CoRoid answers its own support this way
Mail to support@coroid.ai and the contact form on this site start cases in CoRoid's own workflows.
Try the contact formUnderstand
An agent reads the message and our help pages.
Answer
It drafts the reply. A person approves it before it goes out.
File a bug
A bug report becomes a task for the factory, and the customer hears back.
Included in every plan
Cases are counted per month. Model calls are billed like the rest of the agents' work.
- Free
- 100 cases a month
- Professional
- 1,000 cases a month for each agent slot
- Enterprise
- By contract, 10,000 a month by default
Past the limit, new cases from email and forms are kept. They start when the next month begins or when you add an agent slot. Try it runs and the cases one workflow starts for another do not count.
See pricingWrite your first workflow today
Start on the Free plan, with 100 cases a month.