Cases each month
Each plan includes a number of workflow cases a month. A case counts when it starts work; tries don't count, and neither does a case another workflow hands on.
| Plan | Cases a month |
|---|---|
| Free | 100 |
| Pro | 1,000 for each agent slot |
| Enterprise | as agreed in your contract |
Past the limit, nothing is lost: a new case is kept and held, and the workflow's owner gets an alert. A held case runs when the month starts again, when your limit grows (an added agent slot), or when you give it back by hand, which counts it toward this month. The Workflows list shows how many of this month's cases you have used.
How long cases are kept
Closed cases are kept for as many days as your organization's data retention settings say for workflow cases, then deleted. Owners and admins can also:
- delete one closed case from its panel;
- erase one customer: every case about their address, everywhere, from the Workflows list. Cases still open are stopped without sending anything, and the erasure is recorded without the address.
Customer-facing workflows use an EU-only model profile by default.
Rules that always hold
These hold whatever a workflow says:
- Money waits. A change that moves money always waits for a person's yes, and is never earned away.
- Unverified senders wait. A form, or mail whose sender CoRoid could not verify, can't make a workflow change anything or reply without a person's yes: anyone can claim to be anyone in a form.
- Messages are not instructions. What a customer writes reaches the agent as the case's content, never as orders; a tool's input that CoRoid fills from the case (such as the customer's verified address) can't be overridden by the message.
- Keys stay sealed. The agent never sees a key; calls with one go through CoRoid's credential broker.
- Public forms are capped. A form address takes a limited number of forms each day, so a flood can't run up your cases.
- Replies come from you. Mail goes out only from a domain your organization has verified, signed for that domain.