Request a Call
Case Studies

LESS LEAD LOSS WITH AUTOMATION + PIPELINE

Automation CRM case study: this is what happens when leads stop living inside random WhatsApp chats and start living inside a system.
Service

Automation & CRM

Client

SwiftHaul Logistics (Lagos)

Date

March, 2026

THE PROBLEM

Leads were coming in from WhatsApp, Instagram, and website forms — but follow-up depended on memory.

Some leads got replies late. Some were missed. Management couldn’t see what was stuck.

BEFORE (BASELINE) — LAST 14 DAYS

  • Average first response time: 5 hours 20 minutes
  • Leads not contacted within 24 hours: 31%
  • Missed follow-ups (no second touch): 44%
  • Lead-to-payment conversion: 14%
  • Operations pain: constant “Who is handling this?” messages

What was BROKEN:

WHAT WAS BROKEN

  • No central pipeline (no owner, no next step, no follow-up date)
  • No routing rules (assignment was random)
  • No reminder system (leads went cold)
  • No escalation (hot leads and complaints sat in the same queue)
  • No dashboard (management had no daily visibility)

What NEULEAD CHANGED

Built a CRM pipeline in Google Sheets
Stages + owner + next step + next follow-up date (simple enough for daily use).

Automated lead routing with Make/n8n
New lead → assigned to a rep → instant notification with context.

Added follow-up reminders
Daily “follow-ups due” prompts + alerts for leads not contacted fast enough.

Added Telegram escalation
Hot leads/complaints triggered instant alerts to a Telegram group.

Added a dashboard
Leads today, follow-ups due, leads stuck too long, basic rep performance snapshot.

RESULT

WITHIN 4 WEEKS

  • First response time: 5h 20m → 9 minutes
  • Leads not contacted within 24 hours: 31% → 9%
  • Missed follow-ups: 44% → 16%
  • Lead-to-payment conversion: 14% → 23%
  • Time saved: ~9 hours/week (less manual tracking + fewer status checks)

WHY THIS WORKED

Leads don’t get lost. Systems fail.

When every lead has an owner, a next step, and a reminder — closing stops depending on who remembers.

No vanity metrics • Tracking-first • Mobile-first • Built for revenue