Enclave is an app and web based complaint management system with visitor access management, from the moment a citizen files a complaint to the moment a visitor signs out. Built for government offices, enterprises, and large facilities, with IoT-ready access control.
Region: North · 4 campuses · 1,208 units
One system in place of a fragmented stack
Two systems, one platform
Complaint management and visitor access are usually two disconnected tools. Enclave runs them as one, so a ticket, a visitor, and the gate that let them in all share the same record.
Capture every complaint on web, app, kiosk, or desk, route it to the right team, and drive it to resolution against a clock the whole office can see.
Know who is coming, verify them at the gate or reception, and keep a clean log of everyone on site, with the hardware doing the checking for you.
Every channel
A citizen at a counter, an officer on the move, and a caller on a helpline should not land in three different registers. Every channel feeds one queue, one ticket number, and one SLA clock.
Public-facing grievance portal with status tracking by ticket number.
Android and iOS, with photo, location, and voice-note attachments.
Lodge and track over chat, for citizens who never install an app.
Call-centre agents log tickets against the same categories and SLAs.
Touch kiosks in the lobby for walk-in complaints and visitor check-in.
Scan the code on a lift, pump, or corridor to raise a tagged complaint.
Desk staff record grievances directly, with a printed acknowledgement slip.
A monitored inbox converts incoming mail into categorised tickets.
Duplicate detection matches the same issue arriving on two channels, so one problem never becomes three tickets.
End to end
From the moment a grievance is lodged to the moment the citizen confirms it is fixed, each stage is timestamped, owned by someone, and visible to both sides.
Filed on any channel, with photos, location, and category captured up front.
A ticket number goes out instantly by SMS, email, or push notification.
Auto-assigned by category, location, and skill to the right department.
The SLA clock runs. Breach the threshold and it escalates a level automatically.
Closure needs proof: work notes, photos of the fix, and a digital sign-off.
The citizen rates the outcome, and can reopen within a configurable window.
Supervisor, head of department, then leadership, each on its own timer.
Post-closure feedback rolls into department and officer scorecards.
An unsatisfied citizen reopens the same ticket instead of filing a new one.
The platform around them
The two core systems do not stand alone. Every request, asset, and person is connected, so a complaint becomes a work order, a work order draws on inventory, and an asset carries its own maintenance history. Nothing lives in a silo.
A configurable hierarchy from region to room, plus complete records for everyone who uses the facility.
Capture the right detail per category, catch duplicates, and carry a request through to a signed-off job.
Every asset carries its own history, schedule, and parts, so maintenance runs ahead of failure, not behind it.
Control who enters and where they park, from pre-approved guests to daily deliveries and service crews.
Administrators shape workflows, rules, and dashboards to match each site, with no engineering ticket required.
Notifications, documents, audit trail, and analytics run underneath all five layers, so the whole platform moves as one.
The product
Supervisors run the whole facility from a full web console. Officers, guards, and citizens carry the same platform in their pocket, so a complaint raised on a phone lands on the board in real time.
Central Office Complex · this week
Built for every role
A citizen should never see the internal notes. A guard should never edit an SLA. Role-based access gives each person exactly the screen they need and nothing beyond it.
Raise a grievance, track it by ticket number, and request a visit without calling anyone.
Pick up assigned jobs, work them on site, and close them with evidence from the phone.
Verify arrivals, scan passes, and log every entry and exit without a paper register.
Shape the system, watch every site, and answer to auditors with a full trail.
Granular permissions down to the field level, with custom roles, delegation during leave, and maker-checker approval on sensitive actions.
No-code control
Two campuses rarely run the same way. Enclave lets administrators reshape the platform without touching code, so a municipal office and a corporate campus can share one system while following their own playbooks.
Map states from open to closed, with inspection and reopen steps your teams actually use.
Set response and resolution targets by priority and category, with automatic escalation.
Trigger actions from conditions, like auto-escalating a priority grievance to a senior officer.
IoT integrations
Enclave talks to the physical layer, so access events and sensor alerts land in the same platform as complaints and visitors. The barrier that opens, the reader that verifies, and the sensor that trips can all trigger the right action automatically.
Boom barriers, turnstiles, biometric and RFID readers, and ANPR cameras.
Occupancy, water leak, smoke, temperature, and energy meters feeding live data in.
A leak sensor auto-raises a complaint. A flagged plate holds the barrier and alerts security.
MQTT, webhooks, and REST, with a live device registry and health status.

Integrations
Enclave is designed to sit inside an existing environment rather than replace it. Directory, messaging, finance, and field hardware all connect through documented interfaces.
SAML and OAuth single sign-on against Active Directory or LDAP.
Plug in your own provider for acknowledgements and escalation alerts.
Two-way chat for lodging complaints and pushing status updates.
Collect chargeable service fees and reconcile against work orders.
Sync staff master data, departments, cost centres, and inventory.
Readers and access cards drive check-in and attendance events.
Plate recognition and barrier control tied to the visitor record.
REST endpoints, webhooks, and OpenAPI docs for anything custom.
In the real world
A citizen files a grievance at the desk. A visitor checks in at reception. A guard verifies them at the gate. Enclave runs all three from one platform, so nothing falls through the cracks between them.

Staff log a walk-in complaint at the desk while citizens raise their own on the web or app.

Reception verifies each visitor against their invite and issues a pass in seconds.

Gates and guards work from the same watchlists, passes, and IoT-linked barriers.
Built for the enterprise
The platform ships with the infrastructure serious operators expect: open APIs, a full audit trail, deep analytics, and hardened access controls, ready to hand to architects, developers, and DevOps teams.
REST APIs with OAuth and JWT, versioning, rate limiting, webhooks, and OpenAPI docs.
Templated, multi-language messaging with scheduling, retries, and delivery status.
Before and after values, device and IP context, exportable logs and retention policies.
Complaint heatmaps, technician productivity, handling time, and satisfaction index.
Versioned, categorized, searchable storage for complaints, staff, assets, and reports.
Offline drafts, biometric login, background sync, localization, and accessibility.
Bulk onboarding for staff, departments, buildings, and assets. Export to CSV, Excel, JSON, PDF.
One search across complaints, visitors, staff, assets, vehicles, and barcodes.
MFA, device and session management, account lockout, encryption with key rotation, and IP restrictions, on SOC 2-aligned controls.
CI/CD pipelines, blue/green deployment, monitoring and metrics, backup validation, and disaster-recovery drills.
WCAG-aligned accessibility, cross-browser support, performance and load testing, penetration testing, UAT, and knowledge transfer.
Deployment
Public-sector procurement often dictates where data can live. Enclave ships in three deployment shapes from the same codebase, so the hosting decision does not change the product.
We host, patch, monitor, and back up. Fastest to go live, with the least internal overhead.
Deployed into your own tenancy or an empanelled government cloud, under your controls.
Installed in your own data centre, including restricted and air-gapped environments.
Regional language packs across web, app, SMS templates, and printed slips.
WCAG-aligned contrast, keyboard navigation, and screen-reader labelling.
Offline drafts and lightweight payloads for sites with patchy connectivity.
Engineered for scale
Who it's for

Municipal and department offices handling citizen complaints and heavy daily visitor footfall.

Corporate offices managing helpdesk tickets, vendors, and staff and visitor access at scale.

Universities and hospitals coordinating complaints, work orders, and gated campus access.

Townships and gated communities managing resident complaints and visitor entry.
Questions
Yes. The same build deploys as managed cloud, into your private or government cloud tenancy, or fully on-premise in your data centre, including restricted and air-gapped setups. Hosting choice does not remove any features.
Every complaint returns a ticket number by SMS or email at the moment it is lodged. That number works on the public web portal, over WhatsApp, and with the helpline, so nobody is forced to install anything.
The IoT layer connects over MQTT, webhooks, and REST, which covers most controllers, biometric and RFID readers, ANPR cameras, and barrier hardware. Exact device models are confirmed during scoping, since availability differs by site.
Yes. Administrators configure complaint categories, workflow states, SLA targets, escalation tiers, and business rules from the admin console. No code changes and no redeployment are involved.
Every action is logged with the user, timestamp, before and after values, IP address, and device. Logs are exportable and follow the retention policy you set, which is usually what auditors and RTI-style requests need.
Pricing is scoped to your deployment, module selection, number of sites, and user volume, and can be structured for phased rollouts. Our team prepares a written commercial proposal after a scoping call.