Square Phone Ordering That Lands on the Pass
The call that rings at 12:10 becomes a normal Square order, modifiers and all. Where the ticket lands, what your menu keeps, and what to try before a Friday.
On this page
At 12:10 on a Tuesday there are two people behind the counter, a line to the door, and a phone ringing where nobody can reach it. Square already has your menu, your prices, and your modifier groups. It just cannot pick up.
So the call starts outside the till. Someone hears it, holds the order in their head, and keys it in when a hand frees up. That works at 2 p.m. It does not work at 12:10, which is the only time it matters.
TL;DR:
- A phone call ends as an ordinary Square order on the location you connected, so the kitchen reads a ticket instead of a text message.
- Modifiers come off the groups you already built, so a half-and-half pie arrives as two sets of toppings and a notes box arrives as a note.
- The menu comes down once a day, so a price you changed at 11 this morning is quoted from tomorrow's first call.
- If they have paid you before, you already have their card and it is charged while they talk; a first-time caller gets a text link.
- Past 10 items in one order, or 8 of one item, the phone stops and keeps taking what fits, and $99 a month covers about 300 calls.
Where Square stops and the phone starts
Square holds the menu, the prices, the modifier groups, and which store they belong to. It takes the order, the tender, and the receipt, and it puts the ticket where your kitchen already looks: a Square KDS, a receipt printer, or the order screen on the register.
The call is the one part of the order that starts outside all of it. Three things go wrong in that gap, and each has a different fix:
- Nobody picks up. No ticket, no name, no line on the report.
- Someone takes it from memory. A size goes missing or a side drops, and the kitchen builds something nobody ordered.
- Someone writes it on the pad by the till. Now it is a note with an extra step, and the note gets keyed in wrong at 7:55.
Answering fixes the first. Writing into Square fixes the second. Nothing fixes the third except not doing it, which is the same problem every quick-service shop has at 12:10 on a weekday.
From the ring to a Square order
- It answers on the first ring, including after close.
- It reads your Square menu for the location you connected: items, sizes, prices, modifier groups, and whatever is marked unavailable.
- It takes the order the way the caller says it. "Large, half mushroom" opens a half on the pie instead of becoming a sentence at the bottom of the ticket.
- It reads the order back, the way it will print, before anything is created.
- It sorts out the money. Cards off: the order is created and the caller pays when they collect. Cards on: a regular's card is charged while they are still talking, and a first-timer gets a link.
- The order appears in Square as an ordinary order, which is the whole point.
Step four is the cheap one and the one that saves a night. Most wrong phone orders are wrong before the pass ever sees them.
Your menu comes from your Square location
Three things follow from that, and all three matter more than they sound.
The location, not the account. Three stores with three price lists means the phone quotes the one you connected. A shop running one menu everywhere gets one menu.
One pull a day. The menu comes down in the background once a day, and the call that picks up the fresh copy is your first one in the morning. Change a price at 11 and the phone quotes the old one until tomorrow. That is deliberate: an answered call never waits on your menu to load.
Sold out is yours. Mark a dish sold out on the menu board and the phone stops offering it. If Square still says available, your call wins until you restock it.
What you changed here stays changed. A change in Square to anything else lands, and a dish you deleted here does not come back on the next pull. The menu pull that keeps your edits works the same on every POS; Square only decides where the first copy comes from.
What the kitchen reads on the ticket
Square modifier groups are flexible, and that flexibility is the difference between a ticket the line can build and one it argues with.
- Nested groups. A pizza where each half opens its own toppings.
- Required modifiers. A combo that cannot be rung without a side.
- Price by modifier. Oat milk, extra cheese, a premium crust.
- Free text. "No onions, light sauce" stays a note, because that is what your menu says it is.
The phone keeps the shape it is given. If your items are built with real groups, the ticket arrives that way. If the shop has run one notes field for years, you get a faithful note, and the line reads it slowly at the worst moment of the night.
So test with the order your kitchen gets wrong most. A large half-and-half. A sandwich with three swaps. A combo with a required drink. Then look at the Square ticket, not the words on the call.
Where the money lands
Two setups, and they settle in different places.
Cards off. The order is created in Square and the caller pays when they collect. The tender is an ordinary Square sale and the till looks like it always does.
Cards on. A caller who has paid you before already has a card on file, so it is charged while they are still talking and the order shows in Square during the call. A first-time caller gets a text link, the line stays open, they hear it land, and the order appears once it clears.
| What happens | Cards off | Cards on |
|---|---|---|
| What the caller hears | The total, and "pay when you pick up" | The total on the card you already have, or a link |
| When the Square order appears | During the call | During the call for a regular; after the link clears for a first-timer |
| Where the money lands | In Square, at the counter | Your own Stripe account |
| The honest limit | An order you did not charge can still walk before pickup | A first-timer's ticket waits for the payment to clear |
The limit, exactly
The phone stops at 10 items in one order, or 8 of one item. Those are defaults, not house rules: raise them, lower them, add a dollar ceiling, and set any of them to zero to switch it off. That is why a $240 order of four things goes through and a 12-sandwich lunch run does not, unless you say otherwise.
When it stops, the agent tells the caller the order is too large to send through, stays on the line, and keeps taking what fits. Turn on large-party routing and set a handset number, and those calls ring your counter instead.
What to try before you switch the line
- One item, no modifiers. Does it land in Square?
- One item with two modifiers. Are they on the right lines?
- A half-and-half or a required combo. Does the structure survive?
- A dish you marked sold out. Is it still offered after a day?
- Eleven items. Is it refused, and is the caller told why?
- A card order. Does the Square order appear only after the payment clears?
- The test connection. Does a $0.00 ticket come out, and does it stay unpaid?
If a vendor cannot show you the Square ticket for step three, the rest of the demo is a script.
What it costs
Kovo Starter is $99 a month for 750 connected minutes, which is about 300 calls at two and a half minutes each. Unlimited is $299 for 5,000 minutes. There is no per-minute fee and no overage: at the cap, calls forward to your own line instead of being answered.
The trial runs 14 days and takes no card, and the Square setup is written up in our own docs. For the same path on another till, the Toast walkthrough is the closest comparison.
FAQ
Does a phone order show up in Square as a normal order?
Yes. It is created on the Square location you connected, so it lands the way an order rung at the counter lands. Where the kitchen meets it depends on your setup: a Square KDS, a receipt printer, or the order screen on the register. The test connection prints one $0.00 ticket and never marks an order paid, so you can prove the path before a real order uses it.
Which menu does the phone read?
The one on the location you connected, not the catalog for the whole account. A store with its own prices gets its own prices quoted. The menu comes down once a day, so a price you changed in Square at 11 this morning is quoted from tomorrow's first call, not from the call you take at noon.
What happens to a half-and-half pizza or a substitution?
It depends on how you built it in Square. Items built with real modifier groups arrive as groups, and a pie where each half opens its own toppings arrives as two sets of choices the line can build. Items that rely on one free-text box arrive as a note, and the kitchen reads it the way it reads every other note.
Is the card paid through Square?
With cards off, yes, at the counter: the order is created in Square and the caller pays when they collect, so the tender is an ordinary Square sale. With cards on, a returning caller's card is charged while they are still talking and a first-time caller pays a text link, so the money lands in your own Stripe account and the Square ticket is the kitchen's copy.
What happens to a very large order?
The phone stops above 10 items in one order, or more than 8 of one item. Those are defaults, so you can raise them, lower them, add a dollar ceiling, or set any of them to zero. Above the limit the agent says the order is too large to send through, stays on the line, and keeps taking what fits. If you turned on large-party routing and set a handset number, that call rings your counter instead.
Final Thoughts
Square was never the problem. The unanswered ring is, and so is the order that arrives as a note in someone's handwriting. A call that ends as an ordinary Square order, with the modifiers your line already reads, closes that gap without adding a body to the counter.
Connect the location, print the $0.00 ticket, then call in the order your kitchen gets wrong most. Take a test call with your own menu and hear what your Tuesday lunch sounds like when someone answers it.