How To Build A Dealer Portal That Actually Reduces Phone Calls

Most dealer portals fail the same way. They get built, announced, used for a fortnight, and then abandoned — while the sales team keeps answering exactly the same phone calls as before.

The portal was not the problem. The order in which it was built was.

Start by logging the calls, not by designing screens

For two weeks, have whoever fields dealer calls keep a tally. One line per call: what was asked, and roughly how long it took.

You will end up with something like:

• Is this in stock?
• What is my price for this?
• Where is my order?
• Can you resend the invoice?
• What is the lead time on that?
• Do you have the spec sheet?

Now count them. Almost always, two or three question types account for most of the volume.

This is the single most important step and the one that gets skipped. Portals fail because they are designed around what seems comprehensive rather than what is actually being asked. A portal that answers your top three questions perfectly and nothing else will get used. One that answers eleven questions adequately will not.

Solve the top three, properly

Stock availability. This is usually number one, and it is the hardest to fake. Dealers need to trust it, which means it has to reflect reality — including committed stock, not just what is physically present. A portal that says "available" when it is not will lose their trust permanently after roughly one incident. If your stock data is not reliable enough to expose, fixing that comes first.

Their pricing. Dealer-specific, after their discount structure, including any active scheme. This is the one dealers most want and manufacturers are most nervous about. The nervousness is usually misplaced — they already know their prices. What they do not have is a way to check without calling.

Order status. Where is it, what stage, when does it ship. Order status calls are pure overhead: no negotiation, no relationship building, just a lookup a person is performing on someone else's behalf.

Get these three genuinely right before adding anything else.

Make it easier than the phone, or it loses

This is the whole game. Your dealer has a working alternative — calling someone who will answer. The portal only wins if it is genuinely less effort than that call.

Which means:

It must work on a phone. Your dealers are often on a shop floor, in a vehicle, at a customer site. If the portal assumes a desktop, it will not be used where the questions actually arise.

Login must be trivial. Password complexity rules and forced resets will kill adoption faster than any missing feature. Mobile number and OTP is usually right for this audience.

No more than two taps to the common answers. If checking stock takes six taps and a search, the phone is genuinely faster and your dealers are behaving rationally by ignoring you.

It must be current. Stale data is worse than no portal, because it teaches dealers that the portal cannot be trusted — and that lesson does not get unlearned.

Roll it out to your most demanding dealers first

The instinct is to start with the easy-going ones who will not complain. Do the opposite.

Your highest-volume, most impatient dealers generate the most calls and have the strongest incentive to find a faster route. If the portal genuinely saves them time, they will adopt it and tell you exactly what is wrong with it. If it does not survive contact with them, it would not have survived wider release either — you have just found out cheaply.

Then check whether it worked

Run the call tally again a month after launch, in the same format.

If total call volume has not dropped, the portal is not working, regardless of how many dealers logged in. Login counts are a vanity metric — the thing you were buying was fewer interruptions.

If calls have shifted rather than dropped — fewer stock questions, more questions about something else — that is a genuine success. It means the portal absorbed one category and revealed the next one, which tells you exactly what to build next.

A note on sequencing

A portal is an implementation, not a strategy. It is worth building when dealer self-service is genuinely your constraint — when your sales team's time is being consumed by lookups rather than selling.

If your actual constraint is that quotations take four days, a dealer portal will not help. Different bottleneck, different fix. Establishing which one you have is what the Business Health Score is for, and it is a cheaper first step than building the wrong thing well.