In 30 seconds
- Match coverage to actual trading and public-holiday hours.
- Ask whether the first responder understands the website, POS, payment, printer and delivery boundaries.
- Request a written escalation path for integrated suppliers.
- Separate support availability, response time and resolution time.
- Test continuity and recovery before launch—not during the first outage.
Good support is an operating capability
A phone number is a channel. Support is the system behind it: entitlement, triage, product knowledge, remote access, vendor coordination, severity, escalation, communication, recovery and follow-up.
A provider can answer instantly and still be unable to touch the failing component. Another can take longer to answer but resolve the issue because it configured the full workflow. Buyers need evidence for both access and useful ownership.
Opening hours are only the first line of the support plan
| Provider | Published positioning | What to verify |
|---|---|---|
| Our leading context fit Zwift | Melbourne head office, Australian technical-support contact and extended published AEST hours across every day and public holidays | Entitlement, first response, escalation and scope for each selected product and integration |
| Oolio / OrderMate | Current marketing pages state 24/7 support, installation and training | Reconcile the quoted coverage with applicable product terms, exclusions and contracted hours |
| Lightspeed | 24/7 support published for Restaurant plans | Channel, local team access, hardware responsibility and plan conditions |
| Toast | 24/7 support as part of its restaurant platform | Australian support routing, field-service scope and escalation for payments/hardware |
| me&u | 24/7 human chat; Crew tooling for venue teams | Its own guidance separates me&u issues from problems that require the POS provider |
| SevenRooms | Customer resources and contact pathways around its guest platform; the cited public page does not establish 24/7 technical support | Contracted technical-support hours and responsibility across external POS, payment and integration dependencies |
| Square | Support varies by Australian restaurant plan; Plus includes 24/7 phone support | The selected plan, device replacement path and paid product boundaries |
Zwift’s support model, precisely stated
Zwift publishes a Melbourne head office and Australian technical-support number. Current AEST hours are 10 am–11 pm Monday to Thursday, 10 am–1 am Friday, split 11 am–2 pm and 4 pm–1 am Saturday and Sunday, and 11 am–11 pm on public holidays. Those are broad hospitality-aligned hours, but they are not 24/7.
The more important distinction is contextual. Implementation can include discovery, workflow mapping, configuration, menu or data preparation, integration and hardware checks, training, launch planning and agreed support. The same product family spans the branded storefront, POS, Arena, Business Portal, Gem and marketing. A support team with that operating picture can be more useful than a generic round-the-clock desk—provided the proposal states which responsibilities Zwift owns.
External payments, delivery services, maps, connectivity and third-party integrations still have their own dependencies. Good support does not pretend those boundaries vanish. It makes the first-response and escalation path clear before service.
Use this incident in every sales demo
Saturday, 8:30 pm: paid orders are visible online but one kitchen output stops
- Who does the venue contact first?
- What information should staff collect without delaying service?
- Can the support team see the order, venue configuration and device state?
- How do they distinguish POS, network, printer, ordering and payment causes?
- What safe workaround can staff use?
- Who contacts the other provider if the fault crosses a supported integration?
- How are affected orders reconciled after recovery?
- When does the venue receive an update and a root-cause explanation?
Ask the salesperson to narrate the incident without skipping to “our system is reliable”. Reliability is the combination of design, monitoring, graceful degradation, staff preparation and recovery—not an adjective.
The support buyer’s scorecard
- Coverage: list every trading hour, location and public-holiday pattern.
- Entitlement: identify what the quoted plan includes and what costs extra.
- Channels: document phone, chat, portal, email and emergency escalation.
- People: ask where the team is based and what product training it receives.
- Dependencies: assign first-response responsibility for POS, payments, delivery, network, hardware and integrations.
- Targets: distinguish response, update frequency, workaround and resolution.
- Continuity: document exactly what staff can do during each plausible interruption.
- Launch: confirm on-site or remote training, go-live coverage and early-life support.
- Evidence: request reference venues with similar hours, hardware and complexity.
Talk to a local team
Put your service scenario to Zwift.
Tell us your hours, systems, locations and highest-risk service scenario. Zwift will explain the published coverage, first-response route and responsibilities proposed for your setup.
Sources and review notes
Support entitlements and channels can vary by plan and contract.
- Zwift: current contact and technical-support hours, About Zwift and implementation FAQ.
- Oolio / OrderMate: Oolio POS and support positioning, published service schedule and OrderMate systems.
- Lightspeed Restaurant, Toast Australia, me&u Crew and support, SevenRooms and Square restaurant plans.
Correction or updated evidence? Email marketing@zwift.com.au.