Vendors / QSR & drive-thru
SoundHound
SoundHound (Restaurant AI / SYNQ3)
Voice-AI order-taking and staff-assistance layer on the OASYS platform, across drive-thru, phone/SMS/app, kiosk and in-car — it sits in front of a POS rather than being one, owning no terminal, kitchen screen, printer or item master. It DOES name POS integrations (directly Square and Toast in the operator KB; Toast, Oracle MICROS, PAR Brink, QU and Block among 57 named partners) but publishes no pricing and no operator technical documentation (claims: 85% faster service, 11% revenue increase, errors reduced up to 32%).
scored live legacy rubric
- Claims in scope
- 296
- Scored
- 44
- Assessed
- 42
- Unknown
- 254
- Not applicable
- 18
- Values challenged
- 31
unknown, never as no.Identity
- Owner
- SoundHound AI, Inc. (Nasdaq SOUN). Acquired SYNQ3 Restaurant Solutions in December 2023 ('establishing SoundHound as the largest voice AI provider for restaurants'), Allset in 2024, and completed its acquisition of LivePerson on 2026-09-04 — re-verified 2026-09-06.
- Parent
- SoundHound AI
- Who it is for
- QSR and pizza chains automating drive-thru, phone/SMS and in-app voice ordering, plus kiosk and in-car voice channels
- Site
- https://www.soundhound.com/industries/restaurants
Pricing
transparency: quote-only · unit: unknown (not published) · processor lock-in: unknown
- Software
- No pricing published. No per-location or per-terminal figure appears anywhere on the site; the restaurant page routes to 'Talk to a restaurant specialist'. Quote only. The only dollar figures in 1,807 crawled documents belong to the consumer Chat AI app. Re-verified 2026-09-06.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
SoundHound captures a voice order and hands it to the merchant POS "for processing"; it holds no check, seat or table object of its own. `split check` is 0 docs in both the stripped text and the raw HTML of all 1,807 documents, and the two `split` hits are audio-channel and "split-second". This scores SoundHound, not Toast/Square. https://support.soundhound.com/hc/en-us/articles/23680715492755-Does-the-voice-assistant-integrate-with-my-POS · retrieved 2026-09-06 adversarially verified
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
Both conjuncts fail on affirmative sentences. SoundHound publishes that its restaurant product needs no additional hardware and rides the operator POS, so there is no terminal or handheld to create orders or tender cash; and it publishes no offline scope for restaurants. `offline` = 5 docs corpus-wide, 0 in the 120-doc restaurant slice, 0 in raw for every restaurant doc. https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants · retrieved 2026-09-06 adversarially verified
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
Help centre (BMW in-car food ordering) documents future-dated capture: 'Can I schedule an order for later? Yes, you can mention the desired time for the order pickup, otherwise it is placed asap.' The shortfall is everything the claim asks beyond that - the time is whatever the guest says, 'The estimated pickup time cannot be changed' once confirmed, no per-channel lead time is configurable and no computed fire time into a make queue is described; nothing equivalent is documented for the phone/Smart Ordering or drive-thru channels, where the only ahead-of-time language is Smart Lane's marketing line 'Lock-in customers in the face of long lines with advance pre-order'. https://support.soundhound.com/hc/en-us/articles/53052980420115-Placing-Changing-and-Canceling-Your-Order · retrieved 2026-08-08
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
SoundHound ships no first-party payment terminal for EMV or NFC to run on; tender is delegated (Square processes online, Toast orders are set to pay in-store). `EMV` and `NFC` are 0 docs in both text and raw across all 1,807 documents. https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants · retrieved 2026-09-06 adversarially verified
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
SoundHound publishes that tender is handled by the merchant POS (Square online, Toast pay-in-store) and issues no stored-value instrument. `gift card` is 0 docs in text and in raw across all 1,807 documents including the 31-article operator KB. https://support.soundhound.com/hc/en-us/articles/23680557565843-How-do-my-customers-pay · retrieved 2026-09-06 adversarially verified
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
Not scored by this record.
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
payments-split-tender
Not scored by this record.
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
payments-refund-void-controls
SoundHound inserts no authorization step into the merchant's money handling: it publishes that disputes run exactly as before, and payment is executed by Square or Toast. Voids, refunds, discounts and no-sales are therefore not SoundHound actions to gate. `audit log`, `audit trail`, `drawer` and `no-sale` are 0 docs in text and raw; the single `void` doc is arbitration boilerplate. https://support.soundhound.com/hc/en-us/articles/23680596751763-How-are-disputes-handled · retrieved 2026-09-06 adversarially verified
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator
payments-multi-entity-routing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
The claim presupposes a vendor KDS with per-location station rules. SoundHound ships no KDS — kitchen is a sync target on its own drive-thru page and an "integration" in its own newsroom language. `station` 8 docs / 0 in the restaurant slice, `prep station` 0, and all 20 `routing` documents are telephony or IT-ticket routing. https://www.soundhound.com/use-cases/drive-thru · retrieved 2026-09-06 adversarially verified
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
No expo screen exists to consolidate stations: SoundHound publishes no kitchen display product and positions kitchen systems as the operator's own. `expeditor` 0, `expediter` 0, `make line` 0, `prep station` 0 and kitchen-sense `bump` 0 across all 1,807 documents in text and raw. https://www.soundhound.com/use-cases/drive-thru · retrieved 2026-09-06 adversarially verified
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
There is no first-party KDS for a bump bar to attach to, and the claim additionally requires documented supported models: the corpus contains no SoundHound hardware compatibility list of any kind. `bump bar` is 0 docs in text and in raw across all 1,807 documents. https://www.soundhound.com/use-cases/drive-thru · retrieved 2026-09-06 adversarially verified
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
The vendor's own answer to "What can OASYS do for restaurants?" is ordering channels, upsell and cross-location visibility — no back-office module, and the claim requires drivers to be first-class entities reportable from the POS itself, which SoundHound is not (orders "flow directly into your POS for processing"). Delivery-driver sense of `driver` is 0 across all 37 hits; `courier` matches one document, legal boilerplate. https://www.soundhound.com/industries/restaurants · retrieved 2026-09-06 adversarially verified
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
OASYS is published as an ordering and insight layer over the operator's stack and ships no dispatch or operational screen; its restaurant scope statement names ordering channels, upsell and visibility only. Delivery sense of `dispatch` is 0 across all 4 hits, and there is no expo or run-batching surface anywhere: `bump bar` 0, `KDS` 1, `kitchen display` 2, all verified in raw. https://www.soundhound.com/industries/restaurants · retrieved 2026-09-06 adversarially verified
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Not scored by this record.
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
Not scored by this record.
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
The vendor's own enumeration of ordering channels is entirely voice and conversational — phone, SMS, apps, drive-thru, in-car — with no web ordering site on the operator's domain. `web ordering` and `ordering website` are 0 docs in text and raw across all 1,807 documents, and /partners places online ordering with third parties (Olo, CardFree, Incentivio). https://www.soundhound.com/industries/restaurants · retrieved 2026-09-06 adversarially verified
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
The vendor's own help centre enumerates the guest payment flow for every first-party channel and none includes a guest account: in-car ordering — 'Do I need an account to place an order? No, an account is not required. We need only your payment method and your name', captured via a Stripe-hosted QR code, with payment methods updated, deleted or set as default 'on the Stripe-hosted page'; phone ordering — Square customers get a per-order SMS pay link and Toast orders 'will be set to pay in-store' with optional SH Wallet pay-ahead, also an SMS link ('How do my customers pay?', 23680557565843); and 'Do you have an ordering app?' (23681820301203) answers that customers are not asked to download an app. The only saved-payment mechanism documented is Stripe Link on Stripe's hosted checkout ('your payment method is saved securely for faster checkout next time', 53910762918803) — no vendor guest account, no saved addresses, no one-tap reorder in any first-party channel. https://support.soundhound.com/hc/en-us/articles/53020109939987-Account-Payment-Availability · retrieved 2026-08-04
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
CLAIM: a single guest profile automatically merging in-store POS, first-party web/app and kiosk transactions under one identity (phone or email match) with documented dedup/merge behaviour. FINDING: no. The product's documented object model contains no guest record. The Smart Answering eGuide enumerates the dashboard's contents with a genuinely closed introducing sentence - 'Beneath the Welcome section, you'll see the dashboard analytics which provides quick, actionable insights based on the calls coming through the assistant. The metrics can be described as follows:' followed by exactly six bullets, Total Callers / New / Returning / Queries Answered / English-Spanish / Today-Date (https://support.soundhound.com/hc/en-us/articles/23171551042579). The closure test was run rather than asserted: the SAME author uses the open forms elsewhere in the SAME article ('grouped into business categories, such as hours, location, policies, products & services, and more'), so the absence of 'including', 'such as' or 'and more' on the metric list is a deliberate contrast, not an accident. SoundHound therefore does distinguish new from returning callers by phone number for COUNTING, and stops there - no profile object, no per-guest order history, no merge rule. The rest of the model is equally named: the AI Knowledge Base holds Labels that provide Smart Answers or perform Smart Actions; the roles article enumerates the viewable surfaces as 'the call history, knowledge base, and dashboard' (https://support.soundhound.com/hc/en-us/articles/39311726333075). The identity channels the claim needs are positively absent: 'we don't require customers to download an app' (https://support.soundhound.com/hc/en-us/articles/23681820301203), and the transaction lands in the POS ('your customers receive an SMS when the order is received by the POS system', https://support.soundhound.com/hc/en-us/articles/23680557565843). CONTROLS (auditor re-run, Write-tool script, case-insensitive, boundary + stem + substring, positive controls 'SoundHound' 79/168 and 'the' 99/928): in-scope 'loyalty' 0, 'CRM' 0, 'reward' 0, 'guest' 0, 'member' 0 tokenised. POISON PUBLISHED: 'profile' returns 1 in-scope document / 2 hits and both are the analogy 'Just as LinkedIn uses the Profile Level Meter to measure the completeness of a person's profile' - about the assistant's knowledge completeness, not a diner; 'points' 1 hit, 'quick navigation points'; 'loyalty' returns 1 hit OUT of scope and 1 on the restaurants marketing page, and both are the abstract sense (a Five Guys executive saying voice ordering 'helps deepen loyalty and brand appreciation'), not a programme. 'loyalty' is word-boundary 0 in the 639,340-character FY2025 Form 10-K. DECLARED RESIDUE, and it is the nearest thing that exists: 'We do offer SH Wallet for Toast merchants, to enable pay ahead... Contact accountmanagement@soundhound.com to review' is one sentence in the Payment Support section and is the only customer-identity-adjacent object the vendor names; nothing further about it is published. Also excluded on scope, deliberately: SoundHound's consumer in-car Food Ordering app DOES have an account and an Order History, but it is a diner-facing app tied to a vehicle account, the operator never sees it, and it is a different product - see the scope note below. BOUND: 125 articles re-derived from /hc/sitemap.xml (171 locs, 125 ids) and /api/v2/help_center/en-us/articles.json (count=125), zero diff, per-category counts matching, en-us only, fabricated id 404 at 52 bytes; one Zendesk table rendered twice, so not two instruments. RESIDUE: food.houndify.com 302s every path to /login. https://support.soundhound.com/hc/en-us/articles/23171551042579-Smart-Answering-eGuide-Part-1-Getting-Started · retrieved 2026-09-15 adversarially verified
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
The claim requires accrual "without ... a bolt-on loyalty vendor", and SoundHound's own partner directory publishes the bolt-on loyalty vendor as its route to loyalty — Incentivio, plus CardFree and Radius Networks (Flybuy). No accrual model — points-per-dollar, punch, or tier — is configurable in any SoundHound surface. https://www.soundhound.com/partners · retrieved 2026-09-06 adversarially verified
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
One of the claim's three named automations — lapsed win-back — is a published, event-triggered, configurable OASYS capability: "Outreach is triggered by customer signals from your systems" and "Decide who qualifies for proactive outreach, the events that trigger it, and how it gets executed". Birthday and first-visit thank-you have no support: `birthday` matches 4 documents, 0 in the restaurant slice, none a campaign. https://www.soundhound.com/use-cases/outbound · retrieved 2026-09-06 adversarially verified
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
Not scored by this record.
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
Not scored by this record.
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
Not scored by this record.
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
Not scored by this record.
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
Not scored by this record.
Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator
guest-loyalty-cdp-event-api
Not scored by this record.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
Employee Assist is SoundHound's only staff-facing restaurant product and it publishes its own task list — ten items, none of them timekeeping. It is a knowledge and guidance agent on headset or tablet, and SoundHound ships no terminal to clock in at. `clock in`, `timekeeping` and `punch card` are 0 docs in text and raw across all 1,807 documents. https://www.soundhound.com/use-cases/employee-assist · retrieved 2026-09-06 adversarially verified
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
Not scored by this record.
Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.
labor-geofenced-mobile-punch
Not scored by this record.
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
Not scored by this record.
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
The only role model SoundHound publishes anywhere is exactly four fixed tiers over console surfaces (billing, settings, knowledge base, call history, dashboard) — the fixed-tier shape the claim names as its failure mode — with no grant of any discrete action. Separately, six of the claim's seven actions (void, comp, discount, refund, drawer open, price change) are POS transactions SoundHound does not perform at all: payment and disputes are executed by Square or Toast. https://support.soundhound.com/hc/en-us/articles/39311726333075-Roles-and-Permissions-in-SoundHound-AI-Smart-Answering · retrieved 2026-09-06 adversarially verified
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
SoundHound inserts no approval or override step into the operator's transactions — it publishes that disputes run exactly as they did before — so there is no manager override to attribute. `audit log` and `audit trail` are 0 docs in text and raw across all 1,807 documents, and `override` matches one document, outside the restaurant slice. https://support.soundhound.com/hc/en-us/articles/23680596751763-How-are-disputes-handled · retrieved 2026-09-06 adversarially verified
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.
labor-fair-workweek-support
Not scored by this record.
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Not scored by this record.
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
Not scored by this record.
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
Not scored by this record.
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
Not scored by this record.
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
Not scored by this record.
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
Not scored by this record.
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
Not scored by this record.
Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.
labor-digital-onboarding-i9
Not scored by this record.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
SoundHound's only published inventory touch is "Search inventory" in this read-only Employee Assist lookup list, answered from the operator's own data ("AI agents are trained on your manuals, procedures, and live data"). Lookup is not costing. `sub-recipe`, `plate cost` and `food cost` are 0 docs in text and raw; `recipe` matches 2 documents, neither a product surface. https://www.soundhound.com/use-cases/employee-assist · retrieved 2026-09-06 adversarially verified
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
Purchase, recipe and count units require an item master. SoundHound keeps none — it publishes that the assistant synchronises with the operator's existing menus rather than holding items. `yield`, `par level` and `stock count` are each 0 docs in text and in the raw HTML of all 1,807 documents. https://support.soundhound.com/hc/en-us/articles/23680310417811-Do-I-have-to-create-a-separate-menu-for-voice-ordering · retrieved 2026-09-06 adversarially verified
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
The vendor's own answer to "What can OASYS do for restaurants?" enumerates ordering channels, upsell and cross-location visibility — no stock ledger, and counting workflows require one. Corroborated by KB 23680310417811 (the assistant synchronises with the operator's existing menus). `cycle count`, `stock count` and `par level` are each 0 docs in text and raw across all 1,807 documents. https://www.soundhound.com/industries/restaurants · retrieved 2026-09-06 adversarially verified
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
Not scored by this record.
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
Not scored by this record.
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
Not scored by this record.
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
Not scored by this record.
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
Not scored by this record.
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Not scored by this record.
Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.
inventory-transfers
Not scored by this record.
Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.
inventory-commissary
Not scored by this record.
Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.
inventory-lot-traceability
Not scored by this record.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
CLAIM: a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise. NOT DETERMINED. The proposed no rested on a closed six-metric enumeration in the Smart Answering eGuide - 'The metrics can be described as follows:' then Total Callers / New / Returning / Queries Answered / English-Spanish / Today-Date. That enumeration is genuinely closed (the same author writes 'such as ... and more' elsewhere in the same article when he means open), but it is closed over the WRONG SURFACE. It describes the self-serve Smart Answering dashboard at smart-answering.soundhound.com. The surface this claim is about is the Smart Ordering operator portal at food.houndify.com, which 302s EVERY path to /login - including /robots.txt and a fabricated control path - so nothing inside it was seen, and the vendor's own restaurant article points operators at 'your account dashboard, where you can make updates in real-time, anytime' (https://support.soundhound.com/hc/en-us/articles/23188749367187). Worse for the no, the vendor's current platform page publishes an explicitly OPEN description of the reporting surface: OASYS ships 'Agentic analytics - A customizable dash for key KPIs, agentic performance, and more' and an 'Agent console - One dashboard to manage every live interaction in real-time' (https://www.soundhound.com/oasys, grade C). 'and more' on a customizable KPI dash is the opposite of a bound. So a dashboard demonstrably exists and is real-time; whether it carries SALES figures is unresolved, and the mobile-app conjunct is simply undocumented. An enumeration is a bound only over the category it enumerates, and this one enumerates a different product's screen. CONTROLS run anyway, for the next reader (Write-tool script, case-insensitive, boundary + stem + substring, positive controls 'SoundHound' 79 docs/168 hits and 'the' 99/928 non-zero): in the 46 in-scope help articles 'revenue' 0, 'reporting' 0, 'report' 0, 'PMIX' 0; 'dashboard' 7 documents / 16 hits; 'analytics' 1, the sentence quoted above; 'sales' 1 and it is POISON, 'please contact your sales rep'. 'report' returns 9 documents OUT of scope and every one is a consumer 'report a problem with your order' article from the LG / BMW / Food Ordering sets - scope poison. In the FY2025 Form 10-K 'dashboard' is word-boundary 0 and 'reporting' is 116, every one of them 'internal control over financial reporting'. TWO METHOD POISONS WORTH PUBLISHING: a control written inline in a bash `node -e` string returned 0 for EVERY term including 'the', because the shell ate the \b escapes - every figure here comes from a script written to disk with the Write tool and carrying a positive control; and a case-SENSITIVE matcher reads 0 for 'pricing' on this corpus where a case-insensitive one reads 3. TO RESOLVE: obtain a Smart Ordering / OASYS operator-console walkthrough, or any screenshot of the food.houndify.com dashboard. || 320th: 320th NEW SURFACE, not decisive. https://insights.soundhound.com/ ('SoundHound | Client Portal', production, found via crt.sh; SPA shell on every path) ships one anonymous ClojureScript bundle, /js/compiled/app.70EDB5D1D17CEC77BFABAAB2053D1C9A.js (6,590,211 B). Its routes include '/vc' 'Dashboard' under 'Voice Commerce' with an orders list (voice-commerce/orders-load-list-data, orders-reload-list) and '/vi' 'Dashboard' for Voice Insights (conversations-count, conversations-avg-duration, ces-score, scores-by-category, upsell, menu-items, live-data?). The API spec at https://api.restaurants.soundhound.com/swagger.json defines the vi-dashboard config with 'refreshSeconds': 'How many seconds before the dashboard should refresh the data' and voiceInsights.liveData 'Enable live data to be inserted'. So a browser dashboard that refreshes live exists. Word-boundary controls over the bundle: sales 0, revenue 0, 'net sales' 0, 'gross sales' 0, 'average ticket' 0; 'mobile' 22 and 'android' 5 are library/CSS strings, 'app store' 2 is an icon-name list. NOT A BOUND: the bundle also calls /api/reports, /api/reports/save and /api/ai-agent/report-builder-guide, an open report builder, so the zero sales vocabulary cannot carry a no; and food.houndify.com remains login-gated. Retrieved 2026-09-16. || 329th: 329th: NEW SURFACE, a two-store PUBLISHER CENSUS that bounds the MOBILE-APP conjunct, still not enough to publish a verdict. Apple: itunes.apple.com/lookup?id=284973001&entity=software returns SoundHound, Inc.'s complete iOS catalogue - exactly three apps, all consumer (SoundHound - Music Discovery com.melodis.soundhound.free 10.4.1, SoundHound(infinity) - Music Discovery com.melodis.midomi 10.4.1, SoundHound Chat AI App com.hound.hound 3.12.5). Google Play: the developer page play.google.com/store/apps/developer?id=SoundHound+Inc. yields exactly three package ids, the same set (com.hound.android.app, com.melodis.midomiMusicIdentifier, com.melodis.midomiMusicIdentifier.freemium). So SoundHound publishes NO operator/restaurant mobile app on either public store, and the claim's 'accessible from ... a mobile app off-premise' conjunct has no shipped artefact behind it. Held unknown anyway, under this atlas's rule that a voice-AI product lacking a module entirely is a hold rather than a no: SoundHound never owns the sales ledger (the POS does), so 'live SALES dashboard' may simply not be its surface. Re-checked and not productive: the Zendesk Help Center API at support.soundhound.com now lists 125 articles (up from the 46 in-scope of the 320th) and every one added since is consumer order support ('Problems with Your Order at the Restaurant', 'Refunds, Declines & Billing Issues', 'How to Order by Voice'), nothing operator-facing, and the newest updated_at is 2026-09-15 - nothing new since the last pass; docs.houndify.com 301s to www.soundhound.com (no developer portal); restaurants.soundhound.com and docs.soundhound.com do not answer; developers.soundhound.com is NXDOMAIN. Sales vocabulary remains absent from the whole insights.soundhound.com Client Portal bundle (6,590,211 B, re-grepped on disk): word-boundary revenue 0, sales 0, 'total sales' 0, 'net sale' 0, gross 0, AOV 0, 'average order' 0, 'order count' 0, tender 0, while 'orders' 29 and 'ticket' 23 are the Voice Commerce order list. Retrieved 2026-09-18. adversarially verified
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
The operator eGuide enumerates the dashboard's entire analytics surface — Total Callers, New, Returning, Queries Answered, a language toggle and a date range — with nothing financial: no sales, tax, tips, discounts, refunds, tender types or cash deposit. `end of day`, `close out` and `Z report` are 0 docs in text and raw across all 1,807 documents. https://support.soundhound.com/hc/en-us/articles/23171551042579-Smart-Answering-eGuide-Part-1-Getting-Started · retrieved 2026-09-06 adversarially verified
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
CLAIM: a product-mix report at individual menu item AND modifier level, with quantity, gross and net sales, filterable by daypart and revenue center. FINDING: no. This is a POS back-office artefact and SoundHound is not the system of record: 'the voice orders will flow directly into your POS for processing' (https://support.soundhound.com/hc/en-us/articles/23680715492755), the priced menu stays in the POS ('as long as your menu in the POS system has that detail', https://support.soundhound.com/hc/en-us/articles/23681757562259), and menu changes are made by emailing account management (https://support.soundhound.com/hc/en-us/articles/23680243280531). A PMIX report needs an item and modifier price model; the product holds neither. The vendor's only documented report is a six-metric call dashboard - 'The metrics can be described as follows:' Total Callers / New / Returning / Queries Answered / English-Spanish / Today-Date (https://support.soundhound.com/hc/en-us/articles/23171551042579) - and the viewable surfaces are enumerated as 'the call history, knowledge base, and dashboard' (https://support.soundhound.com/hc/en-us/articles/39311726333075). CONTROLS (auditor re-run, Write-tool script, case-insensitive, boundary + stem + substring, positive controls 'SoundHound' 79 docs/168 hits and 'the' 99/928 both non-zero on every run): 'modifier' 0/0 in all three modes across ALL 125 corpus articles, in-scope and out, and word-boundary 0 in the 639,340-character FY2025 Form 10-K; 'PMIX' 0; 'product mix' 0; 'daypart' 0 in the entire help corpus; 'revenue' 0 in-scope; 'reporting' 0 in-scope; 'report' 0 in-scope. POISON PUBLISHED: 'sales' 1 in-scope hit, 'contact your sales rep'; 'report' 9 documents OUT of scope, every one a consumer 'report a problem with your order' article from the LG / BMW / generic Food Ordering sets; the only 'daypart' in this vendor's whole published surface is on a photograph of a third-party HME drive-thru timer screen ('Current Daypart Breakfast 6-11') attached to the Hardware article, which is another publisher's product. 10-K poison: 'API' is word-boundary 2 but whitespace-squashed 124, because the letters sit inside 'capital' and 'rapidly' - a 60x overcount; 'POS' is word-boundary 1 but left-stem 109 and squashed 202, because it is inside 'Position', 'Possible' and 'Post'. BOUND: 125 articles re-derived from /hc/sitemap.xml (171 locs, 125 article ids) and /api/v2/help_center/en-us/articles.json (count=125), zero diff in both directions, per-category counts matching article-for-article, en-us the only locale, a fabricated article id 404 at 52 bytes - but those two instruments are one Zendesk table rendered twice and are not independent, and the href fixpoint over the 125 bodies finds ONE href in total and therefore has no power. RESIDUE, unbounded: food.houndify.com 302s every path to /login, and www.soundhound.com/oasys advertises 'a customizable dash for key KPIs, agentic performance, and more' whose contents are unpublished. The sibling cell reporting-realtime-dashboard was moved to unknown on exactly that residue; this cell is held at no because it asks for far more than a dashboard - gross AND net sales at modifier level with daypart and revenue-center filters - and the product positively holds no item price, no modifier object and no sale of record. https://support.soundhound.com/hc/en-us/articles/23680715492755-Does-the-voice-assistant-integrate-with-my-POS · retrieved 2026-09-15 adversarially verified
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator
reporting-multiloc-drilldown
Not scored by this record.
Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator
reporting-custom-report-builder
Not scored by this record.
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
Not scored by this record.
Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator
reporting-raw-warehouse-export
Not scored by this record.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
CLAIM: a named organizational hierarchy of at least three levels (enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations. VERDICT partial. SHORTFALL, NAMED: the documented hierarchy is exactly TWO levels - organization, then assistant/location - and there is no region, group, district or brand tier as an object; a user is attached to organizations and to assistants and to nothing in between. The partial is NOT self-refuting, and this was checked conjunct by conjunct: of the claim's three conjuncts, the level count FAILS, but 'first-class object' HOLDS (organization and assistant are both named containers a user is assigned to) and 'permissions can be scoped to it' HOLDS explicitly ('Location-specific permissions' appear in two of the four role definitions). Only reporting-scoping is unverified beyond the dashboard being per-assistant. QUOTES, all from https://support.soundhound.com/hc/en-us/articles/39311726333075: 'Users can also be assigned to multiple organizations or assistants, ensuring they have the exact level of access they need'; the role list is closed by the vendor's own count - the setup step reads 'Assign Role: Choose from the four roles (Owner, Admin, Editor, Viewer)' - with Owner 'Full control over all settings, including billing', Admin 'Full control over settings and configuration except billing', Editor 'Location-specific permissions to edit the knowledge base and view call history/dashboard', Viewer 'Location-specific view-only access to the call history, knowledge base, and dashboard'; 'Within each organization or assistant, users can hold different roles. For example, someone could be an Admin for one location but only a Viewer for another'; 'Owners and Admins can add or remove user roles across all their organizations and assistants from a single interface'; and the setup sequence 'Navigate to User Management... Assign Role... Choose Locations/Assistant(s)'. The restaurant-side article agrees: 'you can manage your business name, billing information, as well as the users that are part of the organization. You can also access location settings on the left pane Settings section' (https://support.soundhound.com/hc/en-us/articles/23188749367187). Two container types, four roles, nothing between org and location. NOTE THE LIMIT OF THIS ENUMERATION: it is closed over ROLES and over CONTAINER TYPES, which is the category this claim is about; it does NOT enumerate permissions, and must not be cited as a bound on any permission-level claim. POISON PUBLISHED: 'regional' returns 3 in-scope hits and all three are false friends - 'regional legal requirements' (compliance prose), 'Regional Routing' (a Smart Action that transfers a caller to a branch office, telephony not hierarchy), and 'leverage Editor and Viewer roles to involve regional teams without risking global configuration changes', which is a staffing recommendation that explicitly works AROUND the absence of a regional object. Word-boundary 'region' is 0 in-scope, 'franchise' 0, 'enterprise' 0, 'district' 0, 'hierarchy' 0; on the vendor's marketing pages every 'region' hit is the HubSpot form field 'region na1'. The FY2025 10-K adds only 'For enterprises, we also offer a flexible Gateway to integrate with custom POSs', an integration statement, not a hierarchy. BOUND: 125 articles re-derived from /hc/sitemap.xml (171 locs, 125 ids) and /api/v2/help_center/en-us/articles.json (count=125), zero diff both ways, per-category counts matching, en-us only, fabricated id 404 at 52 bytes; the two are one Zendesk table rendered twice, and the href fixpoint has no power. RESIDUE: food.houndify.com 302s every path to /login; if a brand or region tier exists in that portal it is undocumented, which is why this is partial and not no. https://support.soundhound.com/hc/en-us/articles/39311726333075-Roles-and-Permissions-in-SoundHound-AI-Smart-Answering · retrieved 2026-09-15 adversarially verified
Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator
multi-location-local-override-policy
Not scored by this record.
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
CLAIM: price tiers/zones so one menu item carries different prices per location group, per order channel and per daypart without duplicating the item record. FINDING: no. SoundHound stores no price for any item, so there is no item record on which a zone could hang, and its own account model duplicates rather than shares: each location is a separate assistant synchronised to its own connected POS menu ('once you create a SoundHound for Restaurant account and connect your POS system, the voice assistant will synchronize with your existing menus', https://support.soundhound.com/hc/en-us/articles/23680310417811; 'as long as your menu in the POS system has that detail', https://support.soundhound.com/hc/en-us/articles/23681757562259; menu changes performed by SoundHound account management on email request, https://support.soundhound.com/hc/en-us/articles/23680243280531). The roles article confirms the container model is organization then assistant/location with roles that are 'Location-specific' (https://support.soundhound.com/hc/en-us/articles/39311726333075). Grade-A corroboration: FY2025 Form 10-K, 'Its sophisticated technology learns the menu of each business.' CONTROLS (auditor re-run, Write-tool script, case-insensitive, boundary + stem + substring, positive controls non-zero): 'zone' 0/0 in all three modes both in-scope and out, across all 125 articles - the anticipated 'zone matches timezone' poison did not fire because the token is simply absent; 'daypart' 0/0 in the help corpus; 'district' 0; 'franchise' 0; 'enterprise' 0; 'hierarchy' 0; 'region' word-boundary 0 in-scope. POISON PUBLISHED: the left-stem run lifts 'region' to 3 in-scope documents and all three are false friends - 'regional legal requirements' (compliance prose), 'Regional Routing' (a Smart Action that transfers a caller to a branch, telephony not pricing), and 'involve regional teams' (a staffing recommendation). On the vendor's marketing pages 'region' is the HubSpot form field 'region na1', not a business object. The only occurrence of 'daypart' anywhere in this vendor's published material is on a photograph of a third-party HME drive-thru timer screen ('Current Daypart Breakfast 6-11') attached to the Hardware article - another publisher's product, which cannot carry a SoundHound claim. BOUND: 125 articles, re-derived from /hc/sitemap.xml (171 locs, 125 article ids) and /api/v2/help_center/en-us/articles.json (count=125), zero diff both ways, per-category counts matching, one locale, fabricated id 404 at 52 bytes; these are one Zendesk table rendered twice. The href fixpoint finds one href in 125 bodies and has no power. RESIDUE: food.houndify.com 302s every path to /login, and any private enterprise console is unpublished. https://support.soundhound.com/hc/en-us/articles/23680310417811-Do-I-have-to-create-a-separate-menu-for-voice-ordering · retrieved 2026-09-15 adversarially verified
Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator
multi-location-scheduled-publish
Not scored by this record.
A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator
multi-location-new-store-template
Not scored by this record.
The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator
multi-location-corp-vs-franchisee-roles
Not scored by this record.
Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator
multi-location-royalty-calculation
Not scored by this record.
Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.
multi-location-royalty-collection
Not scored by this record.
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
Not scored by this record.
Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator
multi-location-normalized-item-rollup
Not scored by this record.
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
Not scored by this record.
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
Not scored by this record.
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
Not scored by this record.
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Not scored by this record.
Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.
multi-location-multi-currency-locale
Not scored by this record.
Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator
multi-location-config-audit-log
Not scored by this record.
Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator
multi-location-enterprise-sso
Not scored by this record.
Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator
multi-location-enterprise-api
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
CLAIM: vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs. FINDING: no. The vendor publishes hardware documentation and it names third-party APPLIANCES, never an operating system, a version floor or a device spec; for the phone product it states positively that there is no client device at all. (1) 'Everything is integrated with your POS system without the need for any additional hardware. In addition to the phone number you use for your business, you need to set up an additional phone line...' (https://support.soundhound.com/hc/en-us/articles/23680722879507). (2) The corpus's one hardware document, 'Hardware' in the DI Hardware section (https://support.soundhound.com/hc/en-us/articles/34633044683795), has an EMPTY text body - its raw HTML is 919 bytes consisting of seven <img> tags and nothing else, so a text-only pass records a false absence here and an attachment census is the only instrument that reads it. The auditor downloaded and personally viewed all seven images rather than inheriting the reading. Six are photographs of a drive-thru retrofit and the seventh is a decorative crosshair icon: a Digital Acoustics gBridge-200 audio-over-IP bridge (+12 vdc, one Ethernet port, BYPASS button, ON and STATUS LEDs, MAC 3C:E4:B0:09:C6:A8, s/n 08262409C6A8); an HME drive-thru base station with its status screen; a black enclosure hand-labelled 'B106 AI On/Off Bypass' with a tenant support QR sticker and a phone number; a Delphi Display Systems outdoor order-confirmation screen rendering 'I'm Listening' beside a live three-item order; a Sceptre HDMI monitor showing a two-order confirmation display; and an HME drive-thru timer dashboard (Cars Served / Order Board / Greet / Service Window / Total Drive Thru, 'Current Daypart Breakfast 6-11') mounted on an ASUS panel. Not one names an operating system, a version or a spec. ON WHETHER AN IMAGE-DERIVED READING MAY CARRY A PUBLISHED ZERO: here it may, because the images are one-directional for this claim. They could only have OVERTURNED the no by naming a platform, and they do not; the zero itself is carried by the vendor's affirmative sentence that no additional hardware is required, plus the fact that the claim is about what documentation NAMES. An image-derived zero would NOT be publishable if the images were the only evidence of absence. (3) The marketing page www.soundhound.com/industries/restaurants (grade C) says Employee Assist reaches staff 'through your headset system or a tablet' - 'a tablet' names no platform and no version, so it does not satisfy the claim either. CONTROLS (auditor re-run, Write-tool script, case-insensitive, boundary + stem + substring, positive controls 'SoundHound' 79 docs/168 hits and 'the' 99/928 non-zero): in the 46 in-scope articles 'iOS' 0, 'iPadOS' 0, 'Android' 0, 'Windows' 0, 'Linux' 0, 'iPad' 0, 'tablet' 0, 'browser' 0, 'Chrome' 0, 'minimum' 0. POISON PUBLISHED, and it is live: a case-insensitive substring probe for 'iOS' returns 1 in-scope hit and it is the letters inside 'scenarios'; and OUT of scope 'iOS' returns 4 documents and 'Android' 1, all of them the SoundHound Music consumer app ('SoundHound for iOS: https://apps.apple.com/...', 'cancel your subscription for iOS (Apple) purchases'), so a pass that ignored category boundaries would have scored this cell yes off a song-identification app. In-scope 'device' 1 hit, poison - 'an SMS-capable device of your choosing'; in-scope 'hardware' 1 hit, the quote above; 'spec' reads 10 documents / 40 hits as a left-stem and 0 with both boundaries, every hit being 'specific' or 'special'. BOUND: 125 articles re-derived from /hc/sitemap.xml (171 locs, 125 ids) and /api/v2/help_center/en-us/articles.json (count=125), zero diff both ways; an attachment census over /api/v2/help_center/articles/<id>/attachments.json returned HTTP 200 on all 125 ids, with 4 articles carrying 19 files, all PNG, no PDF and no spec sheet - that census is the reason this cell has any evidence at all. RESIDUE: food.houndify.com 302s every path to /login. https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants · retrieved 2026-09-15 adversarially verified
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
The claim is about first-party terminals surviving an outage. SoundHound's operator KB states it supplies no hardware and rides the operator's POS, so there is no terminal to take orders, print to kitchen or record cash offline, and the corpus contains no restaurant offline-degradation documentation at all. https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants · retrieved 2026-09-06 adversarially verified
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
SoundHound publishes kitchen as an integration target, not a product: the drive-thru page ships "Kitchen & POS sync" as a sync chip, the restaurants page says OASYS scales "without ripping out your POS or kitchen systems", and the vendor's own word for its one KDS reference in 1,807 documents is "kitchen display system (KDS) integration". `bump bar` is 0 and `kitchen display` 2 in text and raw. https://www.soundhound.com/use-cases/drive-thru · retrieved 2026-09-06 adversarially verified
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
CLAIM: public, self-serve API reference readable without a partner agreement, NDA or sales call. VERDICT: no -> partial. NEW SURFACE (320th, found by crt.sh %.soundhound.com, 106 names): https://api.restaurants.soundhound.com/ is a PRODUCTION-named host serving Swagger UI anonymously (robots.txt 404, a nonsense path 404s so it is not a soft-200 catch-all; its /config.json lists exactly two specs, 'swagger' -> swagger.json and 'openapi' -> openapi.json). https://api.restaurants.soundhound.com/openapi.json (390,257 B, OpenAPI 3.1.0, title 'SoundHound Restaurants API', 7 operations, securityScheme ApiKeyAuth = x-api-key header) and https://api.restaurants.soundhound.com/swagger.json (294,231 B, Swagger 2.0, title 'Ramsay', 35 operations across v2/v3/v4: concepts, locations, cohorts, configurations, menu/selections, menu/entities, pricing-data, intent-actions, /v2/order/resolve 'converts a ticket into resolved-products'). Both read whole. The spec is UNLINKED (no SoundHound page references the host) and is the internal menu/configuration service behind the voice ordering agent; it names Casey's in a description, placing it in the restaurant product. MET: a machine-readable API reference for the restaurant menu/location/configuration service is readable anonymously with Swagger UI, which falsifies an unqualified no. SHORTFALL: it is unlinked, carries 'TODO' descriptions, is titled for an internal service ('Ramsay'), and every operation needs an x-api-key for which no self-serve issuance exists (houndify developer signup is not tied to this host; order-agent.soundhound.com answers every path 401 {"error":"unauthenticated"}). Same shape as the arryved precedent (anonymous partner spec, no self-serve access) -> partial. Retrieved 2026-09-16. https://api.restaurants.soundhound.com/openapi.json · retrieved 2026-09-16 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
SoundHound's only developer surface is the Houndify platform — the same infrastructure its restaurant operator login (food.houndify.com) runs on — and the Houndify API License Terms define authentication as an API Key: 'a unique alpha-numeric code, issued by SoundHound, specific to the Houndify Cloud Service when calling a Houndify API', monitored and revocable by SoundHound. No OAuth 2.0 flow, scope, or operator-granted, individually revocable permission appears anywhere in the terms, and no partner-app marketplace exists for the restaurant product. Vendor-issued static keys are precisely the pattern this claim excludes. https://www.houndify.com/terms · retrieved 2026-08-04
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
320th NEW SURFACE, not decisive. NEW SURFACE (320th, found by crt.sh %.soundhound.com, 106 names): https://api.restaurants.soundhound.com/ is a PRODUCTION-named host serving Swagger UI anonymously (robots.txt 404, a nonsense path 404s so it is not a soft-200 catch-all; its /config.json lists exactly two specs, 'swagger' -> swagger.json and 'openapi' -> openapi.json). https://api.restaurants.soundhound.com/openapi.json (390,257 B, OpenAPI 3.1.0, title 'SoundHound Restaurants API', 7 operations, securityScheme ApiKeyAuth = x-api-key header) and https://api.restaurants.soundhound.com/swagger.json (294,231 B, Swagger 2.0, title 'Ramsay', 35 operations across v2/v3/v4: concepts, locations, cohorts, configurations, menu/selections, menu/entities, pricing-data, intent-actions, /v2/order/resolve 'converts a ticket into resolved-products'). Both read whole. The spec is UNLINKED (no SoundHound page references the host) and is the internal menu/configuration service behind the voice ordering agent; it names Casey's in a description, placing it in the restaurant product. The only webhook in either spec is a configuration field of the menu-board namespace: menuBoard.webhookUrl 'URL to send webhooks to from menu board' (16 hits in swagger.json, 2 in openapi.json, all that one field). It proves SoundHound's drive-thru menu board can push to a configured URL, but no event names, payloads or order-lifecycle events (created/modified/paid/voided/refunded) are specified, so it cannot carry yes or partial for this claim. callback 0, subscri 0, notif 0, poll 0; 'event' is POISON ('tool, service or event that disabled this selection'). Also probed from crt.sh: order-agent.soundhound.com (401 on every path), insights.soundhound.com (Client Portal SPA, 6.6 MB; 'webhook' 20 hits are all the lucide Webhook ICON), menu-board.soundhound.com and insights-dashboard.soundhound.com (same 'Menu Board' SPA shell on every path), success.soundhound.com (Rocketlane), accounts.soundhound.com (Cloudflare challenge 403, a refusal). amelia.ai subdomains all Cloudflare 403; synq3.com 301s to soundhound.com/synq3. Retrieved 2026-09-16. || 329th: MERGE HOLD (proposed no/A, held unknown): The published spec itself carries a customer-supplied `menuBoard.webhookUrl` field (9 hits), i.e. SoundHound DOES call out to an operator/partner URL in at least one flow, so 'no webhook surface' is not what the spec shows; what it pushes and whether order events are covered is undocumented. SoundHound also integrates with POS partners over channels this spec does not describe (327th rule). Held; could be a partial if the menuBoard callback's payload is ever documented. PROPOSAL AS WRITTEN: 329th: MOVED unknown -> no/A. The 320th found this surface but left it unresolved; the 328th merge rule settles the shape - a webhooks `no` IS accepted when the vendor's own API is PUBLISHED anonymously and the published spec has no webhook surface and names a static key. Re-fetched and re-controlled today. BOUND: https://api.restaurants.soundhound.com/config.json (188 B) enumerates the host's ENTIRE published spec set, exactly two entries - {"urls":[{"name":"swagger","url":"swagger.json"},{"name":"openapi","url":"openapi.json"}],"urls.primaryName":"openapi"}. Both were fetched whole and anonymously today: openapi.json 394,284 B (OpenAPI 3.1.0, title 'SoundHound Restaurants API', 7 paths / 7 operations, securityScheme ApiKeyAuth = the x-api-key header, i.e. a static key, no OAuth) and swagger.json 294,843 B (Swagger 2.0, title 'Ramsay', 35 paths / 35 operations across v2/v3/v4 - concepts, locations, cohorts, configurations, menu/selections, menu/entities, pricing-data, intent-actions, /v2/order/resolve). 42 operations total. NOT A SOFT-200: the nonsense control path https://api.restaurants.soundhound.com/zzz-nope-control.json answers 404 at 73 bytes, and robots.txt 404s. The spec is LIVE, not retired or staging: openapi.json has grown from 390,257 B on 2026-09-16 to 394,284 B today. CONTROLS, tokenised, case-insensitive, word-boundary, over both spec bodies: callback 0/0, callbacks 0/0, subscription 0/0, subscribe 0/0, notification 0/0, notify 0/0, poll 0/0, polling 0/0, events 0/0, eventType 0/0, sse 0/0, websocket 0/0, pubsub 0/0, push 0/0. OpenAPI 3.1's own `webhooks` top-level object is absent from both. The ONLY webhook token in either document is the single menu-board configuration field menuBoard.webhookUrl, 'URL to send webhooks to from menu board' (8 occurrences in swagger.json, 1 in openapi.json, all that one field) - a drive-thru menu-board display config, not an order-lifecycle event subscription: no event names, no payload schemas, no delivery/retry semantics, and nothing for created/modified/paid/voided/refunded. POISON: bare 'event' scores 5 in openapi.json and 2 in swagger.json and is prose ('tool, service or event that disabled this selection'), not an event type; 'order' scores 46 and 87 and every hit is an order RESOLUTION or ticket path (/v2/order/resolve 'converts a ticket into resolved-products'), not an emitted event. RESIDUAL RISK, stated: this bounds the published restaurants API surface on SoundHound's own api.restaurants host; if SoundHound runs an additional unpublished POS-integration partner API the no would not cover it, and docs.houndify.com now 301s to www.soundhound.com so no second developer portal is published today. Retrieved 2026-09-18. adversarially verified
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator
extensibility-data-symmetry
Not scored by this record.
API rate limits are published as specific numeric quotas with documented throttling behavior and headers.
extensibility-published-rate-limits
Not scored by this record.
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
Not scored by this record.
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Not scored by this record.
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Not scored by this record.
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
Not scored by this record.
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
Not scored by this record.
Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator
extensibility-bi-data-warehouse
Not scored by this record.
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
Not scored by this record.
Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.
extensibility-custom-fields-scripting
Not scored by this record.
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
Not scored by this record.
The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.
extensibility-api-versioning-deprecation
Not scored by this record.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
On-terminal order entry, ticket routing and check printing require a terminal SoundHound does not ship; voice orders route into the operator's existing POS. `offline` is 0 in the 120-doc restaurant slice, `failover` and `redundancy` are 0 corpus-wide in text and raw. https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants · retrieved 2026-09-06 adversarially verified
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
Not scored by this record.
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
Not scored by this record.
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
Not scored by this record.
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
Not scored by this record.
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
SoundHound provides no KDS and no kitchen-printer routing that could keep running offline; kitchen is a sync target on its own drive-thru page. `printer` and `failover` are 0 docs in text and raw across all 1,807 documents; `kitchen display` 2 and `KDS` 1, and the one KDS hit is a newsroom line about integrating with an operator KDS. https://www.soundhound.com/use-cases/drive-thru · retrieved 2026-09-06 adversarially verified
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
Printer failover presupposes the vendor configures and monitors kitchen printers. SoundHound configures no devices — its own KB says the product needs no additional hardware and rides the operator POS, which drives printing. `printer`, `bump bar` and `failover` are 0 docs in text and raw; the single `print` hit is an executive bio. https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants · retrieved 2026-09-06 adversarially verified
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator
reliability-contractual-uptime-sla
Not scored by this record.
The vendor publishes written post-incident reports or root-cause summaries for major outages.
reliability-incident-postmortems
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.
reliability-backup-restore
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
A publicly accessible SoundHound page states the cancellation window — monthly cancel anytime, annual one month before expiry — so the window is diligenceable without a signed quote. The auto-renewal term itself is nowhere stated: `auto-renew` is 0 docs in text and in raw across all 1,807 documents, and the 20-doc www legal set contains no renewal clause. https://support.soundhound.com/hc/en-us/articles/24543816821395-How-do-I-cancel-my-account · retrieved 2026-09-06 adversarially verified
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
Not scored by this record.
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
Not scored by this record.
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
Not scored by this record.
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
STALE-CITATION REPAIR: the old citation https://www.soundhound.com/voice-ai-solutions/restaurants/ now 301s to this page (site rebuilt). Re-verified: no per-location or per-terminal figure is published anywhere. `pricing` reads 11 hits across the 120-doc restaurant slice and not one is a dollar figure; the only dollar amounts in the corpus are the consumer Chat AI app ($19.99/$6.99) and a marketing savings stat. The restaurant page routes to a specialist. https://www.soundhound.com/industries/restaurants · retrieved 2026-09-06 adversarially verified
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
STALE-CITATION REPAIR: the old citation https://www.soundhound.com/voice-ai-products/dynamic-drive-thru/ now 301s to /use-cases/drive-thru (site rebuilt). Upgraded C->B: the operator KB states SoundHound supplies no hardware at all, so there are no terminals, KDS screens or printers of its own to purchase outright at any price. Hardware around the product is partner-supplied (Elo, Acrelec, HME, Andrea per /partners), not sold by SoundHound. https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants · retrieved 2026-09-06 adversarially verified
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
commercial-implementation-fee-published
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).
commercial-source-available-selfhost
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.
commercial-soc2-attestation
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 31 values — 28 upheld, 1 downgraded, 2 upgraded. It separately resolved 15 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| labor-granular-rbac | unknown / F, placeholder: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | The claim's discrete actions (void, comp, discount, refund, drawer open, price change, report access) are staff actions executed on a POS. SoundHound's complete restaurant catalogue — Dynamic Drive-Thru, Smart Lane, Smart Ordering, Dynamic Kiosk, Employee Assist, Voice Insights, In-Car Ordering — is guest-facing voice order capture plus a staff Q&A assistant; no staff-facing transactional workflow exists for per-action permissions to govern. Its Smart Ordering page names Square, Toast and Oracle as the POS platforms orders post into. Same pattern as the acrelec record's resolution of this cell. source |
| labor-manager-override-audit | unknown / F, placeholder: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | Manager overrides and approvals of voids/comps/refunds happen on the chain's POS; SoundHound is a voice order-capture layer in front of it and ships no product in which such an approval could occur or be written to an audit trail. Consistent with the record's identity ('it sits in front of a POS rather than being one') and the resolve-to-no on labor-granular-rbac. source |
| extensibility-oauth-partner-apps | unknown / F, placeholder: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | Read the Houndify API License Terms — the developer platform the restaurant login (food.houndify.com) runs on. Authentication is defined as a vendor-issued API Key ('a unique alpha-numeric code, issued by SoundHound, specific to the Houndify Cloud Service when calling a Houndify API'), monitored and revocable by SoundHound; no OAuth 2.0 flow, scope or operator-granted permission appears anywhere in the terms, and no partner-app marketplace exists for the restaurant product. The vendor's own primary document enumerates the auth mechanism and it is exactly the static-key pattern the claim excludes. Upgraded F to B. source |
| commercial-hardware-purchase-outright | unknown / F, placeholder: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | SoundHound sells software services, not terminals, KDS screens or printers: the Dynamic Drive-Thru page states the product is 'created with integration in mind, working seamlessly with your existing hardware and software', no hardware product appears in the catalogue, and no price of any kind is published (the record already scores commercial-pricing-published no at grade B). Nothing the product requires is purchasable outright at a published price. Mirrors the conversenow record's grade-C resolve-to-no on this cell. source |
| digital-menu-single-source | unknown / F, placeholder: "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The help centre — which earlier passes recorded as HTTP 403 but serves normally with a browser user agent — has a Menu Management section: the voice ordering menu is synchronized from the connected POS menu record ('the voice assistant will synchronize with your existing menus'), so there is no separate digital menu build. But synchronization is documented only for the Square integration, and the companion article says menu changes are made by emailing account management 'and we will take necessary action' — an item edit does not propagate automatically. Present with named shortfalls: partial at grade B. source |
| digital-account-saved-payment | unknown / F, placeholder: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | The vendor's own help centre enumerates the guest payment flow in every first-party channel and none involves a vendor guest account: in-car — 'an account is not required', payment captured via Stripe-hosted QR code and managed on the Stripe-hosted page; phone — per-order SMS pay link (Square) or pay in-store / optional SH Wallet SMS pay-ahead (Toast); and no ordering app exists by design ('we don't require customers to download an app'). The only saved payment is Stripe Link on Stripe's hosted checkout. No guest account, saved addresses or one-tap reorder anywhere — the docs enumerate the alternatives and this is not among them: no at grade B. source |
| multi-location-central-menu-publish | unknown / F, placeholder: "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | The help centre's Menu Management section enumerates the entire menu workflow and merchant menu authoring is not in it: menus synchronize from the connected POS, and changes are made by emailing accountmanagement@soundhound.com or an account manager. No author-once corporate menu, no publish-to-locations action, no publish/version history — the menu record lives in the chain's POS, and enterprise Smart Ordering implementation is SoundHound-performed 'menu ingestion'. Positive enumeration of the alternative: no at grade B. source |
| order-capture-scheduled-orders | partial / D, "'Smart Lane' is marketed as advance pre-ordering ahead of the line; no lead-time-per-cha" | upheld | The cited https://www.soundhound.com/restaurants/ now 301s to /voice-ai-solutions/restaurants/. I fetched the destination: the Smart Lane sentence survives verbatim, so the citation is re-pointable, but it is marketing about pre-ordering while standing in line and cannot carry a timing claim. I then enumerated the Zendesk help centre via the public search API and found article 53052980420115, which states scheduled pickup outright for the in-car channel, plus 'Can I change my pickup time after placing an order? The estimated pickup time cannot be changed.' Partial stands with a named shortfall; the withdrawn leg is the marketing sentence, and the grade moves D -> B on the help-centre article. source |
| commercial-pricing-published | no / B, "Page offers an ROI calculator and a specialist call; no dollar figures at all." | upheld | The cited URL 301s to /voice-ai-solutions/restaurants/; I fetched the destination in full and confirmed the substance - CTAs are 'Talk to a Restaurant AI Specialist' and 'Talk to an Expert', the ROI calculator takes operator inputs and outputs revenue lift, and no software price appears. I also probed /pricing/ (404) and searched the Zendesk help centre for pricing/cost/price/subscription/fee: the only pricing hits are the free music app and Houndify's 'Access a full pricing grid by creating a free Houndify account'. Value unchanged, but the grade drops B -> C because a vendor solutions page is a feature page, not documentation, and the note's 'no dollar figures at all' is withdrawn - the page does print a $11,000 savings figure. source |
| order-capture-split-merge | no / F - Voice ordering front end; check splitting belongs to the POS behind it." | upheld | Re-read KB 23680715492755 in full: the article is a scope statement ("directly integrates with Square", "integrates with Toast", other POS = answer calls only). Delegation of processing is affirmative, not a corpus zero. Re-derived `split check` 0/0/0 and confirmed 0 in raw. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| order-capture-offline-order-entry | no / F - Cloud voice AI; requires connectivity." | upheld | ADJUDICATED AGAINST THE BRIEF (item 11): the coordinator predicted `unknown`; analyst A was right. I read all 5 `offline` hits — CarPlay, NVIDIA GTC x2, Hyundai, Stellantis edge — every one automotive. /oasys/edge-and-cloud is framed on "your device's CPU", "a car entering a tunnel" and a Stellantis quote and never mentions restaurants, so BRIEF 4.2 defeats the old rationale without reaching this claim. A claim whose subject (a terminal) does not exist in the product is `no`, not `unknown`. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| payments-emv-nfc | no / F - Not a payments vendor; no first-party terminals." | upheld | ADJUDICATED (item 13): A's countervailing fact is real — KB 53910762918803 (LG Food Ordering) publishes "You can pay with: Card Apple Pay Google Pay" via Stripe. That is a wallet checkout inside SoundHound's own CONSUMER app, not an EMV/NFC-reading terminal, and the claim is universally quantified over "first-party payment terminals", of which there are none. A's reading is correct; `partial` would misdescribe an in-app Stripe checkout as terminal acceptance. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| payments-gift-cards | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | Re-read KB 23680557565843 in full. SH Wallet is named there but is described only as a pay-ahead SMS link for Toast merchants — no balance, no issuance, no redemption. Verified `gift card` 0 in raw. Does not assert Square/Toast lack gift cards. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| payments-refund-void-controls | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED. A's bound is too clever and I reject it: KB 39311726333075 enumerates four ROLES and describes their access in prose ("Full control over all settings"); it does not enumerate permissions, so "the vendor published its whole permission model" overstates what the article is. It is also scoped to Smart Answering (SMB phone), so it cannot bound OASYS. The `no` survives on a stronger and product-independent ground — SoundHound performs none of the four gated transactions — cited to the disputes article, which is affirmative and grade B. Value and grade unchanged. source |
| commercial-autorenew-terms-published | no / F - Enterprise contracts; no public contract terms surfaced." | upgrade-to-partial | ADJUDICATED (item 10). I re-read /terms-of-service: it is a consumer EULA ("This EULA will remain in effect until terminated") with no subscription or renewal clause, so the legal set genuinely is empty on this. The FAQ-not-contract objection is real but the claim's operative contrast is "publicly accessible ... rather than only in a signed quote", which a public KB article satisfies. One of the claim's two elements is met, one is absent: `partial` is the honest reading and dropping back to `no` would assert the vendor publishes nothing, which is false. Scope caveat stands: this is the self-serve product; no enterprise OASYS contract is published. This is the sweep's most fragile row. source |
| hardware-kds | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED from the "Scale without ripping out" line (which four cells shared) to the drive-thru feature chips, which are affirmative about what OASYS does at the kitchen boundary. I REJECT analyst B's /partners bound (item 6): SoundHound announced KDS integration for Burger King UK yet lists no KDS partner among the 57, which proves the directory is not a census of its integration surface — so "kitchen appears zero times on /partners" is an argument from silence, not a bound. Verified the zero itself (0 hits for "kitchen" and "KDS" on that page) and the newsroom quote (item 8): real, and the vendor's own word is "integration". The `no` survives on the product-page evidence alone. source |
| kitchen-station-routing | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED off the shared marketing sentence. CONFIRMED item 7: I read every `routing` hit — Smart Answering call routing, ServiceNow/IT-autonomics ticket routing, healthcare request routing, and one bank "routing number". Zero are kitchen item routing, and no row in the sweep used `routing` as kitchen evidence. `station` 0 in the 120-doc restaurant slice, 0 in raw for those docs. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| kitchen-expo-consolidation | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED off the shared marketing sentence. Re-derived the brief's `expo` control of 4 and read all four: Paris Expo Porte de Versailles x3, Venetian Expo Center. Entirely trade-show artefact, kitchen-expo sense 0 — the coordinator's figure is correct and no row republished it as evidence. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| kitchen-bump-bar-hardware | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED, and B's load-bearing bound REJECTED for the reason given on hardware-kds — the /partners directory demonstrably omits an integration SoundHound has announced, so its silence on kitchen hardware bounds nothing. I also treat 57 as a FLOOR, not a census (see hardware-kds and my report), which weakens that bound further. The `no` rests instead on the absence of any first-party KDS plus a corpus-wide zero for the claim's own device, verified in raw. source |
| hardware-offline-mode | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | Re-read KB 23680722879507 in full — it is titled "Do I need to purchase any hardware...", so the quote is a direct answer to a hardware-scope question, not a stray line. SCOPE CAVEAT CONFIRMED AND SURVIVED: the article covers the phone product, and drive-thru does deploy partner hardware (HME, Digital Acoustics, Andrea, Elo, Acrelec) — but none of it is a POS terminal, a kitchen printer or a cash drawer, so the conclusion holds for the wider product. /oasys/edge-and-cloud reaches only automotive devices. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| reliability-offline-order-entry | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | Confirmed item 18: /oasys/control-and-security's "99.95 % target platform uptime" is a cloud availability target and satisfies NO reliability cell — the coordinator putting it in the brief as reliability evidence was an error, and this row correctly refused it. Confirmed no row leaned on it affirmatively. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| reliability-offline-kds-printing | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED off the shared marketing sentence to the drive-thru chip line. The newsroom KDS quote (item 8) is verbatim and its reading is fair — but it is grade C and I have not let it carry the verdict, only corroborate. Re-verified `printer` 0 in the raw HTML of all 1,807 docs, so the nav/footer strip did not create it. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| reliability-printer-fallback | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | Tested the coordinator's question (item, evidence concentration): does "no additional hardware" reach printer fallback? Yes — more directly than it reaches offline order entry, because the claim is about a device the vendor would have to supply and monitor. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| labor-clock-in-at-pos | no / F - 'Employee Assist' is voice-based training/handbook access, not timekeeping." | upheld | QUOTE CHANGED from the page hero line to the published task-chip enumeration, which is the sentence that actually does the work. Re-read /use-cases/employee-assist in full: "Deploy AI agents across the tablets and headset systems you already use" confirms no first-party device. Treating the chip list as a floor rather than a ceiling, the verdict still holds because there is no device and no timekeeping vocabulary anywhere in the corpus. source |
| labor-granular-rbac | no / F - SoundHound's complete restaurant catalogue — Dynamic Drive-Thru, Smart Lane, Smart Ordering, Dynamic | upheld | VERIFIED C's inversion (item 14): claimdefs does contain "not limited to fixed cashier/manager/admin tiers", and the article does close the set — "Assign Role : Choose from the four roles (Owner, Admin, Editor, Viewer)". So this is affirmative refutation, not silence. RESOLVED C's own alternative (item 15): the cell scores the vendor, and I decline `unknown`, because the argument that carries it is transaction-existence, not console granularity — an undocumented OASYS role model cannot grant permission over a void SoundHound never performs. CONFIRMED item 16: /oasys/control-and-security's "Functions — Assign — or withhold — specific actions" is scoped per AI AGENT, not per staff role, and no row treated agent-scoping as staff RBAC. The record's "no staff-facing transactional workflow" rationale is FALSE and is replaced above. source |
| labor-manager-override-audit | no / F - Manager overrides of voids, comps, discounts and refunds are POS transactional controls, and SoundHo | upheld | CITATION CHANGED. The Roles article is a role-assignment how-to; it is not where an approval trail would live, so calling it "the place an approval trail would be documented" was an overreach and its only `audit` is the instruction "Regularly Audit Permissions". Considered and rejected as grounds for `unknown`: /oasys/control-and-security names "Refund approval" as one of four generic Agentic Workflow Designer samples (alongside Money transfer, Password reset, Prescription refill) — a cross-industry demo list, not a shipped POS authorization gate — and /trust-center's "transparent decision logs" is agent decision logging, not approver attribution. Value and grade unchanged. source |
| inventory-recipe-bom-costing | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CONFIRMED D's correction of the coordinator's §3 table (item 20): /use-cases/voice-commerce's "Device makers turn conversations into inventory" is ADVERTISING inventory, so the coordinator's "2 product surfaces" was an overcount. But D undercounted too — I found two further SoundHound-capability mentions neither party listed (Vision AI "retail shelf intelligence ... AI-powered inventory awareness" on /resource/when-vision-meets-voice and the Vision AI launch newsroom). Both are shelf-gap answering, read-only, and change nothing here. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| inventory-unit-conversion-yields | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED, and this is the coordinator's own item-5 concern answered: "Scale without ripping out your POS or kitchen systems" does not mention inventory and was decoration on this cell. Replaced with a grade-B operator KB sentence that actually scopes the subject away — SoundHound mirrors the operator's menu and owns no item master — which is why this stays `no` rather than going to `unknown`. Grade improves C to B. source |
| inventory-count-modes | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED off "Scale without ripping out your POS or kitchen systems", which does not mention inventory, to the product-scope FAQ sentence on the same page, which does answer what the product is. I treat that enumeration as a floor, not a ceiling, per project doctrine — it is the item-master absence, not the list, that carries the verdict. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| reporting-eod-closeout | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | Re-read the eGuide and the enterprise counterpart. /use-cases/voice-insights is scoped the same way: its three published scores are Marketing, Efficiency and Satisfaction and its outputs are transcripts and conversation fields — it says "Connects to your existing audio hardware, point-of-sale, and contact center systems", i.e. it READS POS data and never publishes a tender or deposit reconciliation. Two independent surfaces, SMB and enterprise, both non-financial. Every zero I rely on was re-run against corpus.json `raw` (unstripped HTML, all 1,807 docs) as well as `text`: identical. The nav/footer strip manufactured no absence. source |
| delivery-driver-roster | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED — this is one of the four cells the coordinator flagged in the evidence-concentration table, and the flag was right: "Scale without ripping out your POS or kitchen systems" never mentions delivery and was decoration. I re-derived `driver` myself: 37/37/4 docs, and I read every hit — driver's seat, driver experience, "before the driver pulls forward", and metaphorical "key driver of". Delivery sense 0, confirmed in raw as well. The cell stays `no` rather than `unknown` because delivery is an order TYPE SoundHound passes on, not a module it operates. source |
| delivery-dispatch-board | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CITATION CHANGED for the same reason as delivery-driver-roster. I re-derived `dispatch` and read all four documents: an IT facilities work-order agent ("Fred"), an insurance roadside line, Qualitas ambulance dispatch, and police MDT dispatch details. Delivery-dispatch sense 0, confirmed — the coordinator's control figure is right. source |
| digital-first-party-web | no / F - Voice/app channels only; no first-party branded web ordering site product." | upheld | CONFIRMED item 23: the operator-branded reading is the one the claim states ("on the restaurant's own branding/domain"), so D scored it correctly and the SoundHound-branded reading is not what is being asked. CONFIRMED item 22: the Allset release does say "Allset is a marketplace connecting restaurants and local diners", and a marketplace is the opposite of an operator-domain first-party site — sound, though newsroom and corroborating only. CONFIRMED D's `commission-free` check: 1 document, a ChowNow press release about ChowNow's own app, not SoundHound pricing, so commission is unestablished either way and the verdict rests on the channel absence alone. source |
| guest-loyalty-accrual-models | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upheld | CHECKED the direction of the inference (item 21) and it is the correct way round: the partner listing is not being used to give SoundHound a loyalty capability, it is being used to show the capability is somebody else's — and uniquely here that directly refutes the claim's own "without a bolt-on loyalty vendor" wording. I re-derived `points` (25/25/3) and read the hits: pain/control/touch/price/data/navigation points and points of interest, plus the coordinator's own §3 trap sentence (a general listicle) and a blog about Starbucks Rewards. Loyalty-accrual sense on a SoundHound product surface: 0. `punch card` 0 in raw. source |
| guest-loyalty-lifecycle-automation | no / F - Migrated from the 2026-08-01 research pass; no source URL was recorded." | upgrade-to-partial | PRESSED as instructed (item 19). One of three named automations is met, but the claim's mechanism requirement — configurable always-on triggers rather than one-off manual sends — is met affirmatively and explicitly, which is what makes this more than a `no`. I weighed D's three self-flagged grounds: the voice channel is a legitimate campaign channel and the claim does not require messaging; the claim does not require SoundHound to own the guest database; the page is generic OASYS but /use-cases/outbound sits inside the 120-doc restaurant slice and `win-back` is 1/1/1 with that single document being this page. `partial` is generous but honest; it must not be read as a loyalty engine. source |
| commercial-pricing-published | no / C - The restaurant solutions page publishes no price of any kind - no per-location, per-terminal or per- | upheld | Stale-URL repair outside the 26-cell sweep; verdict unchanged, URL re-pointed to the live page and the absence re-bounded. source |
| commercial-hardware-purchase-outright | no / C - SoundHound sells no terminals, KDS screens or printers to purchase: Dynamic Drive-Thru is positioned | upheld | Stale-URL repair outside the 26-cell sweep; verdict unchanged, citation replaced with a grade-B operator-KB sentence that addresses the claim directly. source |
| menu-pricing-modifier-price-by-parent-size | unknown (F) — never examined | resolve-to-no | Value upheld, argument corrected. I verified the three quotes byte-for-byte in the held bodies and re-ran every control myself, case-insensitively and in three modes with two positive controls; 'modifier' and 'multiplier' are 0 across all 125 articles, not merely in scope. I rejected the proposer's framing that the two-article Menu Management section is a 'complete enumeration of the operator's menu controls' - it is one FAQ answer to a different question, and an enumeration is a bound only over the category it enumerates. The verdict survives on the architectural evidence instead: three separate articles locate the priced menu in the connected POS and the only documented way to change a menu is to email account management. I also caught a control defect of my own worth publishing: case-sensitive \bpricing\b reads 0 where case-insensitive reads 3. |
| menu-pricing-topping-quantity-tiers | unknown (F) — never examined | resolve-to-no | Upheld on re-derived evidence, with the proposer's closed-enumeration argument struck for the same reason as the sibling cell. My own controls reproduce 'modifier' 0 and 'multiplier' 0 across the whole 125-article corpus and in the 10-K. I add the boundary-vs-stem disagreement on 'tier' (0 tokenised, 1 as a stem, and the stem hit is a gym membership example) as published poison, and I re-derived the corpus bound from the publisher's sitemap and article API rather than inheriting the proposer's figure. |
| multi-location-price-zones | unknown (F) — never examined | resolve-to-no | Upheld. I reproduced 'zone' and 'daypart' at 0/0 across all 125 articles in three matching modes with working positive controls, and I opened every 'region'/'regional' hit rather than trusting the count - all three in-scope hits are false friends, and the marketing-page hits are a HubSpot form field. New poison I add: the single instance of 'daypart' in this vendor's whole published surface is on a photograph of an HME timer, i.e. a third party's screen. The verdict rests on the vendor positively locating pricing in the connected POS in three separate articles plus a per-assistant account model that duplicates by design. |
| guest-loyalty-unified-profile | unknown (F) — never examined | resolve-to-no | Upheld, and the closed-enumeration defence survives the closure test on this cell - I checked the introducing sentence in the raw body and confirmed the same author writes 'such as ... and more' two paragraphs later when he means an open list, which is the strongest available proof that 'The metrics can be described as follows:' is closed. I opened every 'profile', 'points' and 'loyalty' hit: all poison. I add two things the proposer did not: SH Wallet, named in one sentence in the Payment Support section, is the nearest customer-identity object in the product and is declared as residue rather than ignored; and the consumer Food Ordering category's order history is named and explicitly excluded on scope rather than left silent. |
| reporting-realtime-dashboard | unknown (F) — never examined | downgrade-to-unknown | Downgraded from no/B to unknown/F. The six-metric enumeration is closed - I verified the introducing sentence in the raw body and confirmed the same author signals open lists with 'such as ... and more' - but it is closed over the Smart Answering SMB dashboard, not the Smart Ordering operator portal the claim is about, and a list bounds only the category it enumerates. Two things the proposer did not weigh decide it: food.houndify.com is a total wall (every path, including /robots.txt and a fabricated path, 302s to /login), and the vendor's own OASYS platform page advertises 'a customizable dash for key KPIs, agentic performance, and more' plus 'one dashboard to manage every live interaction in real-time'. An 'and more' on a customizable dashboard cannot support a published zero. The proposer's own note conceded the cell 'should be revisited' if that console carries sales figures, which is an admission that it is not settled. Absence of evidence is unknown, never no. |
| reporting-pmix-modifier-level | unknown (F) — never examined | resolve-to-no | Upheld, but on a narrower argument than the proposer's and explicitly distinguished from the sibling cell I downgraded. The six-metric enumeration alone cannot carry this, because it bounds the Smart Answering dashboard rather than the gated Smart Ordering portal. What carries it is architectural and positive: orders flow into the POS for processing, the priced menu stays in the POS, and 'modifier' is 0 in all three matching modes across all 125 articles and word-boundary 0 in the 10-K, so there is no modifier object for a modifier-level PMIX to report on. I re-ran every control myself with working positive controls and reproduced the 10-K 'API' 2-vs-124 squashed poison, adding 'POS' (word-boundary 1, stem 109, squashed 202 - it is inside 'Position' and 'Possible'). |
| hardware-os-platforms | unknown (F) — never examined | resolve-to-no | Upheld, after doing the thing the challenge demanded rather than trusting it: I downloaded and looked at all seven attachments myself. The proposer's reading is accurate, with one correction - the seventh image is a decorative crosshair icon, so the document is six photographs, and the HME timer screen it shows is a third party's product. The images name appliances only. I state explicitly why an image-derived reading is admissible here: it is one-directional, since the images could only have refuted the zero, and the zero is actually carried by the vendor's own sentence that no additional hardware is needed. New poison I add: 'iOS' case-insensitively matches the letters inside 'scenarios' in an in-scope article, and 'spec' reads 40 stem hits that are all 'specific'. |
| extensibility-public-api-docs | unknown (F) — never examined | resolve-to-no | Upheld, and materially strengthened rather than rubber-stamped. I re-probed every host with a fabricated-path control beside it, which caught a defect in the proposer's own measurements: www.soundhound.com/developers 'returns 404' at exactly 122,311 bytes, byte-identical to a nonsense path, so it is a soft 404 and establishes nothing by itself. The Wayback CDX check the challenge demanded is what actually settles it - docs.houndify.com/reference was already a 302 in captures from 2022 and 2024, so this reference has been account-gated for years, and developer.soundhound.com / docs.soundhound.com / soundhound.com/developers have zero captures ever. I also found the houndify.com sitemap (30 locs, no docs or reference entry) and its robots.txt disallowing /docs/ and /reference/. I have left the free-developer-account tension in the note verbatim rather than resolving it silently, because it is the one reading under which this cell could move. |
| multi-location-org-hierarchy | unknown (F) — never examined | resolve-to-partial | Upheld. I tested the self-refutation risk the challenge named by walking the claim's conjuncts individually: two of the three hold (organization and assistant are named first-class containers, and two of the four roles are explicitly 'Location-specific'), only the three-level requirement fails, so the partial has genuine content. The role enumeration is closed by the vendor's own words - 'Choose from the four roles' - not by my inference. I add a boundary warning to the note: this list is closed over roles and container types only and must never be re-cited as a bound on permissions, which is the exact mistake recorded against this vendor in an earlier session. I opened all three 'regional' hits; all poison, and one of them is a workaround recommendation that positively evidences the missing tier. |
Sources
Every URL this record cites. 21 in total.
- https://www.soundhound.com/industries/restaurants
- https://www.soundhound.com/use-cases/drive-thru
- https://www.houndify.com/terms
- https://support.soundhound.com/hc/en-us
- https://support.soundhound.com/hc/en-us/articles/23680310417811-Do-I-have-to-create-a-separate-menu-for-voice-ordering
- https://support.soundhound.com/hc/en-us/articles/23680243280531-What-happens-if-I-make-changes-to-my-menu
- https://support.soundhound.com/hc/en-us/articles/53020109939987-Account-Payment-Availability
- https://support.soundhound.com/hc/en-us/articles/23680557565843-How-do-my-customers-pay
- https://support.soundhound.com/hc/en-us/articles/23188749367187-How-do-I-manage-my-account-and-make-updates-to-my-voice-assistant
- https://support.soundhound.com/hc/en-us/articles/53052980420115-Placing-Changing-and-Canceling-Your-Order
- https://support.soundhound.com/hc/en-us/articles/53053017234963-Pickup-and-Tracking
- https://support.soundhound.com/hc/en-us/articles/23435230960659-FAQs-and-Support
- https://www.soundhound.com/use-cases/employee-assist
- https://www.soundhound.com/use-cases/outbound
- https://www.soundhound.com/partners
- https://support.soundhound.com/hc/en-us/articles/23680715492755-Does-the-voice-assistant-integrate-with-my-POS
- https://support.soundhound.com/hc/en-us/articles/23680722879507-Do-I-need-to-purchase-any-hardware-to-start-using-SoundHound-for-Restaurants
- https://support.soundhound.com/hc/en-us/articles/23680596751763-How-are-disputes-handled
- https://support.soundhound.com/hc/en-us/articles/39311726333075-Roles-and-Permissions-in-SoundHound-AI-Smart-Answering
- https://support.soundhound.com/hc/en-us/articles/24543816821395-How-do-I-cancel-my-account
- https://support.soundhound.com/hc/en-us/articles/23171551042579-Smart-Answering-eGuide-Part-1-Getting-Started