Skip to content

A service coordination layer between the table and the team

The guest calls. The team knows.

Odazivo turns every request from a table into a task with an owner, a timer and an outcome. Sending a signal is easy. The hard part is making sure someone owns it, responds in time and completes the service.

Book a demonstrationSee how it works
  • 01No guest app
  • 02QR and NFC at the table
  • 03Works alongside your POS

Illustrative view · Demo data

01The problem

Everyone sees the guest calling. Nobody is responsible.

In a busy shift a guest waves, calls out, catches an eye or asks the first colleague walking past. The team notices that someone needs something — but noticing does not create ownership. A signal without an owner usually leaves four questions unanswered.

  1. 01

    What exactly does the guest need?

  2. 02

    Who accepted responsibility?

  3. 03

    How long has the guest been waiting?

  4. 04

    Was the request actually completed?

An ordinary signal

12
  1. the guest waves
  2. everyone sees
  3. nobody owns it
  4. the table waits

Odazivo

12
  1. request from the table
  2. request queue
  3. owner
  4. timer
  5. completed

A notification is not an outcome. Odazivo follows the request until someone owns it and completes it.

02Product view

Watch one shift in 60 seconds.

Walk the whole loop yourself: send a request as the guest, accept it as a team member, complete the service. Everything you see is demo data on an illustrative view.

Interactive view · Demo data

An interactive view in four steps. On the guest's phone choose a request, then in the team view press Accept and Complete. The buttons change the state of the view and announce the change.

01 The guest sends a request

Elapsed: 0:00

Step 1 of 4 · No request — next: Send a request

Guest's phone · Table 12

Primer RestaurantTerrace

Table 12

What do you need?

Choose what you need.

Team device · Request queue

Odazivo · TeamShift in progress
  • Table 4Interior · Waiter
    4:28Nobody has acceptedOver time
  • Table 9Terrace · Bill
    3:10Accepted by NikolaAt risk
  • Table 7Interior · Help
    1:12Accepted by MilaAccepted

The other requests in the queue belong to the same shift: Table 4 has waited longer than its threshold and nobody has accepted it — the case Odazivo makes visible before it becomes a complaint.

Request trail

Sent
—
Accepted
—
Completed
—
Owner
—
Total
—

On the guest's phone choose what the guest needs. The request arrives with the exact table and zone.

03Three perspectives

The same request, three roles.

01Guest

Calls without an app or an account.

Scans a QR code or taps the NFC tag and sees their table's page in the venue's visual identity. Chooses what they need and receives honest confirmation: sent, accepted, completed.

The guest experience

02Team

Sees the queue and takes responsibility.

On a phone or tablet sees the table, zone, request type, waiting time and who owns it. The filters New, Mine, At risk and Over time show what is most urgent.

The team view

03Owner and manager

Configures the venue and sees the state of service.

Sets up zones and tables, the guest page's content and design, opening hours, actions and response thresholds. Access is per venue and per role.

The owner view

04What changes

What changes on your floor.

No numbers and no promises. Six situations every owner recognises — and what they look like once a request has an owner, a timer and an outcome.

  1. 01

    The guest does not wave or call out.

    One tap, and the team knows the table, the zone and what is needed.

  2. 02

    The terrace is not forgotten.

    A table waiting past its threshold rises to the top of the queue, wherever it is.

  3. 03

    The manager sees who accepted and how long it is taking — without walking the floor or asking in passing.

  4. 04

    Nobody asks "who had table 9".

    The request's owner is written next to the table, from acceptance to completion.

  5. 05

    The bill arrives before the guest runs out of patience.

    A bill request has a timer and cannot get lost.

  6. 06

    The shift leaves a trail instead of an argument.

    When it arrived, who accepted it and when it was completed stay on record.

05The difference

Not a QR menu. Not a bell. Not a POS.

Odazivo fills the space those tools leave empty: what happens between the moment a guest asks for something and the moment they are served.

  • Opens content (menu)

    QR menu
    Yes
    Call button
    No
    Team message
    No
    POS
    No
    Odazivo
    Yes, if the venue chooses

  • Carries what the guest needs

    QR menu
    No
    Call button
    No
    Team message
    Yes
    POS
    No
    Odazivo
    Yes

  • Knows the table and zone

    QR menu
    No
    Call button
    Partly
    Team message
    No
    POS
    Yes
    Odazivo
    Yes

  • Measures how long the guest waits

    QR menu
    No
    Call button
    No
    Team message
    No
    POS
    No
    Odazivo
    Yes

  • One owner per request

    QR menu
    No
    Call button
    No
    Team message
    No
    POS
    No
    Odazivo
    Yes

  • Records that service was completed

    QR menu
    No
    Call button
    No
    Team message
    No
    POS
    No
    Odazivo
    Yes

  • Payments and orders

    QR menu
    No
    Call button
    No
    Team message
    No
    POS
    Yes
    Odazivo
    No — stays in the POS

Odazivo does not replace the POS, does not take payment and does not take the order. It works alongside the existing system and organises the service around it.

Your POS keeps handling orders and payment. Odazivo handles the call, the bill, help, waiting and responsibility.

06Who it is for

For floors where one person cannot see every table.

It is worth most where coordination breaks down: several zones, a terrace, separate rooms, busy shifts, changing responsibilities, guests who do not know who serves their area.

  • A small venue where one team member always sees every table

    Coordination rarely fails there, so the benefit is smaller. We are happy to assess it together.

  • A venue looking for full online ordering or a POS replacement

    That is not Odazivo today. Service requests, yes; orders and payment stay in your system.

We do not claim every hospitality business needs Odazivo. We claim that where requests get lost, the loss becomes visible.

01Terraces and gardens

The terrace is out of sight of the bar: a guest waves, and nobody inside sees it.

A request from the terrace enters the same queue as the interior — with zone, table and waiting time — and rises to the top the moment it passes its threshold.

Apply with your terrace for the pilot

02Hotels, pools and rooftops

A guest at the pool sees no staff at all and does not know whom to call.

A sunbed or a table by the pool has its own plate; the request reaches the team responsible for that zone, with an owner and a timer.

Apply with your hotel for the pilot

03Bars and large rooms

At the counter every request is verbal: shouted, heard — or lost.

A request from a table is written down before it is spoken; who accepted it and how long it is taking is visible to the whole shift.

Apply with your bar for the pilot

07Setup

Tables, zones, plates, team. Then a real shift.

Odazivo is software plus a physical touchpoint at the table. Setup covers both and ends with a trial in a real shift, not a presentation.

Plate on the tableIllustrative view · Demo data
  1. 01

    Account and venue

    We create the venue, the roles and the team members.

  2. 02

    Zones and tables

    Interior, terrace, bar — each zone gets its tables and response thresholds.

  3. 03

    Secure table links

    Every table gets a unique, unpredictable link tied to the venue, zone and table.

  4. 04

    QR/NFC plates

    Plates go on the tables. The guest never picks a table number — the link already knows it.

  5. 05

    Content and design

    Menu, links, Wi-Fi, opening hours and the visual preset of the guest page.

  6. 06

    Team and a trial shift

    A short team onboarding, then Odazivo runs in a real shift and we review the experience together.

What hardware is needed

  • The phones or tablets the team already uses (the app runs in the browser, as a PWA)
  • One QR/NFC plate per table — part of the setup
  • Internet at the venue; the guest uses their own phone
  • No new terminals, printers or POS changes
Setup flow and pricing

08Configuration

The owner decides what the guest sees and how the team works.

Three areas in the owner application cover everything a venue needs to control — without technical knowledge.

Content · what the guest receivesIllustrative view · Demo data

01Content

Logo, venue links, menu source: a PDF or an external link. Configured and unconfigured states are clearly distinguished.

Design · preset, preview, publishIllustrative view · Demo data

02Design

Preset selection, a live preview of the guest page, draft and published versions. Advanced colours with contrast validation.

Settings · saved per sectionIllustrative view · Demo data

03Settings

Languages, contact, Wi-Fi, opening hours, which actions the guest sees, response thresholds and repeat-request rules.

09Pricing

Setup, plates and software — no hidden items.

The offer consists of a one-time setup with QR/NFC plates and a software subscription. Packages are structured by venue size and number of tables.

  • One-time setup: account, zones, tables, links, plates, team onboarding
  • Subscription: access to the guest, team and owner applications, with support
  • Additional tables and plate replacement as clear line items
See the packages

10Security

A guest without an account may send a request. They may not cause chaos.

The open guest page is the most sensitive part of the product. That is why protection is built into the server and the database, not only the interface.

  • Data separated per venue

    An account sees only the venues where it holds a membership. Changing a URL or a request does not open someone else's data.

  • Roles: staff, manager, owner

    Permissions are checked on the server and in the database, not by hiding buttons.

  • Abuse protection

    Unpredictable per-table links, repeat limits, opening hours, the ability to mute a table.

  • The server owns the statuses

    Acceptance and completion are recorded in the database, so two people cannot 'own' the same request at once.

Security and privacy

11Next step

A demonstration for your venue, then a pilot in a real shift.

Show us how service flows at your place. We show Odazivo on your zones and tables, and then we try it together in a shift.

Book a demonstrationWhat the pilot looks like

Pilot

What you get if you say yes.

The pilot is Odazivo in your real shift, on your tables, with us alongside. This is the whole scope — no small print.

Duration
14 days
What we set up
  • Account, venue, zones and tables
  • QR/NFC plates for the agreed tables
  • The guest page: menu, links, Wi-Fi, design
  • Team, roles and a short onboarding before the shift
What we need from you

Not much. The rest is our job.

  • Number of tables and zones (approximately)
  • Which devices the team uses during a shift
  • Who will be the account owner and who the manager
  • The menu as a PDF or a link, if you want guests to see it
  • The venue logo, if you have one
What happens at the end
A joint review: what worked, what needs adjusting — then your decision. Moving to the Venue package does not require reconfiguring.

The pilot has no subscription during the trial shifts; we provide the plates for the agreed tables. All other terms are agreed directly, before the first shift.

Apply with your venue for the pilot

12FAQ

What owners ask first.

All questions and answers
Does the guest have to install an app or create an account?

No. The guest scans a QR code or taps the NFC tag and opens a plain page in the browser. No installation, no account, no sign-in.

Does Odazivo replace our POS?

No. Odazivo does not issue bills, take payment or enter orders. It works alongside your existing POS and organises the service around it: calls, bills, help, waiting, responsibility.

What if the team does not allow notifications on their phones?

The app keeps working. While it is open, the request queue refreshes in real time without manual reloading. Push notifications are an extra channel, not a requirement.

How long does setup take?

Configuring the venue, zones and tables is a matter of hours, not weeks. Plates are placed in one visit and the team is onboarded shortly before the trial shift.

13Who is behind Odazivo

A small team from Serbia, in your shift.

A word from the founder
I'm building Odazivo because I've spent years watching guests wave while nobody was responsible. The problem isn't the people — it's that the signal has no owner. So this is not another button; it's a queue where every request has a name, a time and an end. The first venues join the pilot this season. — Uroš, founder
  1. 01

    Built and supported from Serbia

    Development, setup and support are in Serbian and English, from people who come to the venue.

  2. 02

    No guest accounts, no tracking

    The guest leaves no name or phone number. Neither the site nor the product uses tracking tools.

  3. 03

    We sell what exists

    The service-request flow works today. Whatever is planned is clearly labelled as planned.

Security and privacyWhat we will publish after the pilot

Sending a signal is easy. The hard part is making sure someone owns it, responds in time and completes the service.

That is Odazivo.

Book a demonstrationSee pricing

Quick offer

A quick offer for your venue

Number of tables, zones, city and a contact. You receive a written offer after a short conversation — no obligation.

Prefer the full enquiry with details