SymPhos
SymPhos.io

Restaurant operating platform

One system from the phone line to the pass.

An AI answers the phone. A web page takes the online orders. Both land in the same POS as the counter does, and hit the kitchen display the moment they're taken — one menu, one rail, one set of numbers.

Request a demo See how an order moves
Web POS Online ordering AI phone ordering Kitchen display
Live on the kitchen display

Example ticket

The platform

Every way an order arrives, one system.

Most restaurants run a register from one vendor, online ordering from another, and a phone nobody has time to answer. Change a price and you change it three times — and somebody still re-types every order into the register. SymPhos is one system behind all of it.

Counter

Web POS

Runs in a browser on the counter terminal, a tablet, or the owner's laptop — nothing to install, nothing to replace when a terminal dies. Tables, takeout and tabs in one place, and every order from every channel lands here.

Guests

Online ordering

A page your guests open on their phone — nothing to download, no marketplace between you and them, no commission on the order. It reads the same menu, modifiers and hours the register reads, and the order goes straight into the POS as a table or a takeout ticket.

Kitchen

Kitchen display

Phone orders, online orders and counter orders appear on the KDS the moment they're taken — no runner carrying a slip, no gap between the order and the line. Paper too, if the cooks want it: tickets reach the thermal printer through a local bridge, so a spotty connection never stops a print.

Back office

Operations that watch themselves

Scheduled health checks on every location, alerts timed to that restaurant's own hours, and a plain-English digest of what happened overnight — waiting before the doors open.

Phone line

An AI that actually answers the phone.

It picks up on the first ring at 6:40 on a Friday, understands the menu the way a regular says it — "the noodle one, medium spicy, no cilantro" — reads the order back, and puts it in the POS and on the kitchen display before it hangs up. No hold music, no order lost because both hands were full.

  • Answersfirst ring, every ring
  • Understandsyour menu, in plain speech
  • Confirmsread-back before it hangs up
  • Deliversinto the POS and onto the KDS

Next: self-serve kiosk, ordering into the same POS — in development

How an order moves

Five steps, no re-typing.

The same path whether the order starts on the phone, online, or at the counter. Nobody keys it in twice, and nothing waits for someone to notice it.

  1. 01

    The order starts

    The phone rings and the AI picks up on the first ring, or a guest opens your ordering page on their phone — no app to download, no marketplace taking a cut. Either way, nobody behind the counter stops what they're doing.

  2. 02

    It gets taken properly

    Items, modifiers, allergies, pickup time. The system quotes a real window based on what's already on the line, and on the phone it reads the whole order back before confirming.

  3. 03

    It lands in the POS

    As a table or a takeout ticket, in the same place a counter order goes — not in a second tablet someone has to remember to check.

  4. 04

    The kitchen sees it immediately

    Up on the kitchen display the moment it's taken, and on the thermal printer if the cooks want paper. No runner carrying a slip from the front.

  5. 05

    The books close themselves

    The sale settles into the same totals as every walk-in and every online order — one day's numbers, not three reports to reconcile at midnight.

In service

SymPhos isn't a prototype looking for a kitchen. It runs one.

Three Seasons Thai Bistro in Oakland works on this platform every day: the POS at the counter, the online ordering, the kitchen display, the phone line answered by the system. Features don't ship to another restaurant until they've survived a Friday dinner rush here first.

A second restaurant is running on it now too — which is why it was built multi-tenant from the first table: separate data per restaurant, hours and menus per location, and row-level security enforced in the database rather than trusted to the app.

Live deployment
Two restaurants in Oakland, CA — every service
Order channels
AI phone, online ordering, counter — kiosk in development
Kitchen
Kitchen display, plus thermal printing through a local bridge
Architecture
Multi-tenant from day one, row-level security per restaurant
Built by
The operator who has to use it the next morning

Request a demo

Let's run it on your menu.

Tell us about the restaurant. We'll walk the whole path — a phone call answered, the ticket up on the kitchen display, the order settled — on a real menu. Send yours and it'll be the one in the demo.

Or write directly: narin@3seasonsthaibistro.com

We'll reply from a real address within a business day.