Skai Solutions connects to Oracle MICROS, so a phone order taken by the agent arrives as a ticket in MICROS the same way a counter order does, with no re-keying, no second screen and no new hardware. You keep your existing number and your existing POS exactly as they are.
Oracle states more than 200 integration partners and 6.3 billion transactions a year across 180 countries on its Australia and New Zealand Simphony page, read on 6 September 2026. MICROS is the biggest system Skai Solutions connects to and the one where the phone integration behaves least like the other seven, because at that size the menu is usually not controlled in your venue at all.
Oracle MICROS is the enterprise end - hotels, large venues, stadiums and established restaurant groups in Australia and New Zealand.
MICROS sites have the most complex call routing needs and usually the most process around them. Skai Solutions is configured per venue and per call type, and hands off to a human where your procedure requires it.
The boundary is worth reading before a demo, because the honest list is shorter than the one a salesperson would give you.
| Behaviour | Skai Solutions |
|---|---|
| Menu items, prices and modifiers pulled from your live MICROS menu | Yes |
| Order written into MICROS as a ticket against the correct revenue centre | Yes |
| Item marked unavailable in MICROS is refused on the phone | Yes |
| Channel specific pricing or a phone only menu, where you have configured one in Simphony | Yes |
| Course and seat numbers on a dine in check | No |
| Loyalty lookup and points redemption at the point of the call | No |
| Split bills, tabs and open checks | No |
| Kitchen display routing rules beyond what MICROS applies itself | No |
| Taking orders while your site is in Simphony offline mode | No |
The last one is the MICROS specific trap. Oracle publishes offline mode as a Simphony feature, so your terminals keep selling when the venue's connection drops and reconcile afterwards. A cloud phone agent does not have that property. If your link goes down, MICROS keeps trading on the floor and the phone stops, which is the opposite of what most people assume.
In a single site venue on Square or H&L, the person who eighty sixes an item is standing in the building. On Simphony that is often not true. Oracle sells Simphony Frontline Manager precisely so menu items, attributes and pricing can be held at the corporate level with property level flexibility underneath, and its menu management pushes changes across POS devices, digital menu screens, websites and mobile apps at once, with availability set per channel.
Two consequences for phone orders, and neither shows up on a demo:
If you are still working out what the answering layer above a POS actually is, start with what an AI receptionist does for a venue rather than with the integration.
Three failure modes come up on MICROS sites and almost nowhere else. A venue with several revenue centres, say a restaurant, a bar and a function room on the same property, needs the phone ticket pointed at the right one, and a wrong revenue centre produces a ticket that prints in a kitchen that is not cooking it. Second, Oracle's kitchen display already consolidates in house, kiosk, web, app and delivery orders, so the phone stream is one more queue into a screen that is often the real bottleneck at 7.30pm rather than the POS. Third, function and large party enquiries arrive on the same line as pickup orders, and those calls are long, so they are the ones that put everyone else on hold.
Bookings that change on the day belong in the same conversation. If a party of ten calls at 6.40pm to drop to six and cannot get through, the covers are gone whatever your policy says, which is why the rules on charging a no show fee matter less than whether the call gets answered.
No. Checked on 6 September 2026, Oracle's Australia and New Zealand food and beverage pages carry no plan table, no monthly figure and no per terminal price, and the small business Simphony Essentials page that exists on the global site returns a page not found on the ANZ site. Treat MICROS as a scoped, quoted install and budget for implementation as well as licence.
That is worth setting against a published comparison. Square for Restaurants publishes A$0 a month on Free and A$129 a month per location on Plus, read 4 September 2026. The gap is not that one is dearer, it is that with MICROS you cannot budget from a website at all. If you are still sizing the whole phone line rather than the POS, our page on restaurant phone system costs in Australia gives the market bands.
A$299 a month for 500 minutes, or A$599 for 1,500, plus a one-off A$499 setup that covers the MICROS connection and your menu build. In New Zealand that is NZ$325, NZ$649 and NZ$545. Month to month, no lock-in, 30 days' notice. Full pricing.
Before you buy anything, work out what your unanswered calls are actually worth. If the monthly loss is smaller than the fee, don't buy it - we'd rather you found that out now.
Fifteen minutes, your MICROS menu, your hardest order. Bring the one your staff get wrong.
Book a Free DemoDisclosure, recording and retention are configurable, and we will walk through your requirements before go-live rather than after. Bring them to the demo.
No. You keep your existing number and divert calls to Skai. The divert can be switched on and off - during service only, after hours only, or all the time.
Five days from sign-up to live calls. The one-off setup fee covers the menu build, the POS connection and voice tuning for your venue.
Skai transfers the call to your team. It takes the routine volume off your floor and escalates anything that genuinely needs a human.
See every POS Skai connects to, or Skai for New Zealand venues.