Short answer. A customer area is adopted when it answers the question your customers ask on the phone. Count your calls for a week, by reason: in this guide's example, three calls out of four ask where the file is, for an invoice to be sent again, or whether a document has arrived. So build in this order: the status of the file first, with what is blocking and who must act; then documents both ways, invoices, and one request thread. Underneath, a base: sign-in by code, with no password, each customer sees only their own, and a message at every change. Six weeks in the example, one block at a time.
This guide is for the manager of a service company whose phone rings for status questions: a firm, an agency, a design office, an installer, a training centre, a developer, a workshop. And for the founder based in France whose customers, or who personally, follow from afar a file handled in Algeria, at hours when nobody picks up. The definitions quoted come from public sources: the client portal, the one-time password, the insecure direct object reference, the progressive web app; the ranking quoted is OWASP's, 2021 edition. The company, its hundred calls and its calendar are a constructed example. This guide does not cover the legal rules on personal data or on document retention: see your legal adviser.
Why your customers call: one hundred calls sorted
The figure sorts one hundred calls in a week by reason.
The log. For a week, each person who picks up ticks a reason on a sheet: status of the file, document to resend, document received or not, appointment, real question. Five columns are enough. In the example, 76 calls out of 100 are about information that already exists in the company; the customer simply cannot read it without going through someone. What it takes. Each status call interrupts two people, the one who picks up and the one who knows; and the answer depends on who answers.
What a customer area is not. A client portal is an electronic gateway to a collection of digital files, services, and information, accessible over the Internet through a web browser. It is neither a brochure site with a “sign in” button nor an ordering tool: if your customers are retailers placing orders, read the guide to the B2B ordering portal; if your calls are complaints about a delivered product, the guide to complaints and after-sales. Here the subject is files that last: a service, a building job, a procedure, an enrolment.
What goes into a customer area: four blocks and a base
The accented layer is the status of the file.
Four blocks. Status: the stage, what is blocking, who must act, what comes next and when. Documents, both ways: what you hand over to the customer, and what they must provide, as a list. Invoices and payments: what is due, what is paid, the receipt. Requests: a single thread per file, instead of messages scattered over three phones. One block at a time. Status can be delivered alone and is useful from day one; the others are added once it is in use.
The base. It is not seen: sign-in, rights, messages, the log. And one precondition: one customer, one record. If the same customer exists three times, under three spellings, their files will not come together; that is the subject of the guide to the single customer file. And your current software? If the files already live in management software, the customer area does not retype them: it reads them. How to connect the two, with or without a programming interface, is described in the guide to integrating existing software.
The file, as the customer sees it
The figure shows the screen of a file, stopped at the documents stage.
Four answers. Where is my file: the stage, out of five. What is expected of me: “waiting for you”, and the list of what is missing. What happens next, and when: the next step and its time limit. What has already happened: the log. A screen that only shows “in progress” removes no call. Who must act. It is the most useful information on the screen, for the customer as for you: a stopped file always carries a name, theirs or your team's.
The list of documents. Each document has a status: received, missing, to redo, with the reason for the refusal, for example a blurred photo. The customer uploads from their phone; the upload is timestamped and attached to the file, not to one employee's conversation. Every change notifies. A change of stage, a refused document, a document handed over: a message goes out, with a link to the file; without it, nobody comes back to look. The choice of channel, and what each send represents, are covered in the guide to notifications.
«A screen that only shows “in progress” removes no call.»
Who sees what: each sees only their own
The figure lists six actors, and what stays closed to each.
The classic flaw. It has a name: insecure direct object reference, a type of access control vulnerability. It occurs when an application uses an identifier for direct access to an object in its database but does not check for access control: if the address contains an easily enumerated number, such as file 1234, changing it is enough to read other people's. In the 2021 edition of the OWASP ranking, broken access control holds first place, having moved up from fifth. The test. Before opening, sign in as a customer and replace the number of your file with another: the only acceptable answer is a not-found page. It is redone for every new screen.
No password. A customer who signs in four times a year will forget their password, and call back. Sign-in by code avoids that: a one-time password is valid for only one login session or transaction; it arrives on the phone or the email address you already know. The channels, what each send represents and the frauds are described in the guide to sign-in by code. On the team's side. A case officer sees their portfolio, a manager sees everything, and the log keeps who changed what: see the guide to roles, rights and the audit log.
Getting them to use it, in this order
The first step is accented: count.
Nothing to install. A customer opens their file a few times, over a few weeks: they will install nothing for that. The area opens from a link, in the phone's browser. A progressive web app is a type of web app that can be installed on a device as a standalone application: it is enough here, and the guide to the installable web app says when it no longer is. The invitation. It goes out when the file opens, not in a campaign: a message, a link, a code. The first screen shows their file, not a registration form.
On the phone. The team does not refuse to answer: it answers, then adds that it is in the customer's area, and sends the link again. Documents that still arrive on WhatsApp are filed in the right place by whoever receives them, during the first weeks. Three figures, read every Monday. The activation rate: the share of customers with an open file who have signed in at least once. The share of status calls, on the same log as at the start. The share of files complete on the first upload. If activation stays low, look first at the invitation, then at the status screen: does it really say what is blocking?
«The invitation goes out when the file opens, not in a campaign.»
Six weeks, from the call log to the first review, in 2027
Six weeks in the example, the first one to count.
- What the manager receives: the call log, the status screen for files, the list of documents, invoices and requests in one area, the cross-access test passed, and three figures every Monday.
- What the company no longer does: answer “where is my file” from memory, search an employee's phone for a document, send the same invoice three times, find out that a file has been waiting for ten days.
- What is measured: activation rate, share of status calls, share of files complete on the first upload, stopped files and since when.
- What Symloop does: the log and the stages, the customer area block by block, sign-in by code, rights and their test, stage messages, the connection to your software if there is one, then the measurement.
Week 1, the log: calls by reason, and the stages of a file written on one page. Weeks 2 and 3, status and the base: stages, who must act, sign-in by code, rights, and the cross-access test; open files are taken over. Weeks 3 and 4, documents: upload from the phone, list of documents, reason for refusal.
Weeks 4 and 5, invoices and requests. Weeks 5 and 6, the invitation and the review: each new file opens with its invitation, then the call log is redone. In the example, the target set at the start is to bring status calls down from 76 out of 100 to fewer than 30; the log says whether it is met. The duration depends on the number of types of file and on whether software already holds them.
- How do you build a customer area?
- By starting with a count of your calls for a week, by reason. Then one block at a time: the status of files first, then documents, invoices and requests. Underneath, a base: sign-in by code, rights per customer, a message at every change of stage.
- What should go into a customer area?
- Four things: the status of each file with what is blocking and who must act, documents both ways with the list of documents expected, invoices and payments, and one request thread per file. Nothing the customer has not already asked for on the phone.
- Will my customers use it?
- Yes, if the area holds the answer to their question, if the stage message leads to it through a link, and if your team points to it instead of answering from memory. An area announced once, then forgotten by the team, stays empty.
- Do we need a mobile app or a website?
- For a file opened a few times, a web area that opens from a link in the phone's browser is enough: nobody installs an app for that. An app is justified when the customer comes back every week.
- How do customers sign in without a password?
- With a one-time code sent to their phone or email address, valid for a single session. They have nothing to remember, and you have no passwords to reset.
- How can we be sure a customer does not see someone else's file?
- With an access check on every page and every document, not only at sign-in, and with a test before opening: signed in as a customer, replace the number of your file with another in the address. The answer must be a not-found page.
- Can the customer area be connected to our current software?
- Often, yes: if the software exposes its data through a programming interface or regular exports, the customer area reads the files instead of retyping them. This is checked on your software before promising a date.
- Can the customer pay from their area?
- At the least they can see what is due, download their invoice and upload proof of a transfer. Online card payment is a separate piece of work, with its own formalities: it is added afterwards, if your business justifies it.
- What happens to WhatsApp?
- It stays, for talking. But status, documents and invoices live in the file: the team answers, then sends the link to the area, and files the documents received by message. The habit forms file after file.
- How long does it take, and where do we start?
- Six weeks in this guide's example, one block at a time; longer if there are several types of file or software to connect. Start with the week of call logging: it needs no tool and says which block to deliver first.