In the Square Dashboard, open Messages, click the gear icon, choose AI-powered responses and start the setup for Allow AI to answer customer calls. You need a Plus, Premium or Messages Plus subscription, an ordering profile and a Square-provided number, and Square says setup takes about five business days. Then run a week of test calls before customers ring.
Square's restaurant pricing page still marks voice ordering as beta, though the help article never uses the word. Square launched it in October 2025 after an alpha that sellers had to ask to join, and the article lists gaps that matter on a busy phone: no business hours, location questions, reservations or catering, and no paying at the counter. The Square details here come from its own pages and community forum as of October 2026, so check them again before you commit.
What Square asks for before onboarding begins
The help article sets five conditions. A gap in any of them is a likely reason for "about five business days" to stretch into longer, so tick them off before you click Get Started.
| Requirement | What Square's article says | What to do first |
|---|---|---|
| Plan | Square Plus, Square Premium or Messages Plus; you can subscribe during onboarding | Check your current plan. Square's restaurant pricing page lists Free at $0, Plus at $49 and Premium at $149 per location a month |
| Ordering profile | Required; Square creates one if you lack it, and ordering status must be on | In the Dashboard, go to Channels, then Online ordering, then Ordering status, and select each location |
| Business number | A verified, Square-provided number; each location gets its own | Match the legal name and address on your registration papers, because wrong details delay verification |
| Permissions | Account owner, or a team member with Messages permission | Decide who runs setup and who will watch the inbox during service |
| Time | Most setups finish in about five business days, sometimes longer | Do not print a launch date until the activation email arrives |
On the pages I read, Square publishes no separate per-call or per-order price for voice ordering, so the known cost is the plan. If you are on the Free plan, the jump to Plus is $49 per location a month at list price. A Messages Plus subscription is the third route, and its price was not on the pages I checked, so read the figure on the onboarding screen before you accept it. Whether voice ordering suits your phone traffic is a separate question, and what AI phone answering costs and pays back gives you the arithmetic for it.
Setup in order, with a check after each step
The sequence below follows the help article. The checks are mine, added because each step has a quiet way of going wrong.
- Switch on ordering status. Dashboard, Channels, Online ordering, Ordering status, then select every location that should receive phone orders. Square notes that this same switch can turn off Square AI phone orders later, which is worth knowing before you need it. Check: the status reads on for each location.
- Open the AI settings. Click the Messages icon, then the gear icon for Settings, then AI-powered responses. Check: you can see the Allow AI to answer customer calls option. If you cannot, your role may lack Messages permission.
- Start the onboarding. Click Set up (or Get Started) beside Allow AI to answer customer calls and follow the flow. Check: Square emails you a progress update.
- Confirm your business information. Square warns that errors or missing details can delay or reject number verification, and it singles out toll-free verification as one that incorrect business information can hold up. Copy the legal name and address from official paperwork instead of typing the trading name from memory.
- Let Square set up the number. It must be a Square-provided number. If you run several locations, each gets a unique one, so note which number belongs to which kitchen.
- Review every menu. Square says customers can ask for your menu by text, so the callers receive what sits in Square, not what is on your printed card.
- Wait for activation. Square emails about progress and activation. Check status any time under the same Allow AI to answer customer calls setting.
- Write down the number and turn on notifications. Settings, Business numbers shows the number you will test with. Square tells you through Square Messages when the AI cannot handle a call, so notifications must reach the people on shift, not only the owner's phone.
Do not publish the new number yet. Until the test week is over, only your testers should know it exists.
Decide where phone calls go before the number goes live
Square's article is blunt about what the AI will not do: it is "not trained to answer other types of questions such as business hours, location information, reservations", and it does not handle specialised orders such as catering. It suggests that if your phone system has a phone tree or IVR (an automated "press 1" menu), you transfer those calls elsewhere. It also says voice ordering works only with Square-provided numbers, and that you can try forwarding order-related calls from your existing system to the Square number. That leaves three sensible routing plans.
| Plan | How it works | Suits | Watch for |
|---|---|---|---|
| A. Separate order line | Publish the Square number only as the "order for pickup" number. Your main line stays staffed for everything else | A restaurant starting fresh, or one that wants a clean test | Regulars keep ringing the old number, so the new one needs promoting |
| B. Phone menu | Your main line plays "press 1 to order for pickup", which forwards to the Square number; other options ring staff | Restaurants whose phone system already has an IVR | Forwarding adds a step; test it from a mobile and a landline |
| C. Overflow only | Staff answer first; unanswered calls forward to the Square number after a set number of rings | Restaurants that lose calls only at peaks | Callers hear ringing before the AI; tune the ring count |
Alpha testers on Square's community forum described routing calls through their own phone systems in late 2025, including overflow set-ups like plan C. Treat those posts as ideas, not settings, and choose the ring count during the test week: long enough for staff to pick up, short enough that callers do not give up. Whichever plan you choose, keep the original number with its current provider. If you ever need to leave, keeping ownership of your number and data is much easier when the forwarding was your idea and the number never moved.
Make the menu easy to say aloud
A POS menu is written for staff who know it. A caller will say "the chicken wrap" and expect it to land on a ticket. Before testing, make the item names in Square match how people talk. The help article does not say how its AI matches spoken names to items, so the point of the tests is to find out, but you can remove the obvious traps first.
| In the POS today | What a caller says | Safer setup |
|---|---|---|
| Marg LG GF | "A large gluten-free margherita" | Item "Margherita pizza" with separate Size and Base modifier groups |
| No.14 Combo B | "The lunch deal with the soup" | Item "Lunch deal: soup and half sandwich" |
| Fries (reg) and Chips | "Chips" or "fries" | One name used everywhere, in the POS and on the online ordering page |
| Spicy Chix Wrap | "Spicy chicken wrap" | Spell out the words, with no abbreviations |
| Sparkling 330 | "A sparkling water" | "Sparkling water, 330 ml can" |
Two more jobs belong here. First, sort out sold-out items: decide how you mark something unavailable and test that the AI respects it, because a caller who orders the last portion of the special and pays online has been promised something you cannot make. Second, treat allergies as a person's job. Square's article says nothing about allergen handling, so the policy is yours: any call that mentions an allergy, an intolerance or a diet needs a human. Allergy handling is also a fair test when you compare Square's built-in assistant with a separate phone-ordering product, and choosing between POS-built AI and an add-on tool covers where each kind of tool fits.
A week of test calls: schedule, script and scoring
Run the test on the live number, with real payments, because the text-link payment step is part of what you are testing. Each paid test is a real card payment, so order the cheapest item and refund it from the Dashboard afterwards (check how your account treats card fees on refunds). Use several testers and phones: kitchen staff, front-of-house, a friend with a different accent, a landline if you can find one.
| Day | Calls | Focus |
|---|---|---|
| 1 | 8 | Plain orders: one to three items, no changes, pickup soon |
| 2 | 12 | Sizes, modifiers, "no onions", sauces on the side, changing your mind mid-call |
| 3 | 8 | Questions and refusals: hours, ingredients, allergies, reservations, catering |
| 4 | 10 | Noise and voices: speakerphone, a car, a shouting kitchen, fast talkers, different accents |
| 5 | 8 | After closing, sold-out items, orders for later in the day |
| 6 | 10 | Payment and failure paths: unpaid orders, hang-ups, texts that never arrive |
| 7 | 4 | Hand-offs: confirm every call the AI cannot finish reaches a person in time |
That is 60 calls. It sounds a lot, but a call takes two or three minutes and the first two days find most of the problems. Day two deserves the most care: during the 2025 alpha, one seller on Square's community forum reported that special instructions were not supported, and another described pauses of several seconds after asking for a size. Either may have changed since, so time the pauses and note what happens to every special request. Give each tester a script card so the results are comparable. These ten scenarios cover what I would want to know:
| # | The tester says or does | What must happen |
|---|---|---|
| 1 | Orders one large margherita for pickup in 30 minutes | Ticket shows one margherita, large; a pickup time is stated; the text link arrives; the paid order appears in Order Manager or the kitchen display system (KDS) |
| 2 | Orders four items, each with one change | Every change attaches to the right item |
| 3 | Asks for the menu by text, then orders from it | The text arrives with your current menu and the order matches |
| 4 | Asks "What time do you close tonight?" | No invented answer; the caller is told it cannot help or is handed to a person |
| 5 | Says "I'm coeliac, is the arrabbiata safe?" | No reassurance from the AI; a hand-off notification reaches Messages |
| 6 | Orders an item you have marked sold out | The item is refused or an alternative is offered |
| 7 | Calls after closing time | No order is accepted for a time when you are shut; note exactly what the caller is told |
| 8 | Orders, then hangs up before paying | No ticket reaches the kitchen, because Square says orders are finalised only after online payment |
| 9 | Calls from a phone that cannot receive texts | You learn what happens; there is no right answer yet, only a note for your rules |
| 10 | Asks to book a table for six | No half-made booking; the caller is routed to staff |
Record every call on one row: date and time, tester, scenario number, phone type, what was said, what arrived on the ticket, whether the call summary in Messages matched, and a grade. Use three grades. Perfect means the ticket matches what was said, item for item. Minor means the right food with a cosmetic slip, such as a name spelt differently. Major means a wrong or missing item, size or modifier, any mishandled allergy question, or an unpaid order reaching the kitchen.
My suggested bar for going live, which is a judgement call and not a Square rule: at least 19 of the last 20 calls perfect, no major failure on anything involving allergies, and every hand-off notification arriving where a person sees it within two minutes.
A worked test week for a 45-seat pizza and pasta restaurant
Take a 45-seat pizza and pasta restaurant that handles about 90 phone orders a week and loses some calls on Friday and Saturday evenings. The figures below illustrate how a test week can read. They are not results Square has published, or results you should expect.
| Day | Focus | Calls | Perfect | Failures found |
|---|---|---|---|---|
| 1 | Plain orders | 8 | 8 | None |
| 2 | Sizes and modifiers | 12 | 9 | Two sizes missing from the ticket; one modifier on the wrong pizza |
| 3 | Questions and refusals | 8 | 7 | One confident answer about ingredients that the menu text did not support |
| 4 | Noise and voices | 10 | 8 | Two misheard items on the kitchen-noise calls |
| 5 | After hours and sold out | 8 | 7 | A sold-out special accepted |
| 6 | Payment and failure paths | 10 | 9 | A landline caller could not receive the payment text |
| 7 | Hand-offs | 4 | 4 | None, though one notification took six minutes |
| Total | 60 | 52 | 8 failures, 86.7% perfect |
The owner sorts the eight failures by cause. Three trace to item names and modifier structure, which she can fix: "Marg LG" becomes "Margherita pizza" with size and base groups. One is the sold-out special, which becomes a rule: whoever marks it sold out does so in the system before service, not after the first complaint. One is the ingredient answer, which becomes a rule that any ingredient or allergy question goes to a person. Two are kitchen noise, which she cannot fix, so the rule is that a person scans every voice-ordered ticket on the KDS during the first fortnight. One is the landline, which becomes a line in the phone greeting on the main number: "orders need a mobile number for the payment text". The six-minute notification is not among the eight, because the call itself went right, but it breaks the two-minute bar, so she changes where the alerts land (see the fallback section below) and repeats the hand-off calls.
She makes the changes and runs a second round of 20 calls: 19 perfect, one minor, and every hand-off alert seen within two minutes. That meets the bar, so she goes live on a Tuesday, not a Friday, with the manager watching Messages. The lesson is in the sequence. Most of the improvement came from the menu, which is her data, not from anything about the AI.
Staff fallback: a handover rule for calls the AI cannot finish
Square says it notifies you through Square Messages when the AI cannot handle a call, and that a summary of the call appears in Messages. The notification is only as good as the person who sees it. Early testers on Square's community forum in late 2025 reported that missed-call alerts went to the account holder, which is no use when the account holder is at home and the kitchen is full. One tester routed the notifications to a Square printer as a workaround. Those are older posts, so check where your own alerts land during the test week.
Write the fallback down as a card and pin it where the manager works:
VOICE ORDERING HANDOVER CARD
Who watches Square Messages this shift: [manager name]
Check the inbox: at the start of service, then every 10 minutes at peak
Hand-off notification: call the customer back within 10 minutes
Callback script: "Hi [first name], it's [restaurant]. You rang a moment ago
and our assistant couldn't finish your order. Can I take it now?"
Anything about allergies or diets: a person takes the order, always
Ticket check: scan every voice-ordered ticket on the KDS during the first 14 days
SWITCH IT OFF (Messages settings, where you turned it on) if:
- two wrong orders in one service
- any allergy mistake
- tickets stop arriving in Order Manager or the KDS
Then: tell the owner, note the date and time of each bad call, and forward
the details to Square's feedback address given in its help article.The switch-off rule matters more than it looks. Square lets you disable the feature from the same setting you used to turn it on, and the Ordering status switch can also stop AI phone orders. A rule written in advance means nobody has to decide, mid-rush, whether a bad night is bad enough. Square asks for feedback by email and wants the date and time of any call that went wrong, so keep the log. That is also how you tell whether the problem is your menu or Square's product.
Tell callers it is an assistant, in the greeting and online
People should know they are talking to an automated assistant. During your tests, note whether the greeting says so in plain words. If you have customers in the EU, the transparency duty in Article 50 of the EU AI Act (tell people when they are interacting with an AI system) has applied since 2 August 2026. It falls mainly on the provider of the system, which here is Square, so it is a fair question to put to Square. Your own signage should say it too, whatever the answer.
Add a short line wherever customers find your phone number: the website, the Google listing description and the menu. Something like this works:
Phone orders for pickup are taken by an automated assistant and paid for
online by text link. For questions about opening hours, allergies,
reservations or catering, please call [main number] or speak to our team.That line also sets honest expectations about what Square says the AI cannot do, so fewer callers are surprised when the payment text arrives. Square's own community staff described pay-at-pickup as a known feature request in late 2025, so assume it is still missing until the help article says otherwise.
The first live fortnight: reading the log and a payback sum
For 14 days, spend five minutes at the end of each service on two screens. In the Dashboard, open Orders and filter by the order source the help article calls Voice AI assisted. Then open Messages, check the Inbox and the Transactional tab, and read the call summaries for the same orders. Compare them. A ticket without a matching summary, or a summary describing an order the kitchen never saw, is the kind of gap you cannot find any other way. Square's help article describes summaries and conversation history in Messages, and trade press covering the launch said every call is logged there. It does not say how long records are kept or whether audio is stored, so do not promise customers recordings or deletion until Square answers in writing.
At the end of the fortnight, work out whether it paid. Do not count staff time saved unless you actually cut hours, because the same people are standing there either way. Count calls you used to lose, and count the profit on them, not the sales, because every recovered order still uses food. Suppose your phone provider's call log shows 12 unanswered calls a week at peak, you guess a third of those callers would have ordered at an average of $28, and about 65% of each sale is left after food, packaging and card fees:
| Line | Weekly | Monthly (4.33 weeks) |
|---|---|---|
| Sales from missed calls recovered: 12 x one third = 4 orders x $28 | $112 | $485 |
| Profit left on those sales at an illustrative 65% | $73 | $315 |
| Plan upgrade from Free to Plus, at list price | minus $49 | |
| Refunds, remakes and goodwill from AI errors (your own estimate) | minus $10 | minus $43 |
| Net gain | about $223 |
Counting the $485 of sales as the gain would overstate the result by $170 a month. The sum is also only as good as the "one third" guess, so measure it: for two weeks, ring a sample of the missed numbers back and ask whether they wanted to order. If you are already on Plus or Premium, the upgrade line is zero and the case is stronger. Either way, the eight-point checklist for AI phone answering trials covers what else to weigh before you keep it running.
Five signs Square voice ordering is not ready for your phones
Voice ordering is built for pickup orders from a menu that fits in a text message. These patterns suggest waiting:
- Most calls are not orders. If the phone is mainly reservations, opening-hours questions and enquiries, the AI will hand off most of what it hears, and you will have bought a call router.
- Customers pay on collection or in cash. Square's article says every order must be paid before processing. A neighbourhood restaurant whose regulars pay at the counter will lose some of those calls.
- Delivery is your main channel. Square's staff said during the alpha that the feature was built for pickup orders, and the help article does not mention delivery for phone orders.
- Your menu is built on half-and-half pizzas, build-your-own bowls or long modifier chains. Run those scenarios on day two before anything else; if they fail, fix the menu structure first.
- You are not on Square for the till. Orders go to Square's Order Manager and KDS, so a different POS means a different tool.
If two or more apply, compare other restaurant phone AI options before investing a week of staff time. If none apply and the numbers work, the test week above is a cheap way to find out whether a beta feature is good enough for your Friday night.
Square voice ordering: questions owners ask before switching it on
Does Square AI voice ordering take cash or pay-at-pickup orders?
No. Square's help article says all orders must be paid before processing, through a text link to an online cart. During the 2025 alpha, testers on Square's community forum asked for pay-at-pickup, and Square's staff called it a known feature request. If most of your phone customers pay on collection, test that group first or wait.
Can the AI answer questions about hours, reservations or catering?
Square says it is not trained for business hours, location information, reservations or specialised orders such as catering. Send those calls to a person with a phone menu (IVR) or a separate staffed line, and include them in your test week to confirm the AI hands off instead of guessing.
Can I keep my existing restaurant phone number?
Voice ordering works only with Square-provided business numbers. Square's article says you can try forwarding order-related calls from your existing phone system to that number. Keep your original number with its current provider so you can switch back if the trial goes badly.
Where can I see what the AI said to callers?
In Square Messages: open the Inbox or the Transactional tab, search by phone number or name, and read the call summary. The help article does not say how long summaries are kept or whether audio is stored, so ask Square before you make any promise to customers about recordings.
Does Square charge extra for voice ordering?
On the pages I read, Square lists no separate per-call or per-order price. The known costs are the plan: Plus at $49 or Premium at $149 per location a month on the restaurant pricing page, or a Messages Plus subscription. Confirm the figure on the onboarding screen before you accept.
Further reads
- AI Phone Ordering for Takeaways: A Test Checklist for Menus and Postcodes — A test checklist for numbered menus and delivery details.
- How to Set Up an AI Phone Line for Takeaway Orders — How a dedicated AI order line is built from scratch.
- AI for Restaurant Order Management: One Queue for Every Channel — Bring phone, web and app orders into one queue.
- AI Food Insights Tool: Toast IQ, Square AI or a Spreadsheet? — What Square AI's reporting side can and cannot tell you.
- AI Ordering vs Delivery Apps: What a Takeaway Actually Pays — What direct ordering saves compared with delivery app commission.
- Maple AI for Restaurants: Voice or Pro Plan, and Who Needs Which — Maple Voice answers and transfers calls; Pro adds orders and reservations. Compare the monthly cost, break-even orders and the test to run first.
- AI Drive-Thru Ordering: What a Fast-Food Franchisee Controls — Who really decides on AI drive-thru ordering in a franchise: three models, the clauses to read, questions to put in writing and a lane-level sum.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Square help article 'Take orders with AI-powered voice ordering' and Square's restaurant pricing and Square AI pages (October 2026); Square's launch announcement and Restaurant Dive's coverage (8 October 2025); Square Community alpha and feedback threads (2025); EU AI Act Article 50.