24/7 Pizza Orders via Text.

Your customer texts the AI number we generate to place their order, an AI agent greets them, asks for their order, asks clarifying questions about size, toppings, pickup vs. delivery, builds the cart, and sends the ticket directly to your POS. The whole interaction is by SMS — no app, no download, no signup.

2% per order processed. No monthly minimum. No setup fee. No per-message fee. No contract. On a typical $30 order, that's $0.60.

About 30 minutes. Connect your POS, set up your menu and business hours, and your agent is live. Test it with a friend and you're taking real orders.

Toast, Square, Clover, Heartland, Aldelo, and Lightspeed. Orders flow directly to the kitchen printer or KDS without re-keying.

Almost certainly yes. For any POS that exposes a public ordering API or accepts webhooks, we can build a custom integration in a few days. For legacy or closed systems (e.g. older on-prem POS like Aloha or Micros without an ordering API), we still work — the agent sends the completed order to a designated email, printer, or shared screen at the store, and your staff confirms with a one-tap acknowledgment so the kitchen can start the ticket. You get the full automation on the customer side; the only manual step is a single tap at the kitchen, which is faster than typing the order in.

Yes. You can use your own in-house delivery drivers, or dispatch through Uber Direct — you keep 100% of the food revenue and pay no commission or per-order fees to anyone but us. The customer texts their address, the agent confirms the drop-off, and the driver is dispatched automatically.

Yes. You can send a campaign — a coupon, a Friday-special drop, a winback, a birthday offer — and the customer replies to that exact text to place their order. The marketing message becomes the start of the conversation, the AI agent takes it from there, and the ticket prints to your POS. No second channel, no app, no friction.

Yes — that's the whole point. During the Friday-night rush, the AI handles every incoming order in parallel, with no busy signal, no hold time, and no dropped calls. Each customer has their own thread, and every ticket prints to your POS in the order it was completed. The only thing it can't do is make the kitchen faster.

Either way — your choice. By default, we route payments through your POS's existing processor, so funds land directly in your existing merchant account and reconcile the same way they do for in-store orders. If you prefer to use an outside provider like Stripe, Authorize.net, Square Online, or any other gateway, we can plug that in instead — useful if you want lower card-present rates, want to keep a separate online-payment processor, or already have a gateway contract you want to keep. PCI scope stays on the processor in both cases; we never store card data.

Yes. You control your ready-time window from a simple dashboard. If a Friday rush stacks up and you need to push pickup times from 30 minutes to 45, or add 15 minutes to every delivery estimate, you change it in one place and the agent immediately starts quoting the new window to new customers and updating the existing ones who haven't picked up yet. You can also pause new orders entirely if the kitchen is slammed — every in-flight order still goes through, but no new tickets print until you unpause.

Yes. The agent handles size, toppings, sides, special instructions, and common dietary requests (gluten-free, dairy-free, etc.). It only offers items in your menu, so hallucination is impossible.

The agent remembers the last order per customer. A repeat customer can text "same as last time" and the agent re-builds the entire cart. This is the highest-converting feature in the system.

Yes. The agent is POS-agnostic. We re-point the integration; your menu and customer data stay the same.

Then they'll call. Text ordering replaces the phone for customers who prefer it, but your existing phone number keeps working. Most operators run both — text for the 80% who prefer it, phone for the 20% who don't.