Three Form Types, One Inbox, No Assignment Rules

When we audited the high-performance transmission shop in Kokomo, the lead routing situation was the quietest problem on the list. No single moment where something obviously breaks. Just friction spread across every inbound contact.

Here is what we found: three different form types on the site, all going to one shared sales inbox. Spec forms from customers configuring custom builds. Repair intake forms from customers dropping off converters for rebuild. General contact forms from everyone else. Four people on the sales and tech bench. No assignment rules. No response timer. Whoever opens the inbox reads the email, figures out what it is, and decides who should have it.

At 30 to 45 inbound leads per week, that is 6 to 12 minutes per email to read, classify, and route. That adds up to $3,900 to $7,800 per year in admin time doing work that a webhook and two conditionals could handle.

The Real Cost Is Not the Hours

The labor math matters, but the bigger problem is what happens in the gap.

A shared inbox is not a routing system because it has no memory of who last touched what. A spec-form lead comes in at 9 a.m. Person A skims it and figures person B is better for it, but does not explicitly hand it off. Person B does not know it exists. The lead sits. By noon, if someone does pick it up, they're the third or fourth set of eyes on it and the first one to actually act.

High-value leads do not wait. A customer who submitted a 40-field spec form for a custom build worth several thousand dollars is evaluating multiple shops. Response time is part of the pitch. A business that gets back in two hours beats one that gets back in two days, even if the product is the same.

The shared inbox creates random response times because it relies on whoever happens to check the inbox at the moment the email is visible and unclaimed. That is not a system. It is a coincidence.

What Routing Actually Requires

The form already contains the information you need. A spec form has different fields than a repair form. A repair form has different urgency than a general contact. The type of the submission tells you who should own it and how fast they need to respond.

Routing is three steps:

First, a webhook fires on form submit, before anything hits the inbox. The webhook reads the form type from the submission data.

Second, a conditional assigns it. Spec form goes to the tech lead. Repair intake goes to the service desk. General contact goes to the first available sales rep. The assignment happens automatically, before any human sees it.

Third, a timer starts. If the assigned person has not opened or responded within a set window, a flag goes up. Not a buried email notification. Something visible.

That is the whole build. Three nodes in an automation flow. No platform, no new tool the team has to learn. The inbox can still exist for visibility. It just stops being the decision point.

Why This Does Not Get Built

Every business with this problem has lived with it long enough that it feels like the normal cost of operating. The leads come in, they get handled, nobody tracks the ones that slipped. The shared inbox does not announce when something fell through. It just quietly holds the evidence.

The audit surfaces it because we are looking for it. We are estimating hours per week and putting a dollar figure on them. When a shop owner sees that their team is spending 4 to 8 hours per week reading and routing submissions that the system already has the data to route automatically, it becomes a different conversation.

The fix is not a commitment to a new platform or a six-month integration project. It is a webhook, a conditional, and a timer. Two weeks to spec and ship, probably less. The savings start immediately.

If your business has more than one form type and a shared inbox, the routing is happening by hand right now. That is the thing to fix first.