“Sir, mera file kahan tak pohncha?” at eleven at night, fourteen more by morning. The status call looks like a customer service problem, but it is a records problem. What a good customer portal shows, what it must keep out of sight, and where files actually get stuck.
It is eleven at night and a counsellor at a study-visa agency in Lahore gets a WhatsApp: “Sir, mera file kahan tak pohncha?” She knows the answer is somewhere in a blue folder on a shelf at the office. She replies “kal check kar ke batati hoon”, and tomorrow morning there are fourteen more messages like it waiting. Every agency owner reading this has lived that morning.
The status call looks like a customer service problem. It is really a records problem. The customer asks because they cannot see anything, and the office struggles to answer because the file itself lives on paper and in somebody’s memory. Fix where the file lives and the call mostly stops on its own. That is what a customer portal is for, and this piece is about what a good one does and, just as important, what it should keep out of the customer’s sight.
An agency sells a process, not a product. A UK student file goes from admission to fee deposit, then the CAS letter, the tuberculosis test, the bank statement, biometrics and finally the decision. A Gulf work visa needs a medical, a protector stamp and a ticket. Each step depends on a document, and most of those documents have to come from the customer.
So the customer is waiting on the agency, and the agency is waiting on the customer, and neither can see the other’s side. The customer does not know their bank statement was the wrong period. The counsellor does not know the customer sent the corrected one to a colleague’s number. The result is a phone that never stops and files that sit for a week because of one missing page nobody chased.
Real scenario
A portal earns its keep when the customer can answer their own question in ten seconds. That means three things, and they are the three things NavoBook’s customer portal shows:
This part matters more than most software vendors admit. The portal shows no money: not the agreed amount, not the receipts, not the balance. An agency’s pricing is often negotiated file by file, and a customer who sees the balance in a portal will screenshot it and compare it with a friend’s. Money conversations belong with a person.
It also shows no office remarks. The note that says “father unsure about funds, follow up carefully” is for the counsellor, not for the family reading over the student’s shoulder. In NavoBook those notes stay on the case inside the ERP, and the portal never carries them.
| WhatsApp and a folder | A customer portal | |
|---|---|---|
| Where the status lives | In the counsellor’s head and a paper folder | On the case, updated when the office closes a stage |
| Who answers “where is my file?” | Whoever picks up the phone, after finding the folder | The customer reads it themselves, at any hour |
| Documents | Photos in a chat, forwarded, saved to a phone, lost | Uploaded against the exact document on the checklist |
| A bad scan | “Dobara bhej dein” and nobody remembers why | Rejected with a reason the customer reads before uploading again |
| Privacy | Passport and CNIC scans sit on staff phones | Each customer reaches only their own case and files |
| Offers | A broadcast list that half the customers have muted | Running offers shown inside every customer’s portal |
Most delays in a visa file are not the embassy. They are a document that arrived late, arrived wrong, or arrived on the wrong phone. A portal fixes the loop only if each upload lands against a specific item on the checklist, so the office never has to work out what a photo was meant to be.
In NavoBook the customer uploads a PDF or a photo straight against the document it is for. That document becomes Received and waits for the office. The counsellor opens it, and either marks it Verified or Rejected, and a rejection needs a reason: “scan is cut off at the bottom”, “statement must cover the last six months”. The customer reads that reason in the portal and the next upload is right the first time. Only an approver can waive a document altogether, so a junior cannot quietly skip the police certificate to close a stage on time.
Key insight
A portal that shows a status the office never updates is worse than no portal at all. So the process has to be the agency’s own, and it has to be enforced, not just listed.
NavoBook lets you build the process per case type yourself. For each stage you decide whether it is required or optional, whether stages must close in strict order, whether one needs a manager’s approval, and which documents it asks for, picked from a document library you keep once. A stage cannot close while one of its mandatory documents is still outstanding. When a new case opens it copies its type’s process, so if you add a step for next year’s intake, the files already running are not rewritten underneath you.
This is the same idea we describe for manpower and Umrah files on the agency software page: the case is the unit of work, and the money received and spent sits on it too, so each file also shows the margin it earned. That stays inside the office.
Agencies hold some of the most sensitive paper in the country: passports, CNICs, bank statements, family registration certificates. Today most of it travels through personal phones and sits in chat histories long after the staff member has left.
A portal moves those files into one place with a login. In NavoBook a customer login is answered only with that customer’s own cases and files. Another customer’s case simply does not exist for them, and the server refuses a customer login on every screen outside the portal, whatever is typed into the address bar. The office still works in the full ERP with its own users and roles. The two never mix.
An agency cannot charge its customers for a portal. Nobody pays extra to check their own visa status, so per-login pricing would make the portal something you ration instead of something you hand to everyone. Customer portal logins in NavoBook do not count as users of your plan. The agency sets the customer’s password from their customer record and can switch a login off later, and the history stays.
Honesty here saves an argument later. Customers cannot sign themselves up: the agency creates each login, which most agencies prefer anyway. A forgotten password is reset by the office, not by an e-mailed link. And the portal does not yet send SMS or WhatsApp alerts when a stage moves; the customer sees the change when they log in. Notifications are on our roadmap, and we would rather tell you that now than in your second week.
Do not start with the portal. Start with one case type, the one that makes up most of your files, and write down its real stages and the documents each stage needs. Load that into the process builder, run your next twenty files through it inside the office, and fix the list where reality disagrees. Then switch the portal on and hand logins to those twenty customers. The process has to be right before the customer can see it.
If you are still running files from a spreadsheet, our guide to moving from Excel to an ERP covers the import side, and the owner’s dashboard shows what the month looks like once every file carries its own numbers. The night-time “file kahan tak pohncha?” will not vanish completely. But it becomes the exception, and the answer is already on the customer’s screen.
From PKR 20,000 a month, all 23 modules included. No hidden per-module fees.