By Rakibul Hasan, Moonlab
CRM automation means your customer relationship tool does routine jobs for you: creating contacts, assigning leads, sending reminders and nudging deals along. Here are ten workflows that fit most small businesses, with notes on how each works and what can go wrong.
Whatever CRM you use, such as HubSpot, Pipedrive, Zoho or GoHighLevel, the ideas are the same. Features and limits differ by plan, so check your vendor's current documentation. For choosing a CRM, see moonlab.space/guides/choose-crm-small-business.
Before you automate: tidy the basics
Automation multiplies whatever is already there. If your pipeline stages are vague and your data is messy, you will get messy results faster. Agree a short list of deal stages, decide what counts as a qualified lead and make sure each contact has an owner.
Also decide what must stay manual, such as pricing decisions and sensitive conversations. Automation should handle the routine so people can focus on those.
Workflows 1 to 4: capture and respond
These get new leads in and acknowledged.
- 1. Lead capture. Every form, email enquiry or chat creates a contact and a deal, tagged with the source.
- 2. Lead assignment. New leads go to an owner by area, service or rotation, and the owner gets an alert.
- 3. Instant acknowledgement. The lead receives a short confirmation, see moonlab.space/guides/speed-to-lead.
- 4. Duplicate check. Before creating a contact, the workflow searches by email and phone and merges or flags matches.
Workflows 5 to 7: keep deals moving
These stop deals from going quiet.
- 5. Follow-up tasks. When a quote is sent, a task is created for three days later to check in. Templates are in moonlab.space/guides/lead-follow-up-sequence.
- 6. Stale deal alert. A deal with no activity for a set number of days notifies the owner and their manager.
- 7. Stage-based actions. Moving a deal to a stage triggers the right next step, such as sending a booking link or creating a proposal task.
Workflows 8 to 10: after the sale and data care
These cover what happens once a deal closes and keep the CRM useful.
- 8. Won deal handover. A won deal creates a project or onboarding checklist, sends a welcome message and may create an invoice in your accounting tool.
- 9. Review and referral request. A few days after the job is done, the customer gets a request for a review or referral, see moonlab.space/guides/get-more-google-reviews.
- 10. Data cleanup. A scheduled check finds missing phone numbers or emails, inconsistent names and lost deals with no reason, and creates tasks to fix them.
Guardrails that protect your customers
Automation that talks to customers needs limits. Add a rule that stops messages once a customer replies or the deal changes status. Check consent before marketing emails or texts, since rules such as GDPR, PECR and the TCPA apply. This is not legal advice.
Avoid sending several automated messages on the same day, and keep a way for a person to pause automation on a single contact.
How to roll it out
Start with one or two workflows, such as lead capture and follow-up tasks. Run them for two weeks and look at what the logs show. Fix errors, then add the next. Add alerts for failed runs and name an owner for each workflow.
Most CRMs have built-in automation. If you need to connect other tools, an automation platform can help, compared in moonlab.space/guides/zapier-vs-make-vs-n8n.
A worked example: setting up three workflows in a week
Say a small solar installer in Texas uses Pipedrive, HubSpot or a similar CRM, and wants to fix missed follow-ups. Day one: agree the pipeline stages, for example new, contacted, survey booked, quote sent, won and lost, and define what qualifies as a stale deal, such as no activity for seven days. Day two: build lead capture, so every form submission creates a contact and a deal in the new stage, tagged with the source, and assigns it to the next person in a rotation. Day three: add the follow-up task rule, so when a deal moves to quote sent, a task appears for three days later called check in with customer.
Day four: add the stale deal alert, which messages the owner each morning with a list of deals idle for seven days. Day five: test with ten dummy contacts, try odd cases such as a duplicate email and a deal moved backwards, and fix the results. In week two, review the run history and ask the team which automations helped and which annoyed them. Remove or adjust anything nobody uses.
The same approach works whatever tool you use. Keep a one page list of every automation: what triggers it, what it changes, who owns it and when it was last reviewed. When someone asks why a customer got a message, that list is the first place to look, and it stops old automations from running unnoticed after the business changes. Here are the checks to run for every workflow you add.
- Does it have one clear trigger and one clear outcome?
- What happens if the contact already exists?
- What happens if a required field is empty?
- Does it stop when the customer replies?
- Who is alerted when it fails?
- Can a person pause it for one contact?
- Mistake: automating before stages and ownership are agreed.
- Mistake: so many alerts that the team ignores all of them.
What to measure
Track response time to new leads, the share of leads that get a follow-up, how long deals stay in each stage and how many deals are stale. These show whether the automation helps or just adds noise.
If you want help picking and building these, the free audit at moonlab.space/contact is a place to start, and moonlab.space/services/sales-and-leads has more detail.
