Every inquiry finds its team.

Around 800 inquiries a month came in through 5 channels. A workflow in Pharen Hub gives each one a team and saves over 90 hours of searching a month.

Two women consultants in conversation
Industry
Consulting
Services
  • Process design
  • lead routing
  • CRM handover

A consulting firm receives around 800 inquiries a month, through the website form, by email, as referrals, via LinkedIn and from conversations. Today they all land in one list in Pharen Hub, and a workflow takes care of the lead routing. It checks whether the contact already exists, an agent sorts new inquiries by need, relevance and timing, a rule hands them to the team for the right region, and every working day at 8 a.m. the Hub shows where a follow-up is due.

Before, each inquiry took around 8 minutes of searching, more than 100 hours a month in total, and one in 5 inquiries never got a follow-up. Today it is around 1 minute per inquiry. That saves over 90 hours a month, which at €45.00 per working hour, the German average for 2025, comes to around €4,200. The first reply usually goes out the same day, where it often took 2 days before. People still hold the conversations.

With Pharen, the team has:

  • brought around 800 inquiries a month from 5 channels together in one list
  • cut the search per inquiry from around 8 minutes to around 1 minute, over 90 hours a month
  • saved working time worth around €4,200 a month
  • given every inquiry a team and a follow-up date, including the roughly 160 a month that used to fall through the cracks
  • brought the first reply from often 2 days to usually the same day
  • recognised known contacts before anyone writes to them a second time

Starting point

There were enough inquiries, around 800 a month, almost 40 on a normal working day. The trouble was that they came from everywhere: through the form on the website, by email, as referrals, via LinkedIn and from personal conversations. It was often unclear what was really new, what had already been answered and who should get in touch next.

None of this was meant to become an aggressive sales machine. The team wanted to spot good conversations sooner and follow up reliably, without forcing every inquiry straight into an overloaded CRM.

Every inquiry stayed where it arrived

A LinkedIn chat stayed on LinkedIn. A referral sat in the inbox. A website form got forwarded. That worked fine as long as a few people kept everything in their heads.

So before anyone could reply, there was the search. Is this person already a contact? Has someone already replied, and who is responsible? That meant going through the inbox, LinkedIn messages and notes, around 8 minutes per inquiry. Across 800 inquiries, that was more than 100 hours a month. At €45.00, what an hour of work cost on average in Germany in 2025 (according to Germany’s Federal Statistical Office), the search alone cost around €4,800 a month.

One in 5 inquiries fell through the cracks

Because nobody was clearly responsible, everyone relied on someone else to reply. The first reply often came only after 2 days. Around 160 inquiries a month, one in 5, got no second message after the first. Some contacts were written to twice, others not at all.

A study published in the Harvard Business Review in 2011 shows how expensive a long wait is. Across 2,241 US companies, the first reply to a test inquiry took 42 hours on average, and 23 percent never replied. A second analysis of 1.25 million inquiries at 42 companies found that a contact attempt within one hour led to a conversation with the decision maker nearly 7 times as often as an attempt one hour later, and more than 60 times as often as one after 24 hours or more.

Implementation

Lead routing with one list for 5 channels

In Pharen Hub we set up one list for all inquiries, plus a workflow that fills it and distributes them. The workflow enters inquiries from the website form by itself. An agent reads forwarded emails and picks up name, region and request. The team enters referrals, LinkedIn messages and conversations by hand into the same list, and that starts the process too.

At the start, no contact has to be scored yet. Every inquiry first needs a source, a short assessment, a team and a next step.

Lead routing as a workflow in Pharen Hub in 4 lanes. At the top, it takes inquiries from the website form and the email inbox into the list. In the middle, it matches each new inquiry against existing contacts, an agent sorts new inquiries, a rule picks Team North, East, South or West, then it schedules the follow-up and hands the contact over to the CRM. At the bottom, every working day at 8 a.m. it looks for inquiries that are due and still open and flags them.
The workflow, rebuilt with sample data in Pharen Hub. At the top, the website form and the inbox add new inquiries, in the middle each new inquiry runs from the match to the CRM, at the bottom the Hub looks for due inquiries every working day at 8 a.m.

An inquiry goes through 5 steps

  1. Match the contact. The workflow checks whether the person already exists. If a conversation is already running, the inquiry goes to the existing contact as a note, and nobody writes to the person a second time.
  2. Sort the inquiry. For new contacts, an agent suggests a category based on need, relevance and timing: first meeting, documents first, or follow up later.
  3. Choose the team. A rule assigns the inquiry by region to Team North, East, South or West.
  4. Plan the follow-up. The inquiry gets a status and a date on which the team gets back in touch.
  5. Hand over to the CRM. The contact goes into the CRM, and the inquiry is assigned.

Every working day at 8 a.m., the Hub looks for inquiries whose date has come and that are not yet closed, and sets a reminder on the contact.

A category alone would have changed nothing. Inquiries fell through the cracks because nobody was responsible. That is why the AI process automation connects the agent’s suggestion with a rule for the team and a date.

The Anfragen list (inquiries) in Pharen Hub with 12 sample inquiries, each with name, source, region, request, category, assigned team, status, follow-up date and email
The shared list with sample data. Each of the 12 inquiries has a team and a follow-up date. 3 are new, 3 have a first meeting scheduled, 2 are waiting for documents. The inquiry from David L. is closed, so the Hub no longer sends reminders about it.

People hold the conversation

The workflow sends nobody a message and turns nobody down. The category is a suggestion that the responsible person can correct. The process is there to help the team coordinate, and it does not rate anyone by criteria they cannot see. Our German post on lead management with AI explains why a short inquiry is no basis for judging the customer.

Result

Over 90 hours less searching a month

Whether the contact already exists, who is responsible and when to follow up is now in the list before anyone opens the inquiry. Per inquiry, around 1 minute remains for a look at category and team, where it used to be around 8. More than 100 hours a month have become around 13.

That saves the team over 90 hours a month, more than 2 working weeks. At €45.00 per working hour, that is around €4,200 a month.

First reply on the same day

The first reply now usually goes out the same day. Before, it often took 2 days. The roughly 160 inquiries a month that used to fall through the cracks now have a team and a date. Once the date comes, the Hub keeps reminding the team until the inquiry is closed.

If one in 6 of these 160 inquiries books, that would be around 27 additional engagements a month. This does not promise any particular conversion rate. Whether a conversation turns into an engagement depends on the offer, the timing and the conversation itself. What can be measured is what the process influences: the time to the first reply, inquiries without a team and overdue follow-up dates.

Inquiries still come from everywhere

Website, inbox, referrals, LinkedIn and conversations all stay. Now they all land in one place, with team, status and date.

Every inquiry now finds its team, and the team can find every inquiry again. 📬

Published on , updated on .

More case studies

What's on
your horizon?