---
title: "Create a customer portal for requests and documents · Lyntev"
description: "Need a customer area on your website? See how to define requests, documents and access for each company, and how much a bespoke portal may cost."
url: "https://lyntev.com/en/services/client-portal"
language: "en-GB"
---

[Home](<https://lyntev.com/en>)[Services](<https://lyntev.com/en/services>) 

# A portal where each customer follows their requests

“Have you received my document?” and “What stage is my request at?” are different questions. An acknowledgement may be enough for the first. For the second, customers need to return to the process and see what has changed. The answer helps decide how much is worth developing.

 [Calculate my customer portal](<https://lyntev.com/en/request-a-quote?tipo=sistema&objetivo=portal-clientes>)

## How much does it cost?

For a standalone system, the estimated cost of the “Portal or customer area” module, with basic accounts and permissions, is 2800 € to 5600 €. Dedicated hosting from 39 € per month. The diagnostic assessment costs 400 € and is deducted if you proceed. The proposal sets the price and payment for each stage, integrations, storage and applicable external charges before you contract.

 [Check bespoke system prices](<https://lyntev.com/en/pricing#sistemas>)

## When is it worth creating a customer area?

### The customer only needs to deliver a file

If the interaction ends with submission, a form with confirmation and a contact reference may be enough. Before adding user accounts, consider whether someone would have a concrete reason to return to the website.

### The customer returns to follow the work

An installer can publish the final report for a job and let the customer follow a correction. Define what each status means. “Awaiting customer” is only useful if the portal shows which document is missing, who should supply it and where they can do so.

### There is already software managing the requests

Start by opening that software’s customer area, if one exists, and follow a request from end to end. If a feature is still missing, identify which system holds the official status and what happens if the connection fails. This makes it possible to quote only for the missing part.

## What does the customer see after a technical visit?

Fictional example for preparing a proposal. A maintenance company supports several shops. Each shop manager needs the local report, while the management team follows all the jobs.

North Shop request

The manager opens the “freezer door will not close” request. She receives a reference and sees the “visit scheduled” status. The internal note about allocating technicians stays within the team.

Visit report

The technician prepares the report. The customer sees the document when the person responsible publishes it. If there is a correction, they should be able to identify the current version by its date and revision.

Access by shop

The North Shop manager views only her shop. When authorised, the management team follows North and South. A different company has its own set of requests and files.

End of contract

Agree the export format and the period of access to the history. Include a trial handover of reports to the person who will be responsible for the archive.

Replacing the manager

In the handover test, invite the new person responsible only to North Shop and remove the previous person’s access. Reopen the old link using the previous account. Access should be closed, and reports should remain available to the person now responsible.

## What to bring for a portal quote

[Calculate my customer portal](<https://lyntev.com/en/request-a-quote?tipo=sistema&objetivo=portal-clientes>)

- Choose a typical request. Write down the customer’s first action and the point at which they consider the matter resolved.
- Prepare a fictional report and mark which parts are visible to the customer, the internal team and the person approving publication.
- Count the entities needing access. Distinguish individual customers from companies with several shops or departments.
- Specify where each request’s status is held today and whether that software supplier permits export or integration.

## Find out more

- [Bespoke software](<https://lyntev.com/en/bespoke-software>)
- [Define each person’s permissions](<https://lyntev.com/en/guides/define-team-permissions>)
- [Prepare requirements to request proposals](<https://lyntev.com/en/guides/write-verifiable-software-requirements>)
- [Test the portal handover](<https://lyntev.com/en/guides/test-system-before-acceptance>)

## Sources and documentation

- [Microsoft Learn · acessos por contacto e por conta num portal](<https://learn.microsoft.com/pt-pt/power-pages/security/table-permissions>)
