Questions, answered

Anything with a modern browser. A tablet or front-desk PC for self-service registration, a smart TV or a small PC connected to a screen for the display, and the computers your staff already use for the counter console. Current and previous versions of Chrome, Edge, Firefox and Safari are supported.

Most teams are ready in a day: create services, add counters, invite staff, then open the registration page and the display. You configure everything yourself, and we help with onboarding whenever you ask.

English at launch. The interface is prepared for translation, and Filipino is the first language planned.

Not yet. HANA QMS is online and every device needs an internet connection during opening hours. If a connection drops, the display keeps the last known state with a small “reconnecting” notice and recovers on its own, and staff are warned so they never act on stale data. Offline operation is planned for a later release.

No. Customers enter their name (a mobile number is optional), choose a service and get a number. They follow their turn on the waiting-room display, or check their status on their own phone by queue number or mobile number.

Yes. The public status page lets a customer look up their ticket by queue number or mobile number, with no sign-in. It shows their status, position in the queue and estimated wait, refreshes on its own, and never shows anyone else’s details. You can switch the page off if you do not want it.

It is the number of tickets ahead in the service, times that service’s average service time over the last 30 days, divided by the counters currently serving it, rounded up to whole minutes. When there is not enough history it uses the service’s default time. It is shown as guidance, not a promise.

Yes. When printing is on, the registration page opens the browser print dialog with a compact ticket made for standard receipt printers. You can also switch printing off and let customers rely on the screen.

Each service has a prefix of 1 to 3 letters, and each ticket is that prefix plus a running number, for example A001, A002. Numbers restart daily per branch and service, and a number is never reused on the same day, even if the ticket is cancelled.

Yes. Register customer opens the same three steps inside the Staff / Counter panel. Staff can choose the branch and a priority class, and are warned if the same name and mobile already has an active ticket for that service today.

You define priority classes such as Senior citizen, PWD and Pregnant, and their order. Higher-priority tickets are called first within the same service, a fairness rule keeps standard customers moving, and screens show a symbol only, never the reason.

Staff can recall the ticket, up to 3 times by default, or skip it. A skipped ticket stays recallable for 30 minutes by default and then becomes No show automatically. Skipped and No show tickets are reported separately from served ones.

No. A transferred ticket keeps its queue number and its original registration time, so the customer keeps their place in the new line. Parked tickets also return to their original position when resumed.

Each ticket can only be taken once. The first counter to call it gets it, the other counter is told and its list refreshes, and it simply calls the next ticket.

A smart TV browser or a small PC connected to a screen. Open the branch’s display link once; it needs no sign-in after that and runs full screen on a 16:9 display.

Yes. Upload videos in Settings, choose their order and turn them on or off; they loop and pause for every call. Announcement messages, such as opening hours, scroll along the bottom between calls.

Yes. The chime and spoken voice can be switched on or off and their volume set, and a display can be muted where sound is not wanted. Calls still appear on screen.

Yes. Each branch has its own services, counters, display and numbering, staff only see the branches they are assigned to, and reports run per branch or across all of them. A company with a single branch never sees branch controls.

Yes. Set your company and application name, upload a logo and pick one of 4 theme templates. A live preview shows the result, which then applies to the kiosk, tickets, status page and display.

Add an account with full name, username and access level. The system shows a secure temporary password once, and the person must change it at first sign-in. Accounts with history are deactivated rather than deleted.

Yes. Set a daily ticket limit per service, for example 100. Registration for that service closes when the limit is reached, and the page says so.

Your admins can download a backup of your configuration and queue data at any time, and restore one after a clear warning and a typed confirmation. The platform also keeps its own daily backups of every company.

We collect the minimum: a name, and a mobile number only if the customer wants to give one. The display shows only numbers and counters, public pages never show another customer’s details, and personal fields are removed after your retention period (90 days by default). This supports your duties under the Philippine Data Privacy Act.

No. Every company’s users, settings, tickets and reports are strictly isolated, including on public pages and in exports. The platform team cannot read customer names or mobile numbers unless your admins can see a logged support session.

Yes. Queue activity lists every ticket event, such as called, recalled, transferred or completed, with the time, staff member and counter. Admin changes, exports and backups are recorded too, and no user can edit or delete an entry.

You see a plain-language message explaining the limit and how to upgrade, and nothing is deleted. Upgrades take effect immediately. You can see your plan, its limits and how much of each you use at any time.

Each plan sets limits for branches, staff accounts, counters, services, displays, display videos, priority and routing rules, report history and CSV export. Tell us about your branches and we will recommend a plan.