Each clip is 15 to 30 seconds and shows one task from start to finish in a demo building: a request moves across the board, a resident votes, an invoice is generated. Pick the product you care about; each group links to its page, with the details and the limits.
The recordings use fictional data and the English interface, with the captions in the picture. The text under each video says what it shows.
In Easybilly a building has premises with no area. A spreadsheet upload fills the areas after a preview, the setup wizard sets the maintenance fee by premises type and assigns account numbers to every premises, and the building ends up ready for invoicing, shown with its first invoice.
Easybilly generates the monthly invoices for a building: select the premises, check the invoice preview with the total, then generate. The invoices appear in the list as Awaiting payment, and one of them opens as the document a resident receives, with Share, PDF and Print.
Easybilly imports a bank payment file for a building: the preview matches each row to a premises account, the import records the payments, and the payments overview updates. The invoice list then shows each invoice as Paid, Partial or Awaiting payment.
An emergency leak request for one unit is assigned to an executor and dragged across the kanban board from Open to In progress. The board groups requests by executor and status, so a dispatcher sees who is working on what.
An employee writes one sentence to the Unitify bot in Telegram. In AI mode the bot prepares a ticket and shows the proposed action; the ticket is created only after the employee presses Confirm, and it then appears in the Tickets list on the web.
A resident reports a dead intercom panel in the app and attaches a photo. In the web app the request gets an executor and a responsible person and moves to In progress and Completed. The resident sees each status in the app, rates the work and leaves feedback.
In the technician app a technician opens Today, starts the Daily building round task, answers the checklist, notes that nothing was found and sets the status to Completed.
The plan of a demo community shows each plot on the map. Layer switches colour the plots that have open requests or residents, and a click on a plot opens its card with the residents and the open requests.
A manager writes an emergency announcement: type, title, text and the building as the audience. After confirming, it is sent (sending can be cancelled within 15 seconds) and the resident sees it in the Updates feed of the app. The wait after sending is cut in the video.
With auto-reply switched on for residents, a resident writes in the Chat tab of the app and the AI assistant answers from the Resident Guide the management uploaded. Managers see the same conversation in Chats, with the replies marked as Assistant. The waiting time for each reply is shortened in the video.
A manager adds the fitness room as a bookable resource: name, category and location, a photo, one-hour slots, capacity, opening hours and the building. The new resource then appears in the resource list.
A resident opens Booking in the app, picks the fitness room, chooses a day and a time slot and books it. The same booking shows up in All Bookings for the manager.
A manager creates a survey for one building: type Survey, the building as the audience, a title, a description, dates and one question with three answer options. After Publish, the survey is listed in the Voting management panel as Published.
A resident opens Voting in the app, starts the survey, picks an answer, confirms and submits it, and gets a receipt. The manager's panel then shows the results per answer option.
Start free, or book a walkthrough with the team.
