Building a customer portal your customers actually use

Your customer service team answers the same questions every day: the status of an order, a copy of an invoice, the outstanding balance, whether a payment has arrived. Each call takes a few minutes and pulls someone away from work that needs a person. A customer portal should take those questions off the phone. Most do not, because they were designed around what the company wanted to show.

Our recommendation

Build the portal around the questions customers already ask, make login as easy as a WhatsApp message, and make sure the data behind it is accurate and current. A small portal with four reliable features gets used. A large one with stale data gets abandoned within weeks.

Start with your call log

Before you design anything, spend two weeks counting. Ask the sales coordinators and accounts team to tally every customer call, email and WhatsApp message by reason. For a manufacturer or distributor, the list usually looks something like this:

• Order status and expected dispatch date.
• Copy of an invoice, delivery challan or credit note.
• Account statement and outstanding balance.
• Payment confirmation.
• Price list or scheme details.
• Complaint or return status.

The top four reasons are your first release. Nothing else goes in until those work well.

Make login trivial

B2B customers are often a purchase clerk at a dealer, an accountant at a hospital or the owner of a small shop. They will not remember a password for a portal they use twice a month.

• Login with a one time password sent to a registered mobile number.
• Allow several users per customer account, each with their own number, so you know who did what.
• Send direct links in WhatsApp and email messages, for example "View invoice 2381", that open the right page after login.
• Make every page work on a phone first. Many of your customers will never open it on a desktop.

Get the data right

A portal is only a window onto your other systems. If the ledger in the portal does not match the ledger your accounts team quotes on the phone, customers will call to check, and you are back where you started.

• Pull invoices, credit notes and ledgers from your accounting system, whether Tally, SAP Business One or Odoo, so there is one copy of the truth.
• Update order status from the system dispatch actually uses. If dispatch updates a spreadsheet, fix that first.
• Show the time of the last update on every screen, so customers know how current the information is.
• Decide in advance what happens when data is missing. "Invoice not yet available, usually ready within 24 hours of dispatch" is better than an empty page.

Features that come next

Once the first release is used regularly, consider:

1. Online ordering against the customer's own price list, with their usual items shown first.
2. Payments through UPI or net banking, with automatic matching to invoices.
3. Raising and tracking complaints or returns with photos.
4. Downloadable documents such as test certificates, warranty cards or GST certificates.

Ordering is often the feature the business wants most, and the one customers adopt last. Many dealers prefer to place orders with a salesperson they know. Let the portal support that relationship.

Getting customers to use it

Launch emails do little. What works is building the portal into everyday contact.

• When someone asks for an invoice copy, send the portal link.
• Have salespeople show the portal on the customer's phone during a visit and log them in there and then.
• Put the portal link and a QR code on invoices and statements.
• Track which customers have logged in and follow up personally with the largest accounts that have not.

What it costs and how long it takes

A first release covering orders, documents, ledger and payments, connected to one accounting system, is typically an eight to twelve week build for a small team, depending on how clean your data is and how easy your ERP is to integrate with. Off the shelf dealer portals exist for some ERPs and can be quicker if your needs are standard. Build custom when your ordering rules, schemes or document types are specific to your business.

Customer data in the portal falls under the DPDP Act 2023, so keep access logs, limit what each user can see to their own account, and agree retention periods with your legal team.