AI CITY TECHNOLOGIES

From reporting a problem to tracking the work

Every request has an owner, a progress trail and a recorded history.

Report an issue quickly

Residents report a problem with a title, description, urgency and attached photos or files. They can write the request themselves or start from Arega’s draft, then track its status in their request list.

A title, description and urgency

Explain what happened and how urgent it is so the service team has the right starting information.

Photos and attachments

Attach a photo of the problem or a relevant document so staff can review supporting material.

Write a request or use an Arega-assisted draft

Write the request yourself or use Arega’s proposed text, reviewing it before submission.

Your own request list and statuses

Find your requests in your own list and see the current stage of each issue.

Keep delivery on track

The team assigns an owner, priority and deadline to each request. Views and filters for new, ongoing, closed and overdue work show who is handling each issue and what remains unresolved.

Assign a responsible person

Assign the request to a specific employee so responsibility for the resident’s issue is clear.

Set a deadline and priority

Set the expected deadline and priority to organize the work queue.

Review new, ongoing and closed work

View new requests, work in progress and completed items separately.

Highlight overdue requests

Identify overdue requests in the list to investigate delays and move the work forward.

Search and filter by work status

Filter by status or search for a specific issue to navigate a large work queue quickly.

Requests awaiting replies or assignment

Identify requests that have no assignee or are waiting for the next reply.

Average resolution-time overview

Review request states and average resolution time in the management summary to assess service delivery.

Keep the conversation with the request

Residents and staff can communicate within the request, adding comments and further photos. Replies and status changes stay in the same history, which Arega can summarize or use to prepare a draft response for the team.

Messages between the resident and responsible person

Keep request-related questions and replies in the same record so information is not scattered across conversations.

Updates on work progress

Add comments about completed steps or the next action to keep the other party informed.

Additional photos

Add new photos to the existing request to show a changed situation or the outcome of work.

A history of replies and status changes

Replies and status changes stay together so the full progression of an issue can be reviewed later.

AI summaries and reply drafts for the team

For a long history, obtain Arega’s summary or draft reply for the team to review before use.

Turn a chat issue into a task

A building-chat issue can become a task proposal whose text you can review. The required support or applicable administrator review leads to an actual request linked to the original proposal.

Prepare a request proposal from a discussion

Turn a problem discussed in chat into a proposed request for the service workflow.

Review and edit the suggested text

Review the proposed title and description so they accurately represent the issue discussed.

Gather participant support

Discussion participants can indicate support to move the proposal through the required process.

Turn an accepted proposal into a request

A proposal with majority support can become a request; cases requiring separate review first go to an administrator.

Preserve the link between the proposal and the request

The created request retains its link to the original proposal, connecting discussion with execution.

Availability depends on the user’s role, enabled services and compatible equipment.