Meet Sam.
An AI phone-ordering assistant being developed to work from the approved menu, clarify an order, and read it back for confirmation.
Calling and interruption handling are still being validated.
SCALLion
In development · Pilot preparation
Every order.
One clear view.
A clearer connection between the phone, the order, and the people preparing it.
SCALLion is being developed for AI phone ordering with Sam, a shared Active order queue, and owner-controlled setup.
SCALLionAn example order
Phone orderingA conversation with Sam
One beef samosa, the two-piece serving, for pickup.
Read back. Confirm. Share with the team.
Active ordersNew · Pickup
Ready for the team’s next step.
1×
Beef samosaTwo-piece serving
Illustrative menu and order data
PhoneConfirmed orderShared view
Built around the restaurant workflow
Designed for teams who need orders to stay understandable from the first conversation to the next action.
The workflow in development
From a conversation
to a shared next step.
The aim is a connected workflow, with a clear place for confirmation and staff oversight.
Give the team one view.
A shared Active queue brings incoming orders into a common workspace, with order details and the next preparation step close at hand.
A consistent handoff from order intake to staff review.
Keep decisions visible.
Explicit order confirmation and owner controls are central to the design. An uncertain request needs review, rather than becoming an assumed order.
A pilot must validate the complete workflow before customer use.
The business stays yours
Your menu.
Your hours.
Your oversight.
Ordering depends on the details being right. SCALLion’s development puts store setup and owner review alongside the ordering workflow.
Talk through your setupStart with an approved menu.
Use the business’s reviewed items, options and availability as the basis for ordering. Menu setup and pilot scope need to be agreed for each deployment.
Set the operating details.
Owner Settings cover store information and opening hours, with protected access for changes that affect the workflow.
Make privacy part of preparation.
Agree how audio, transcripts and operational data will be processed, accessed and retained before a pilot. Those choices depend on the selected deployment and services.
Integration in development
Delivery needs
a defined handoff.
Delivery integration is part of SCALLion’s development direction. Provider approval, access and end-to-end validation are required before a supported connection can be offered.
No delivery-provider partnership or live integration is being represented here. Discuss the intended provider and workflow when defining a pilot.
Common questions
Before we discuss a pilot.
Can I use SCALLion today?
SCALLion is in development and pilot preparation. It is not being offered here as a generally available product. Calling, device behavior and complete operational workflows still require validation before customer use.
Does it replace my point-of-sale system?
This page does not promise a point-of-sale replacement or universal compatibility. A pilot discussion should establish your existing systems, the desired handoff and which connections can be supported.
Is it a standalone tablet product?
Current development pairs a local PC backend with a tablet interface. Supported devices, headset behavior and deployment requirements need to be validated for the selected pilot. Standalone tablet readiness is not claimed.
Which delivery providers are connected?
Delivery integration is in development. No live provider connection or partnership is claimed on this page. Provider approval, access and testing are prerequisites for any supported integration.
A focused next step
Tell us how
your orders move.
Bring your current workflow, the handoff that needs attention, and what a useful pilot would need to prove.