Restaurant automation software stops at the resolver layer. That is where the phone channel lives.

Most restaurant automation software automates one of six layers: point of sale (Clover, Square, Toast, NCR Aloha, Revel), kitchen display and expediter routing, online and app-based ordering, inventory and supplier reorder, labor scheduling, and reporting. Every comparison article lists the same six categories. None of them automate the phone channel, because automating the phone requires a resolver that translates a caller's sentence into a POS item ID with the right modifier tree. PieLine is the resolver, sitting in front of the POS and writing a ticket that the POS and every downstream system treats as a normal order.

A resolver is the piece that takes a human utterance, for example 'can I do a large pep, light sauce, thin crust, and a Coke', and outputs a machine payload the POS will accept without human review. In PieLine that payload contains the Square or Clover or Toast catalog object IDs for the pizza variation, the modifier group IDs for crust and sauce level, the beverage catalog ID, and the fulfillment type. The resolver is not the language model; it is the mapping the language model writes into. Without this layer, you have voice transcription, which is still manual.

Because their source of truth is a touch UI. A cashier touches a button that is already tied to the item ID. The mapping problem is solved at the UI layer by humans pressing buttons. When you move to voice, the mapping problem comes back in full, because the caller does not say 'item ID 48812', they say 'a Coke'. The resolver is the piece that handles that gap. Restaurant automation software built around touch interfaces never needs one. Restaurant automation software that automates voice cannot work without one.

PieLine's onboarding team scrapes your online menu, maps each item to the specific POS item ID and modifier group IDs in your POS (Clover, Square, Toast, NCR Aloha, or Revel), and writes a dish description record for each item covering ingredients, spice level, sweetness, and preparation notes. The language model is then grounded in your actual catalog, not a generic menu prompt. Restaurants go live the same day on the phone side because the resolver is assembled in the onboarding workflow rather than left to the operator.

Yes. Integration means the pipe exists. Resolver means the mapping on top of the pipe exists. Most automation software integrates with a POS and then writes whatever the operator configured. PieLine integrates with the POS and also owns the resolver, so a voice utterance becomes a correctly-IDed ticket without the operator drawing the map. If you already have a voice tool plus a POS, you are likely hand-maintaining the mapping between them, which is where accuracy falls off a cliff during menu changes.

Yes, and most operators do. The question is whether the phone channel is part of your revenue mix. At peak times, 30 to 40 percent of restaurant calls go unanswered. Every automation category that exists, including POS and KDS, can be fully deployed while the phone keeps bleeding. The rational purchase sequence for operators with heavy phone volume is POS first, KDS second, and a phone resolver third, treating it as a peer to online ordering rather than a voicemail tool.

When a restaurant changes its POS catalog, PieLine resyncs the catalog tree (item variations, modifier sets, prices) and updates the dish description records during the first-month active refinement window. New items flow in automatically. Discontinued items stop being resolvable. Operators do not hand-edit the mapping table. The dish description layer is the one piece that benefits from a human review during the first month, because spice and sweetness annotations inform the small-talk half of calls, not the order-taking half.

PieLine is $350 per month flat for up to 1,000 answered calls with money back on the first month, $0.50 per additional call. A dedicated phone employee runs $3,000 to $4,000 per month and handles one call at a time. Most POS subscriptions land in the $60 to $165 per location per month range for base tier plus hardware capex. A KDS display subscription is typically $25 to $50 per terminal per month. The phone resolver line item sits between a KDS and a phone employee in monthly cost, while handling 20 simultaneous calls and replacing the per-location phone hire.

The standard articles do not. Open the top-ranking pages and you will find tables of POS systems, KDS vendors, online ordering platforms, and inventory tools, plus pricing tiers and feature checkmarks. The mapping layer between utterance and POS ID never appears as a row. That gap is the single most visible evidence that the phone channel has been excluded from the automation conversation by the category as a whole.