A phone order taken by Skai Solutions arrives in Tevalis as a ticket, the same way a counter order does, with no re-keying, no second screen and no new hardware on your pass. You keep your existing number and your existing terminals, and setup takes 5 days.
Tevalis is a hospitality technology platform founded in the United Kingdom, with more than 2,500 sites and over 8,500 terminals installed globally. It has an office in New Zealand and is distributed here through local partners, which is the practical reason it turns up in this market far more often than its UK origin would suggest.
The important thing about the Tevalis install base, for anyone thinking about the phone, is its shape. Tevalis is built for operations with more than one revenue point: hotels with several outlets, stadiums, theatres, food halls, visitor attractions, pubs and multi-site restaurant groups. Its integrations directory, read 12 October 2026, lists more than 200 specialist providers across payments, reservations, ordering, loyalty, delivery and stock management, and it carries a region filter with Australia and New Zealand as separate options, which is a fair signal that the local install base is real rather than incidental. Single owner operated cafes are not the typical Tevalis site.
That matters because a group has a different phone problem from a single venue. A single venue misses calls because everyone is on the floor. A group misses them because the caller reached the wrong place, or a central number that nobody owns, and gave up somewhere in the middle.
Five steps, and none of them touch your hardware.
The menu build is the work that makes the difference, and it is why setup is five days rather than an afternoon. Regulars order by nickname and the agent only knows what was loaded, so the useful part of go-live is the hour spent on the twenty items people ask for by the wrong name.
Yes, and on Tevalis this is usually the whole point. Skai Solutions routes by venue, so a caller reaches the right location's menu, hours, booking rules and pickup times rather than a generic group line that hands them to whoever answers first.
Three things a group should test on a demo, because they are where routing quietly fails. Ask what happens when a caller names a suburb rather than a venue. Ask what happens when one site is closed and the other is not. And ask what happens on a public holiday when two sites have different hours, which is the case that breaks most central-number setups.
Accents are the other multi-site variable. A group with venues in Auckland and Brisbane is asking one speech model to handle two quite different sets of vowels plus Māori place names. Skai Solutions is tuned on Australian and New Zealand speech for exactly this reason, and a demo in a quiet room proves nothing about it. Put a real order through on a real line.
Worth setting out, because "Tevalis POS" is a stack rather than a till. Tevalis names its own modules like this: Point of Sale, which it calls EPOS Core, plus mPOS for handhelds, Self Service Kiosks, Stock Management, Kitchen Management, Finance Management, Customer Management, Centralised Management, and Business Analytics and Insights. A site usually runs some of that list, not all of it, and which modules you run changes what a phone order can do when it lands.
The two that matter most for the phone are Kitchen Management and Centralised Management, and almost nothing written about phone answering goes near either.
This is the question that decides whether an integration is useful or just technically true. The Tevalis Kitchen Management System describes its own behaviour, read 12 October 2026: orders taken on EPOS or mPOS appear on screen the moment they are placed with no re-keying, tickets can be displayed as a single item, a list, a consolidated view or a ticket view with the fonts, colours and layout configurable, tickets are automatically prioritised, and colour-coded warnings and late flags show a ticket running behind before it reaches the pass. Items can be bumped individually or the whole ticket bumped in one go, and online and delivery orders from integrated providers land in the same view.
Three consequences for a phone order, and they are the honest ones.
What does not sync, plainly: nothing we send changes a product, a price, a menu layout or a tax setting. Modifiers and sold-out states are read from Tevalis, so an item marked unavailable there cannot be sold on the phone, and an item with a badly named modifier in Tevalis will be badly named on the phone too.
Through Tevalis, yes, and that is the right place for it. Centralised Management lets a head office team control products, menus, POS layouts, price changes, promotions, tax rates, currencies and user permissions across every brand and site, with price groups per location and changes pushed to the whole estate, a single brand or selected venues. Because the agent reads the live menu, a central price change reaches the phone at the same time it reaches the terminals, with nobody updating a second system.
One detail no vendor page mentions, including ours until now. Tevalis describes that central tax control as "VAT rates", because it is a British-built platform selling into this region. An Australian or New Zealand operator is therefore setting GST through a field named for a different country's tax. It works, and it is not a criticism of the product. It is worth knowing before a head office user goes looking for a field called GST and does not find one.
It does not change your menu, your pricing or your Tevalis configuration. It reads what is there. If an item is wrong in Tevalis it will be wrong on the phone, and the fix belongs in your back office rather than in the agent.
It does not replace your floor staff on anything requiring judgement about the business, such as whether to squeeze a table of eight into a full Saturday. It does not handle ticketing, gaming or attraction flows that some Tevalis sites run alongside food and beverage. And it is not the right buy for a Tevalis site whose phone mostly carries supplier calls and general enquiries rather than orders and bookings. In that case a basic message-taking plan does the job for less, and it is not us.
A$299 a month for 500 minutes or A$599 for 1,500, plus a one-off A$499 setup covering the Tevalis connection, the menu build and voice tuning. In New Zealand that is NZ$325, NZ$649 and NZ$545. Prices exclude GST. Month to month, no lock-in, 30 days' notice.
For a group, the number worth working out before you buy is not the fee, it is the cost of the hour you currently roster to cover the phone at each site. Cover a dinner peak from 5pm to 9pm seven nights and that is about 121 hours a month, roughly A$4,000 at the A$33.05 award-free adult casual rate before superannuation or penalty rates. That is Skai Solutions' own arithmetic on published Fair Work rates, shown so you can put your own roster through it. If the monthly loss is smaller than the fee, do not buy it.
Full numbers sit on the Australian pricing page and the New Zealand pricing page. The full list of POS systems shows what else connects today. If you are still working out how this category behaves on a real line, start with how AI phone answering works step by step, and the booking side of the same problem is on what labour should cost.
Fifteen minutes, your menu, the order your staff get wrong most often.
Book a Free DemoYes. A phone order taken by the agent arrives in Tevalis as a ticket, the same way a counter order does, with no re-keying and no second screen. The one-off setup fee covers the Tevalis connection and your menu build, and setup takes five days.
Yes. Skai Solutions routes by venue, so a caller reaches the right location's menu, hours, booking rules and pickup times rather than a generic group line. Test the awkward cases on a demo: a caller naming a suburb, one site closed while another is open, and a public holiday where hours differ by site.
No. You keep your existing number and divert calls to Skai Solutions, and the divert can be switched on and off for during service only, after hours only, or all the time. No new handsets, no new terminals and nothing added to your pass.
No. It takes orders against your live Tevalis menu including modifiers and sold-out items, so stock state in Tevalis governs what it can sell. It reads your configuration and does not change it, so an item that is wrong in Tevalis will be wrong on the phone until it is fixed in the back office.
Five days from sign-up to live calls. Most of that is the menu build and voice tuning rather than the connection itself, because the agent only knows the items that were loaded and regulars order by nickname.
The call transfers to your team. Anything outside the order and booking flow, including complaints, supplier calls and changes to a booking made under another name, should be handed over rather than attempted, and every call leaves a transcript and a recording so you can audit what it got wrong.