The register rings and the guest vanishes
Your POS watches every table pay and does nothing with it. The guest who came three Fridays running and then stopped is a pattern your systems saw — and nobody's system acted on.
Thirteen screens covering a working restaurant — menus, point of sale, kitchen display, table tablets, inventory, and a public ordering and reservation site on your own address — with every guest landing in the same contact record your marketing already uses. An order is CRM activity the moment it happens; no sync to configure, no second customer list.
Tuesday is slow because the only people who know about Tuesday are the ones already sitting in the room.
It is that nobody has the hours, and the cost of skipping it never shows up as a line on any invoice.
Your POS watches every table pay and does nothing with it. The guest who came three Fridays running and then stopped is a pattern your systems saw — and nobody's system acted on.
Third-party ordering brings you the sale and keeps the relationship. The guest who ordered through the app is the app's customer, marketed to on the app's behalf — including toward whoever is paying the app more this month.
The couple who loved dinner will not remember to say so on Saturday. The only moment the ask works is right after the meal — and no one on a busy floor is going to make that ask by hand.
Install
The Restaurant app is a one-time purchase from the app marketplace inside your workspace. It runs on your workspace's own contacts, payments and automations — no integration project, nothing to sync.
Serve
Menus with modifier groups and one-tap 86'ing, a POS that splits checks evenly or by item, per-station kitchen tickets, a per-table tablet screen for the guest, and a live floor view of open checks and upcoming bookings.
Publish
Ordering and reservations at /eat/your-restaurant — or your own custom domain — fully under your brand. The ready-made website template reads the live menu, so 86'ing a dish updates the site and the kitchen at once.
Return
Every guest is a CRM contact, so slow nights get a broadcast to the people who actually come in, the review request goes out with the receipt, and the reply lands in the same inbox as everything else.
These are not roadmap items. Each one is running in production today, described here in the same words the full product catalog uses.
Run the floor, the kitchen, and online orders from the system that already holds your customers.
Thirteen screens covering a working restaurant — menus, point of sale, kitchen display, table tablets, inventory, and a public ordering and reservation site on your own address — with every guest landing in the same contact record your marketing already uses.
Reach a whole segment on any channel, from one screen.
One-off blasts by email, SMS, ringless voicemail, outbound IVR or AI call — one composer, one audience builder, real analytics. Multi-step follow-ups are automations.
Define an audience once as rules and let it keep itself current.
Rule-based audiences over the contact record and everything attached to it, so “booked but never showed, and nobody has called them in two weeks” becomes a saved segment you send to — not a spreadsheet someone exports again every Monday.
Every finished job asks for the review by itself.
Generate a trackable review link per customer and send it from a workflow the moment work is marked complete. You see who opened it, who clicked, and who left one.
Stop switching apps to find out what you already told them.
Inbound and outbound SMS, email, WhatsApp, Messenger, and Instagram threaded together per contact, with color-coded bubbles for direction.
See what a contact paid without opening Stripe.
Connect one or more Stripe accounts and sync customers, payments, refunds, subscriptions, and failed charges into Chirply's customer and revenue views.
This is the part of Chirply that solves restaurant suite. See the other 14 areas — CRM, scheduling, messaging, automations, funnels, commerce, reputation and the rest — all included in the same workspace.
You do not have to migrate anything to find out whether this works. Start the trial, set up the one thing you came here for, and judge it on that.
Your trial runs on Scale, the top plan, so nothing is locked while you evaluate. If restaurant suite is all you need afterwards, Grow at $77/mo carries it — switch down before the trial ends and keep the lower price.
Your order
$0 today. A card keeps the workspace running after the trial, and Scale renews at $97/month unless you change plans or cancel first.
Cancel any time before day 14 and nothing is charged. Calls, texts, emails and contacts are unlimited on every plan — you bring your own Twilio, Mailgun and model keys and pay those providers directly.
No trial subscription charge today. Cancel before renewal.
Provider usage and optional app purchases are separate. The card only exists so a workspace you decide to keep does not stop working on day 31.
The 14-day trial delivers the platform it runs in — the CRM, messaging, payments and reviews. The Restaurant app itself is a separate one-time purchase from the app marketplace inside your workspace, available on any plan. You buy it once; it is not a per-terminal monthly subscription.
Cards are taken on your own Stripe account, so you pay Stripe's processing fees and nothing on top. Online orders come through your own site on your own domain — there is no per-order marketplace commission, because there is no marketplace in the middle.
Yours. Ordering and reservations live at /eat/your-restaurant or on your own custom domain, fully under your brand, with no mention of the platform. Guests get their own links to track an order, pay from their phone, or cancel a reservation without calling.
Thirteen screens of a working restaurant: menus, POS, kitchen display, table tablets, a live floor view, inventory with recipes that deplete stock as dishes are fired, a reorder list, and the public ordering and reservation site.
Your guests are contacts, so 'people who have ordered before' is a segment, not an export. Send that segment a text about tonight — from your own number, with replies threading into the same inbox your team already answers.
Weighing it against something specific?