We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

We’ve updated the interface fields for filling out issues. Filling out requests, surveys, and checklists is now smoother and faster.

Linking locations to QR codes is now even easier. The app remembers where you’ve already linked them and automatically suggests the right location next time.

Linking locations to QR codes is now even easier. The app remembers where you’ve already linked them and automatically suggests the right location next time.

Linking locations to QR codes is now even easier. The app remembers where you’ve already linked them and automatically suggests the right location next time.

Closed requests are now easier to find — the Archive is available alongside all other request lists. We’ve added even more transparency to performance tracking: request lists and details now show the automatically calculated completion duration — e.g., “closed in 2h 15m.”

Closed requests are now easier to find — the Archive is available alongside all other request lists. We’ve added even more transparency to performance tracking: request lists and details now show the automatically calculated completion duration — e.g., “closed in 2h 15m.”

Now it’s easier to navigate the list of requests. Instead of showing only the location name, the full location path is displayed — for example: Building → Floor → Kitchen. If you have similar names on different floors or in different buildings, there’s no need to open a request to find out where exactly the issue occurred — the relevant information is visible right away. For large facilities, you can expand or collapse the full path as needed.   In addition, when assigning executors or assistants manually, you’ll now see not only their names but also their job titles. This is especially useful for large company with many employees — it helps you quickly find the right person for the request.

Request analytics are now more accurate. Previously, requests could be closed immediately, skipping the ‘In-progress’ stage. Now the workflow is unified: before closing, the assigned employee must first start the request. This ensures that reports reflect more accurate request timelines.

Request analytics are now more accurate. Previously, requests could be closed immediately, skipping the ‘In-progress’ stage. Now the workflow is unified: before closing, the assigned employee must first start the request. This ensures that reports reflect more accurate request timelines.

Sometimes a request can’t be completed for objective reasons — it falls outside the area of responsibility or is no longer relevant. Now, such requests can be rejected with a clear explanation, so they don’t linger in the system. • When an employee rejects a request, it will be archived with the status “Rejected”. • The requester will receive a notification with the reason for the rejection. • In the Rejected Requests report, managers can review the reasons and use the insights to improve processes.

Sometimes a request can’t be completed for objective reasons — it falls outside the area of responsibility or is no longer relevant. Now, such requests can be rejected with a clear explanation, so they don’t linger in the system. • When an employee rejects a request, it will be archived with the status “Rejected”. • The requester will receive a notification with the reason for the rejection. • In the Rejected Requests report, managers can review the reasons and use the insights to improve processes.

Sometimes a request can’t be completed for objective reasons — it falls outside the area of responsibility or is no longer relevant. Now, such requests can be rejected with a clear explanation, so they don’t linger in the system. • When an employee rejects a request, it will be archived with the status “Rejected”. • The requester will receive a notification with the reason for the rejection. • In the Rejected Requests report, managers can review the reasons and use the insights to improve processes.

Sometimes a request can’t be completed for objective reasons — it falls outside the area of responsibility or is no longer relevant. Now, such requests can be rejected with a clear explanation, so they don’t linger in the system. • When an employee rejects a request, it will be archived with the status “Rejected”.  • The requester will receive a notification with the reason for the rejection. • In the Rejected Requests report, managers can review the reasons and use the insights to improve processes.

You can now view the maintenance history of a specific location or equipment by scanning a QR code. To show the Maintenance History icon on the action screen, go to the location settings and define who can access the history. Access can be public (visible to everyone), limited to authenticated users, or restricted only to users with specific roles. Tapping the Maintenance History icon opens the full list of requests for that location — both resolved and planned.

You can now view the maintenance history of a specific location or equipment by scanning a QR code. To show the Maintenance History icon on the action screen, go to the location settings and define who can access the history. Access can be public (visible to everyone), limited to authenticated users, or restricted only to users with specific roles. Tapping the Maintenance History icon opens the full list of requests for that location — both resolved and planned.

You can now view the maintenance history of a specific location or equipment by scanning a QR code. To show the Maintenance History icon on the action screen, go to the location settings and define who can access the history. Access can be public (visible to everyone), limited to authenticated users, or restricted only to users with specific roles. Tapping the Maintenance History icon opens the full list of requests for that location — both resolved and planned.

For the convenience of employees, we have redesigned requests’ service info in the iOS app. • Request date and number are now at the top. • For requests created in chats, the marker "From Chat" will display. • The location is provided right below the request type. • Status, resolution time, SLA are all in one field. • The requester information is more structured. • The responsible and assistants are listed in a single block. • You can now call the employee who assigned the request.

Rating and reopening requests is now more convenient: • In the mobile app, the Reopen Request button has been moved from the menu directly into the request content. • Tasks created in chats can now be rated from the conversation view.

A comment specifying the reason for an SLA change is now recorded in the request history along with the updated resolution time. For the text label attribute, you can now define not only the font size but also apply bold or italic formatting. Location confirmation via QR code is now supported in offline mode. Enable this option in the attribute settings, and the employee’s location will be captured offline and verified later when they finish the inspection.

• Added a new feature to ensure nothing important gets overlooked. Now employees can mark critical or urgent requests as high-priority. This will be logged into the request history, and the responsible will get a notification to resolve the request as soon as possible. High-priority requests will be clearly marked and will appear at the top of the list in the Profile. • Additionally, you can view details of closed requests directly from the chat, no need to navigate to the archive.

• Added a new feature to ensure nothing important gets overlooked. Now employees can mark critical or urgent requests as high-priority. This will be logged into the request history, and the responsible will get a notification to resolve the request as soon as possible. High-priority requests will be clearly marked and will appear at the top of the list in the Profile. • Additionally, you can view details of closed requests directly from the chat, no need to navigate to the archive.

We've improved request grouping in the mobile app, giving users with extended permissions access to 4 groups now instead of 3: • My — this group is available to all users and displays new requests ready to be started. • Assigned by me — a new group for users with permissions to assign requests. No more tediously searching for assigned requests — every request you've assigned will be right here. • For review — just like before, this group contains requests that should be reviewed and closed. • For monitoring — this new group contains requests that don’t require immediate action. Here you'll find requests for your team to resolve and requests created in locations you monitor. Since no action is needed, this group is listed last. Closed requests are automatically moved to the archive, which has also been optimized and now includes a universal search. Additionally, we've boosted request processing performance — it’s faster than ever!