Your identity stays visible
Use your organization name, visual identity, information architecture, and service modules so the experience feels native to your venue or practice.
Branded Experience
Your service experience, under your brand.
Branded Experience gives an organization a configurable browser portal for information, forms, requests, and secure communication. Visitors can enter from a link, QR code, or NFC touchpoint without first learning a new back-office system.
Best fitOrganizations that need one clear digital front door
Typical accessWeb link, QR code, or NFC touchpoint
Important boundaryIt complements—not automatically replaces—your systems of record
What this solution does
A focused front door for every visitor
Instead of sending guests across disconnected forms, inboxes, downloads, and chat tools, you can assemble the relevant steps into one branded experience. The visible portal is paired with City of Hats Operations for staff handling and can connect to supported messaging channels through Unified Inbox.
Fewer hand-offs
Put instructions, intake, requests, documents, and communication behind one predictable entry point.
Sensitive steps can move securely
Use Hat-based secure channels for workflows that should not continue through ordinary email or consumer chat.
Core workflows
Configure the experience around the journey
The exact modules depend on the deployment. A portal can start small and expand as the organization confirms its workflow, permissions, integrations, and compliance requirements.
Guided forms and intake
Collect the information needed for a request while keeping the next action obvious.
Document exchange
Give visitors a defined place to send or retrieve files instead of relying on loose email attachments.
Secure communication
Move appropriate conversations into Hat channels with the controls available to that deployment.
Appointments and requests
Present booking or request workflows without exposing the staff tools behind them.
Multilingual presentation
Offer localized interface content; availability and quality depend on the configured languages and translation workflow.
QR and NFC entry
Connect physical spaces, cards, signs, badges, or printed material to the correct digital experience.
How it works
From discovery to a working portal
A good deployment begins with the visitor journey and the information boundary—not with a long feature list.
Map the journey
Identify who enters, what they need, what information is sensitive, and which staff team owns the response.
Configure and connect
Choose the modules, branding, access points, roles, retention rules, and any approved integrations.
Pilot and refine
Test with a limited audience, review accessibility and privacy behavior, then expand with evidence from real use.
Security and privacy
A branded experience still needs explicit boundaries
City of Hats can protect supported communication and help reduce unnecessary identity exposure. The organization remains responsible for its notices, lawful basis, records, staff access, and connected systems.
Encrypted Hat channels
Supported Hat-to-Hat content is protected by the City of Hats encryption model; endpoint access and recipient behavior remain part of the threat model.
Pseudonymous access where appropriate
A workflow may use Hat identities instead of requiring a visitor to expose a personal phone number to another participant.
Scoped staff handling
Operations can separate venue and staff workflows, subject to the roles and permissions configured for the deployment.
Reviewable claims
Security statements should be checked against the Security Evidence Center and the final deployment architecture.
Scope clarity
Important boundary
A strong fit when
You need a branded digital front door, want to reduce fragmented visitor journeys, and can assign an owner for content, permissions, and follow-up.
What it does not replace
It is not automatically an electronic health record, student information system, property-management system, legal practice-management system, CRM, or general-purpose website builder.
Confirm before deployment
Confirm required modules, integration behavior, accessibility, data location, retention, staff roles, translation expectations, and regulatory obligations during solution design.
Straight answers
Questions teams ask before a demo
Product scope reviewed: 10 August 2026
Do visitors have to install the City of Hats app?
Not for every portal interaction. Branded browser experiences can be opened from a normal link, QR code, or NFC touchpoint. A secure Hat workflow may ask a participant to create or open a Hat when that capability is required.
Can the portal use our logo and visual identity?
Yes. Branding and portal presentation can be configured for the organization. The exact level of customization is confirmed during solution design.
Does Branded Experience replace our current software?
Usually no. It is the visitor-facing layer and workflow entry point. Existing record, booking, CRM, clinical, education, hotel, or legal systems may remain authoritative and require an integration.
Is every portal interaction end-to-end encrypted?
No. Public information pages and ordinary browser requests are not the same as an end-to-end encrypted Hat channel. The deployment must make the boundary visible and route sensitive communication into the appropriate protected workflow.
How do we evaluate security and compliance?
Start with the Security Evidence Center, Privacy Policy, and your own risk assessment. Compliance depends on the configured deployment, contracts, processes, connected providers, jurisdiction, and how your organization uses the service.
Explore the platform
Build the complete workflow
Design the journey before choosing the modules.
Tell us who the portal serves, what visitors need to accomplish, and which systems or regulatory requirements must be considered.