CRM Workflow Examples for Small Business

1. New inquiry ownership

Trigger when a valid inquiry is created. Assign an owner, create the initial opportunity, send an acknowledgement and create an internal follow-up task. Exit the generic path as soon as the prospect replies or books.

2. Qualification branch

When a required qualification field is completed, route qualified opportunities into the sales pipeline and move ineligible requests into a clearly labeled state. Do not hide disqualification inside a note.

3. Appointment booked

Use a booking event to stop pre-booking sales prompts, send confirmation, notify the owner and update the opportunity if the appointment is a legitimate stage transition.

4. Opportunity idle alert

If an active opportunity has no meaningful activity beyond the team's internal threshold, create a task or alert. Do not automatically move the stage forward or mark the deal lost simply because time passed.

5. No-response transition

After the active follow-up window ends without engagement, set a no-response or nurture-eligible status, stop frequent outreach and preserve the lead for later reporting.

6. Reactivation enrollment

Periodically identify eligible dormant contacts using source, age, prior state, permission and exclusion criteria. Enroll only the segment that still has a relevant reason to hear from the business.

7. Closed-won handoff

When the opportunity is deliberately marked won, stop sales nurture and start the appropriate onboarding/service workflow. This is a clean example of pipeline state controlling communication.

Turn examples into testable acceptance criteria

For each workflow, write what must be true before launch. A new inquiry flow should create exactly one expected opportunity; an appointment flow should stop pre-booking prompts; a closed-won flow should never leave the customer in sales nurture. Acceptance criteria make QA objective.

Keep a small set of test contacts representing common edge cases and run them after major workflow edits. That practice is more valuable than relying on memory about how an automation is supposed to behave.