The 101-second reference call that replaces the phone-etiquette training module, and the seven segments every well-formed inbound order passes through

Because once the phone line is automated, the part of the job that used to be 'coach the cashier on how to take a phone order' collapses into 'read the reference recording and flag drift on a handful of weekly calls that stray from it.' The reference call is the one concrete artifact that anchors every shift briefing, every new-hire orientation, and every Monday review. Without a shared recording, drift is felt but not seen. The 101.8-second Denny's sample shipped in public/audio/dennys-order.mp3 is the anchor PieLine uses internally and hands to the operations manager on week one.

The file is public/audio/dennys-order.mp3, 101.815 seconds long. It is transcribed into 46 speaker-tagged captions stored in src/components/voice-activity-data.ts as a static export. Each caption is a {speaker, start, end, text} record that the product uses to render its voice-activity visualization on the homepage, and the operations manager uses to isolate any segment in seconds. The file is checked into the product repo, so the reference does not drift with every marketing refresh.

Greeting (0.0s to 3.4s). Intent capture, where the caller states the order in free form (5.4s to 9.4s). Clarifier, where the agent asks the modifier questions the menu requires (16.0s to 25.7s). Customer resolution, where the caller commits to modifiers (29.4s to 35.1s). Upsell attempt with a single pairing suggestion (52.5s to 59.4s). Read-back of the full order (75.4s to 84.1s). POS placement, narrated out loud with a total and a pickup window (89.1s to 99.3s). If a live call is missing two or more of these, it goes into the flagged pile for the PieLine onboarding team.

Ten minutes, seven steps. Open ten sampled calls from the prior week. For each, tick the seven segments against the reference. Flag any with two or more missing segments. Send the worst three recordings to PieLine onboarding with a one-line note ('modifier missing for bread substitution' or 'upsell skipped on combo flow'). That is the job. Out of roughly 1,000 weekly calls at a single location, the sampling window needs ten, the onboarding feedback loop needs three. Everything else the manager leaves alone.

Because upsell before the main order is confirmed pollutes the customer resolution step and degrades accuracy. In the reference call the agent hears the full order ('lumberjack slam, scrambled, sourdough, Coke'), reads it back inline at 38.0s through 41.9s, confirms with the caller, captures the caller's name at 47.6s, and only then attempts the dessert pairing at 52.5s with 'Before I finish up, would you like to add a sweet treat like a slice of New York style cheesecake.' That ordering is non-negotiable; moving the upsell earlier breaks the mental model of the caller and drops attach rate by a measurable margin in PieLine's internal review.

It evaporates. The module used to cover tone, pace, hold etiquette, script compliance, and how to ring in a modifier on the POS. After PieLine, the caller never hears a human on the phone, so there is no tone to train, no hold to explain, no script to enforce, and the POS entry happens automatically at the 89.1s mark in the reference call. The only remaining human-side training is 'here is the file, here are the seven segments, here is where to click to hear the upsell.' That training takes a single shift briefing.

Three show up repeatedly. First, the clarifier segment compressing (agent skips the bread question on a sandwich, driving a modifier miss two days later). Second, the upsell attempt firing too early (before the read-back, which confuses the caller). Third, the POS placement narration dropping (the 'Placing your order now. Done.' at 89.1s through 92.0s disappears, which means the caller does not know whether to wait for confirmation or hang up). All three are fixable by pushing a policy note to PieLine onboarding; the manager is not the one patching the agent.

The POS write happens during the placement segment at 89.1s. The agent says 'Placing your order now' and pushes the order to the restaurant's existing POS: Clover, Square, Toast, NCR Aloha, Revel, Lightspeed, SpotOn, TouchBistro, or one of 50-plus other integrations. The receipt prints in the kitchen the same way it prints for a walk-in, tagged with a phone-origin flag and the POS item IDs that PieLine's onboarding team mapped at go-live. The operations manager does not configure the integration per-call; it is set once and runs.

$350 per month per location for the first 1,000 calls, $0.50 per call beyond that, month-to-month with a first-month money-back guarantee. Go-live is typically same-day: scraping the public menu URL, normalizing modifier groups, mapping POS item IDs, and forwarding the restaurant's line takes about half a day. Active call review by the PieLine team runs through the first month, so the operations manager inherits a stable agent by week four rather than debugging one on week one.

The reference file on disk is permanent; it is the anchor specifically because it does not move. When a restaurant goes live, PieLine generates a location-specific calibration call against the actual menu (different dishes, different modifier graph, different upsell pairing) and that becomes the operations manager's local reference. The structural shape (seven segments, upsell after read-back, POS narration at the placement mark) stays constant across every calibration call. A new hire can learn the shape on the Denny's sample and read any location's local reference the same way.