CRM workflow: how to build one, with practical examples

Saved work

A new inquiry lands in your CRM, and two people assume the other person will respond. You discover it days later while checking the pipeline. All avoidable with a CRM workflow.

A CRM workflow is a defined sequence of tasks and decisions for handling a lead, deal, or customer request in your customer relationship management system. It describes what starts the work, what happens next, and who takes responsibility. Workflows can cover sales activities, customer onboarding, and service processes.

Some steps can remain manual. A salesperson might assess a request while automation assigns its owner, creates a reminder, or updates a record. Workflow automation is the software-driven part of that process; you don’t have to automate every decision.

A CRM workflow example for sales inquiries

Use this illustrative design for a service business that receives quote requests through its website. The one-business-day response target is a sample operating choice, not an industry benchmark or a promised result.

Workflow elementExample rule
TargetGive every eligible quote request an owner and record a human follow-up within one business day.
TriggerA form submission creates a linked request or deal record with the required routing fields populated.
Eligibility checksThe source is the quote-request form, the request is open, and usable contact details are present. Send incomplete requests to manual review.
OwnerAssign the relevant service owner. If no rule matches or assignment fails, route the request to the sales coordinator.
Duplicate controlCheck the form’s unique submission ID where available. A retry with an already-processed ID should not create another task.
ActionCreate one linked task containing the original submission time, request details, and agreed due date. The assigned person handles the reply and records their outreach.
EscalationAt the deadline, check whether the request is still open and human follow-up remains unrecorded. If both are true, notify the coordinator once.
ExitStop first-follow-up reminders when outreach is logged or the request is closed, cancelled, or marked invalid.
Repeat entryRun once per genuine request. A new request can start a new run; ordinary edits must not restart the old one.
ExceptionsSend missing information, failed assignments, and failed actions to a review queue owned by the coordinator.

A personal reply sent or a logged call attempt counts as human follow-up in this example. An automated receipt doesn’t count, and an outreach attempt doesn’t mean the prospect was reached.

If your integration fills routing fields only after creating the record, trigger on a ready-for-routing status change instead. Treat the table as a design specification, confirm which controls your CRM can enforce, and use manual review for unsupported steps.

How to build your own CRM workflow

1. Choose one outcome and a finishing point

Choose one recurring handoff rather than your entire customer lifecycle. Start where you regularly have to chase an update, clarify responsibility, or recreate information before someone can act.

Write success as completed work, not a notification sent. Agree with the person receiving the handoff on what counts as finished, then choose a measure you can record before and after the change.

2. Choose the right record and required fields

Decide whether the process follows a person, a deal, or an individual request. If a customer can have several active requests, use separate linked records where your CRM supports them rather than overwriting one contact-level status.

Identify the fields needed for routing, ownership, timing, and completion. Specify who supplies missing information, and send incomplete records to a named reviewer instead of quietly excluding them.

Check your account’s capabilities before building. HubSpot’s documentation notes that some workflow record types require specific subscriptions and that workflow-count limits depend on your subscription. If you’re still selecting software, compare your mapped requirements against our guide to choosing a CRM.

3. Separate the trigger from the conditions

A trigger starts a run, while conditions determine whether the record qualifies to continue. Pipedrive’s documentation distinguishes change-based conditions, such as a stage changing to proposal, from state-based conditions, such as a stage currently being proposal.

Write the starting event and eligibility checks separately. For a stage-based workflow, check whether your configuration runs only when the stage changes or also when another field changes while the record remains in that stage.

4. Assign actions, owners, and deadlines

For each action, name the person responsible, the information they’ll receive, and the deadline. Add a backup owner for requests that don’t match a routing rule or can’t be assigned to the intended person.

Specify working hours, time zone, and holiday treatment instead of leaving “one business day” open to interpretation. Pipedrive distinguishes a fixed delay from waiting for an event, such as an email reply; choose the mechanism that matches your rule.

Keep human approval for decisions such as discounting, unusual contract terms, or complaint resolution. Design the surrounding workflow to assign the review, provide the necessary context, and record the decision.

5. Define stop rules and repeat entry

Define what cancels pending reminders, such as recorded outreach, a completed handoff, or a closed request. Recheck the relevant status after a wait and before a new action, rather than relying only on the status recorded at entry.

Decide whether the same record can enter again and what new event permits it. In HubSpot, re-enrolled records start at the beginning and repeat workflow actions; not every enrollment trigger supports re-enrollment.

Add a duplicate-work check using a stable request identifier before creating another task. Don’t treat a shared email address as sufficient evidence that two inquiries are the same request; one customer may be asking about separate projects.

6. Test exceptions before a live pilot

Test both eligibility and the actions that follow. HubSpot offers a criteria test and a separate workflow test that simulates how a record proceeds, but those tests evaluate the workflow’s current version.

Include these cases in your test set.

  • A qualifying new request reaches the correct owner and creates only one task.
  • A request with missing routing data reaches the manual-review queue.
  • A retry using the same request ID doesn’t create another task.
  • An unrelated record edit doesn’t restart the workflow.
  • A completed or closed request doesn’t receive another reminder after a delay.
  • An out-of-hours request gets the intended deadline, including weekend and holiday treatment.

Use controlled test records and internal recipients before a small live pilot. Give a process owner responsibility for checking failures, reviewing pending work, and pausing the workflow if results don’t match the design.

Three more CRM workflow examples

These are suggested process designs rather than vendor-specific templates. Adapt their timing, fields, and approval steps to your team and account capabilities.

Proposal follow-up

When a proposal is marked as sent, assign its owner a follow-up task after your chosen interval. Before creating the reminder, check that the deal still needs follow-up and hasn’t already reached a decision. Salesforce includes stage-based task automation among its sales workflow examples.

Customer onboarding

Once a deal meets your agreed ready-for-delivery requirements, create a handoff task with the scope, start date, and customer contact. Ask the delivery owner to accept the handoff rather than treating the notification as completion. Salesforce identifies new-customer onboarding as a CRM workflow use case.

Renewal preparation

Use a stored renewal date to create an account-review task before your chosen renewal window. Have the account owner check the relationship and unresolved issues before approving outreach. Renewal reminders are another use case in Salesforce’s workflow overview.

Check messaging permissions before automating emails

Keep internal assignments, replies to requests, and promotional sequences separate in your design. Don’t treat the presence of an email address in your CRM as proof that you have permission to send marketing messages.

The CRTC lists consent, sender identification and contact information, and a working unsubscribe mechanism as core requirements for commercial electronic messages under Canada’s Anti-Spam Legislation (CASL). Applicable exemptions and exceptions need to be considered when determining which requirements apply.

Keep the consent basis and supporting records with your customer data, and check eligibility and opt-out status before marketing sends. The CRTC’s guidance explains that implied consent depends on specified conditions and that the sender bears the burden of proving consent. Have a qualified adviser confirm the rules relevant to your messages and recipients before enabling customer-facing automation.

Measure completed work, not triggered actions

Record a baseline before switching the workflow on, then review it after a defined pilot period. For the sales inquiry example, use measures that distinguish a working handoff from a task that was merely created.

  • On-time follow-up rate: Among eligible requests whose deadlines have passed, calculate the percentage followed up by their deadline.
  • Overdue unanswered requests: Count open, eligible requests with a past deadline and no logged human follow-up.
  • Time to first follow-up: Measure median business hours between receipt and first recorded outreach for requests already followed up. Read this alongside the overdue count.
  • Exceptions and duplicate tasks: Count affected requests and inspect the reasons, rather than treating every error notification as a separate problem.

Exclude test records, spam, and confirmed duplicate requests consistently. Keep the same eligibility rules across reporting periods, and revisit the workflow when staff responsibilities, forms, stages, or integrations change.

Complete the design table for your business. Keep customer-facing automation off until the assignment, timing, and stop rules behave as intended.

Get new small business insights by email

Practical ideas and useful articles to help you make better business decisions.

HelperX Bot

Not sure what to read next?

I can suggest related Tech Help Canada articles based on the topic you’re reading now.

Tech Help Canada Staff researches, writes, and reviews practical content for business owners and professionals. Our coverage spans business, marketing, SEO, technology, and the tools and systems people use to grow and operate online. We focus on clear, useful information backed by research, hands-on experience, and editorial review. Learn more about our team and editorial standards. Need help with something? Contact Us

Leave a Comment

Tweet
Share
Share
Pin
WhatsApp
Reddit
Email