# CRM automation: what to automate, what to keep, and when to use an agent

Migaru, Oct 31, 2026 · Guides

> CRM automation does a CRM’s routine work for you. What to automate first, what should stay with a person, and when a rule beats an AI agent.

**CRM automation** is a CRM doing its routine work by itself: logging emails and meetings, creating and updating records, assigning leads, setting reminders and drafting the next message. Automate the facts and the busywork, keep judgements and anything a customer reads with a person, and save AI agents for work whose steps can’t be written down in advance.

Most teams start the other way round, automating emails before they have automated the record. This guide goes through what to automate, in what order, and where a rule is better than an agent.

## What a CRM can automate

The work falls into seven kinds, roughly in the order they pay off:

- **Capture.** Filing email threads, meetings and calls on the right contacts and accounts, creating a contact when someone new appears, and keeping last-contact dates current. Everything else depends on it.
- **Upkeep.** Summaries of accounts and deals, likely duplicates flagged for merging, company details filled in, and values worked out from other fields, such as a deal’s total from its monthly fee and term.
- **Routing.** Giving a new lead or a form fill an owner, by territory, by turn or by the account it belongs to, and telling them.
- **Tasks and reminders.** A task when a promise comes due, when a deal has gone quiet, or when a deal reaches a stage that needs something done.
- **Messages.** Follow-ups and sequence steps drafted when they come due, and for cold outreach, campaigns sent within set hours and limits.
- **Hand-offs.** Sending a record to another system when something happens to it: a won deal to billing, or a new customer to the team that onboards them.
- **Reporting.** Dashboards counted from live records, instead of a spreadsheet somebody updates on Friday.

## What should stay with a person

Automation is cheap to add, and expensive to trust again once it has got something wrong in front of a customer. Keep these with a person, even when software prepares them:

- **Judgements about a deal.** Stage, value, close date and forecast category. Let software propose a change with its reason, and make accepting it one click, but don’t let it move a deal silently. A forecast built from changes nobody made is one nobody believes.
- **Anything a customer reads, until you trust it.** Start with drafts you approve. Let messages send by themselves only once you have read enough of them, and then only inside limits that stop for a reply, a bounce or an unsubscribe.
- **Merges and deletions.** Two companies with similar names are not always one company. Flag likely duplicates, and let a person merge them.
- **Price and terms.** Discounts, contract terms and anything else that commits the company.
- **Calling a deal lost.** A deal that has gone quiet may only have paused. A rule can flag it; a person should decide it is over.

## Triggers or agents?

There are two ways to automate CRM work, and they suit different jobs.

A **trigger-based automation**, usually called a workflow or a rule, waits for something to happen and then runs fixed steps: *when* a deal moves to Proposal, *if* its value is over a threshold, *then* create a task for the owner’s manager. It does the same thing every time, costs almost nothing to run, and is easy to check. It breaks when the world doesn’t fit the rule: an email from an address it has never seen, a promise made in passing on a call, a deal that is plainly dead but still says Negotiation.

An **AI agent** is given a goal and decides the steps: read this call and turn what was promised into tasks; prepare me for tomorrow’s meetings; find accounts like our best customers and draft a first email to each. It copes with messy input no rule could describe, but it is less predictable, so it needs a source for what it claims and a person to approve what it changes.

- **Use a trigger** when the condition and the action can each be written as a sentence with no “it depends” in it: assign, notify, create a task, set a field, send a record somewhere.
- **Use an agent** when the input is language, such as an email, a transcript or a web page, or when the steps depend on what it finds.
- **Use both** when a rule decides *when* and an agent decides *what*: when a deal reaches Proposal, have an agent draft a summary of it for the owner to check.

[Agentic CRM](https://www.migaru.ai/blog/agentic-crm) goes further into what agents should be allowed to do, rung by rung, and the guardrails that make it safe. [How to use AI in your CRM](https://www.migaru.ai/blog/ai-in-crm) covers the uses of AI beyond automation.

## Six automations to set up first

If you are starting from a CRM nobody updates, this order gets the most back for the least risk:

- **Capture every conversation.** Connect mailboxes, calendars and the call recorder, so threads and meetings are filed on their records. Until this runs, every other automation works from what someone remembered to log.
- **Create contacts and accounts as you meet people.** Matched on email address and web domain, so the same person or company isn’t created twice.
- **Route inbound leads.** A form fill, or a reply asking to buy, becomes a contact on the right account, with an owner who is told straight away.
- **Turn promises into tasks.** “I’ll send the pricing on Thursday” becomes a task due Thursday, linked to the call it was said on.
- **Flag deals that have gone quiet.** A task or a note for the owner when a deal has had no conversation for longer than your usual cycle allows.
- **Draft the follow-up.** When a task with a contact comes due, a draft written from what was promised, waiting for its owner to edit and send.

Notice what isn’t on the list: sending. Turn that on last.

## Common CRM automation mistakes

- **Automating a process nobody follows.** Write the rule after the team agrees how the work is done, not to make them agree.
- **Rules that fight.** Two rules setting the same field, or a rule undoing what a person just changed. Every field should keep a history of what changed it, so you can find out which.
- **Automating on top of bad data.** A rule that routes by industry routes junk if industry is free text. Clean the field, or capture it, first. [CRM hygiene](https://www.migaru.ai/blog/crm-hygiene) covers how.
- **Sending before reading.** A sequence nobody reads sends its worst step to your best prospect.
- **Testing on customers.** Try a new rule where it can’t email anybody: a copy of the workspace, or a test record of your own.
- **A notification for everything.** If every change pings someone, nobody reads the pings. Notify people when something needs them to act.

## How Migaru automates the CRM

Migaru automates the record first, and leaves the judgements and the send button with you.

- **Capture, on every plan:** Gmail or Outlook with its calendar, Slack, and a notetaker for Google Meet, Zoom and Teams. Contacts and accounts are created from the people you email and meet, matched by email address and web domain, and every record’s last and next interaction is worked out from its mail and meetings.
- **Fields, one at a time:** each field is set to fill itself, to suggest a change for somebody to approve, or to be left alone. Summaries are written for you, and a deal’s stage, value and close date are suggested unless an admin changes that.
- **Deals:** opened by itself when someone writes in to buy, or when a company you’ve been talking to is plainly buying, with its owner told why.
- **Tasks and follow-ups:** promises from calls and email become tasks, and once you turn it on, a follow-up is drafted when one comes due and waits in Review, for you to approve into your own drafts.
- **Workflows, on Pro and above:** rules with a trigger, conditions and actions, described in a sentence and read back to you before they are saved. A rule can send a record to an address you set, and every change it makes shows in the field’s history as made by a workflow.
- **Scheduled agent operations, on Pro and above:** written in plain language, beside the skills and knowledge the agent works from, and run by an agent that can read every record and the apps you connect.
- **Website forms, on every plan:** point a contact form, a sign-up or any webhook at an address, and everyone who fills it in becomes a contact at their company’s account.
- **Sending:** follow-ups and sequence steps are drafts. Only Outreach campaigns a person writes and launches, on Growth, send by themselves, inside set hours and daily limits, and a reply, bounce or unsubscribe stops them for that person.
- **Trying it first:** on Enterprise, a [sandbox](https://www.migaru.ai/help/try-changes-in-a-sandbox) runs workflows, operations and the agent on a copy of the workspace, where a rule’s Send to a URL step records what it would have sent instead of sending it.

[How records keep themselves up to date](https://www.migaru.ai/help/how-records-keep-themselves-up-to-date) lists every field it writes or suggests, and [Follow-ups, sequences and Outreach](https://www.migaru.ai/help/follow-ups-sequences-and-outreach) says what it drafts and what it sends.

## Frequently asked questions

### What is CRM automation?

A CRM doing its routine work by itself: logging conversations, creating and updating records, assigning leads, creating tasks and reminders, drafting messages and sending records to other systems. It works best when it automates the facts and the busywork, and leaves judgements, and anything a customer reads, with a person.

### What are some examples of CRM automation?

Filing every email and meeting on the right account, creating a contact when someone new replies, assigning a form fill to an owner, turning a promise made on a call into a task, flagging a deal that has gone quiet, drafting a follow-up when a task comes due, and sending a won deal to the billing system.

### What is the difference between CRM automation and an AI agent?

An automation runs fixed steps when something happens, the same way every time. An agent is given a goal and decides the steps, which lets it handle language such as emails and call transcripts that no rule can describe. Use automations for predictable work, and agents, with a person approving what they change, for the rest.

### What should you not automate in a CRM?

Judgements about a deal, such as its stage, value and close date; merging records and calling deals lost; price and terms; and, until you have read enough drafts to trust them, any message a customer will read. Software can propose all of these, but a person should decide.

### Which CRM automations should you set up first?

Capture of email, meetings and calls first, then contacts and accounts created as you meet people, routing for inbound leads, tasks from promises, a flag for deals that have gone quiet, and drafted follow-ups. Turn on anything that sends by itself last.

---

Canonical page: https://www.migaru.ai/blog/crm-automation
Last updated: 2026-10-31