A visible queue
Route incoming work into a shared operational view instead of relying on forwarding chains and personal inboxes.
Operations
One workspace for the team behind the experience.
Operations is the staff-facing workspace paired with Branded Experience. It helps teams receive, assign, discuss, and resolve venue-scoped requests without forcing every workflow through a shared email inbox.
Best fitTeams handling sensitive or multi-step service requests
Typical accessAuthorized staff workspace
Important boundaryWorkflow scope depends on configuration and connected systems
What this solution does
Turn a visitor request into an owned workflow
When a guest, patient, parent, or client submits a request, Operations gives the responsible team a defined place to handle it. The objective is not to reproduce every enterprise system; it is to create a clearer and more secure service layer around communication, documents, status, and hand-offs.
Scoped responsibility
Organize work by venue and configured staff roles so the appropriate team can own the next action.
Communication stays attached
Keep supported messages, files, and updates near the workflow they belong to.
Core workflows
The operational layer around sensitive service
Available workflows are configured for the organization and may require integration work when another platform remains the system of record.
Request intake and triage
Receive portal or supported-channel requests, establish priority, and direct them to the right operational owner.
Case-style tracking
Keep status, notes, documents, and communication organized around a defined matter or service request.
Controlled document handling
Move appropriate documents through a dedicated workflow with explicit staff ownership.
Appointments and follow-up
Coordinate requested times and next steps; authoritative scheduling may remain in a connected system.
Secure conversations
Use Hat-based communication for supported sensitive exchanges between staff and external participants.
External-channel routing
Pair with Unified Inbox for supported WhatsApp Business, Messenger, and LINE workflows while respecting their separate privacy boundaries.
How it works
A request moves with ownership
The final workflow is designed around the team’s actual responsibilities, escalation rules, and recordkeeping obligations.
Receive and classify
A request enters from the configured portal or channel and is categorized with the minimum information needed.
Assign and work
An authorized staff member owns the next action, uses the approved communication path, and records the required status.
Resolve and retain appropriately
The team closes or hands off the work under the organization’s retention, audit, and system-of-record rules.
Security and privacy
Security is shared between platform and process
Encryption cannot correct excessive permissions, weak endpoint practices, or an unclear retention policy. Operations should be deployed with role review, staff training, and a documented data flow.
Role and venue scope
Access is organized around configured staff and venue boundaries; the organization must review who receives each role.
Protected communication paths
Supported Hat-channel content uses City of Hats security controls, with limitations documented in the Security Evidence Center.
Connected-system boundary
Data sent to a CRM, EHR, SIS, PMS, provider API, or another system becomes subject to that system’s controls and retention.
Operational governance
The customer remains responsible for notices, lawful use, permissions, records, incident handling, and sector-specific requirements.
Scope clarity
Important boundary
A strong fit when
Your team needs a shared, scoped workflow around service requests and sensitive communication, and you can define ownership, escalation, and retention.
What it does not replace
Operations is not automatically a CRM, EHR, SIS, PMS, help desk, document-management platform, or regulated records archive.
Confirm before deployment
Confirm required roles, workflow states, integrations, audit expectations, exports, retention, business continuity, and administrator responsibilities before launch.
Straight answers
Questions teams ask before a demo
Product scope reviewed: 10 August 2026
Is Operations the same as Branded Experience?
No. Branded Experience is the visitor-facing portal. Operations is the staff-facing workspace used to handle the requests and communication behind that portal.
Can several teams work in the same environment?
A deployment can be structured around venues and configured staff responsibilities. The exact tenancy, roles, escalation, and reporting model must be confirmed for the organization.
Does it replace our CRM or industry software?
Not by default. Operations can act as a secure service and communication layer, while another platform remains the authoritative customer, clinical, student, property, or matter record.
Can staff handle external messenger conversations?
Supported channels can be routed through Unified Inbox. Those conversations retain the security and data-handling boundaries of the external provider until they enter the configured City of Hats workflow.
What should security teams review?
Review data flows, staff roles, endpoints, integrations, retention, incident procedures, recovery expectations, and the claims and limitations published in the Security Evidence Center.
Explore the platform
Build the complete workflow
Show us how work reaches your team today.
We will map the intake points, owners, sensitive data, required integrations, and important limits before proposing a workflow.