Skip to content

Reading 08 · Novamedia

The client wanted a WhatsApp bot.

A company that sells to other businesses asked Novamedia for an automated WhatsApp service. A first contact waited a few hours for an answer.

The first contact waited a few hours for a reply.

The path of a WhatsApp contact

  1. Contact comes in

    On the company's WhatsApp

  2. Wait

    A few hours

  3. First reply

    From the company's team

Source: Novamedia, customer service at a B2B company.
01

Method stage: Problem

What looked like the problem

Speed. A bot would answer right away, any time of day.

02

Method stage: Evidence

What evidence I would look for

Who handles each type of contact? How long does the customer wait, and how many contacts never get an answer?

03

Method stage: Evidence

What the evidence showed

I read the WhatsApp conversations, asked each person on the team and counted the contacts that never got a reply. Nobody knew who answered what. Every contact landed in the same place, and some of them got lost.

04

Method stage: Problem

What the real problem was

The issue was ownership, not speed. Automating that process would only make the mistake happen faster.

05

Method stage: Decision

What I would decide first

Fix the process before automating it: one owner per type of contact, clear criteria to qualify who comes in and a deadline for the first reply. Only then did automation go in. First response time went from a few hours to under 1 hour.

What it looked like

Speed.

Root cause

The issue was ownership, not speed.

Decision

Fix the process before automating it: one owner per type of contact, clear criteria to qualify who comes in and a deadline for the first reply.

What changed · WhatsApp first response

Beforea few hours
Afterunder 1 hour

Do this tomorrow

Open your company's last 20 WhatsApp conversations and write down, for each one, who answered and how long the customer waited.

Other readings

Next reading · coming soon