hexylGive customers a useful portal alongside your existing software
Choose the information and actions customers need, agree smart sign-in and test what each person can see and change.
In this guide
Check what your existing portal already does
List the questions customers contact you about repeatedly: finding a confirmation, continuing a conversation or requesting a change. Compare those tasks with your current patient or customer portal. If it already completes them well, agree what Hexyl would improve before introducing another sign-in.
- Identify the system that owns bookings, payment status and shared documents.
- Select one first task and list the channels or records it needs.
- Agree which information is visible to customers and which remains internal.
Make sign-in and updates predictable
Agree the supported sign-in options, including emailed links, and how expired links or changed email addresses reach support. Match the signed-in account to the correct customer record before displaying communications. A successful sign-in alone does not grant access to another person’s information.
For booking changes, show the current saved appointment, check the requested change and display confirmation only after the diary accepts it. If the connection is temporarily unavailable, label the request as pending or offer team help. A portal message should have a clear response expectation.
Test access as two different customers
Use fictional accounts and records for setup checks. Confirm which call summaries, messages and documents appear; do not promise that every historic communication is imported automatically.
- Sign in as customer A and check that customer B’s records are inaccessible, including through copied links.
- Try an expired sign-in link, a removed sharing permission and a family member with booking-only authority.
- Change a booking in the existing system and confirm the portal shows the correct updated state.
Measure useful self-service
Track completed customer tasks, failed sign-ins, requests needing staff help and repeat administrative calls. Review access exceptions and information that becomes out of date. Compare support effort before and after the agreed first task launches. Portal registration counts alone do not show that customers can get something done.
Start with the scope you need
Start with Portal and one agreed customer task. Connect, Book, Pay and Flow are added only for the actions and connections required. Portal needs a scoped quote; a missing public price does not mean it is free.
- Hexyl Portal — Customer portal & smart sign-in
Optional additions
- Hexyl Connect — Calls, messages & web chat
- Hexyl Book — Bookings & appointment reminders
- Hexyl Pay — Payments & deposits
- Hexyl Flow — Software connections & automation
Your proposal confirms inclusions, product tiers, supported actions and setup costs. Related products are not automatically added to a package.
Explore Hexyl PortalContinue with a related guide
Plan separate appointments for each person, handle partial availability and keep booking permissions separate from access to private information.
Hexyl Connect · channel handoverContinue a phone enquiry on WhatsApp without starting againAgree how a caller chooses WhatsApp, how the conversation is matched and what happens when the message cannot be delivered.
Hexyl Flow · software connectionsCheck what a useful software connection needs to doDescribe the everyday task first, then confirm system access, supported actions and how your team handles exceptions before launch.