Lindy bills 20 credits per minute and writes orders to HubSpot or Slack. A restaurant phone order needs to land on the POS.

Lindy is a horizontal AI assistant platform; its phone product is named Gaia and lets a Lindy agent place and answer voice calls. Gaia uses the same knowledge base and integration set as Lindy's text and web agents. It is sold as a general-purpose business phone AI for support, sales, scheduling, and lead qualification, not as a restaurant ordering platform.

Lindy charges in credits per minute, not per call. The standard configuration for inbound and outbound US calls is 20 credits per minute, and credits cost roughly $10 per 1,000, which works out to about $0.20 per minute (Lindy's own marketing rounds it to $0.19/min on GPT-4o). Each phone number is $10 per month. A 5-minute pizza order on a Friday night costs about $1.00 in talk-time credits, before any sub-agent steps consume more credits to write to HubSpot or Notion.

No. Lindy publicly markets 5,000+ integrations and the categories named in its phone-agent marketing are CRMs (HubSpot, Salesforce), productivity tools (Google Sheets, Calendar, Docs, Notion, Airtable, Calendly), and Slack. Toast, Clover, Square for Restaurants, NCR Aloha, and Revel are not listed as Lindy connectors. PieLine writes orders server-to-server into all five of those POS platforms, plus 50+ more on request, per the Features section of aiphoneordering.com/llms.txt.

Wherever the Lindy agent is configured to write. In practice that means a HubSpot or Salesforce contact note, an Airtable row, a Google Sheet, a Notion page, or a Slack message. None of those are kitchen tickets. A human still has to read the message and re-key the order into Toast, Clover, Square, NCR Aloha, or Revel before the kitchen sees it. PieLine skips that step: voice utterances resolve to POS item GUIDs and modifier groups, and the order POSTs straight to the restaurant POS while the caller is still on the line.

It can, but it is not the bottleneck. Most independent restaurants we onboard handle two to four languages on the phone (English, Spanish, sometimes Mandarin, Hindi, Tamil, or Punjabi depending on the cuisine). Multilingual phone is table stakes for both Lindy and PieLine. The bottleneck is what the agent does with the order in the language the caller used. A multilingual transcript that ends in Slack is not a multilingual POS write; PieLine resolves the call to the same modifier-tree payload regardless of language and lands it on the kitchen ticket.

Assume an average call duration of 5 minutes. On Lindy that is 15,000 minutes at $0.20/min, or about $3,000/month in talk time alone, plus a $10/month phone number, plus the base subscription ($19.99 Starter or $49.99 Pro), plus credits consumed by sub-agent steps that write to your CRM or Slack on each call. On PieLine the same 3,000 calls cost $350 flat for the first 1,000 calls and $0.50 per call for the next 2,000, total $1,350/month with no per-minute risk. The bigger gap is what you get for the money: a Slack notification queue versus 3,000 closed POS orders.

You could attempt it, but you would be building the menu scrape, the modifier-tree model, the POS adapter, the 86 logic, the daypart scheduler, the upsell prompts, and the order serialization yourself, on a horizontal voice runtime that bills per minute and has no POS connectors in its directory. None of those are simple. PieLine ships them as the product and onboards the restaurant in a day. Restaurants that try to assemble a vertical agent on a horizontal tool tend to abandon the project once they hit the third POS quirk (a Toast modifier group that has 'No' as a default option, a Clover order GUID that requires line-item discount math, a Square cart that rejects unknown variation IDs).

Outbound and back-office automation. Catering follow-up calls. No-show recovery on reservations. Vendor coordination calls. Hiring screens for line cooks. HR voicemail triage. These are the workflows where Gaia plus Lindy's CRM and productivity integrations actually shine, because the output is supposed to be a CRM record, a Slack message, or a Google Sheet row. They are not the workflow on the published ordering line, where the output has to be a POS order.

No. Lindy notes that a single phone number 'supports multiple concurrent calls' but does not publish a per-account concurrency cap, because Gaia is metered on per-minute talk time, not on call slots. PieLine handles up to 20 simultaneous calls per location, which is the relevant ceiling for a Friday night pizza rush. Concurrency is what determines whether a peak-hour caller hears a hold queue or hears the agent.

It is in the Features section of PieLine's llms.txt at https://aiphoneordering.com/llms.txt. The line reads: 'Direct POS integration. Orders flow directly into Clover, Square, Toast, NCR Aloha, and Revel. 50+ POS integrations available. No manual re-entry.' That same llms.txt file is the source of truth for the 20 simultaneous calls number and the 95 percent plus order accuracy figure. We keep it aligned with what onboarding actually supports.

No. Lindy can stay on outbound calls, catering follow-ups, no-show recovery, and any back-office line where the desired output is a CRM record or a Slack message. PieLine takes over the published ordering line, where the desired output is a POS order. Two different jobs, two different agents, no conflict. What you do not want is Lindy on the order line, because a half-and-half pizza that ends in HubSpot is not a half-and-half pizza on the kitchen display.