Best Phone Agent for Cafes
Five cafe phone agents ranked on price per call, the standing order, and the pastry case that empties by nine. Kovo takes the rubric at 93; Loman wins on payment.
On this page
The best phone agent for a cafe is Kovo, at $99 a month for 750 connected minutes and 93/100 on the rubric below. Loman is second at 80 and wins the payment row. The cafe test is the standing order and the case that empties by nine, and both are scored in the ranking.
At 7:10 on a Tuesday the cafe phone is ringing and the only person who could answer it is steaming oat milk. The call is a regular, and what they want is "the usual": a 12 oz oat flat white, one pump of vanilla, and the almond croissant, warmed.
Your counter learns that order in about three weeks. A phone agent has to be told it on day one, and that is what this shortlist separates. We sell Kovo, and the rubric is printed so you can check the verdict.
TL;DR:
- Kovo scores 93/100: $99 for 750 connected minutes, about 33 cents an answered call, choices and modifiers intact on the ticket.
- Loman scores 80 and wins payment outright, charging any card during the call, from $199 per location.
- Hostie is 58 and fits a brunch room and host stand; Kea is 57 on a quote, and Sadie is 47 as a receptionist rather than an order line.
- Forty missed calls a month at an $11 ticket is $440, which is more than the milk delivery and the card fees together.
- None of the five recognises "the usual" unless the build is a named menu item, so write your ten most repeated drinks down before you shop.
The rubric, and why these weights
Ranking phone agents by "AI quality" is unmeasurable and every vendor wins it. Ranking by what a cafe pays for is checkable, so the weights follow the money.
| Weight | Criterion | Why it decides |
|---|---|---|
| 25% | Price per answered call | The bill is the first objection |
| 20% | Reservations included, no platform fee | A table call is the highest-value call |
| 15% | Order limits the owner controls | One fixed cap does not fit four restaurant types |
| 15% | Payment that closes on the call | An unpaid ticket is a kitchen waiting |
| 10% | POS depth you actually run | A ticket that needs retyping is not an integration |
| 10% | Channels on one brain (phone, chat) | Two menus is two truths |
| 5% | Setup without a scheduled onboarding | Speed to first call |
Price is the row a cafe should argue about, because the ticket is small. A cafe taking 200 calls a month cannot carry a $450 subscription whatever the voice sounds like, and at 80 calls a month the arithmetic goes the other way for all five products. Each vendor is scored 1 to 5 per row against public information read in October 2026, then weighted out of 100.
The ranking
| # | Product | Score | Price | Reservations | Card on the call | Best for |
|---|---|---|---|---|---|---|
| 1 | Kovo | 93 | $99 / $299 | Own book, included | A card the shop already holds, charged on the line; link for a first-timer | A takeout line at a fixed price |
| 2 | Loman | 80 | From $199 | OpenTable write-back | Any card, captured in the call | Closing the transaction on every call |
| 3 | Hostie | 58 | $199 / $399 | OpenTable, Resy | Not publicly documented, confirm | A brunch room, a host stand, one inbox |
| 4 | Kea | 57 | Quote | Limited | Not publicly documented, confirm | A custom build on a quote |
| 5 | Sadie | 47 | Quote | Reservations per the vendor | Not publicly documented, confirm | Interruption, not order capture |
Kovo wins on price per answered call, an included book, owner-set limits, and chat. Loman wins the payment row outright. Read down the card column and most of the decision is made: the product that closes the payment inside the conversation costs twice as much at low volume.
Kovo — 93/100
Kovo answers, takes the order the way the caller says it, reads it back, and writes the ticket to the POS or printer the shop already uses. Nested choices survive, so a flat white with an oat swap, one pump of vanilla, and an extra shot arrives as three choices rather than a note in a comments field.
A card the shop already holds is charged off-session while the caller is on the line, and the ticket reaches the bar during the call; a first-time caller gets a Stripe link and pays without hanging up. The limit: the agent takes the build your menu names, so "the usual" is a menu line, not a memory.
Loman — 80/100
Loman is the closest thing to a finished transaction here: order, modifiers, card charged during the call, ticket into the POS, no human between the caller and the bar. It publishes nine POS integrations and onboarding under 24 hours, and from $199 a month with no per-minute fees (published pricing, October 2026), which the vendor states rather than proves.
For a cafe doing 600 calls a month on a $14 average, that card path can pay for itself. Price per answered call is the row it loses to Kovo, at 66 cents against 33. The two-column version is in Kovo vs Loman.
Hostie — 58/100
Hostie is a guest communications layer first: reservations, guest questions, and one inbox for calls, texts, and email, with forwarding to staff. Order taking is documented on the $399 per-location tier against a $199 base (published pricing, October 2026).
A cafe with a brunch room and a host stand gets real value from that inbox, because the table and the question are the same conversation. A takeout counter pays for a workflow it would not touch. The limit to test is how much of an order is written into the POS versus handled inside Hostie. The Hostie comparison goes through the split.
Kea — 57/100
Kea takes orders and is sold on a quote, which makes it the hardest row to judge from a website. A quote can be the lowest all-in number here or the highest, and you will not know which until a sales call.
What it has going for it is custom scope without a published rate card, which suits a cafe whose menu will not fit a fixed product: a subscription for a morning office run, a pastry box priced by count, a rotating single-origin list. Ask for the monthly number at your call volume in writing, with per-location, per-minute, and setup charges broken out (quote-based, October 2026), then hold it next to the $99 and $199 columns above.
Sadie — 47/100
Sadie is framed as an AI receptionist: hours, location, policies, reservations, and message taking, sold on a quote, with a published ceiling of 20 concurrent calls (quote-based, October 2026). That ceiling is unusually honest disclosure for the category, and it is worth asking every other vendor for the same number.
If your calls are "do you have outdoor seating" and "where do I park", a receptionist is the right shape, and the published concurrency number is the reason it scores as well as it does on setup. The limit is the shape: a message is not a ticket for the bar. The Sadie alternatives page covers that boundary.
The call a cafe loses while the ticket prints
Most phone-agent writing is about misheard words. At a cafe the loss is different, and it happens on a call the agent takes perfectly.
A regular says "the usual" and means four things at once: a size, a milk, a syrup pump, and a pastry. Your counter has that in its head because the customer has been coming since March. A phone agent arrives at the same words with no memory of the caller, so the same sentence becomes a question, and the regular who hears that from a machine orders online instead, or walks two doors down.
The fix is not a feature you shop for. It is a menu line. Name the build the way the customer names it, price it as one item, and fix the choices inside it. Ten named habit items cover most of a cafe's repeat calls, and the agent then takes "the usual" in under 20 seconds with the oat swap intact. That is a 20-minute job in the menu editor, and the highest-return task on this page.
The second cafe failure is the case, and it is the same problem in reverse: a croissant that sold out at 9 a.m. keeps getting offered until the menu says otherwise, because Kovo re-pulls the menu once a day and the call path only pulls when it is two days old. Toggle the item off in the menu board at the moment you mark it off at the counter, and a Square or Clover shop gets its sold-out flag through the pull too.
The test call to run on each vendor
Do the same calls with each product, on your own menu, and write down what the bar receives. Twenty minutes beats any demo script.
"A 12 oz oat flat white, one pump of vanilla, extra shot, and an almond croissant, warmed."
Then read the ticket, not the transcript. The choices should arrive as choices, the croissant as a food line, and the milk swap as a modifier rather than a note.
Five more calls, in this order:
- A sold-out item: mark the almond croissant unavailable an hour before the call.
- The soup of the day, and whether it has dairy, answered from your own words.
- The line cut-off: a breakfast sandwich after the kitchen stops making them.
- An office order of a coffee box and a dozen pastries: past 10 items in total. Ticketed, or declined with a reason?
- A card order. Did the ticket wait for payment, or print?
An analysis in QSR Magazine estimates the average restaurant at around 150 missed calls a month, and at a cafe most of that lands between 7 and 9:30 a.m., which is why the first call on this list is the one to time with a stopwatch.
FAQ
Which phone agent is best for a cafe?
Kovo scores highest on our rubric (93/100): $99 a month for 750 connected minutes, about 33 cents an answered call, drinks and pastries ticketed to Toast, Square, Clover, Olo, or a printer, and order limits the shop sets. Loman is second at 80 and is the pick when every call has to end paid in the call. Hostie at 58 fits a cafe with a brunch room and a host stand, where the reservation inbox is the real problem.
How are the scores calculated?
Seven weighted criteria: price per answered call (25%), reservations included (20%), owner-controlled order limits (15%), payment that closes on the call (15%), POS depth (10%), channels on one brain (10%), and setup without a scheduled onboarding (5%). Each vendor is scored 1 to 5 per row against published information read in October 2026, then weighted out of 100. The weights follow what a cafe actually pays for, and the rubric box sits above the table.
Can a phone agent learn a regular's usual order?
Not by recognising a voice, and no product here claims otherwise. The workaround costs one menu line: add the drink as an item named for the regular's habit, with the milk, the syrup, and the pastry as fixed choices under it, and Kovo then takes it in about 20 seconds with the choices intact. Do that for your ten most repeated drinks and the gap mostly closes. It is a 20-minute job in the menu editor.
Will it know when the pastry case is empty?
Only if the item is marked unavailable in the menu it reads. Kovo refreshes the menu from its source once a day, and the call path pulls when the menu is two days old, so a croissant you sold out of at 9 a.m. is still offered until the board says otherwise. Sold out is an owner toggle, and a Square or Clover shop gets that flag through the pull as well. Shops that sell out by noon should toggle items off as the case empties.
How much does a cafe phone agent cost per call?
Divide the monthly price by the calls you actually get. Kovo Starter is $99 for 750 connected minutes, roughly 300 calls, so about 33 cents an answered call. Loman publishes from $199 with no per-minute fees, which is 66 cents at the same volume, and Hostie's order taking is on a $399 tier (published pricing, October 2026). At an $11 average cafe ticket, all three are a small slice of the revenue they handle, or a large one if you take 80 calls a month.
Final Thoughts
The best phone agent for a cafe is the one that can take your ten most repeated drinks without a follow-up question, at a price your ticket can carry. That is a menu problem first and a voice problem second.
On the rubric that is Kovo: $99 a month for 750 connected minutes, about 33 cents a call, 14 days free and no card, a book included, and limits you set. Loman is the answer when the card has to be charged before the caller hangs up, and Hostie when the phone is brunch tables rather than takeout.
Write the named builds, run the test calls, and read the ticket at the bar. Take a test call.