A material study photographed in bright daylight. Pleated turquoise glass layers curve up and meet overhead to form one open arch in the right half of the frame, daylight passing straight through the opening so the inside of the arch reads paler than the glass around it. The left of the frame is empty pale mint.
  1. Home
  2. Services
  3. Web Applications and Portals
  4. Customer portals and booking

Part of Web Applications and Portals

Customer portalsand booking.

A customer portal is a private account where customers see their orders, documents, invoices and status, and book their own appointments against real availability. It is one of three services under Web Applications and Portals.

A place customers go instead of calling, available at any hour, reading from the system that actually holds the answer.

Book a discovery call Request a performance audit

Know what you are building? Book a discovery call. Not sure where the problem is? Request the audit.

HUREAL / Material studies

In your words

Soundslike this?

  1. The phone rings all day with questions that have an answer in a system.

  2. Booking an appointment means leaving a message and waiting for a call back.

  3. We exchange documents with customers by email and hope nobody replies to the wrong thread.

  4. Intake forms get filled in the waiting room instead of before it.

  5. Our staff copy the same information from one screen to another.

  6. A customer asks where their order is and we have to ask the warehouse.

  7. We send reminders by hand, and the ones we forget become no shows.

If the work that needs to stop is internal rather than customer facing, the page is Custom web applications.

In plain language

The same handful of questions,answered without you.

Most of what a front desk or an inside sales team does all day is answer the same handful of questions: where is my order, when is my appointment, do you have my document, what do I owe, can I move it to Thursday. Each answer is fast. The interruption is not.

The saving is not the answer. It is the interruption.

A portal gives the customer a place to get those answers themselves. A booking system lets them act on real availability rather than requesting a call back. Both work because they read from the system of record rather than from a copy, so what the customer sees is true.

Both sides get built, because one fails without the other. The customer experience is half the project. The staff tools, the exceptions, the waitlist and the overrides are the other half, and they are the half that decides whether your team trusts it enough to stop answering the phone.

When this is not the answer yet. A portal is not the answer where the questions are genuinely different every time, or where the answer does not exist in a system at all. Where the system of record is a filing cabinet, the honest first project is getting the record into something a portal could read, which is Integrations and Data or Custom web applications rather than this.

The capability table

What a portalbuild includes.

Fourteen capabilities, what each one does in plain words, and what it changes for the business. The last group is the one that decides adoption, and it is the one most often cut.

Customer portals and booking systems, the capability table
Capability What it does What it changes
The accountWhat a customer can see and do
Account creation, sign in and recovery With security appropriate to what the account actually holds. The front door is designed rather than inherited.
The record view Orders, appointments, files, documents, invoices, status and history. The five most common questions are answered without a person.
Document exchange both ways With permissions and an audit trail. Files stop living in email threads.
Payments, deposits and invoice views Where the relationship involves money. The question of what is owed answers itself.
BookingAgainst real availability
Booking against the real calendar With rules for buffers, resources and staff. A slot that is offered is a slot that exists.
Rescheduling and cancellation Respecting your policies rather than a default. A change stops consuming a phone call each time.
Reminders and confirmations By email and text, in the customer's language. No shows stop being a surprise.
Intake and forms before the visit Completed at home rather than in the waiting room. The appointment starts on time.
Your sideThe half that decides adoption
Connection to the system of record Practice management, ERP, CRM or scheduling system. The portal shows the truth rather than a stale copy.
Staff tools Calendar management, exceptions, waitlist and overrides. Your team can handle the things the rules do not cover.
Notifications to your team For the cases that need a person. Nothing waits for somebody to notice it.
Privacy design, documented Scoped access, logging and retention, written for your privacy officer's review. The determination is theirs, and they have something to read.
Adoption measurement How many contacts the portal handled, and which ones it did not. The business case is checked rather than asserted.
A path for customers who will not use it Because they are not going away. Nobody gets a worse service for phoning.

Scroll the table sideways to read it.

How it works

Four things a customerused to phone about.

The parent's drawing, and this page is the one it was drawn for. Four customer actions at nine at night feed one portal, which reads from and writes to the systems that already hold the answers. The phone call for those four things stops.

Scroll the drawing sideways to read it.

Four things a customer used to phone about, at nine at night. One of them still needs you, and the drawing says which.

What the system does

The work, the path it takes, and everything HUREAL builds. It never means anything else.

What stays with a person

The line, its single opening, and the plate standing in it. On a light board it is the one dark plate.

What you already run

Present, named, and not for sale. The lowest contrast on the board, deliberately.

  1. Four actions, at nine at night.

    Check a status, upload a document, book a slot, pay an invoice. They are on the drawing because they are the four most common reasons somebody calls, and because each one has an answer that already exists in a system.

  2. One portal, one login, your rules.

    Who can see what, what a customer may change themselves, and what needs a person, decided in design rather than discovered in support.

  3. It reads and writes the system of record.

    Orders, documents, schedule and accounts stay where they are. The portal is a window rather than a second copy, because a second copy is a second version of the truth and the customer will find the difference before you do.

  4. The phone call stops.

    That struck through line is the business case. It is also the thing to measure: how many contacts the portal handled, counted rather than assumed, and reported every month after launch.

  5. Anything outside the rules waits for you.

    With the file attached. A cancellation inside the notice window, a document that does not match, an account on hold. The exception queue is a screen your staff work in, not an inbox.

Both sides get built. The staff tools, the exceptions, the waitlist and the overrides are half the project, and they are the half that decides whether your team trusts the other half.

Where this lands hardest

The deliverables

What youend up with.

  • A place customers go instead of calling

    Available at any hour, reading from the system that holds the answer.

  • Bookings in the real calendar

    With the right buffers, resources and staff rules.

  • Documents exchanged in a system with a record

    Instead of by email.

  • Reminders and confirmations that go out on their own

    By email and text, in the customer's language.

  • Staff tools for everything the rules do not cover

    Calendar management, exceptions, waitlist and overrides.

  • A privacy design document

    Scoped access, logging and retention, ready for your privacy officer.

  • Measurement of how many contacts the portal handled

    And which ones it did not.

  • A designed path for customers who will never use it

    Because they are not going away and should not get a worse service.

What is not on this list. The internal process behind the counter. Where the work to be systematised is your team's rather than your customer's, the page is Custom web applications. Where the answer a portal would show does not exist in any system yet, the first project is Integrations and Data.

By category

What a portalconnects to.

By category, because the category is the question. A portal that reads from a copy rather than from the system of record is a second place to be wrong, in front of a customer.

  • Practice management and records

    Where a clinic's appointments and files are true.

    practice management systems, electronic records, an in house register

  • ERP and order management

    Where an order status actually lives.

    NetSuite, SAP, Sage, an in house system

  • CRM

    Where the relationship and the owner are recorded.

    Salesforce, HubSpot, Zoho, Dynamics

  • Scheduling and dispatch

    Where staff, resources and routes are allocated.

    a dispatch board, a scheduling system, calendar systems

  • Payments and invoicing

    Where a deposit or a balance is taken and reconciled.

    card, Interac, digital wallets, your acquirer

  • Messaging

    Where a reminder or a confirmation is actually sent.

    email, text messaging providers, your existing phone system

  • Document storage

    Where the files exchanged have to be kept.

    SharePoint, Google Drive, Dropbox

  • Identity

    Where sign in, recovery and roles are handled.

    your own account system, single sign on providers

Every connection is validated by HUREAL's engineers during scoping and confirmed in writing before signature. Where a system genuinely cannot be connected, you hear it during discovery rather than during the build, and the scope is drawn around it instead of making a platform migration the price of entry.

Asked and answered

Questions peopleactually ask.

  • Will our customers actually use it?

    Some will immediately, and adoption grows when the portal is genuinely faster than calling. We design for that and we measure it. We also design what happens for customers who will never use it, because they are not going away and they should not get a worse service.

  • Our data is sensitive. Is a portal safe?

    Sensitive data is exactly why this should be designed rather than added on. Scoped access, encryption, logging, retention rules and consent are design requirements from the first session, and we document what was built so your privacy officer or counsel can review it. The determination is theirs.

  • Can it connect to our practice management or ERP system?

    Most modern systems can be connected, and some are harder than others. We check the specific system by name during discovery and tell you what is involved before it becomes your problem. Older and locked down systems are where surprises live, so we look at those first.

  • What if two people book the same slot?

    They cannot, because the portal books against the real calendar rather than against a copy of it, with the buffers and resource rules your team already works to. Where a rule cannot be expressed, the slot is held for a person instead of being offered.

  • Can customers cancel and reschedule themselves?

    Yes, inside the policies you set. Outside them the request waits in a queue for your team with the reason attached. A policy enforced by the system is also a policy you can change in one place rather than by retraining everybody.

  • How do we know it saved anything?

    By counting. Contacts handled by the portal, bookings made outside office hours, documents exchanged without email, and the calls that still came in and why. The measurement is set up before launch so the first month is a baseline rather than an argument.

  • Who owns it?

    You do. The code, the content and the data are in your own accounts with admin access from day one, and the customer records stay in the system of record they already live in rather than being copied into ours.

  • What does it cost?

    The build price is set after the discovery call and sent in a written proposal, because an honest number needs the scope, and here the scope is mostly which systems have to be read and how strict the rules are. The number is written into the signed scope and does not move once it is signed.

Three pages next to this one

Where thissits.

Close

Two ways to start.Both end with a document you own.

Book a discovery call

For when you know which process is costing you and want the scope before the spend. A discovery call with the people who actually run it. We map it end to end including the exceptions, name what a system would take over, and afterwards you get a written proposal with a scope, a price and a timeline you can sign or walk away from.

Book a discovery call

Request a performance audit

For when you want the evidence before the decision. We look at what you have against the job you want it to do, and give you a prioritised plan with the arithmetic attached. The document is yours either way.

Request a performance audit

Know what you are building? Book a discovery call. Not sure where the problem is? Request the audit. If neither is right for you, we will say so, and tell you what is.

Not ready for either? Talk to the demonstration in your browser for three minutes, or paste your own address and hear it answer as your business. No form and no booking, and the transcript arrives by email a minute later.

Hear it work
A material study photographed in bright daylight. A thin sliver of the monumental pleated turquoise glass wave enters from the right edge of a very wide frame, its fins and one polished silver ribbon catching the light at the crest, above a pearl reflective floor that runs the full width. The left of the frame is an almost empty pale mint room.

Their own answers, at nine at night.

HUREAL / Material studies