Route enquiries directly to the right people

An email arrives in a shared inbox. One person reads it, forwards it, and waits for a reply. By the time the right colleague sees the case, valuable time has often passed.

It does not have to stay that way.

If you want to route enquiries automatically, you need clear information. The system needs to see what the enquiry is about, where the contact came from, and who handles the case. Without this information, no rule can work well.

Clear rules instead of forwarding emails

Many teams use one inbox for everything. New enquiries, customer requests, applications, and invoices all arrive there. This is simple at first, but quickly becomes unclear as email volume grows.

A new enquiry should go straight to the right team. In a business with several locations, the postal code may be enough. Where several services are offered, the topic can determine the route.

This shortens the process.

First define the types of cases you receive. Then assign each type to a person or team. Everyone should be able to see these rules and update them when needed.

For example, a workflow might look like this:

• Product questions go to sales.
• Service cases go to the support team.
• Contacts from a region go to the local contact person.
• Existing customers remain with their assigned contact.

These rules need to be simple. If three teams are responsible for the same case, even a good tool will not help. Clear boundaries reduce follow-up questions and internal emails.

Good data from the first contact

A form can ask for more than a name and email address. A field for the topic helps the system classify the case immediately. Location, country, or customer group can also matter for routing.

Only ask for information you will use.

A long form puts many people off. A selection field for the topic and a field for the postal code are often enough. The team can clarify the rest later.

Free-text fields still have a place. Customers often want to describe their issue in their own words. However, a free-text field should not be the only source used for routing.

Selection fields are clearer.

Emails can also be sorted using fixed details. The subject line, a known email address, or a word in the text can trigger a rule. However, unclear emails should go to an open queue.

Check existing contacts first

A new name is not always a new customer. The person may already have received a quotation or be speaking with support. The system should therefore search by email address and company before creating a new record.

Duplicate data leads to errors.

Without this check, sales may create a new record even though support already knows the customer. Information about the last conversation, open items, or an earlier quotation is then missing. The team has to merge the data manually later.

A CRM needs clearly defined processes for this. New contacts, existing customers, and open cases must be clearly marked. The article “A CRM Needs a Clear Process for SMEs” explains which rules make sense.

The person who already has the relationship should see the case. This applies especially to complaints, ongoing quotations, and enquiries about an earlier order. The customer does not then need to explain their situation again.

Work starts after routing

Correct routing alone is not enough. The responsible employee also needs a clear task. Otherwise, the contact may be in the right area but remain unread.

Every new case needs a status.

Simple examples include “new”, “in progress”, “waiting for customer”, and “completed”. These terms show the team what is currently open. They also help when a colleague is ill or on holiday.

Also define what happens after an enquiry is received. An enquiry may require a callback, an email, or an appointment. The system can create a task directly and notify the person handling it.

This means the next step is not missed.

A short acknowledgement can also be appropriate. However, it should only be sent when it fits the case. For an urgent service outage, an acknowledgement alone is not real help.

Keep open cases visible

Some enquiries do not fit any rule. A topic may be missing from the form, or a customer may mention a new service. These cases must not remain in the shared inbox.

Set up an open queue for them.

A designated person reviews the cases there and forwards them. This can happen once a day or more often when needed. What matters is that it is clear who monitors this queue.

Incorrectly routed cases are useful too. They show where a rule is missing or too broad. If the team often has to forward a case, the workflow should be adjusted.

Check these points in particular:

• Which cases are left without a team?
• Which cases are frequently forwarded?
• Which information is missing from the form?
• Which people or locations have changed?

This keeps routing close to day-to-day work. New services, new regions, or new colleagues can then be added promptly. It helps prevent outdated rules that nobody knows about anymore.

Do not leave follow-up to chance

Communication often does not end after the first email. A reply, appointment, or approval may still be missing. The workflow should therefore continue after the first step.

A task can provide a reminder.

If a customer does not reply, the CRM can send a prompt after a defined period. The person handling the case can then see which cases are still open. This keeps the enquiry visible without anyone maintaining lists.

The article “Follow Up on Leads While Interest Is Still There” describes how defined follow-up steps help. The number of emails is not what matters. A clear next step is.

Frequently asked questions

How can I route enquiries automatically?

You can sort enquiries by topic, location, customer group, or product. The system needs clear information from the form or email for this. A rule can then send the case to the right person.

What information do I need for automatic routing?

You only need information that determines the right route. Topic, postal code, and whether the customer is new or existing are often enough. Too many fields make the form unnecessarily long.

Can I automatically send emails to the right team?

Yes, emails can be sorted by subject line, sender, or specific words. However, unclear emails should go to an open queue. This allows someone to review cases where the rule is not a reliable fit.

How do I avoid duplicate replies to an enquiry?

You can avoid duplicate replies with a visible case owner and a clear status. Before creating a record, the CRM should search for known contacts. This lets the team see whether someone is already working on the case.

What happens to enquiries without a matching rule?

Enquiries without a rule go to an open queue for review. A responsible person can assign the case to the right team there. Each of these cases also shows where the workflow still has a gap.

How often should I review enquiry rules?

You should review the rules when there are new teams, locations, or services. Incorrectly routed cases also provide a useful indication. It is therefore worth reviewing open and forwarded contacts regularly.