What to Automate in Your CRM First, and What to Keep Manual

What should a business automate in its CRM first?

Start with internal steps that happen often and follow a rule you can say in one sentence. For most businesses, a sensible order is to assign new leads, remind people to follow up, create the tasks that go with a stage change, escalate tickets at risk, and notify the right person. A mistake in any of these lands on your own staff, who can fix it before a customer notices.

Before you build anything, put each candidate through four questions. If the answer to any of them is no, leave that step manual for now:

Does this happen often enough that building the rule will pay back the time?
Would two of your managers describe the rule the same way?
Is the data the rule depends on filled in reliably?
If the rule fires by mistake, can someone undo it in a minute or two?

What should stay manual in a CRM?

Keep a step manual when the right answer depends on context that a field cannot hold, or when a wrong message would cost you the customer's trust. The software can still gather the details and hand the work to a person who decides.

These cases usually belong with a person:

Discounts and special prices. A rule can send the request to a manager, and the manager approves or refuses it.
Replies to complaints. A rule can open the ticket and alert the owner, and a person writes the answer.
Marking a deal as lost. The rep knows why it was lost, and that reason feeds your reports later.
Moving a large or long-standing account to a new rep. A manager should decide this and tell the customer personally.
Billing errors, contract disputes and payment conversations that have gone past the first reminder.

How should lead assignment and follow-up reminders work?

Give each new lead one named owner as soon as it arrives, along with a dated next step. Those two rules close a familiar gap in sales: a lead that everyone saw and nobody called. Our guide on managing and qualifying leads covers the scoring and stages that sit behind them.

Choose the simplest assignment basis that matches how you sell. Territory suits reps who cover different cities, such as Riyadh and Jeddah or Amman and Baghdad. Product line suits teams where different people sell different things. Taking turns suits a team selling one offer to one market. Whichever you choose, add a fallback owner for leads that match nothing, and find out what your CRM does when a record matches two rules. Also check the field the rule reads: assigning by city fails every time the city is empty, so make that field required on the form first.

Reminders should depend on what has actually happened. A fixed reminder three days after a lead is created nags the rep who already called. HubSpot's documentation explains why this takes some design: an event trigger cannot detect that something did not happen, so you wait, then check with a branch. The examples below use time limits you should adjust to your own sales cycle:

A new lead has no logged call after two working hours: remind the owner.
There is still no call by the next working day: alert the sales manager, who decides whether to reassign it.
A deal has had no activity for 14 days: create a task for the rep to check in or close it.
An offer has had no answer for three days: create a task for the rep to call.

What should happen automatically when a deal changes stage?

A stage change should create the work that stage requires, while a person keeps the decision to move the deal. The rep knows whether the customer really agreed. Once the rep records that, the system can take care of what comes next.

Let automation move a record by itself only when a system event proves the change, such as a signed offer or a received payment. Useful stage rules look like this:

Deal moved to the proposal stage: create a task to send the offer by a set date.
Deal won: create an onboarding task for the delivery team and notify them with the deal details attached.
Deal lost: prompt the rep for a reason, and create a reminder to check back in a few months if the reason was timing.
Offer signed: move the deal forward and tell the owner.

How should ticket escalation and notifications be set up?

Escalate a ticket before its target is missed, and send the alert to one named person who can act on it. An alert that fires after the deadline only tells you what already went wrong. Our guide on SLAs in customer support explains how to set those targets.

A simple ladder suits most support teams. The assigned agent gets a warning first. If the target is then missed, the ticket goes to the team lead. Urgent tickets can skip the first step.

Notifications need the same discipline. Each one should tell someone what they must do now. Staff stop reading alerts when most of them need no action, and then they miss the urgent one too. A few habits keep the volume down:

Alert the owner first, and the manager only after a wait.
Use one channel for each type of alert, so people know where to look.
Move updates that need no action into a daily summary or a report.
Review your alerts every month and delete the ones nobody acted on.

How do you design a simple trigger and action rule?

Write the rule as one sentence before you open the builder: when this happens, if this is true, do this, and stop when that happens. A manager can check that sentence without ever seeing the software. For example: when a ticket is created, if its priority is urgent, assign it to the on-duty agent and notify the team lead, and skip it if someone already owns it.

That sentence contains the parts every rule needs, plus one that people forget:

The trigger is the single event that starts the rule, such as a ticket being created or a deal changing stage.
The condition narrows it down, such as priority being urgent or the city being Jeddah.
The action is the change you want, such as assigning an owner or creating a task.
The stop condition says when the rule should leave the record alone.
The owner is the person who answers for the rule when it misbehaves. Keep a short list of rules with their owners.

What usually goes wrong with automation rules?

Rules tend to fail by repeating or colliding, so check for these before you publish. The examples come from Zendesk and HubSpot documentation, and other tools have their own versions of the same problems:

Endless loops. Zendesk says an automation must contain an action that cancels one of its conditions, or it "will continue to fire in an endless loop". Make sure each rule changes something that stops it matching again.
Chain reactions. Zendesk also notes that actions from one trigger can affect how others fire, and that changes made by automations can cause triggers to run. Check which other rules read the field you are changing.
Timing that is looser than you assumed. Zendesk's automations run every hour, though not always on the hour, so a rule built on them could not promise a 10 minute escalation. Ask your vendor how often timed rules are checked.
Running once when you meant every time. HubSpot enrolls a record only the first time it meets the triggers unless you set up re-enrollment. Decide which behavior you want for each rule.

How do you test an automation before it goes live?

Test on sample records first, then run the rule on real work with a small group, and read the run history before you widen it. A preview alone is not enough, because previews skip parts of a real run.

Find out what your own tool's test covers. HubSpot's test shows whether a record meets the enrollment criteria and previews each action, and it states that "No actual actions will be executed". HubSpot also warns that a record passing the test might still not enroll, for example if it already completed the workflow and re-enrollment is off. Freshworks checks conditions and actions against a sample record, but says the trigger is checked only when the workflow is active.

Work through this checklist:

Try a record that should match and a record that should not.
Try a record with empty fields, such as no city or no phone number.
Try a case where things change during a delay, such as a customer who replies or a ticket that gets resolved while the rule is waiting.
Send customer messages to a staff phone or inbox first, and read them as a customer would.
Release the rule to one team or one product for a week, and look through its runs each day.
Agree who can pause the rule, and repeat a shorter version of this test whenever someone edits it.

How do you avoid automations that annoy customers?

Give every customer-facing automation an exit, so it stops when the customer replies, buys, books or asks you to stop. The messages people resent tend to be the ones that ignore what they just did, such as a payment reminder that arrives an hour after they paid. These habits help:

Check the record again right before sending, because the situation may have changed during a delay.
Set a limit on messages per customer per week across all rules, since separate rules add up.
Send during working hours in the customer's country, and update the schedule if your hours change in Ramadan or on public holidays.
Say who the message is from and how to reach a person.
Keep service messages apart from promotions, so an order update never carries a sales pitch.
Check what happens when a personal field is empty, so nobody receives a greeting with a blank where their name should be.

What rules apply to automated WhatsApp messages?

On the WhatsApp Business Platform, automated messages need opt-in, a route to a person and approved templates outside the 24-hour window. The WhatsApp Business Messaging Policy requires opt-in permission and says businesses "must respect all requests" to block, discontinue or opt out. It allows automation during the 24-hour window as long as you offer "prompt, clear, and direct escalation paths", such as an in-chat transfer to a human agent or a phone number.

Meta's documentation says that once the window closes, you can only send pre-approved templates. Our guide on WhatsApp marketing campaigns goes deeper on campaigns. Meta updates these rules, so check its current pages before launch. Privacy and marketing rules also depend on your country and sector, so confirm yours with a legal adviser before you automate customer messages.

How does Repzo handle this?

Repzo Workstation includes workflow automation with a no-code builder. You drag in one trigger and connect condition, delay and action steps. A condition follows a Yes or No branch, a delay waits minutes, hours or days, and a schedule can run a workflow every hour, day, week or month.

Each step has a Test tab, and a workflow only goes live when you publish it. On the trigger, Find a recent record loads a real sample record. Preview values shows what an action would use, and the documentation states that "Preview never contacts anyone". Conditions and delays cannot be tested alone and are checked during real runs, which is one more reason to pilot with a small group. The documentation also suggests trying larger changes in a sandbox, where emails and messages are captured and never delivered.

Workflows run a published version, so later edits stay in draft until you publish the update. Pause stops new runs, and you can restore an earlier version. The Runs tab and Execution History show each run with its status, and a failed run shows the error.

The pricing page lists workflows in the Pro plan, and every plan starts with a 7-day free trial. If you have a specific rule in mind and want to know whether it fits, ask our sales team.

The public documentation lists these triggers and actions for the jobs in this guide:

Leads and follow-ups: the site lists routing leads and sending follow-ups among the jobs for workflows. A Form Submitted trigger can start them, and activities have Due, Overdue and Reminder Due triggers. Actions include Assign Owner, Create Task and Create Reminder.
Deals: triggers for Stage Changed, Won and Lost. The documentation's own example creates an onboarding task when a deal is won, waits a day, checks the deal type and posts to a team chat channel.
Tickets: triggers for Status Changed, SLA Warning, which fires 15 minutes before a target is missed, and SLA Breached, with Escalate Ticket and Update Ticket actions.
Notifications: Notify User, Send Chat Message, Send Email and Send WhatsApp Template.
Customer exits: Wait Until Event Happens pauses a run until the record hits an event, with separate Happened and Timed out paths, and Opt Contact Out is an inbox action.

Frequently asked questions

How many automations should a small business start with?

One or two. Lead assignment and a follow-up reminder are a good first pair for most sales teams. Run them for a few weeks, fix what breaks, and add the next rule once the team trusts the first ones.

What is the difference between a trigger and a condition?

A trigger is the event that starts a rule, such as a new ticket. A condition is a check made after that, such as whether the ticket is urgent. The trigger decides when the rule looks at a record, and the condition decides whether it acts.

Should an automation reassign a lead if the rep does not respond?

It can, as long as the rep gets a warning first and the team has agreed the time limit. Alerting the manager at that point is often safer, because the rep may be on leave or in the middle of a conversation the CRM does not show.

Can we automate WhatsApp follow-ups to leads?

Yes, for leads who opted in. Outside the 24-hour window you can only send approved templates, and you must honor requests to stop. Add a stop condition so the sequence ends as soon as the lead replies, and pass the conversation to a person.

How do we know an automation is working?

Read the run history for failures in the first week, then watch the number the rule was meant to change, such as time to first call or overdue tickets. Also watch opt-outs and complaints. If those rise after a new rule goes live, pause it and review.

Do we need a developer to build CRM automations?

Usually not for rules like the ones in this guide, as long as your CRM has a no-code builder. Connecting an outside system may need technical help, so ask your vendor before you plan around it.

What to automate in your CRM first, and what to keep manual

The short answer

Key takeaways