Client portal on a website: when you really need one

A client portal sounds professional. Customers log in, see their orders, download documents, check status. Owners often ask for one in the first conversation about a new site. Sometimes it is exactly what the business needs. More often, a simpler tool does the same job at a fraction of the cost and effort.

What a portal actually is

A client portal (also called a personal account or client area) is a private part of your site. Each customer logs in and sees only their own data:

• orders and their status;
• invoices, contracts, acts and other documents;
• bookings and history of visits;
• project stages and files;
• messages with your team.

Behind it there must be a database that your team keeps up to date. That last point is where many portals fail: if staff do not update statuses, clients see wrong information and call anyway.

When a portal makes sense

If most of your answers are in the "No" rows, read on for alternatives.

Cheaper options that solve the same problem

1. Status messages in Telegram. When an order changes status, the team presses a button and the client gets a message. "Your documents are ready", "The courier is on the way". No login, no password reset, works on any phone. For many clients this is most of what they wanted from a portal. Many businesses in Armenia start here.

2. A Telegram bot with a "My order" button. The client presses it and sees the current status from your system. The bot can also send documents as files. A Telegram bot costs from $500 at Kinto.

3. A shared folder per client. For document-heavy services, a Google Drive folder shared with each client works surprisingly well for small volumes.

4. A simple CRM with notifications. If requests already go to a CRM or a table, status changes there can trigger messages. Our guide to leads in Google Sheets shows a starter version.

If you do need a portal

Plan these parts before talking to developers:

1. Who logs in. Clients only, or also partners and staff with different rights.
2. How they log in. Phone and code, email and password, or Telegram login. Phone code is easiest for most clients in Armenia.
3. What they see. A precise list of screens and data.
4. Where data comes from. Your CRM, accounting, or the portal's own admin panel. See admin panel: what you can edit for what staff usually manage.
5. What they can do. Only view, or also upload files, pay invoices, rebook.
6. Languages. If clients are relocants and locals, the portal needs the same languages as the site.
7. Who updates it. Name the person on your team.

Security basics

A portal stores personal data, so the bar is higher than for a public site: https everywhere, strong login, rights checked on every page, regular backups, and updates. Our article on website security basics lists what to ask your developer. Plan ongoing support from the start; at Kinto support starts at $900 for 6 months.

Step-by-step path

1. Count how many "what's the status" questions your team answers per week.
2. Start with status messages in Telegram for a month.
3. If clients still ask for documents and history, add a bot with "My order".
4. If that is not enough, build a portal on top of your CRM.

Each step uses the data from the previous one, so nothing is wasted.

Cost at Kinto

More about our sites on the website development page.

Describe what your clients ask most often, and we will tell you which option fits. Telegram: @kinto_am.