So when you started looking for a solution, what were you actually searching for?

We were mainly looking to improve data input into Pipedrive. Specifically, we were looking for a way to voice control data input into Pipedrive.

That's a narrower brief than most people start with. You weren't shopping for an "AI CRM assistant" in the abstract — you knew the mechanism you wanted.

The problem was clear enough. The people were in cars. The data wasn't getting in. Voice was the obvious bridge.

How does it work in practice now?

WhatsApp to Hints to Pipedrive. They can already fill in info and make notes in Pipedrive while driving — when safety allows it, of course.

So the note gets created at the moment it's fresh, not at 9pm at the kitchen table.

That's the whole idea.

Let's talk about rollout. What was the initial reaction from the team?

We found some resistance, as expected. We're trying to train and support people to use it properly. Some are using it consistently. Some have given up on it.

That's a more honest answer than we usually get. What separates the ones who stuck with it from the ones who didn't?

The main concern is names not being entered correctly. That's the thing that frustrates people.

Walk us through what goes wrong.

When someone gives their first note, the name is usually already in there — they're dictating naturally, so the contact's name is part of what they say. Hints creates a record in Pipedrive from that, and creating a record triggers our automations. If the name came through wrong, fixing it afterwards doesn't help, because the wrong name is already sitting in those automations.

So the error propagates before anyone can catch it.

Exactly. I've told the team to manually type a name in WhatsApp and then use voice for everything else. That works. But it's a workaround, and you have to remember to do it.