Service · Websites and web development

Customer portal

A customer portal should be built around the questions your customers ring about most: where is my order, can you resend the invoice, can we have the same as last time. Every question a customer can answer alone frees up time for your service team.

Send an enquiry See the scope

From 6 weeks

first release

Data

from your systems

with two factors

Documents

invoices and contracts

What the service covers

A portal is only as useful as the number of enquiries it takes over. That is the test for every feature we include.

Talk it through with us

Login

Email with a one-time code, two-factor sign-in or single sign-on with Microsoft Entra ID for business customers.

Orders

What was ordered, at what price and in what status, plus a reorder button.

Documents

Invoices, delivery notes, certificates and contracts pulled from e-conomic or Business Central, ready to download.

Customer terms

Individual prices, discounts and account contacts for customers on an agreement.

Users and permissions

Customers invite colleagues themselves and decide who may view invoices and who may only place orders.

Notifications

Email or text message when a status changes, so nobody has to phone and ask.

How we deliver it

From six weeks. The timeline depends mostly on whether your business system can deliver data through an API.

Enquiries

We gather the most frequent customer questions. The portal must solve those, not look impressive.

Design

Roles, permissions, sections and data flow between the portal and your systems.

Development

Interface, login, integrations and notifications.

Rollout

We invite the first customers, share a guide and measure how many calls disappeared.

A customer portal holds personal data, so GDPR applies in full. That means data minimisation, access logging, hosting in the EU and a process for customers' rights of access and erasure. Designing this in from the start is far cheaper than retrofitting it when the Danish Data Protection Agency or a customer starts asking questions.

Common questions

Yes, if it solves a real problem: checking status, fetching documents or reordering. A portal with a profile page and an empty history gets no use, and it should not be built.

It is possible through an approved MitID broker, and it makes sense when the portal shows sensitive information about private individuals. For business customers, two-factor login or single sign-on with their own Microsoft account is usually more practical.

Usually not. A portal that works well in a mobile browser does the same job with no installation. An app is justified when you need push notifications or offline work.

Related services

View the whole area

Service WordPress development A bespoke theme, a lean plugin list and a link to your bookkeeping Service Shopify and other platforms Shopify, Webflow or headless Next.js, depending on the job Service Small business website and catalogue A handful of pages and a product catalogue with enquiries instead of a basket Service Corporate website A structure for customers, candidates and partners

Design your customer portal

Tell us what customers contact you about most often. We will build the portal around exactly those questions.

Email
office@apply.dk

Coverage
All of Denmark, delivered remotely

I agree that Apply may handle my details as set out in the privacy policy