# Automations: the system does the routine and shows why

A payment is overdue: a task for the rep and an email to the client. A new inquiry: an owner by rule. Every system action is signed “Automation,” so the record shows who did what.

**In short.** Krokul is a B2B CRM with an automation engine: twelve triggers (a new deal, a stage change, a deal field change including custom fields, a deal inactive for N days, an overdue task, a deal or document date or a contact’s birthday, which is how the system reminds you that a contract ends in N days, a client who hasn’t bought for N months, a client’s segment change, a payment received, an overdue payment, a document created, a document signed by all parties in Vchasno e-document exchange) and fourteen actions (create a task, assign an owner, move a stage, change a deal field, add or remove tags, notify a colleague with text or a template, send the client an email or SMS from a template, change the client’s terms, create a project from the deal, call a webhook or your own integration rule). One rule holds up to ten actions, with conditions on pipeline, source, owner, stage, amount and tag; a field changed by a rule starts the next rule, up to three steps in a chain. Every action is signed “Automation,” the run log shows each time a rule ran and how it ended, and the client never gets the same email twice for the same event. Rules are set up by an implementation partner after a consultation, so the automation follows your process.

**Who it’s for:** B2B companies with repeating steps after the sale; teams where reminders and handoffs depend on people; implementation partners mapping a client’s process.

**Plan:** Available from the Money plan, $149 per month, 1,000 transactions included

## What it looks like without Krokul

1. An invoice has been overdue for a week. The sales rep “remembered to follow up,” the accountant thought the rep had. The client didn’t know about the invoice.
2. The deal was won on Friday. The project was created on Wednesday, because the project manager learned about the win at a meeting.
3. Automations in your previous CRM were set up “just in case,” and they sent emails to clients nobody knew about. Everything got turned off.

## What Krokul does

### Triggers on chain events

A new deal or inquiry, a change of stage or of a deal field, including custom ones, an inactive deal, an overdue task or payment, a payment received, a client who stopped buying or changed segment, a document created or signed by all parties in e-document exchange. A contract ends in N days: a date trigger reminds you ahead of time. The rule knows which deal, task, document or client it fired from.

### Actions that leave a trail

A task with an owner and a due date, an owner assignment, a stage move, a new value in a deal field, tags, a notification to a colleague, a templated email or SMS to the client, new client terms, a project from the deal, a webhook to an external system or a call to your own integration rule. Every action is signed “Automation,” so the record shows the system did it.

### Several actions with conditions

Up to ten actions per rule, with conditions on pipeline, source, owner, stage, amount or tag: a deal over a limit means an approval task for the manager; a payment above a set amount means a notification to the owner. A field changed by a rule starts the next rule, up to three steps, and a rule never starts itself.

### No duplicate emails to clients

The client never gets the same email or SMS twice for the same event, even if the system restarts mid-run. An action that fails doesn’t break the rule’s other actions and is recorded with the reason.

## How it works

1. **The implementation partner maps the process with you** Which events matter, who should get what, what the system does on its own and what it only reminds about. It’s a one- or two-hour consultation, not a week.
2. **Rules are set up** The implementation partner adds triggers, conditions and actions in the rule editor. A rule is turned on for one pipeline or source and tested on a few records.
3. **The system does the routine** An overdue payment: a task and an email. A won deal: a project and a task for the project manager. A signed contract: the deal’s next stage. An inquiry: an owner. People do what requires a decision.
4. **You can see what the system did** The rule’s actions are signed “Automation” on the record, and the run log shows every run: when, on which record and how it ended; entries are kept for 90 days. A rule that does the wrong thing is turned off with one toggle, and that goes into the activity log too.

## Result

- Reminders and handoffs happen on their own, the same day.
- The project manager learns about a won deal the moment it is won, not at a meeting.
- The record shows what the system did and what a person did.

## What’s not included

Krokul has a rule editor (trigger → conditions → actions), and setup comes from an implementation partner, who maps the process with you and adds the rules. Complex business processes with multi-level approvals and branching are the product’s next step. Automations don’t message clients in messengers on your behalf without a template you have approved.
What the engine can’t do yet: notify a role, since notifications go to a specific person; a chain of rules starting rules stops at the third step, and the cut shows in the run log; a field changed by a bulk action doesn’t wake the field-change trigger.

## Questions

### What triggers are there?

Twelve: a new deal (including from an inquiry), a stage change, a deal field change (including custom fields; one field per rule), a deal inactive for N days, an overdue task, a deal or document date or a contact’s birthday (including “the contract ends in N days”), a client who hasn’t bought for N months, a client’s segment change, a payment received, an overdue payment, a document created (with a condition on its type), a document signed by all parties in Vchasno e-document exchange.

### What actions are there?

Fourteen: task, owner assignment, stage move, deal field change (title, comment, amount, discount, source, contact date, expected close date, custom fields), add or remove a tag, a notification to a colleague with text or a template, a templated email or SMS to the client, a change of client terms, a project from the deal, webhook, a call to your own outbound integration rule. Up to ten actions per rule, with conditions.

### Can I turn a rule off?

Yes, with one toggle; turning it off and on is logged too.

### How is this different from automations in a typical CRM?

Besides deal stages, Krokul triggers know about payments, overdue dates, clients who stopped buying, segment changes and signed documents; every action is signed “Automation,” and the run log shows every run. An implementation partner sets them up, so the rules follow your process.

### How much does it cost?

Automations are included in the Money plan, $149 per month. System actions don’t count as transactions, except those that create a new deal, document or payment.

## Tell an implementation partner what annoys you every day

Find a partner in your region, describe three routine tasks, and next week the system will be doing them, with the records showing exactly what it did.

Included in the Money plan.

## Next in the chain

- [Agents and partners register deals themselves](https://krokul.com/en/solutions/agents/index.md)
- [Won the deal? Turn it into a project and track hours against what’s paid](https://krokul.com/en/solutions/projects/index.md)
- [The API covers everything in the interface](https://krokul.com/en/solutions/api/index.md)
- [An AI assistant that sets up the system in plain words](https://krokul.com/en/solutions/assistant/index.md)

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs