Skip to content
AVERIQ
LanguageRUEN
Discuss a project

Reconstructed from the working system

Field measure

On site, a person closes the job on the phone. The office sees the same status.

Mobile · 2026

The public screens are reconstructed. Live orders, company amounts, and internal access are not shown.

Task

Take the measurer's shift and the installer's shift onto the phone, without starting a second database of requests.

Starting problem

The office board does not fit in the hand on site. If the phone keeps its own list, the statuses have diverged by evening.

What was examined

The phone needs today's visits, the card for the site, payment, and handing cash in. The other reports stay in the web account.

How it is built

The app calls the API of the same CRM. The role decides which screens are open. A manager sees payments and cash collection. The person doing the work sees their own jobs.

What the interface shows

  • Large actions, with no table that has been shrunk to fit.
  • The job is called a measure or an installation, not a ticket.
  • Handing cash in is not hidden in a general menu.

Open the demonstration

What the sample shows

The app is built as a working client of the CRM. The portfolio has no store reviews, and no invented install counts.

Modules of the same platform

  • Request board

    A request lives on the board, not in the correspondence between the measurer and the manager.

  • Cash desk and payments

    Payment, the cash desk, and debt look at one request, not at three different spreadsheets.

  • City sites

    A person chooses a city and leaves a request, without entering the internal account.

  • Order account

    The client needs the status of the order, not the company's whole board.

  • Shift calendar

    The shift is visible as a day: who is going out, who is calling back, and what is already closed.