INTEGRATIONS
What Fork Time connects to, and what it does not need to.
Fork Time connects to CloudWaitress, PushPOS and Square POS for phone ordering, sends and receives guest messages through the WhatsApp Business Platform, SMS and email, takes card payments and deposits through Stripe, and exposes live availability and booking actions through an MCP server for compatible AI clients that have been configured with Fork Time. Guest channels and payments are built in rather than added on, because Fork Time holds its own reservation book instead of syncing with another platform. That means reservations, AI answering, deposits, waitlists, walk-in tools and guest records all work with no integration connected at all. A POS connection is needed only for phone ordering. If your point of sale is not listed, tell us which one when you book a demo, because that is how we decide what to build next.
WHAT IS BUILT IN
These are not integrations you configure. They are how the product works. If you build restaurant software and want to connect it to Fork Time, start on the partners page.
Guest channels. Phone through Telnyx, WhatsApp through the WhatsApp Business Platform, SMS, email through Resend, and web chat on your own site. A guest reaches you on any of them and the conversation lands in the same inbox against the same guest record.
Payments and deposits. Card holds and deposits run through Stripe. Fork Time never takes custody of guest money; it moves between the guest and your restaurant.
AI assistants. Fork Time provides an MCP server for compatible clients and workspaces configured with Fork Time. Where the client supports the required actions, it can check live availability and complete a booking with your rules applied, or let an operator work with the live book by asking. Client support, account plans and administrator settings vary. The connection does not guarantee placement or a Reserve button in consumer AI search.
The reservation system itself. There is nothing to connect it to. Fork Time is the book, so there is no sync to fall out of step and no second platform to keep paying for.
POINT OF SALE
Three official integrations, each verified against your specific configuration before you go live.
CloudWaitress (cloudwaitress.com). Online ordering and reservations for restaurants. Founded by Christopher Timm, who built the first version in 2012 for his family's restaurant in New Zealand and launched it commercially in Perth in late 2015. CloudWaitress is headquartered in Australia and runs on a commission-free model: the restaurant keeps the full order value on pickups, deliveries and QR dine-in, and pays a flat plan fee instead. It runs on the Windows and Android devices a venue already owns, and its own POS integrations include Lightspeed, Abacus and PushPOS. Available now. We confirm your CloudWaitress setup and exactly what data moves in each direction before activation.
PushPOS (pushpos.com). Hybrid cloud point of sale built in Australia for hospitality and retail. Hybrid means the till keeps trading when the internet drops: transactions store locally and sync when the connection returns, with an optional 4G SIM fallback across three networks. It runs on standard Windows hardware and takes payments through Zeller, Tyro, Linkly, ANZ Worldline, Westpac, NAB and Verifone terminals, with Uber Eats, DoorDash, Uber Direct and Xero connected. PushPOS reports more than 1,200 Australian businesses on the platform. Available now. We confirm your PushPOS build, order types and terminal setup before activation.
Square POS (squareup.com). Payments and point of sale. Available now. We confirm your Square products, permissions and venue setup before activation.
All three support phone ordering on the $299 plan. If you run CloudWaitress for online orders and PushPOS at the counter, Fork Time connects to both, so a phone order lands in the same flow as a web order.
WHY THE POS LIST IS SHORT
Most reservation platforms publish a long integration directory. A share of those entries are one-way connections built once and not actively maintained, and the restaurant discovers which is which during service.
We verify each connection against your actual configuration before you go live. That takes real time per integration, which is why there are three and why all three work.
HOW THE NEXT ONE GETS CHOSEN
By demand, and that is the whole process. Tell us which point of sale you run when you book a demo. The systems our restaurants actually use are the ones we build next, and we would rather add a fourth that works than list a twentieth that does not.
If your POS is not here, Fork Time still runs. You lose phone ordering and nothing else.