Management and Reporting

Find a visitor's arrival, check a vendor's recent visits or follow up on a resident's concern. The ZUUL management website gives authorized staff searchable community records and reports, with access based on their role and the community they manage.

 

Start with the question, then find the record

 

A manager answering a question about yesterday's arrival can find the visitor log and review any attached ID and plate images. Staff can also search resident, vendor, vehicle, access, package, key and concern records, then use supported exports and custom reports for follow-up and planning. Reports for rentals, amenities and Patrol follow the selected modules and permissions.

 

Understand the work at each entrance

 

The Guard Monitoring Dashboard shows recorded visit counts, processing times, reported calls and cases needing attention by guard account and entrance. A manager can narrow the view to an entrance and time period, then review delays with the gate team.

 

Can the dashboard measure individual attendance?

 

No. Shared accounts describe team activity, not an individual employee's attendance. Processing times can include waiting and connectivity delays, and missing measurements do not mean no work occurred. Guard Monitoring is operational reporting, not a time clock or the Centurion Patrol and Dispatch module.

 

Ask Community AI, then open the record

 

Which reservation requests await approval? Which maintenance reports need follow-up? Community AI helps authorized managers find recorded information they have permission to see, then open the source records to review it. It is a manager-only reporting assistant, not a service for residents or guards to ask general questions.

 

The manager decides what to do next through the usual authorized tools. Community AI cannot grant entry, open gates, approve requests, change records, take payments or send notices. It is separate from identification processing with ID AI and residents' telephone visitor requests with AI Call-In.

 

A practical onboarding path

 

GTS works with your team to gather resident data and policies, identify missing or incorrect imported information, schedule training and plan resident communications. Staff test the selected processes before launch, with support for residents during the transition.

 

Our standard plan targets a 45-day deployment followed by 45 days of extended support, with the schedule aligned to data readiness, installation and the selected scope.