Notes for owners · Channel and customer growth
A partner portal or a WhatsApp group: five tests that decide it
Five yes-or-no tests tell a manufacturer whether a dealer WhatsApp group still does the job or whether a partner portal would pay for itself, with the cheap fixes to try first.
The GullySales team · Updated 17 Oct 2026 · 5 min read
On this page
Picture a dealer group with two hundred unread messages every morning and last season's price list still pinned, and a vendor has just offered you a portal. Before you pay for anything, count. A WhatsApp group is enough while one person can answer every dealer from memory and nothing important is lost between messages. A portal starts to pay when that stops being true, and a fortnight of your own chats will tell you which side you are on.
Count the last fortnight before you decide
Take a sheet and tally these from real chats, not from how you feel the group works.
| What to look for | Your count |
|---|---|
| Questions three or more dealers asked you in the same words (price of one model, dispatch status) | |
| Times you could not find an order, payment screenshot or claim when a dealer asked | |
| Orders placed against a price list you had already replaced | |
| Promises made to a dealer by one of your people that another did not know about | |
| Notices you sent that you cannot say were read, by dealer |
Give one point for each row that is above zero. Zero or one: stay on WhatsApp and tidy it. Two or three: do the repairs below and count again later. Four or five: scope a portal. The threshold is a rule of thumb. A manufacturer with eight dealers who scores five has a discipline problem. One with eighty who scores three has a size problem.
What can you repair inside the group?
Much of the pain comes from how the group is used. Try these before spending anything.
Make the dealer group announcement-only. Replies then reach one person privately, and notices are not buried. Pin a single price list with its date in the file name. Delete the old one when the new one goes up. Take orders on a short form, a shared sheet or a form link, and treat a chat message as a request to fill it. Keep one register of claims and complaints; our note on getting dealer orders off personal WhatsApp shows a layout that needs no software.
If the first and third rows of your tally fall to zero after these repairs, you did not need a portal yet.
What does a portal give that a chat cannot?
Be specific, because "visibility" sells portals and delivers little. Three things a portal does better than a chat. It shows each dealer their own price list, by tier, so a gold dealer cannot see a silver dealer's rate. It lets a dealer see the order or claim status without calling you. And it keeps a dated record of who opened each notice and who completed which training, which blue ticks cannot promise.
The saving is mostly your staff's hours spent answering and re-sending. That is real only if the hours are real, so count them for a fortnight before you believe a vendor's figure.
What does it cost besides the licence?
Someone has to own the content. That person needs time set aside every week, which is the cost vendors mention least. Price lists, schemes and training files go stale in a portal exactly as they do in a group. Dealers must be taught to log in, and a few never will, so you will run both channels for a while. Your data has to be clean first: a portal built on a price list with three versions publishes all three.
Allow for training time too. Each dealer needs to see once how to check an order, download a price list and raise a claim, and the first few will phone you anyway. A short printed card with those three steps, and a named person to call when a login fails, will save goodwill. If your dealers change counter staff, the training repeats with every new face, which vendor figures leave out.
Skip it if most of your dealers are small traders who work from a phone and a notebook. They may not touch a login, unless you can give them something they want, such as quicker payment of claims.
The pump maker who bought the portal first
Take an invented pump maker in Coimbatore that sells through sixty dealers across Tamil Nadu and Kerala. After a demo, the owner bought a portal licence before counting anything. Eight weeks later eleven dealers had logged in. The rest still messaged the owner's phone, because the questions they asked, about stock and a delayed dispatch, were not what the portal answered.
The owner went back and did the tally. It scored two: a repeated stock question and a lost transfer screenshot. Orders moved to a form, the group was split into an announcement list and a private line, and the stock question was answered from a shared sheet the godown updated at closing time. Two weeks later the repeated questions had thinned. The lost screenshots had not, and that told the owner what a portal had to do for the business: keep payment proofs against dealer accounts. The licence was not wasted, but it had been bought before the job was known.
How do you scope a first portal?
Write the two or three jobs it must do, taken from the rows you still fail, and ignore the rest of the vendor's feature list. For the Coimbatore maker the list was one line: payment proof against the dealer account, visible to both sides. Launch it to your ten most active dealers, not all sixty, and watch whether they log in without being chased. If they do, extend it. If they do not, ask what they wanted instead before you add anything.
Open the group tonight
Open your dealer group this evening with a pen and fill in the tally. Date it, score it and keep the page, then repeat the count after the repairs and see which rows moved. Partner portal and PRM implementation is the service that scopes a portal from the rows you still fail, and the rest of our sales work sits under sales. If your score comes back at four or five, or you cannot read it, tell us what you need.
