Vendors / QSR & drive-thru
ConverseNow
ConverseNow Technologies, Inc.
Voice AI that answers restaurant phone and drive-thru orders and injects the completed order into the incumbent QSR POS. It is not a POS.
dossier live
- Claims in scope
- 182
- Scored
- 182
- Assessed
- 143
- Unknown
- 39
- Not applicable
- 132
- Values challenged
- 61
Identity
- Owner
- ConverseNow Technologies, Inc.
- Founded
- 2018, Austin, Texas. Founders Vinay Shukla (CEO) and Rahul Aggarwal (Chief Product Officer), who previously built Endeavor Software Technologies together and sold it to Genpact in 2016 — https://conversenow.ai/about.html (retrieved 2026-08-02)
- Scale
- 2,000+ restaurants at the time of the Valyant AI acquisition (July 2024). The vendor's own About page claims coverage of '40+ states'; Deliverect's integration listing shows the product live in five countries — Australia, Canada, Mexico, the United Kingdom and the United States (retrieved 2026-08-02). Vendor-claimed volume metrics, claim-level only: 2,000,000+ conversations per month and 83,000+ labor hours repurposed per month (homepage); 1M+ calls since the May 2025 release, 4.55/5 guest satisfaction, 95% drive-thru non-intervention rate and 90%+ order accuracy (platform-updates page). Current location count, headcount and ARR are not disclosed. Total disclosed venture funding is reported at roughly $29M across three rounds by private-market aggregators; treat as unverified.
- Who it is for
- Multi-unit pizza and QSR chains — enterprise and franchise brands running Aloha, Brink, Qu, Xpient, Focus or Olo, deploying across dozens to thousands of stores. Named brands in press coverage: Domino's, Wingstop, Jet's Pizza, Denny's, Fazoli's, Hardee's/Carl's Jr., Blake's Lotaburger. Not an independent-single-store product: there is no self-serve signup, no published price and no trial — every path on the site ends at 'Book a Consultation'.
- Site
- https://conversenow.ai/
Lineage
- 2018 — founded: ConverseNow founded in Austin, Texas by Vinay Shukla and Rahul Aggarwal to build AI voice ordering for restaurants. Venture-backed; investors named on its own About page are Craft Ventures, Enlightened Hospitality Investments, 2048 Ventures, Bridge Investments, Clutch, Knoll Ventures, Live Oak Ventures, Moneta Ventures and Tensility.
- 2024-07-09 — acquired: ConverseNow acquired Valyant AI, the drive-thru voice AI vendor behind the 'Holly' assistant, combining the leading phone-order and drive-thru voice players and giving ConverseNow its drive-thru lane capability.
Pricing
transparency: quote-only · unit: unknown · processor lock-in: no
- Software
- quote-only. Terms of Use section 5 states ConverseNow 'charges you a subscription fee for Services in the amount set forth in the order form or invoice', billed 'monthly, quarterly or annual', with payment due in 30 days and 1.5%-per-month interest on late amounts. No dollar figure appears anywhere on the site and the sitemap contains no pricing page. A $299/month 'Standard Plan' figure circulates via competitor comparison pages and SEO aggregators with no vendor attribution; it is not recorded here.
- Card processing
- not applicable — ConverseNow is not a payment processor and publishes no card rates. Its end-user terms state 'Pricing, payment processing, taxes, and receipts are handled by the Restaurant or its payment processors.'
- Contract
- unknown — the published Terms of Use has no Term section; billing frequency (monthly, quarterly or annual) is stated but the commitment lives in the unpublished order form
- Early termination
- unknown — the published Terms of Use contains no termination, early-exit or liquidated-damages clause in either direction
- Hardware
- none — ConverseNow sells no hardware SKU
API posture
public API: partner-gated
- Cost to integrate
- unknown — no published partner program, certification fee or revenue-share terms. Access runs through 'Book a Consultation'.
- Webhooks
- unknown — no webhook contract, event catalogue, retry policy or signing model is published
- Data export on exit
- unknown — no documented bulk export of call transcripts, order records or guest data. The privacy policy (https://conversenow.ai/privacy-policy.html) routes individual data-subject requests through the 'Parent Restaurant Organization' with 30-day access and 45-90 day deletion windows, and states general personal data is retained for the period necessary for service execution up to 1 year. No operator-facing self-serve export is documented. Sharpened on 2026-09-09 — the Terms of Use is not merely silent on post-termination data return, it carves out operator data by reference to a definition it never supplies — the string 'Customer Data' appears exactly ONCE in the whole document, in the phrase '(defined below)', and the definition never arrives; none of its thirteen numbered sections is a term, termination, data-return or export section; and the end-user terms' survival enumeration at section 18 lists ownership, disclaimers, limitations, indemnity, dispute resolution and privacy, with no data-return obligation among them. That settles the absence of a contractual export RIGHT (commercial-post-termination-export-window is now `no`) but deliberately NOT the absence of an export FEATURE — a Terms of Use is not a feature enumeration, so commercial-data-export-self-serve and extensibility-data-portability-exit stay `unknown`.
- Notes
- Direction of integration is inbound-to-POS: ConverseNow writes orders into Aloha/Brink/Qu/Xpient/Focus/Olo and, since April 2026, into Deliverect's order-management platform, rather than exposing a POS of its own. The 'Order Injection API' is marketed as the inverse — driving ConverseNow's ordering engine from a customer's own mobile app or kiosk. No specification, auth model, versioning policy, rate limit or changelog is published for either direction. The subdomain picture was re-probed 2026-09-09 and the earlier 'do not resolve' was wrong: api., developer. and developers.conversenow.ai are NXDOMAIN, but docs.conversenow.ai (A 34.123.64.3) and app.conversenow.ai (A 142.93.23.88) DO resolve and drop every TCP connect on 80, 443, 8080 and 22, while a fabricated control subdomain returns ENODATA — the hosts exist and are firewalled. Wayback shows docs.conversenow.ai answering in 2023 with a 302 into conversenow.auth0.com/authorize behind an oauth2_proxy CSRF cookie, so ConverseNow runs a private SSO-gated documentation host and an operator application host, neither ever anonymously readable. That surface is UNMEASURED, NOT ABSENT: no absence in this record may be bounded to it, and two verdicts were overturned back to unknown on 2026-09-09 for exactly that reason. It does not rescue a publication claim, since documentation behind SSO is not published. status.conversenow.ai resolves and serves, exposing 'API Server' and 'POS Server' as monitored components — so the API exists, it is simply not documented publicly.
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
Grade corrected from E to C by the 2026-08-02 adversarial pass — the cited URL is the vendor's own feature page, not third-party reporting — and the stale 2026-08-01 retrieval date refreshed to match the surrounding scope-absence sweep. Value unchanged and correct: ConverseNow's complete published product set is four voice/API products, there is no terminal, no table entity and no seating model of any kind, so a graphical floor-plan editor is absent by product scope. https://conversenow.ai/products.html · retrieved 2026-08-02 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no terminal, handheld or order-entry UI of any kind — orders are captured by voice and written into the integrated POS (Aloha, Brink, Qu, Xpient, Focus, Fiserv, Olo) — so this order-entry capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no terminal, handheld or order-entry UI of any kind — orders are captured by voice and written into the integrated POS (Aloha, Brink, Qu, Xpient, Focus, Fiserv, Olo) — so this order-entry capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld. The claim asks whether terminals and handhelds keep creating orders with the internet down and whether the vendor publishes offline scope; ConverseNow has no terminal, so the first half has no subject and the second half is a measurable disclosure zero. products.html enumerates the complete product set as four items — "Phone Order AI", "Drive-Thru Automation", "SMS AI Conversations" and "Order Injection API" — and the last of those is explicitly a way to drive ConverseNow FROM someone else's device: "Seamlessly integrate AI-powered ordering into your mobile apps and kiosks." No hardware SKU, order screen or handheld appears anywhere on the live surface. Across the frozen corpus the words offline, outage, fallback, failover, store-and-forward and degraded occur ZERO times, and the six apparent hits for edge are all the string inside "acknowledge" — opened and discarded, as were the two apparent API hits in about.html, which are the string inside "rapid". The single terminal hit is the privacy policy's "mobile device identifiers" boilerplate, not a product. Present-controls in the same run, tokenised on word boundaries: voice 57, order 84 — the matcher fires. (A loose-stem run read pos 41; on word boundaries pos occurs ONCE, in insights.html's "and your POS system", so the stem figure was reader noise and pos is not usable as a control here.) Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/products.html · retrieved 2026-09-09
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
The evidence is the bullet "Kiosk compatibility" under the Order Injection API. That supports the API/channel cells, not a first-party kiosk. ConverseNow ships no kiosk software or hardware SKU and publishes no ADA/VPAT or unattended-EMV detail. Scoring partial on a *first-party* cell from a compatibility bullet is exactly the marketing-as-capability error. || 326th: MERGE HOLD (proposed no/B, held unknown): ConverseNow is voice-AI middleware with no kiosk product at all; the 325th rule holds a module the product lacks entirely at unknown rather than no. PROPOSAL AS WRITTEN: 326th, MOVED unknown -> no, and the grade rises because two signed-contract documents now corroborate the product page. CLAIM: 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. VERDICT: no. EVIDENCE: ConverseNow's kiosk story is explicitly someone else's kiosk. products.html lists the Order Injection API as 'Seamlessly integrate AI-powered ordering into YOUR mobile apps and kiosks', with the bullets 'Mobile app integration / Kiosk compatibility / Real-time ordering / Custom workflows'; the Terms and Conditions for Restaurants scope the Platform to 'restaurant food-ordering channels such as phone calls, drive-thru (/in) and digital kiosk'; and the End-User Terms of 27 May 2026 describe 'a voice-AI platform designed to assist restaurants in automating and personalizing customer orders across channels including telephone, drive-thru, and self-service kiosks', i.e. ConverseNow supplies the voice layer into a kiosk the restaurant already owns. The published product set remains exactly four (Phone Order AI, Drive-Thru Automation, SMS AI Conversations, Order Injection API); no kiosk hardware, kiosk app, kiosk build or accessibility statement exists - 'ADA', 'WCAG', 'accessibility' and 'conformance' score 0 word-boundary hits in the whole publisher corpus, and 'kiosk' scores 0 in the 7.77 MB dashboard bundle. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. || 333rd: 333rd, NEW SURFACE: the vendor's own webinar series, 9 ConverseNow YouTube videos no prior pass had transcribed (playlist 'Webinars' PLB89GDFAHoaSntxMMHUKUasD6R5YLy9rO: fhuwRxxq9H0, UqHvzHh77fI, t4BQb06Pz4A, BdDdFiotXlI, cJIB8JBgo_w, hKvxHukDQ20, PrKBUyoPiw4, plus 9NK4V15KGrk 'Voice Intelligence Overview' and testimonial XIpl7sCNfRI; ~7.3 h, 452 KB of caption text, fetched via youtube-transcript-api, saved under .cache/q333/conversenow/a/cap/). The channel has 2 public uploads and 3 playlists (21 videos); the 10 live-call clips and 2 uploads then hit YouTube IpBlocked/429 on both the transcript API and yt-dlp timedtext, so their audio stays unread. Vendor webinar = grade C. Plus a second new surface for this cell: the acquired Valyant AI kiosk page (Wayback, valyant.ai/kiosk.html, 2022 capture, fetched by slug b this session to .cache/q333/conversenow/b/vlw_kiosk.html). It describes a VOICE LAYER on someone else's kiosk: 'Upgrade your restaurant kiosks with microphone and speaker-enabled hardware ... the integration process will work through a single application-programming-interface (API) call between your software provider and Valyant's proprietary conversational AI software.' So the kiosk, its screen and its menu render belong to the restaurant's kiosk vendor; no first-party kiosk, no ADA/VPAT. 0 hits for 'kiosk' in the 9 webinar transcripts. Retired Valyant-branded surface. Held unknown under the no-module rule (the 326th hold). Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown (no ConverseNow module; merge rule: no module = hold unknown). (1) USPTO full-text patent census of the assignee: Google Patents xhr query returns 9 ConverseNowAI + 5 Valyant AI filings (US11704753B2/US11354760 'Order post', US11355122, US11355120, US11348160, US11810550, US11514894, US11574345, US12340358, US20220270164A1, US20220318860A1; Valyant US10592706B2, US11023955B1, US20230206919A1); 12 image-only PDFs from image-ppubs.uspto.gov + Justia full text for 11704753/11354760/11355122 (the rest 403). The specs model 'the menu of the restaurant' as an ontology the dish classifier reads, with the cart posted 'using an applications programming interface (API) of the POS system of the restaurant' -- the menu master is the host POS; 'modifier', 'out of stock', 'daypart', 'catering', 'future' = 0 in the text read. A patent is an invention disclosure, not a shipped feature: corroboration only. (2) Deliverect's integration page /en-us/integrations/converse-now (found via its sitemap): ConverseNow is a Deliverect order CHANNEL ('send all incoming orders straight to your POS'), marketing only. (3) Olo partner page: marketing prose only. (4) Two previously unread vendor live-call clips transcribed locally (yt-dlp audio + faster-whisper base.en): 51a4AYfd_FE, W15KtwxEWlM; the other 8 live-call clips downloaded to .cache/q334/conversenow/a/aud but not transcribed (CPU contention, ~11 min per audio minute). Retrieved 2026-09-18. adversarially verified
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
Downgraded from partial by the 2026-08-02 adversarial pass. The claim enumerates three drive-thru workflow elements — order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment — and none is evidenced. The Drive-Thru Automation bullets are "Reduced wait times", "Increased throughput", "Track order accuracy" and "Real-time analytics"; the December 2024 update adds a non-intervention rate and order confirmation boards. Nothing touches lane structure or vehicle sequencing, and ConverseNow ships no lane controller or timer. The existence of a drive-thru voice product is credited at digital-drivethru-ai and order-capture-voice-ai; it does not carry this cell. || 325th: 325th, TWO NEW SURFACES, still unknown; neither carries lane sequencing. (1) The FIRST piece of crew-facing DOCUMENTATION this record has ever held: 'Voice AI FAQ' (retired page, recovered from Wayback at capture 20250422170054 of conversenow.ai/voice-ai-frequently-asked-questions/). It documents the drive-thru operating model verbatim: 'AI will be live during peak hours when the store is at its busiest. Between the hours of AI operation, crew members should NOT press their headset buttons and let the AI (and our agents) complete the order'; override is 'Simply press the talk or audio button on your headset and begin speaking. The system will automatically mute the AI and let you handle things from there'; 'once installed, the drive-thru AI device will always be turned on during the designated AI operation hours selected by your store's management ... when a car pulls up to the drive-thru speaker, the virtual assistant will automatically greet the guest'. (2) The shipped dashboard carries per-session `drive_thru_mode` ('Drive Thru Mode') and `drive_thru_status` ('Drive Thru Status') columns, which show a mode concept exists but do not enumerate its values. Neither surface mentions order-point/pay-window/pickup-window separation, tandem-lane or order sequencing, or pull-forward/parking-spot assignment - the three things the claim asks for and which belong to the base station and POS rather than the voice layer. Also re-derived today: conversenow.ai is no longer the WordPress/Elementor site the old notes describe. It is now a static GitHub Pages site (Server: GitHub.com, Last-Modified 2026-05-29) whose robots.txt allows all and whose sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html), plus terms-and-conditions.html and end-user-terms.html linked from the footer: 8 pages total, and every other path returns the same 1,910-byte 404 (control: /zzz-nonsense.html). The retired WordPress corpus was enumerated from Wayback CDX (1,354 captures; ~60 distinct non-asset HTML paths) and several of those retired pages have never been read by this record - see the rows in this file. Retrieved 2026-09-17. || 333rd: 333rd, NEW SURFACE: the vendor's own webinar series, 9 ConverseNow YouTube videos no prior pass had transcribed (playlist 'Webinars' PLB89GDFAHoaSntxMMHUKUasD6R5YLy9rO: fhuwRxxq9H0, UqHvzHh77fI, t4BQb06Pz4A, BdDdFiotXlI, cJIB8JBgo_w, hKvxHukDQ20, PrKBUyoPiw4, plus 9NK4V15KGrk 'Voice Intelligence Overview' and testimonial XIpl7sCNfRI; ~7.3 h, 452 KB of caption text, fetched via youtube-transcript-api, saved under .cache/q333/conversenow/a/cap/). The channel has 2 public uploads and 3 playlists (21 videos); the 10 live-call clips and 2 uploads then hit YouTube IpBlocked/429 on both the transcript API and yt-dlp timedtext, so their audio stays unread. Vendor webinar = grade C. Plus the acquired Valyant drive-thru page (Wayback 2022, .cache/q333/conversenow/b/vlw_drive-thru.html) and 1080p frames of the vendor explainer w37qmNvBHYM (39 scene frames read). Valyant: 'NX-1A hardware integrates directly with your existing headset systems, including the HME ION and EOS platforms and 3M / Par XT1 and G5 ... we integrate directly with your point-of-sale platforms including Aloha, Micros, Brink, Revel ... insert orders in under one second'. That is the ORDER POINT only: the agent speaks at the speaker post and injects the order; nothing on pay/pickup window separation, tandem-lane sequencing or pull-forward. The explainer frames show a drive-thru car, a speaker post and a POS order panel, no lane or window model. 'lane' = 0 in the 9 webinar transcripts. Held unknown (lane structure is the host POS/timer system's). Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown (no ConverseNow module; merge rule: no module = hold unknown). (1) USPTO full-text patent census of the assignee: Google Patents xhr query returns 9 ConverseNowAI + 5 Valyant AI filings (US11704753B2/US11354760 'Order post', US11355122, US11355120, US11348160, US11810550, US11514894, US11574345, US12340358, US20220270164A1, US20220318860A1; Valyant US10592706B2, US11023955B1, US20230206919A1); 12 image-only PDFs from image-ppubs.uspto.gov + Justia full text for 11704753/11354760/11355122 (the rest 403). The specs model 'the menu of the restaurant' as an ontology the dish classifier reads, with the cart posted 'using an applications programming interface (API) of the POS system of the restaurant' -- the menu master is the host POS; 'modifier', 'out of stock', 'daypart', 'catering', 'future' = 0 in the text read. A patent is an invention disclosure, not a shipped feature: corroboration only. (2) Deliverect's integration page /en-us/integrations/converse-now (found via its sitemap): ConverseNow is a Deliverect order CHANNEL ('send all incoming orders straight to your POS'), marketing only. (3) Olo partner page: marketing prose only. (4) Two previously unread vendor live-call clips transcribed locally (yt-dlp audio + faster-whisper base.en): 51a4AYfd_FE, W15KtwxEWlM; the other 8 live-call clips downloaded to .cache/q334/conversenow/a/aud but not transcribed (CPU contention, ~11 min per audio minute). Cell-specific: patent US11704753B2/US11354760 claims 'order posts' deployed in drive-through lanes/parking lot for parallel order taking (multiple vehicles ordering at once) -- an invention disclosure, no shipped product, no pay/pickup-window separation or pull-forward; 'Order post' appears on no conversenow.ai page. Retrieved 2026-09-18. adversarially verified
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
CLAIM: captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders. VERDICT: partial (moved from unknown). SHORTFALL: the timers are of the AI ORDER-TAKING SESSION plus one vehicle event, not the claim's order/pay-window/pickup-window triple, and ConverseNow reports no per-window or total-lane time. EVIDENCE (the vendor's own shipped dashboard, not marketing): the Olive AI dashboard ships a closed Drive Thru Sessions table, `var driveThruHeadCells` = Franchise ID, Store ID, `Start Time` (call_start_time), `End Time` (call_end_time), `AHT (sec)` (average handle time, numeric and sortable), Friendliness, Policy Adherence Rate, `Cart Value` (order_total), Difficulty, Improvements, Strengths, Dishes, `Tracker ID`, Recording - i.e. the timing is per individual session and is joined to an order value and a tracker id. The session record it maps carries more time fields than the table shows: `call_start_time`, `vehicle_departure_time`, `drive_thru_mode`, `drive_thru_status`, `average_check`, `dashboard_link`, `transcript_url`, and the grid's column set DRIVE_THRU_SESSIONS_CSV_COLUMN_ORDER = [franchise_id, store_id, call_start_time, call_end_time, aht, friendly_score, policy_adherence_rate, order_total, understanding_difficulty, improvements, strengths, dishes, tracker_id, dashboard_link, transcript_url, audio_player_url] is a CSV download (onDownloadFull), so the per-order timings are exportable. A sibling table exists for phone (phoneHeadCells: Call Date, Start Time, `AHT (Secs)`, Cart Value, Call Category, Dishes) and for FrontDesk AI (call_start_time, call_end_time, `Avg Call Duration`, Escalation Status, SMS Sent), and the app's own label for the drive-thru data source is `Drive Thru` (voice-intel-dt) versus `Phone`. BOUND: the Olive AI customer dashboard is now a CLOSED corpus, not a sample. Its entry bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, re-fetched by me today, 7,770,702 bytes) opens with a Vite loader table, `__vite__mapDeps` d=["assets/forecastRealData-CA3-729w.js","assets/_sentry-release-injection-file-Bv3kP-4K.js"], and the ONLY call site in the file is __vite__mapDeps([0,1]) - so the app is 3 files, the loader table is exhausted in one round with 0 misses. Soft-200 control: /assets/index-ZZZNOPE.js returns 200 with 446 bytes of SPA shell, against 7.77 MB of JavaScript for the real asset, and the hash DXIYe81a is the one the live index.html references. Production JS the vendor does not publish as documentation = grade B. CAUTION for the next pass: Olive is a general analytics platform whose app registry also routes /apps/game-insights, /apps/game-services, /apps/finance-dashboard and /apps/finance-analytics, so not every module in it is the restaurant voice product. Retrieved 2026-09-17. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-17 adversarially verified
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
Upheld by the 2026-08-02 adversarial pass against the differentiator-yes bar. The vendor's platform-update page documents the December 2024 next-generation GenAI launch "across phone, text, drive-through, and kiosks for all served brands" with "POS system integration", a 95% non-intervention rate defined as orders handled entirely by AI without live agent assistance, over 90% order accuracy and sub-second response; the May 2025 entry reports 4.55/5 satisfaction across more than a million calls and a 25% reduction in order time. A first-party voice agent whose completed orders are written into the integrated POS (Aloha, Brink, Qu, Xpient, Focus, Fiserv, Olo, ItsaCheckmate) — the claim exactly. https://conversenow.ai/insights.html · retrieved 2026-08-02 adversarially verified
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this order-capture behaviour. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 327th: 327th, NEW SURFACE, still unknown. Checked individually against the censused Olive analytics app rather than the shared 2026-08-02 boilerplate. The app has `/peak-load`, `/server-scaling`, `/servers/utilization` and `/provider-rebalancing`, and 17 `capacity` hits - all of which are INFRASTRUCTURE capacity for the voice/LLM providers, not per-channel order capacity per time slot; `throttl` scores 0 in every corpus file. No quote-time or slot-limit concept exists anywhere in ConverseNow's published surface. Held unknown, not no: ConverseNow does not own the order queue it feeds. Retrieved 2026-09-18. || 333rd: 333rd, NEW SURFACE: the vendor's own webinar series, 9 ConverseNow YouTube videos no prior pass had transcribed (playlist 'Webinars' PLB89GDFAHoaSntxMMHUKUasD6R5YLy9rO: fhuwRxxq9H0, UqHvzHh77fI, t4BQb06Pz4A, BdDdFiotXlI, cJIB8JBgo_w, hKvxHukDQ20, PrKBUyoPiw4, plus 9NK4V15KGrk 'Voice Intelligence Overview' and testimonial XIpl7sCNfRI; ~7.3 h, 452 KB of caption text, fetched via youtube-transcript-api, saved under .cache/q333/conversenow/a/cap/). The channel has 2 public uploads and 3 playlists (21 videos); the 10 live-call clips and 2 uploads then hit YouTube IpBlocked/429 on both the transcript API and yt-dlp timedtext, so their audio stays unread. Vendor webinar = grade C. Still unknown; the webinars show ConverseNow RELAYS the host platform's quote time and computes none. cJIB8JBgo_w at 32:31 (live Domino's demo): 'order quote time again where you're pulling every all that information off from your dominos.com site so whatever it's reflecting there that's what we will communicate'. POISON: 'throttling' occurs once, fhuwRxxq9H0 25:44, 'there's no throttling to the call volume' (call concurrency, not kitchen capacity). No capacity slot or quote-time extension of ConverseNow's own. Held unknown (no module). Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown (no ConverseNow module; merge rule: no module = hold unknown). (1) USPTO full-text patent census of the assignee: Google Patents xhr query returns 9 ConverseNowAI + 5 Valyant AI filings (US11704753B2/US11354760 'Order post', US11355122, US11355120, US11348160, US11810550, US11514894, US11574345, US12340358, US20220270164A1, US20220318860A1; Valyant US10592706B2, US11023955B1, US20230206919A1); 12 image-only PDFs from image-ppubs.uspto.gov + Justia full text for 11704753/11354760/11355122 (the rest 403). The specs model 'the menu of the restaurant' as an ontology the dish classifier reads, with the cart posted 'using an applications programming interface (API) of the POS system of the restaurant' -- the menu master is the host POS; 'modifier', 'out of stock', 'daypart', 'catering', 'future' = 0 in the text read. A patent is an invention disclosure, not a shipped feature: corroboration only. (2) Deliverect's integration page /en-us/integrations/converse-now (found via its sitemap): ConverseNow is a Deliverect order CHANNEL ('send all incoming orders straight to your POS'), marketing only. (3) Olo partner page: marketing prose only. (4) Two previously unread vendor live-call clips transcribed locally (yt-dlp audio + faster-whisper base.en): 51a4AYfd_FE, W15KtwxEWlM; the other 8 live-call clips downloaded to .cache/q334/conversenow/a/aud but not transcribed (CPU contention, ~11 min per audio minute). Retrieved 2026-09-18. adversarially verified
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this order-capture behaviour. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 331st: 331st, per-cell re-grep, still unknown. Both live products.html demo transcripts quote only ASAP times ('ready in about 10 to 20 minutes', '9 to 19 minutes'); the 7.77 MB Olive bundle scores 0 for future order, scheduled order, order ahead, advance order, pre-order, promise time; 12 retired WordPress pages recovered this pass (technology, restaurant-phone-orders, restaurant-drive-thru, restaurant-management, customer-retention-strategies, Papa Gino's Fast Track, etc.) have no scheduling vocabulary ('future' hits are 'future of restaurants' slogans; 'schedule' is 'Schedule a demo'). certspotter for conversenow.ai (16 names) adds no host crt.sh had not listed. ConverseNow injects into the restaurant's POS, which owns fire time. Retrieved 2026-09-18. || 332nd: 332nd, NEW SURFACE (the vendor's own YouTube channel, ConverseNow, UCK67Cf6lhLUmQxT1XH2A0QQ), still unknown. The retired sample-call page (Wayback copy of conversenow.ai/voice-ai-in-action/, already on disk at .cache/q325/conversenow/) embeds one YouTube video per call. The clip titled "Fazoli's - user request advance order" sits under that page's 'Agent Escalation' heading, not under 'Phone AI' or 'Drive-thru AI'. Its video W15KtwxEWlM is titled 'Fazoli's Live Call - Pickup - Becky - User Requests Advance Order' (published 2022-06-03, 214 s, description 'Example of an actual ConverseNow phone call.'). It belongs to the vendor playlist PLB89GDFAHoaQ2BPhIeqqvE4LUrQdNQfXB, titled 'Live Calls - Examples of AI Escalating to Call Center Agent'. That playlist has 10 videos, and the others are transfers to the store or to an agent. So in 2022 the vendor itself showed an advance-order request as a case where the AI hands the call to a human agent, not one it takes on its own. It does not settle the claim. The clip is from 2022 and a retired generation, so it cannot carry a `no`. What the human agent did with the order, and whether the POS got it as a future-dated order, is only in the audio. The auto-generated caption track is listed, but the timedtext endpoint returned 0 bytes for all 8 clips tried, and there is no local speech-to-text tool. No per-channel lead time is stated anywhere. Retrieved 2026-09-18. || 333rd: 333rd, NEW SURFACE: the vendor's own webinar series, 9 ConverseNow YouTube videos no prior pass had transcribed (playlist 'Webinars' PLB89GDFAHoaSntxMMHUKUasD6R5YLy9rO: fhuwRxxq9H0, UqHvzHh77fI, t4BQb06Pz4A, BdDdFiotXlI, cJIB8JBgo_w, hKvxHukDQ20, PrKBUyoPiw4, plus 9NK4V15KGrk 'Voice Intelligence Overview' and testimonial XIpl7sCNfRI; ~7.3 h, 452 KB of caption text, fetched via youtube-transcript-api, saved under .cache/q333/conversenow/a/cap/). The channel has 2 public uploads and 3 playlists (21 videos); the 10 live-call clips and 2 uploads then hit YouTube IpBlocked/429 on both the transcript API and yt-dlp timedtext, so their audio stays unread. Vendor webinar = grade C. Still unknown. Tokenised controls over the 9 transcripts: 'advance order', 'future order', 'order ahead', 'pre-order', 'preorder', 'schedule(d) order' = 0; the only near hits are poison: 'scheduled delivery option' (t4BQb06Pz4A 50:19) is Looker REPORT e-mail scheduling, 'tomorrow'/'later today' (BdDdFiotXlI, t4BQb06Pz4A) are webinar housekeeping. The 2022 clip W15KtwxEWlM ('User Requests Advance Order', filed by the vendor under AI escalation to a human agent) was downloaded at 1080p: its video track is ONE static title card (Fazoli's / ConverseNow logos, 1 scene over 214 s), so the evidence is audio only, and its captions were refused (429) again. No per-channel lead time or fire-time injection anywhere. Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown (no ConverseNow module; merge rule: no module = hold unknown). (1) USPTO full-text patent census of the assignee: Google Patents xhr query returns 9 ConverseNowAI + 5 Valyant AI filings (US11704753B2/US11354760 'Order post', US11355122, US11355120, US11348160, US11810550, US11514894, US11574345, US12340358, US20220270164A1, US20220318860A1; Valyant US10592706B2, US11023955B1, US20230206919A1); 12 image-only PDFs from image-ppubs.uspto.gov + Justia full text for 11704753/11354760/11355122 (the rest 403). The specs model 'the menu of the restaurant' as an ontology the dish classifier reads, with the cart posted 'using an applications programming interface (API) of the POS system of the restaurant' -- the menu master is the host POS; 'modifier', 'out of stock', 'daypart', 'catering', 'future' = 0 in the text read. A patent is an invention disclosure, not a shipped feature: corroboration only. (2) Deliverect's integration page /en-us/integrations/converse-now (found via its sitemap): ConverseNow is a Deliverect order CHANNEL ('send all incoming orders straight to your POS'), marketing only. (3) Olo partner page: marketing prose only. (4) Two previously unread vendor live-call clips transcribed locally (yt-dlp audio + faster-whisper base.en): 51a4AYfd_FE, W15KtwxEWlM; the other 8 live-call clips downloaded to .cache/q334/conversenow/a/aud but not transcribed (CPU contention, ~11 min per audio minute). Cell-specific: the 2022 clip W15KtwxEWlM ('User Requests Advance Order', filed by the vendor under AI escalation) is now transcribed: guest at 24s 'I would like to order 75 breadsticks to pick up at 5 p.m.'; the AI answers only with a size prompt ('What size for your breadsticks'), the guest asks for a representative at 47s, and a HUMAN agent takes it ('this will be a pick up order by 5 p.m. right?', 146s, total $38.52). So the time-of-pickup order went to a person, not the AI; no per-channel lead time, no fire-time injection. 2022 retired generation: cannot carry a `no`. Retrieved 2026-09-18. adversarially verified
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this order-capture behaviour. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 328th: 328th, per-cell re-grep, still unknown. 'catering' scores 0 in vendor prose across the entire 48-file corpus (the single hit is a prior pass's own control list inside cn-ctx.txt, excluded); deposit 0, 'balance due' 0, 'lead time' 0. POISON: 'quote' scores 140 but every hit is either d3/SQL string-quoting internals or the 2021 Deal Registration Terms' sales-quote prose, and 'event' scores 249, all DOM/analytics events plus the retired blog's conference tag - neither is a catering event. ConverseNow owns no order queue (it injects into the restaurant's POS), so there is no separate catering queue for the claim to describe. Held unknown (module absent). Retrieved 2026-09-18. || 333rd: 333rd, NEW SURFACE: the vendor's own webinar series, 9 ConverseNow YouTube videos no prior pass had transcribed (playlist 'Webinars' PLB89GDFAHoaSntxMMHUKUasD6R5YLy9rO: fhuwRxxq9H0, UqHvzHh77fI, t4BQb06Pz4A, BdDdFiotXlI, cJIB8JBgo_w, hKvxHukDQ20, PrKBUyoPiw4, plus 9NK4V15KGrk 'Voice Intelligence Overview' and testimonial XIpl7sCNfRI; ~7.3 h, 452 KB of caption text, fetched via youtube-transcript-api, saved under .cache/q333/conversenow/a/cap/). The channel has 2 public uploads and 3 playlists (21 videos); the 10 live-call clips and 2 uploads then hit YouTube IpBlocked/429 on both the transcript API and yt-dlp timedtext, so their audio stays unread. Vendor webinar = grade C. Still unknown, and two webinars now say how catering reaches the voice agent: it is ROUTED AWAY. PrKBUyoPiw4 at 42:40: 'with like non-profits or really large catering orders right we could customize the ivr to you know funnel those calls maybe directly to a catering number their catering manager ... or the store'. hKvxHukDQ20 at 40:29-40:51: 'from a catering perspective ... we could prompt ... based on the phone number ... specific questions ... two if you prefer your team just handle those calls ... we can adjust our ivr to have an option where we just automatically route those calls you know directly to the site'. No quote, deposit, balance-due or event schedule anywhere in ~7 h. Held unknown under the no-module rule (ConverseNow has no catering module; the catering flow belongs to whatever the store routes to). Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown (no ConverseNow module; merge rule: no module = hold unknown). (1) USPTO full-text patent census of the assignee: Google Patents xhr query returns 9 ConverseNowAI + 5 Valyant AI filings (US11704753B2/US11354760 'Order post', US11355122, US11355120, US11348160, US11810550, US11514894, US11574345, US12340358, US20220270164A1, US20220318860A1; Valyant US10592706B2, US11023955B1, US20230206919A1); 12 image-only PDFs from image-ppubs.uspto.gov + Justia full text for 11704753/11354760/11355122 (the rest 403). The specs model 'the menu of the restaurant' as an ontology the dish classifier reads, with the cart posted 'using an applications programming interface (API) of the POS system of the restaurant' -- the menu master is the host POS; 'modifier', 'out of stock', 'daypart', 'catering', 'future' = 0 in the text read. A patent is an invention disclosure, not a shipped feature: corroboration only. (2) Deliverect's integration page /en-us/integrations/converse-now (found via its sitemap): ConverseNow is a Deliverect order CHANNEL ('send all incoming orders straight to your POS'), marketing only. (3) Olo partner page: marketing prose only. (4) Two previously unread vendor live-call clips transcribed locally (yt-dlp audio + faster-whisper base.en): 51a4AYfd_FE, W15KtwxEWlM; the other 8 live-call clips downloaded to .cache/q334/conversenow/a/aud but not transcribed (CPU contention, ~11 min per audio minute). Cell-specific: the same W15KtwxEWlM call (75 breadsticks for 5 p.m.) is a large order handled by a human escalation agent, consistent with the 333rd finding that catering calls are routed away from the AI. Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no terminal, handheld or order-entry UI of any kind — orders are captured by voice and written into the integrated POS (Aloha, Brink, Qu, Xpient, Focus, Fiserv, Olo) — so this order-entry capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no terminal, handheld or order-entry UI of any kind — orders are captured by voice and written into the integrated POS (Aloha, Brink, Qu, Xpient, Focus, Fiserv, Olo) — so this order-entry capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Menu, modifiers & pricing engine
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
331st, MOVED unknown -> partial. CLAIM: guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels. VERDICT: partial - account, saved profile/favourites and reorder of a previous order are published; tokenized saved payment is not (the demo flow says pay at the store). EVIDENCE: (1) Privacy Policy (vendor legal, grade B, live 2026-09-18, https://conversenow.ai/privacy-policy.html), 'Account Registration - To submit your order to the restaurant, you may be required to provide ... your first name and last name, email address, postal address, telephone number, and loyalty membership details. You may also provide payment data and profile data to help speed up and facilitate your future orders. Online Orders - You can place an online order for carryout or delivery through a registered account or as a guest'; 'Profile Data. We may collect your interests, favorites, and other profile data'. (2) End-User Terms 6 'User Accounts. If the Service allows or requires you to create an account or profile, you must provide accurate information'. (3) products.html live demo transcripts (vendor marketing, C): 'I see you placed an order with us before. Would you like to go with that again today?'; 'I see we have your usual order saved ... your favorite order is Chicken Alfredo Bread Bowl Pasta ... Would you like to add that again?'; 'Would you like to save this order as your favorite?'. SHORTFALL: the same transcripts end 'you can pay for this order at the store', End-User Terms 8.3 puts payment processing with the Restaurant or its processors, and nothing says a stored card is tokenized - the privacy policy's 'Payment Data ... payment instrument number ... and the security code' is a collection statement, not a saved-wallet feature, and it is in tension with EUT 8.3. WHY THIS IS NOT THE 'NO FIRST-PARTY FLOW' HOLD: the End-User Terms (effective May 27 2026, https://conversenow.ai/end-user-terms.html) define a guest-facing ordering Service of ConverseNow's own: 2.1 'By selecting "I Agree," "Place Order," "Submit," or any similar button at checkout or on a kiosk'; 2.3 'SMS/Text Link Assent. If you receive a text message containing a link to these Terms and proceed with the ordering process'; 5.1 'The Service lets you interact with automated voice assistants and related interfaces to place and manage orders with the Restaurant through phone, drive-through, kiosks, and related communication channels'; and products.html lists 'SMS AI Conversations ... Easy text ordering / Personalized AI memory'. The earlier holds were written before these terms were on disk (325th) or on the payment clause alone (328th). Controls re-run over the 7.77 MB Olive bundle: favorite 0, reorder 0 (the dashboard is analytics; the memory lives in the voice agent). Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
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
Downgraded from partial by the 2026-08-02 adversarial pass. The upsell configuration is real but conversational — "Upsell Logic" by time, order size or guest behavior, with A/B testing — and is credited once, at menu-pricing-upsell-prompts. This claim is scoped to a digital checkout surface presenting suggestions with attach-rate reporting, and ConverseNow operates no such surface: the enumerated product set is four voice/API products, and digital-first-party-web, digital-native-app and digital-qr-table are all scored no on that same enumeration. Absent by product scope, not merely undocumented. https://conversenow.ai/products.html · retrieved 2026-08-02 adversarially verified
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this digital-ordering behaviour. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind.
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
331st, MOVED unknown -> partial. CLAIM: a 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. VERDICT: partial - pickup and delivery in one flow, with a mode-specific ready/delivery time, are published; curbside check-in and dine-in/QR are not. EVIDENCE: Privacy Policy (grade B, https://conversenow.ai/privacy-policy.html): 'Online Orders - You can place an online order for carryout or delivery through a registered account or as a guest. If you place a carryout order, you will need to provide your first name and last name, email address, telephone number, and order information ... If you place an order for delivery, you will also need to provide your postal address.' End-User Terms 8.1: '... discounts, loyalty redemptions, and pickup/delivery times are determined by the Restaurant.' products.html live transcripts (C) open 'Will this order be for pickup or delivery?' and close 'Your order should be ready in about 10 to 20 minutes'; the retired sample-call library (Wayback, already in the record) titles a clip "Domino's - delivery - time estimates". SHORTFALL: over 32 text files (live site + legal, 12 retired WP pages, the Wayback set) curbside and dine-in each score 1, both in retired-blog industry commentary ('used curbside pickup and drive-thrus'; 'eliminating dine-in revenue'), never as a ConverseNow mode, and 0 in the Olive bundle; no arrival check-in or QR table concept exists; mode-specific FEES are not described (fees are 'determined by the Restaurant'). WHY THIS IS NOT THE 'NO FIRST-PARTY FLOW' HOLD: the End-User Terms (effective May 27 2026, https://conversenow.ai/end-user-terms.html) define a guest-facing ordering Service of ConverseNow's own: 2.1 'By selecting "I Agree," "Place Order," "Submit," or any similar button at checkout or on a kiosk'; 2.3 'SMS/Text Link Assent. If you receive a text message containing a link to these Terms and proceed with the ordering process'; 5.1 'The Service lets you interact with automated voice assistants and related interfaces to place and manage orders with the Restaurant through phone, drive-through, kiosks, and related communication channels'; and products.html lists 'SMS AI Conversations ... Easy text ordering / Personalized AI memory'. The earlier holds were written before these terms were on disk (325th) or on the payment clause alone (328th). Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Downgraded from partial by the 2026-08-02 adversarial pass. The claim requires the vendor to ship a self-order kiosk with POS-equivalent menu and modifier logic, an accessibility-compliant UI and unattended EMV. The only kiosk evidence is the bullet "Kiosk compatibility" under the Order Injection API, plus kiosks named as one channel the GenAI voice platform was deployed across — third-party kiosks running ConverseNow's voice layer. ConverseNow ships no kiosk software or hardware SKU and publishes no ADA/VPAT or unattended-EMV detail. Aligned with the sibling cell order-capture-kiosk-first-party, which was downgraded to unknown on the same bullet. || 326th: MERGE HOLD (proposed no/B, held unknown): same as order-capture-kiosk-first-party: no kiosk product exists, claim does not apply, held unknown. PROPOSAL AS WRITTEN: 326th, MOVED unknown -> no. CLAIM: vendor SHIPS a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. VERDICT: no, on all three conjuncts. ConverseNow ships no kiosk - the kiosk is the restaurant's, and ConverseNow integrates voice into it via the Order Injection API ('Kiosk compatibility'); it publishes no accessibility conformance ('ADA', 'WCAG' 0 hits); and it takes no payment at all - the End-User Terms state 'The Restaurant remains the sole seller and merchant of record for your order; it determines pricing and taxes, receives payment, prepares the food, and is exclusively responsible for order fulfillment', and every published sample call closes with 'you can pay for this order at the store'. 'EMV', 'chip', 'contactless' and 'unattended' score 0 across the publisher corpus. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. || 334th: 334th, re-read, still unknown (no-module hold stands; do not re-propose no). The acquired Valyant AI kiosk page (Wayback, on disk at .cache/q333/conversenow/b/vlw_kiosk.html, (c) 2021) confirms the shape: 'Upgrade your restaurant kiosks with microphone and speaker-enabled hardware ... the integration process will work through a single application-programming-interface (API) call between your software provider and Valyant's proprietary conversational AI software' - a voice layer on the operator's own kiosk, no kiosk SKU, no accessibility or EMV statement. Retired brand, so it could carry a positive at most partial and no no. Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Re-sourced onto vendor platform-update documentation. Phone Order AI is the company's founding product and its actual business; the May 2025 release documents live inbound phone handling at scale (one million-plus calls, 4.55/5 satisfaction, 25% faster order processing) with completed orders injected into the integrated POS rather than transcribed by staff. Corroborated by the Valyant acquisition release and trade coverage. https://conversenow.ai/insights.html · retrieved 2026-08-02 adversarially verified
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Upheld by the 2026-08-02 adversarial pass from the vendor's own platform-update page rather than press coverage. Drive-through is one of the four channels covered by the December 2024 GenAI launch "for all served brands", operating at a 95% non-intervention rate stated as orders completed without live agent assistance, with real-time order confirmation boards integrated with POS systems. The human-escalation path is corroborated from the partner side by Deliverect: "flexible deployment (full automation or assist mode)". Capability originates with the Valyant AI acquisition of 2024-07-09. https://conversenow.ai/insights.html · retrieved 2026-08-02 adversarially verified
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Upgraded from partial by the 2026-08-02 adversarial pass on evidence the prior passes did not use. SMS AI Conversations is one of four enumerated first-party products ("Easy text ordering", "Order status updates"), and the December 2024 platform update puts text into production rather than merely naming it: the next-generation GenAI platform was launched "across phone, text, drive-through, and kiosks for all served brands", with "POS system integration". Conversational text ordering that lands in the POS is the whole of this claim. Outstanding disclosure gaps that fall outside it: no 10DLC or consent-handling detail, no described payment-capture path over SMS, and no separate SMS product documentation. https://conversenow.ai/insights.html · retrieved 2026-08-02 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
331st, MOVED unknown -> partial. CLAIM: 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. VERDICT: partial - loyalty membership is captured INSIDE the ordering flow against the restaurant's own program; redemption is contemplated but its mechanics are not documented. EVIDENCE: Privacy Policy (grade B, https://conversenow.ai/privacy-policy.html): 'To submit your order to the restaurant, you may be required to provide ... telephone number, and loyalty membership details.' End-User Terms 8.1 (https://conversenow.ai/end-user-terms.html): 'Orders are placed with the Restaurant. Any product descriptions, availability, pricing, taxes, fees, discounts, loyalty redemptions, and pickup/delivery times are determined by the Restaurant' - i.e. the loyalty program is the restaurant's (the same one as in-store), and redemptions occur on orders placed through the Service. The shipped Olive dashboard (already in the record) scores each store on `asked_for_loyalty_per` = 'Asked for Loyalty (%)', so the ask is a scripted step of the order, not post-purchase enrolment. SHORTFALL: no published sentence says points ACCRUE automatically or describes how a reward is redeemed by voice/SMS; over 32 text files redeem 0, 'redemption' 1 (the EUT clause above), and all 5 'point(s)' hits are 'point of sale'/'pain points'/'inflection point' (POISON named). WHY THIS IS NOT THE 'NO FIRST-PARTY FLOW' HOLD: the End-User Terms (effective May 27 2026, https://conversenow.ai/end-user-terms.html) define a guest-facing ordering Service of ConverseNow's own: 2.1 'By selecting "I Agree," "Place Order," "Submit," or any similar button at checkout or on a kiosk'; 2.3 'SMS/Text Link Assent. If you receive a text message containing a link to these Terms and proceed with the ordering process'; 5.1 'The Service lets you interact with automated voice assistants and related interfaces to place and manage orders with the Restaurant through phone, drive-through, kiosks, and related communication channels'; and products.html lists 'SMS AI Conversations ... Easy text ordering / Personalized AI memory'. The earlier holds were written before these terms were on disk (325th) or on the payment clause alone (328th). Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Unknown re-confirmed by the 2026-08-02 adversarial pass, on corrected grounds. The prior pass could not locate the cited language and downgraded partly for that reason; the language is in fact on the product page — promotional management via configurable "Coupons/Discounts" with options to "honor vs offer, optimizing for local deals" — and the original citation was accurate. It still does not reach the claim, which requires a discount defined once to be honoured identically across POS, kiosk and first-party digital with channel eligibility controls. ConverseNow operates none of those as ordering surfaces, promotions are defined in the POS, and whether the voice agent honours or offers a coupon says nothing about cross-channel parity or eligibility control. || 331st: 331st, NEW SURFACE, still unknown. Retired /technology/ page (Wayback 20220519143710): onboarding means 'we ... train our voice AI on your menu, upsells, LTOs, coupons and other details', and offers can be customised 'at the franchise, regional and national levels'. That describes ConverseNow keeping its OWN trained copy of the restaurant's coupons, which points away from define-once parity, but it is a retired 2022 page and says nothing about channel eligibility controls, so it cannot carry a no. Retrieved 2026-09-18. adversarially verified
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
Privacy policy positions ConverseNow as controller and routes guest rights through the restaurant; no operator bulk export documented. https://conversenow.ai/privacy-policy.html · retrieved 2026-08-01
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this digital-ordering behaviour. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 328th: MERGE HOLD (proposed no/B, held unknown): ConverseNow has no digital checkout at all: End-User Terms 8.3 puts payment processing with the restaurant or its processor. A product that lacks the module entirely is held unknown (325th/326th rule); the contract quote is kept as the bound. PROPOSAL AS WRITTEN: 328th, MOVED unknown -> no. CLAIM: 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 (incl. the March-2025 client-side script-integrity requirements) and supporting 3DS. VERDICT: no on every conjunct; the first two are affirmatively refuted, not merely absent. EVIDENCE: End-User Terms 8.3 Payment: 'Pricing, payment processing, taxes, and receipts are handled by the Restaurant or its payment processors. Contact the Restaurant for any billing or refund questions'; and section 1: 'The Restaurant remains the sole seller and merchant of record for your order; it determines pricing and taxes, receives payment'. ConverseNow hosts no checkout and no payment fields. The publication conjunct is separately bounded over the same 48-file corpus: PCI 0, 'PCI DSS' 0, 3DS 0, '3-D Secure' 0, tokenization 0, cardholder 0, 'SOC 2' 0, SOC2 0, 'ISO 27001' 0, HIPAA 0, 'penetration test' 0 - ConverseNow publishes no compliance or certification statement of any kind and has no trust page (no trust./security. host resolves; /security on conversenow.ai returns the site's own 1,910-byte 404, matched by the /zzz-nonsense control). NOTE for a later pass: cards ARE presented somewhere in the phone flow - the dashboard's closed non-order-reason enumeration carries 'Card Issue' = 'Guest provided a credit card that could not be processed' - but the contract places that processing with the Restaurant's processor. Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no first-party web or app ordering surface, no digital checkout and no guest account system; the ordering surfaces are voice and text. This digital-ordering capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Recycles the same "Personalized AI memory" bullet. Nothing documents a guest profile store, cross-channel identity merge, dedup, or operator access to profiles. Repeat-caller recall in a voice session is not a unified profile. || 325th: 325th, NEW SURFACES, still unknown. (1) The vendor's shipped dashboard measures whether the assistant confirmed the guest - `guest_name_confirmed_per` = 'Guest Name Confirmed (%)' and `asked_for_loyalty_per` = 'Asked for Loyalty (%)' in POLICY_ADHERENCE_STORE_TABLE_LABELS - which proves a guest NAME and a loyalty ask exist in the call script, but there is no customer object, no profile screen and no cross-channel identity anywhere in the closed bundle. (2) A retired sample-call library, recovered from Wayback (conversenow.ai/voice-ai-in-action/ capture 20250516165503 and /dominos-sample-calls/ capture 20250516182058), titles individual recordings "Domino's - recall guest name and last order", "Domino's - used last order" and "Domino's - save order as favorite" - the strongest indication yet that a per-guest order history is stored, but these are marketing clip titles (grade D), phone-channel only, and name no profile store or identity key. BOUND: the Olive AI customer dashboard is now a CLOSED corpus, not a sample. Its entry bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, re-fetched by me today, 7,770,702 bytes) opens with a Vite loader table, `__vite__mapDeps` d=["assets/forecastRealData-CA3-729w.js","assets/_sentry-release-injection-file-Bv3kP-4K.js"], and the ONLY call site in the file is __vite__mapDeps([0,1]) - so the app is 3 files, the loader table is exhausted in one round with 0 misses. Soft-200 control: /assets/index-ZZZNOPE.js returns 200 with 446 bytes of SPA shell, against 7.77 MB of JavaScript for the real asset, and the hash DXIYe81a is the one the live index.html references. Production JS the vendor does not publish as documentation = grade B. CAUTION for the next pass: Olive is a general analytics platform whose app registry also routes /apps/game-insights, /apps/game-services, /apps/finance-dashboard and /apps/finance-analytics, so not every module in it is the restaurant voice product. Retrieved 2026-09-17. || 331st: 331st, NEW EVIDENCE, still unknown. The live Privacy Policy names the identity key: log files record 'phone number, caller name associated with your telephone service provider ... This information allows us to recognize you and help customize your ordering experience ... more efficient tracking of your transaction history'; the live products.html transcripts show the effect ('I see we have your usual order saved'). That is a phone-keyed guest memory inside ConverseNow's own voice/SMS channels. It does not merge in-store POS, web/app or kiosk transactions and no dedup/merge behaviour is documented, so the claim's merge conjuncts are unmet and a partial would rest on the key alone. Retrieved 2026-09-18. 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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this guest-data or marketing behaviour. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 328th: 328th, per-cell re-grep, still unknown. The closed Olive dashboard has a 'Coupons' tab, but it is read-only reporting: the 46 coupon hits are cube-query keys, filter labels, drilldown columns, a `coupon_mention` call flag ('Calls where a coupon or promotional code was mentioned by the guest. Helps measure campaign effectiveness') and CSV download names - no coupon authoring, no eligibility rule, no combinability setting. Controls over the 48-file corpus: stacking 0, stackable 0, combinable 0, exclusivity 0, 'promo code' 0, redeem 0. POISON: 'exclusive' scores 114 and every hit is contract boilerplate ('non-exclusive license') or MUI docs strings in the UI showcase bundle. The one authoring-adjacent sentence anywhere is products.html's 'Coupons/Discounts - Configure to honor vs offer', a per-coupon honour/offer toggle, not a stacking engine. Retrieved 2026-09-18. adversarially verified
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
Upsell can key off guest behavior, but no audience-definition or offer-issuance tooling is documented. || 331st: 331st, NEW SURFACE, still unknown. The retired WordPress /technology/ page (Wayback 20220519143710) says 'Process coupons and gift cards with ease, and customize offers at the franchise, regional and national levels' and 'Our voice AI tailors upsell items based on a restaurant's unique menu and each guest's individual order'. The first is a GEOGRAPHIC hierarchy of offers, the second in-call upsell personalisation; neither issues an offer to an audience defined by recency, frequency, spend or items. The Olive bundle's 'Send re-engagement campaign immediately' / 'retention offer' strings sit beside `player_id`, 'Starter Pack' and iOS/Android rows, i.e. a UI-showcase template, not ConverseNow product. Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Downgraded from partial by the 2026-08-02 adversarial pass. The claim requires both email and SMS campaigns sent natively. The SMS half rests entirely on the bullet "Promotional messaging" with no list management, segmentation, scheduling or send reporting described. The email half fails on positive enumeration: ConverseNow lists its channels twice — four products on the product page and "phone, text, drive-through, and kiosks" in the December 2024 platform update — and email appears in neither, with no marketing or campaign product in the six-page sitemap. https://conversenow.ai/products.html · retrieved 2026-08-02 adversarially verified
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
326th, MOVED unknown -> no on the customer contract, a document this record has never held. CLAIM: 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. VERDICT: no. EVIDENCE: ConverseNow contractually places the entire consent obligation on the restaurant rather than performing it. Terms and Conditions for Restaurants, section 8 Indemnification: 'YOU AGREE TO INDEMNIFY ... DUE TO OR ARISING FROM ... (D) YOUR COMMUNICATIONS (CALLS, TEXTS, EMAILS), INCLUDING FAILURE TO OBTAIN REQUIRED CONSENTS, USE OF AUTOMATED/PRERECORDED MESSAGES, OR YOUR INSTRUCTIONS REGARDING TARGETED ADVERTISING, SALE/SHARING OF PERSONAL INFORMATION, OR ANALYTICS.' No consent ledger, consent timestamp, source-of-consent field or per-channel preference object appears anywhere: the token 'consent' scores 0 word-boundary hits in the entire 7,768,391-byte Olive AI dashboard bundle (which is a closed corpus), and its 22 hits in the publisher corpus are all in the Privacy Policy and End-User Terms as the END GUEST's consent to ConverseNow's own processing, plus the demo form's 'I consent to receive ConverseNow information and promotional material via phone, email and text messaging (SMS)' - ConverseNow's own lead form, not a merchant feature. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-09-18 adversarially verified
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
326th, MOVED unknown -> no. CLAIM: handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform. VERDICT: no. EVIDENCE: ConverseNow sells an SMS product - products.html lists 'SMS AI Conversations: Engage customers through intelligent texts for orders, support, and promotions ... Easy text ordering, Personalized AI memory, Promotional messaging, Order status updates' - and the End-User Terms even define an SMS acceptance path ('2.3 SMS/Text Link Assent'). Yet '10DLC', 'A2P', 'TCPA', 'The Campaign Registry', 'TCR', 'brand registration' and 'campaign registration' all score 0 word-boundary hits in the 8-document publisher corpus AND 0 in the 7.77 MB dashboard bundle. The contract instead pushes messaging compliance onto the restaurant wholesale (section 8(D), quoted in guest-loyalty-consent-management). Nothing tells the operator that registration exists, is handled by ConverseNow, or is theirs. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-09-18 adversarially verified
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
CLAIM: reports redemption AND incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. VERDICT: partial - the redemption half ships, the sales half does not. EVIDENCE (Olive analytics app, censused bundle): four coupon endpoints exist - `${API_BASE_CUBE}/coupons/performance`, `/coupons/frequently-used`, `/coupons/breakdown-by-store`, `/coupons/donut`. The Coupon Performance table is defined as columns `{key:`coupon`,label:`Coupon Code`}` and `{key:`order_count`,label:`Total Orders`}`; the donut maps `{coupon, order_count, order_percentage}` with CSV download `Frequently_Used_Coupons` carrying exactly `{Coupon, 'Order Count', 'Order Percentage'}`, and `Coupon_Breakdown_by_Store` adds the store dimension. There is also a per-call category `{type:`coupon_mention`,label:`Coupon Mentioned`,tooltip:`Calls where a coupon or promotional code was mentioned by the guest. Helps measure campaign effectiveness.`}`. SHORTFALL: every coupon field is a COUNT or a PERCENTAGE of orders; the bundle has no coupon revenue field at all ('coupon_revenue' absent, 'Coupon Sales' absent, and 'net sales'/'gross sales' are 0 across the whole corpus), so redeemed offers are never tied to check totals and no incremental-sales figure is produced. Retrieved 2026-09-18. https://app.olivelabs.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld and now resting on the vendor's own contract language rather than on an inference. The claim requires self-serve export of the full guest list and transaction history without a fee or a support ticket. The privacy policy documents the exact opposite mechanism, and exclusively: "Access and Data Portability. You may confirm whether we process your personal data and access a copy of the personal data we process." is a per-individual statutory right, it is rate-limited — "You may only make a verifiable consumer request for access or data portability twice within a 12-month period" — and it is not even addressed to the operator: "Such requests will have to be made to the Parent Restaurant Organization (or their franchisee)". There is no operator-facing route at all. CSV, spreadsheet, download your, guest list, customer list and bulk occur ZERO times in the frozen corpus, and the only two export hits are end-user-terms 22.6, trade-sanctions compliance ("You agree to comply with applicable export and sanctions laws related to your use of the Service"), which is a homonym and is discarded. Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-09
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this guest-data or marketing behaviour. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 327th: MERGE HOLD (proposed no/B, held unknown): Same family as extensibility-webhooks-push (held in the 326th). The word 'documented' does not turn an unreachable partner surface into a bounded publication census; the agent flagged this row itself. PROPOSAL AS WRITTEN: CLAIM: exposes a DOCUMENTED outbound guest and order event API or webhook stream a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). VERDICT: no, on the documentation conjunct, which is the one a publication census can bound. EVIDENCE: no doc host exists (docs./api./developer.conversenow.ai are NXDOMAIN on today's crt.sh-derived list), the only live API host answers 401 on every anonymous spec path, and the censused dashboard bundle plus the site and legal corpus score 0 for CDP, Klaviyo, Punchh, Bridg, Olo, 'event stream', and 0 for webhook in the dashboard bundle. POISON NAMED: `subscribe` scores 33 but every hit is RxJS (`SafeSubscriber`, `unsubscribe`, `ObjectUnsubscribedError`, `_trySubscribe`); `webhook` scores 3 only in the separate Olive UI showcase bundle, in generic integration-catalogue strings, not a ConverseNow event stream. WEAKER THAN I'D LIKE: this is the same family as extensibility-webhooks-push, which the 326th merge HELD on the grounds that an undocumented partner API is not bounded by a dashboard bundle. The distinction I am leaning on is the word 'documented' in this claim's text, which makes it a publication claim; if the owner rejects that distinction, hold this at unknown with the corpus note. Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
326th, MOVED unknown -> no. CLAIM: provides ADMIN tooling to fulfil guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records. VERDICT: no - rights exist, operator tooling does not. EVIDENCE: the Privacy Policy (Last Modified May 14, 2026) sets out a full rights list - 'Your State Privacy Rights ... Access and Data Portability. You may confirm whether we process your personal data and access a copy ... data will be provided in a portable format. Correction ... Deletion. You may request that we delete personal data about you' and 'The right to know. The right to delete. The right to opt-out' - but every route is a request made by the GUEST to ConverseNow ('contact us by writing to us at privacy@conversenow.ai'), never a screen the restaurant operates. The vendor's own shipped dashboard, a closed corpus, carries no DSAR, erasure or subject-request surface at all: 'consent' 0, 'opt-out' 0, 'DSAR' 0 word-boundary hits across 7,768,391 bytes, and its user-management endpoints are staff-account CRUD (/tenant_user/..., /audit/user/{id}) not guest-record tooling. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
328th, MOVED unknown -> no, and a TRAP a future pass would otherwise fall into. This is a documentation claim ('Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing'), so the publication census carries it. EVIDENCE: what ConverseNow publishes is explicitly RULE-configured, not model-generated - products.html's 'AI Your Way' list reads 'Upsell Logic - Configure by time, order size, or guest behavior' and 'Coupons/Discounts - Configure to honor vs offer, optimizing for local deals'. No page, changelog entry or contract describes a model proposing offer content, an audience or a send time, and there is no campaign or send concept at all (promo code 0, stackable 0, redeem 0, 'gift card' 0 across the corpus). THE TRAP: the shipped Olive dashboard exposes an 'Upsell Intelligence' tab whose service calls are /cube/upsell-intelligence/item-modifier-recommendations and /cube/upsell-intelligence/cart-recommendations, rendered as 'Item Modifier Recommendations' and 'Cart Recommendations'. These are REPORTS, not a recommender: the column config is {itemColumnLabel:'Offered Item', valueColumnLabel:'Item Upsell Value'} with drilldown keys ['offered_count','accepted_count'] - a historical table of what the voice agent already offered and how often guests accepted. Separately, 'Recommended Nugget', 'Promotion Recommendations' and 'Recommended Action' in the same bundle belong to Olive's HR and finance analytics apps (Employee_ID, Years_Since_Last_Promotion, nine-box grids, Recommended_For_Promotion), not to the restaurant voice product. BOUND: 48 files as above. Grade C because the operative citation is a marketing page. Retrieved 2026-09-18. https://conversenow.ai/products.html · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. There is no loyalty, CRM, segmentation or campaign product; guest data handling is governed by the privacy policy and routed through the Parent Restaurant Organization rather than exposed as operator tooling. This guest-marketing capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Archived feature page (grade C, 2022-08 capture) for 'Looker, your data dashboard', which the page says is included for operators and shows sales, average ticket, order data and AI performance. A sales dashboard exists. The claim's 'within minutes' and its browser-plus-mobile-app conjuncts are unevidenced. The live site keeps only a Drive-Thru bullet, 'Real-time analytics', which does not reestablish the dashboard itself. Looker is Google's BI product embedded by the vendor; the page offers operators dashboards, emailed reports and alerts, nothing about export, a builder or BI connectivity. https://web.archive.org/web/20220808215759id_/https://conversenow.ai/looker/ · retrieved 2026-09-12 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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Reporting is confined to in-product voice and conversation analytics; there is no sales, cash, labor or product-mix reporting layer, because ConverseNow does not own the transaction. This reporting capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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: PMIX report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center. VERDICT: no. NEW SURFACE (327th) - the Olive analytics app is now CENSUSED, not merely sampled. app.olivelabs.ai serves a Vite SPA titled 'Olive AI' (S3+CloudFront, Last-Modified 2026-09-17) whose single entry module /assets/index-DXIYe81a.js is 7,770,702 bytes and whose ONLY lazy-chunk table is `__vite__mapDeps=(i,m,d=(m.f||(m.f=["assets/forecastRealData-CA3-729w.js","assets/_sentry-release-injection-file-Bv3kP-4K.js"])))` - one data chunk (24,547 B, fetched) and the Sentry release stub. There is no other loader, so entry+chunk IS the whole app. The identical bundle hash (md5 6133f2525703f0e3c90922f3c652450f) is served from olive.analytics.conversenow.ai, which is what ties Olive to ConverseNow. 203 distinct API paths were enumerated from it (.cache/q327/conversenow/endpoints.txt). EVIDENCE: the app's only item/modifier-level reporting is Upsell Intelligence - `${API_BASE_CUBE}/upsell-intelligence/item-modifier-recommendations`, `VARIANT_CONFIG={item_modifier:{title:`Item Modifier Recommendations`,itemColumnLabel:`Offered Item`,valueColumnLabel:`Item Upsell Value`}}`, and StatCards `Modifier Upsell Attempt %`, `Modifier Upsell Success %`, `Modifier Upsell Value $`. Those count OFFERED and ACCEPTED upsells, not units sold. BOUND/CONTROLS over the whole corpus (both bundles, the 8-page conversenow.ai site, the 3 legal docs, the platform-update page, olivelabs.ai): tokenised \b word-boundary case-insensitive - PMIX 0, 'product mix' 0, 'item mix' 0, 'net sales' 0, 'gross sales' 0, 'units sold' 0, 'quantity sold' 0, 'revenue center' 0, daypart 0. Positive controls that prove the regexes fire on this corpus: upsell 183, coupon 46, franchise 69. Retrieved 2026-09-18. https://app.olivelabs.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Reporting is confined to in-product voice and conversation analytics; there is no sales, cash, labor or product-mix reporting layer, because ConverseNow does not own the transaction. This reporting capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Reporting is confined to in-product voice and conversation analytics; there is no sales, cash, labor or product-mix reporting layer, because ConverseNow does not own the transaction. This reporting capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Reporting is confined to in-product voice and conversation analytics; there is no sales, cash, labor or product-mix reporting layer, because ConverseNow does not own the transaction. This reporting capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Reporting is confined to in-product voice and conversation analytics; there is no sales, cash, labor or product-mix reporting layer, because ConverseNow does not own the transaction. This reporting capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
CLAIM: 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. VERDICT: partial (from unknown). EVIDENCE: all three conjuncts appear as shipped, named surfaces in the production ConverseNow analytics app. Side-by-side: tab 'Store Performance Comparison' (value 'store-performance') in KPIDashboard, alongside tabs 'Summary', 'Conversenow KPIs', 'KPI Dashboard v2'; endpoint ${API_BASE_CUBE}/summary/store-breakdown. Group->location: ${API_BASE_CUBE}/summary/store-breakdown-drilldown and ${API_BASE_CUBE}/kpi-dashboard/store-breakdown-kpi-drilldown. Location->transaction: ${API_BASE_CUBE}/all-orders/orders-drilldown, ${API_BASE_CUBE}/kpi-dashboard/total-orders-drilldown, ${API_BASE_CUBE}/summary/calls-drilldown, ${API_BASE_CUBE}/summary/non-orders-drilldown, with per-transaction columns 'Order Total', 'Order Status', 'Order Handle Time (sec)', 'Call Start Time', 'Call End Time', 'Call Number', 'Coupon Code', 'Recordings Links', 'Store ID', 'Store Name', and a row export at ${API_BASE_CUBE}/all-orders/orders-drilldown/download. SHORTFALL (why partial, not yes): the denominator is ConverseNow-handled voice traffic only - the filter defaults are DEFAULT_SUMMARY_FILTER_CHANNELS=['phone'] and DEFAULT_DT_FILTER_CHANNELS=['drivethru'] - so a 'group total' is the total of AI-handled calls and orders, not of all store transactions, and the drill reaches a call/order record rather than a POS receipt. Nothing is published about this app in any vendor document; the evidence is the shipped code alone. NEW SURFACE (never mined before this session): crt.sh on conversenow.ai returned 173 distinct names; almost all are dead (NXDOMAIN) tenant hosts, but olive.analytics.conversenow.ai is LIVE and PRODUCTION (a separate olive.analytics.staging.conversenow.ai exists in the CT log, so this is the prod copy). It serves a Vite SPA titled 'Olive AI'. Its login copy is ConverseNow's: 'Use your account credentials to access the ConverseNow dashboard', 'Please enter a valid email linked to your ConverseNow account', and BRAND_URL_MAPPINGS={conversenow:['olivelabs.ai/olive','analytics.conversenow.ai/olive','olive.analytics.conversenow.ai',...],olive:[]} with a ConverseNow logo asset (/converse_now/Converse-Now-Logo-RGB.png) and footer links to conversenow.ai/privacy-policy.html and conversenow.ai/terms-and-conditions.html. CENSUS: the Vite loader table is complete and closed - const __vite__mapDeps=(i,m,d=(m.f||(m.f=['assets/forecastRealData-CA3-729w.js','assets/_sentry-release-injection-file-Bv3kP-4K.js']))) - so the whole app is 3 files (index 2,263,314 B + forecast chunk 3,950 B + sentry shim); the forecast chunk contains no further loader entries, so the fixpoint closed in 1 round with 0 misses. No source maps: <bundle>.js.map returns the 446-byte SPA shell and so does the nonsense control <bundle>.js.NONSENSE.map and /zzz-nonsense-path, byte-identical - so those .map 200s are soft-200s and were not used. Identifiers are NOT minified in this build, so component, tab, column and endpoint names are the vendor's own. POISON FOUND AND EXCLUDED: (a) the bundle embeds a Snowflake SQL-function autocomplete dictionary, so the single 'SCIM' hit is SYSTEM$GENERATE_SCIM_ACCESS_TOKEN and several 'SAML' hits are SYSTEM$GENERATE_SAML_CSR / SYSTEM$MIGRATE_SAML_IDP_REGISTRATION - not features; (b) every 'MFA'/'TOTP' string (69/20 hits) comes from the bundled AWS Amplify auth library (FetchMFAPreference, SetUpTOTP, IncorrectMFAMethod) - library code, not a configured policy; (c) the app also ships DEMO apps for video games, HR and SaaS finance whose data comes from chunkedMockApiService/mockApiService (11 hits) - all 36 'cohort' hits, LTV, DAU and retention-heatmap strings are that MOCK game app and are NOT ConverseNow capability. Only endpoints under API_BASE$1='/api/summary-dashboard', API_BASE_CUBE='${API_BASE$1}/cube' and API_BASE='/api/dt-scorecard/cube' (68 hits, withCredentials:true) are live tenant data. Retrieved 2026-09-17. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-17 adversarially verified
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
CLAIM: self-service report builder letting a non-developer choose dimensions, measures and filters and SAVE the result, rather than only fixed canned reports. VERDICT: partial (from unknown). This does not re-litigate the 2026-09-12 audit, which upheld unknown on the retired 2022 Looker page; this is a different, live surface. EVIDENCE: the app ships an authoring surface with saved, publishable artefacts: routes /narrative, /narrative/workspace/:id?, /narratives/shared/:id, /nugget; tab labels 'Snippets', 'Nuggets', 'Tables', 'Visuals'; and thunks narratives/checkTitle, narratives/editNarrative, narratives/deleteNarrative, narratives/getAllNarratives, narratives/publishNarrative, narratives/shareNarrative, snippets/fetchSnippets. Filters are operator-chosen: FiltersBar applies {dateFrom, dateTo, brand, ownerName, serviceType} plus a date grammar of is_any_time / is_in_range / is_in_the_last / is_on_the_day with 'Last 7 days', 'Last 2 weeks', 'Last month', 'Specific Day', 'Relative', 'Custom Date', and a saved ${API_BASE$1}/user-preferences/filters. SHORTFALL: there is no dimension/measure picker - the tabs themselves ('KPI Dashboard', 'Summary', 'Coupons', 'Upsell Intelligence', 'All Orders', 'Store Sessions'; 'Executive Dashboard', 'Call Categories', 'Policy Adherence', 'Upsell Attempts', 'Friendliness', 'System Alerts', 'All Sessions', 'FrontDesk AI', 'Compare'; 'Dashboard', 'Day/Hourly Metrics', 'All Orders') are fixed canned reports, and the only way to compose a new one is to ask Olive Assist and save the answer as a snippet into a narrative. NEW SURFACE (never mined before this session): crt.sh on conversenow.ai returned 173 distinct names; almost all are dead (NXDOMAIN) tenant hosts, but olive.analytics.conversenow.ai is LIVE and PRODUCTION (a separate olive.analytics.staging.conversenow.ai exists in the CT log, so this is the prod copy). It serves a Vite SPA titled 'Olive AI'. Its login copy is ConverseNow's: 'Use your account credentials to access the ConverseNow dashboard', 'Please enter a valid email linked to your ConverseNow account', and BRAND_URL_MAPPINGS={conversenow:['olivelabs.ai/olive','analytics.conversenow.ai/olive','olive.analytics.conversenow.ai',...],olive:[]} with a ConverseNow logo asset (/converse_now/Converse-Now-Logo-RGB.png) and footer links to conversenow.ai/privacy-policy.html and conversenow.ai/terms-and-conditions.html. CENSUS: the Vite loader table is complete and closed - const __vite__mapDeps=(i,m,d=(m.f||(m.f=['assets/forecastRealData-CA3-729w.js','assets/_sentry-release-injection-file-Bv3kP-4K.js']))) - so the whole app is 3 files (index 2,263,314 B + forecast chunk 3,950 B + sentry shim); the forecast chunk contains no further loader entries, so the fixpoint closed in 1 round with 0 misses. No source maps: <bundle>.js.map returns the 446-byte SPA shell and so does the nonsense control <bundle>.js.NONSENSE.map and /zzz-nonsense-path, byte-identical - so those .map 200s are soft-200s and were not used. Identifiers are NOT minified in this build, so component, tab, column and endpoint names are the vendor's own. POISON FOUND AND EXCLUDED: (a) the bundle embeds a Snowflake SQL-function autocomplete dictionary, so the single 'SCIM' hit is SYSTEM$GENERATE_SCIM_ACCESS_TOKEN and several 'SAML' hits are SYSTEM$GENERATE_SAML_CSR / SYSTEM$MIGRATE_SAML_IDP_REGISTRATION - not features; (b) every 'MFA'/'TOTP' string (69/20 hits) comes from the bundled AWS Amplify auth library (FetchMFAPreference, SetUpTOTP, IncorrectMFAMethod) - library code, not a configured policy; (c) the app also ships DEMO apps for video games, HR and SaaS finance whose data comes from chunkedMockApiService/mockApiService (11 hits) - all 36 'cohort' hits, LTV, DAU and retention-heatmap strings are that MOCK game app and are NOT ConverseNow capability. Only endpoints under API_BASE$1='/api/summary-dashboard', API_BASE_CUBE='${API_BASE$1}/cube' and API_BASE='/api/dt-scorecard/cube' (68 hits, withCredentials:true) are live tenant data. Retrieved 2026-09-17. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-17 adversarially verified
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
Archived Looker feature page (grade C, 2022-08 capture), under 'Advanced reporting': automated reports on sales, order volume and average ticket, emailed as often as the operator likes (the raw text continues '’d like'). That meets the cadence-and-email conjunct. The recipient-list and any-report conjuncts are not addressed. Not repeated on the live site. Looker is Google's BI product embedded by the vendor; the page offers operators dashboards, emailed reports and alerts, nothing about export, a builder or BI connectivity. https://web.archive.org/web/20220808215759id_/https://conversenow.ai/looker/ · retrieved 2026-09-12 adversarially verified
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
326th, MOVED unknown -> no. CLAIM: 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. VERDICT: no. POISON, and it decides the direction: the Olive bundle's raw counts of snowflake (11), redshift (6), bigquery (6) and warehouse (10) are almost all an embedded SQL-formatter dialect registry ({mysql, n1ql, plsql, postgresql, redshift, singlestoredb, snowflake, spark, sqlite, tidb, trino...}) plus a Snowflake keyword table (WAREHOUSE_LOAD_HISTORY, CURRENT_WAREHOUSE, SYSTEM$GET_SNOWFLAKE_PLATFORM_INFO). The ONE real Snowflake usage runs the OPPOSITE way to this claim: the dashboard lets a tenant register an INBOUND datastore it will read FROM - {tenant_id, data_stores:[{datastore_type:'Snowflake', config:{schema, account, username, warehouse, auth_method:'private_key'}}]} with the credential values stored encrypted - and then POSTs to https://prod-service.olivelabs.ai/generate_datastore_json/generate_datastore_json/v1 and to a remoteTables endpoint to enumerate that database's tables and columns (fetchDatatables, dataTablesSlice). That is ConverseNow INGESTING the customer's warehouse for analysis, not exporting transaction-level data to a customer-controlled destination. The only egress the dashboard ships is manual CSV: POST /cube/<module>/drilldown/download per report module. 'sftp' 0 hits, 's3' 5 (all AWS SDK internals), no schedule object, no destination configuration, no delivery log. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
No public REST or GraphQL reference covering orders, payments, menu or labor, and no route to self-service credentials. Developer subdomains do not resolve (probed 2026-08-02); the status page confirms an "API Server" component exists internally, but nothing about it is published and integration is partner-gated through sales. https://conversenow.ai/products.html · retrieved 2026-08-02
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
326th, MOVED unknown -> no. CLAIM: emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behaviour and payload signature verification. VERDICT: no - see extensibility-webhooks-push: 'webhook' is 0 hits across both the 7.77 MB shipped dashboard bundle and the complete publisher corpus, and neither retry nor signing is documented anywhere because there is nothing to retry or sign. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this reporting behaviour. An operator console plainly exists — upsell configuration, A/B tests and analytics are all described — but not one screenshot, field list, export format or retention figure for it is published. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 327th: 327th, NEW SURFACE, still unknown. Two new hosts were opened and neither publishes commercial terms for data access: prod-service.olivelabs.ai answers every anonymous path with HTTP 401 {"detail":"Access token not found in Authorization header. Please include: Authorization: Bearer <COGNITO_ACCESS_TOKEN>"} - so an authenticated API demonstrably EXISTS - and the rebuilt olivelabs.ai site has no /pricing, no /terms and no /legal (all return its own 2,690-byte 404, matched by the nonsense control). ConverseNow still publishes no price list or plan tiering anywhere, so whether raw-data access is included in a standard subscription cannot be determined in either direction; an absence of published pricing is not evidence that access is gated. Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown. (1) Three certspotter-listed hosts no prior pass probed - api-qa-core-service.olivelabs.ai and api-qa-service-management.olivelabs.ai answer 401 on every spec path (/openapi.json, /docs, /swagger.json, /v3/api-docs, /api/openapi.json, /swagger/v1/swagger.json) AND on the nonsense control /zzz-nonsense, so they are blanket-gated, not spec-less; api-qa-performance-insights.olivelabs.ai is 404 on every path incl. root; prod-grafana.olivelabs.ai 302s to a login. (2) Public developer registries: SwaggerHub orgs conversenow/ConverseNow/olivelabs 404; npm search 'conversenow' 0 packages; PyPI 'conversenow' 404; Docker Hub namespace conversenow 0 repos. (3) The olive-backend OpenAPI on api.qa.olivelabs.ai (185 paths, already on disk from the 331st) is the Olive Labs generic BI product (tenants, sso-configurations, llm-api-keys, apps), not the restaurant ordering API. Net: the Order Injection API remains unpublished and gated, so the partner-API merge rule still blocks any capability or cost verdict. Retrieved 2026-09-18. adversarially verified
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
Archived Looker feature page (grade C, 2025-04-22 capture of the retired WordPress site; re-fetched 2026-09-15, HTTP 200, 53,854 bytes raw). The raw HTML says 'Looker is included in your ConverseNow experience as another example of our commitment to our partners.' It also says 'Especially helpful for multi-unit owners, view data by franchise or store level to compare call volume, order conversion, coupon use and other bottom-line factors'. POLARITY: the claim's yes means reporting is NOT paywalled. 'Included' meets the no-add-on-analytics-SKU conjunct in the non-paywalled direction, and the store comparison partly meets the multi-location conjunct. SHORTFALL: (1) ConverseNow publishes no plan structure. The raw page has zero hits for plan, tier, add-on, upgrade, pricing and additional cost, so 'entry-level plan' cannot be checked. 'Included' is one undated marketing sentence, not a price list, and the page's call to action is 'Contact our Sales team'. (2) Of the reports the claim names, the record scores labor productivity and comps/voids audit no, and PMIX unknown. The comparison metrics are call, conversion, coupon, sales and ticket, not labor or voids. (3) The page has been withdrawn from the live static site, so it may not describe current contracts. Looker is Google's BI product, embedded by the vendor. The same page, 2022-08 capture, already carries four other reporting and multi-location cells. https://web.archive.org/web/20250422152943id_/https://conversenow.ai/looker/ · retrieved 2026-09-15 adversarially verified
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
328th, MOVED unknown -> no. This is a PUBLICATION claim ('Documents a historical retention window of at least 24 months of transaction-level detail'), so a publication census can carry it, and the one figure ConverseNow publishes is shorter than the claim asks. EVIDENCE: privacy-policy.html (Last Modified 14 May 2026), heading 'Retention Period': 'ConverseNow will retain your personal data for the period necessary for the execution of the services or to attend to your requests or claims up to 1 year. After this time, ConverseNow will keep retaining the data only to the extent necessary to fulfill its obligations provided by the law or the European laws and regulations.' The reporting detail at issue sits inside that category: End-User Terms 11.2 lists '(b) order details (items, preferences, location, time, payment status ...)' and '(c) audio/voice recordings and transcripts of interactions' as the data processed. No second retention figure, archive tier or retrieval fee is published anywhere. POISON NAMED: the token '24 months' DOES score 1 hit in the Olive dashboard, and it is not a retention window - it is a lookback dropdown (6 months / 12 months / 24 months) on the provider_risk infrastructure analysis screen. 'archive' scores 9 and every hit is either MUI's Archive icon/menu item or the ARCHIVE keyword inside the bundled sql-formatter's Hive and Spark keyword lists. BOUND: 48 files - the 8-document site, both Olive bundles, the mined dashboard string sets, 11 retired WordPress pages. Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
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
Archived Looker feature page (grade C, 2022-08 capture): operators can set up custom email alerts, for example when a coupon is overused or a store underperforms. That matches the claim's operator-configured metric alert delivered by email. The mechanism is not documented, and the live site does not repeat it. Looker is Google's BI product embedded by the vendor; the page offers operators dashboards, emailed reports and alerts, nothing about export, a builder or BI connectivity. https://web.archive.org/web/20220808215759id_/https://conversenow.ai/looker/ · retrieved 2026-09-12 adversarially verified
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
CLAIM: natural-language query or AI assistant answering ad-hoc questions against the operator's own sales and labor data, returning a figure or chart rather than a help article. VERDICT: partial (from unknown). EVIDENCE: the ConverseNow dashboard ships 'Olive Assist' with a /chat route, placeholder 'Ask a question' / 'Ask anything', greeting 'Hello! How can I help you today?', over a websocket getWebSocketURL=(v='v6')=>'wss://prod-core.olivelabs.ai/chat/'+v+'/ws' whose CHAT_EVENTS include DATASTORES, CLARIFICATION and KEYWORD_CLARIFICATION. It generates and runs SQL over the tenant's warehouse and returns data, not prose: the error enum is 'SQL generation error', 'SQL execution error', 'Snowflake execution error', 'Chart generation error', 'Summary generation error', LLM_ERROR_WITH_ENGINE_INITIALIZATION, LLM_ERROR_WITH_FETCH_METADATA, LLM_ERROR_WITH_SEMANTIC_CLARIFICATION, LLM_ERROR_WITH_STANDALONE_QUESTION_GENERATION, and the response payload keys are chart_data and table_data. Answers can be starred and saved: narratives/getSnippetsByUserId, narratives/getVisualsByUserId, narratives/publishNarrative, narratives/shareNarrative. SHORTFALL: the queryable data is ConverseNow voice/order data (calls, orders, coupons, upsells, CSAT) - there is no labor data anywhere in the app, and labor is an excluded category for this record; and the tab permission model (app_access, olive_read_only_access, olive_crud_access) is per tenant, so I cannot show Assist is entitled for every restaurant customer. NEW SURFACE (never mined before this session): crt.sh on conversenow.ai returned 173 distinct names; almost all are dead (NXDOMAIN) tenant hosts, but olive.analytics.conversenow.ai is LIVE and PRODUCTION (a separate olive.analytics.staging.conversenow.ai exists in the CT log, so this is the prod copy). It serves a Vite SPA titled 'Olive AI'. Its login copy is ConverseNow's: 'Use your account credentials to access the ConverseNow dashboard', 'Please enter a valid email linked to your ConverseNow account', and BRAND_URL_MAPPINGS={conversenow:['olivelabs.ai/olive','analytics.conversenow.ai/olive','olive.analytics.conversenow.ai',...],olive:[]} with a ConverseNow logo asset (/converse_now/Converse-Now-Logo-RGB.png) and footer links to conversenow.ai/privacy-policy.html and conversenow.ai/terms-and-conditions.html. CENSUS: the Vite loader table is complete and closed - const __vite__mapDeps=(i,m,d=(m.f||(m.f=['assets/forecastRealData-CA3-729w.js','assets/_sentry-release-injection-file-Bv3kP-4K.js']))) - so the whole app is 3 files (index 2,263,314 B + forecast chunk 3,950 B + sentry shim); the forecast chunk contains no further loader entries, so the fixpoint closed in 1 round with 0 misses. No source maps: <bundle>.js.map returns the 446-byte SPA shell and so does the nonsense control <bundle>.js.NONSENSE.map and /zzz-nonsense-path, byte-identical - so those .map 200s are soft-200s and were not used. Identifiers are NOT minified in this build, so component, tab, column and endpoint names are the vendor's own. POISON FOUND AND EXCLUDED: (a) the bundle embeds a Snowflake SQL-function autocomplete dictionary, so the single 'SCIM' hit is SYSTEM$GENERATE_SCIM_ACCESS_TOKEN and several 'SAML' hits are SYSTEM$GENERATE_SAML_CSR / SYSTEM$MIGRATE_SAML_IDP_REGISTRATION - not features; (b) every 'MFA'/'TOTP' string (69/20 hits) comes from the bundled AWS Amplify auth library (FetchMFAPreference, SetUpTOTP, IncorrectMFAMethod) - library code, not a configured policy; (c) the app also ships DEMO apps for video games, HR and SaaS finance whose data comes from chunkedMockApiService/mockApiService (11 hits) - all 36 'cohort' hits, LTV, DAU and retention-heatmap strings are that MOCK game app and are NOT ConverseNow capability. Only endpoints under API_BASE$1='/api/summary-dashboard', API_BASE_CUBE='${API_BASE$1}/cube' and API_BASE='/api/dt-scorecard/cube' (68 hits, withCredentials:true) are live tenant data. Retrieved 2026-09-17. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-17 adversarially verified
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
326th, MOVED unknown -> partial on a module no prior pass reported. CLAIM: 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. VERDICT: partial. EVIDENCE: the Olive AI dashboard ships a real cohort engine - getLTVCohorts(), a RetentionHeatmap component keyed on cohort_date x day_number holding retention_rate, and the vendor's own in-app explanatory text 'Each cell represents retained_cohort_users_on_day_x / installs_day0 for that cohort' - so lifetime-value and retention cohorting exist as shipped product, alongside the per-session tables the 325th enumerated. SHORTFALL, and it is the claim's operative half: the cohort key is a session/user-acquisition construct ('installs_day0'), not an identifiable guest record. This record's own guest-loyalty-unified-profile note establishes there is no customer object, no profile screen and no cross-channel identity in this bundle; the guest-level metrics the dashboard does publish are policy-adherence percentages (guest_name_confirmed_per, asked_for_loyalty_per), not new-vs-returning counts or visit frequency. Grade B (shipped code). BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Reporting is confined to in-product voice and conversation analytics; there is no sales, cash, labor or product-mix reporting layer, because ConverseNow does not own the transaction. This reporting capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Reporting is confined to in-product voice and conversation analytics; there is no sales, cash, labor or product-mix reporting layer, because ConverseNow does not own the transaction. This reporting capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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 as a FIRST-CLASS object that reporting AND permissions can be scoped to. VERDICT: partial (from unknown). EVIDENCE: reporting carries four named levels as first-class filter and breakdown dimensions, not a flat store list: 'Brand' (filter key 'brand'; table 'Performance across Brands (most recent period)' with columns 'Brand', 'Active Stores', 'Billing Stores', '$ Sales (w/o tax)', '$ Avg Check', 'Avg CSAT', 'Total Calls', 'Conversion %'), 'Owner'/'Owners'/'Franchise'/'Franchise ID'/'Franchise Name'/'Franchisee'/'Franchisee Identifier' (filter key 'ownerName', column key 'franchise_id'), 'Region', and 'Store' ('Store ID', 'Store Name', 'Store Address', 'Store City', 'Store State', 'Store Phone Number'; keys store_id, store_id_store_number), with 'Store Breakdown', 'Store-Level Call Category Breakdown', 'Store-Level Upsell Metrics', 'Store-Level Policy Metrics', 'Store-Level Friendliness Metrics'. SHORTFALL: the permission conjunct is NOT met - the role model scopes to apps and data domains, not to hierarchy nodes: the whole permission vocabulary is app_access, access_users, access_roles, access_domains, olive_read_only_access, olive_crud_access, and the role editor's scoping fields are 'Allowed Apps' and 'Allowed Domains'. Nothing binds a role to a brand, franchisee, region or store. NEW SURFACE (never mined before this session): crt.sh on conversenow.ai returned 173 distinct names; almost all are dead (NXDOMAIN) tenant hosts, but olive.analytics.conversenow.ai is LIVE and PRODUCTION (a separate olive.analytics.staging.conversenow.ai exists in the CT log, so this is the prod copy). It serves a Vite SPA titled 'Olive AI'. Its login copy is ConverseNow's: 'Use your account credentials to access the ConverseNow dashboard', 'Please enter a valid email linked to your ConverseNow account', and BRAND_URL_MAPPINGS={conversenow:['olivelabs.ai/olive','analytics.conversenow.ai/olive','olive.analytics.conversenow.ai',...],olive:[]} with a ConverseNow logo asset (/converse_now/Converse-Now-Logo-RGB.png) and footer links to conversenow.ai/privacy-policy.html and conversenow.ai/terms-and-conditions.html. CENSUS: the Vite loader table is complete and closed - const __vite__mapDeps=(i,m,d=(m.f||(m.f=['assets/forecastRealData-CA3-729w.js','assets/_sentry-release-injection-file-Bv3kP-4K.js']))) - so the whole app is 3 files (index 2,263,314 B + forecast chunk 3,950 B + sentry shim); the forecast chunk contains no further loader entries, so the fixpoint closed in 1 round with 0 misses. No source maps: <bundle>.js.map returns the 446-byte SPA shell and so does the nonsense control <bundle>.js.NONSENSE.map and /zzz-nonsense-path, byte-identical - so those .map 200s are soft-200s and were not used. Identifiers are NOT minified in this build, so component, tab, column and endpoint names are the vendor's own. POISON FOUND AND EXCLUDED: (a) the bundle embeds a Snowflake SQL-function autocomplete dictionary, so the single 'SCIM' hit is SYSTEM$GENERATE_SCIM_ACCESS_TOKEN and several 'SAML' hits are SYSTEM$GENERATE_SAML_CSR / SYSTEM$MIGRATE_SAML_IDP_REGISTRATION - not features; (b) every 'MFA'/'TOTP' string (69/20 hits) comes from the bundled AWS Amplify auth library (FetchMFAPreference, SetUpTOTP, IncorrectMFAMethod) - library code, not a configured policy; (c) the app also ships DEMO apps for video games, HR and SaaS finance whose data comes from chunkedMockApiService/mockApiService (11 hits) - all 36 'cohort' hits, LTV, DAU and retention-heatmap strings are that MOCK game app and are NOT ConverseNow capability. Only endpoints under API_BASE$1='/api/summary-dashboard', API_BASE_CUBE='${API_BASE$1}/cube' and API_BASE='/api/dt-scorecard/cube' (68 hits, withCredentials:true) are live tenant data. Retrieved 2026-09-17. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-17 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
Upheld by the 2026-08-02 adversarial pass, which confirmed the sentence on the product page: "Menu, pricing, and behavior tuned by region/store." That establishes centrally configured per-store menu and price variation — the override half. Shortfall: the lock half is entirely absent. No field-level lock model, no statement of which attributes a store may edit and which corporate freezes, and no admin documentation of any kind; the menu itself lives in the integrated POS. Resting on one marketing sentence, this cell should not be inflated toward yes without an admin guide that does not exist. https://conversenow.ai/products.html · retrieved 2026-08-02 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Menus, prices, tax and gift/loyalty balances live in the POS, so the enterprise constructs this claim describes are not ConverseNow's to publish or enforce. This multi-location capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this multi-location or enterprise-administration behaviour. The privacy policy distinguishes a Parent Restaurant Organization from its Franchisee, which implies some tenancy model, but no permission or hierarchy model is published. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 327th: 327th, NEW SURFACE, still unknown. The Olive analytics app's 203-endpoint census contains no menu, price or promo WRITE path of any kind - every endpoint is a read-side cube query, filter listing, drilldown or CSV download - and 'price book' scores 0 corpus-wide. POISON NAMED: 'scheduled' scores 2 in the bundle and both are d3-transition's scheduler ('too late; already scheduled', the CREATED/SCHEDULED/STARTING state enum); 'effective date' scores 2 and both are the End User Terms' own effective date, not a menu effective date. ConverseNow publishes nothing that authors a menu, so there is no publish pipeline for a future-dated activation to belong to; held unknown rather than no, per the rule for a module the product does not have. Retrieved 2026-09-18. adversarially verified
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
Only the published time-to-open conjunct is met. The archived Technology page (capture 2025-06-25), under 'Get started in no time', says: 'Go live with your first store in 4 – 6 weeks, with additional stores taking just 3 – 5 days. Just send us your menu and a few details about your restaurant, and we’ll take care of everything.' Shortfall: no configuration template or clone mechanism is documented. 'template', 'clone', 'copy' and 'duplicate' each get 0 hits in the raw page. Setup is done by the vendor ('We do the heavy lifting for you'), so an operator has no provisioning mechanism to use. The figures are for going live with voice AI at a store that is already open, not for opening a POS store. Grade C because this is marketing copy. https://web.archive.org/web/20250625041113id_/https://conversenow.ai/technology/ · retrieved 2026-09-15 adversarially verified
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
Privacy policy distinguishes the Parent Restaurant Organization from its Franchisee, but no permission model is published. || 324th: NEW SURFACE, cell NOT moved. The production analytics app does carry franchisee IDENTITY as a reporting dimension - 'Franchise', 'Franchise ID', 'Franchise Name', 'Franchisee', 'Franchisee Identifier', 'Franchisee Name', 'Owner', 'Owners', filter key 'ownerName', column key franchise_id - so the data model knows who owns a store. But the PERMISSION model does not distinguish a franchisor tenant from a franchisee tenant: the complete permission vocabulary in the app is app_access, access_users, access_roles, access_domains, olive_read_only_access, olive_crud_access, and roles scope only to 'Allowed Apps' and 'Allowed Domains'. Nothing lets corporate see franchisee sales while the franchisee owns its own employee/banking data, and this product holds no employee, banking or labor data at all. Stays unknown. Retrieved 2026-09-17. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Menus, prices, tax and gift/loyalty balances live in the POS, so the enterprise constructs this claim describes are not ConverseNow's to publish or enforce. This multi-location capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Menus, prices, tax and gift/loyalty balances live in the POS, so the enterprise constructs this claim describes are not ConverseNow's to publish or enforce. This multi-location capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Archived Looker feature page (grade C, 2022-08) shows above-store reporting for multi-unit owners, comparing stores on sales and discount (coupon) metrics. That meets the aggregation conjunct in part. The labor/voids/item-mix and ranking/variance-flag conjuncts are unevidenced. Uses the same block as reporting-multiloc-drilldown, for different conjuncts. Not repeated on the live site. Looker is Google's BI product embedded by the vendor; the page offers operators dashboards, emailed reports and alerts, nothing about export, a builder or BI connectivity. https://web.archive.org/web/20220808215759id_/https://conversenow.ai/looker/ · retrieved 2026-09-12 adversarially verified
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
CLAIM: item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. VERDICT: no. EVIDENCE: the Olive analytics app DOES ship a three-level org hierarchy - `LEVEL_COLORS.brand/.franchisee/.store`, rows pushed as `{Level:`Brand`,Value:fe.brandValue}`, `{Level:`Franchise`,Value:fe.franchiseeValue}`, `{Level:`Store`,Value:fe.storeValue}`, with filter endpoints /cube/filters/brands, /cube/filters/franchise-ids, /cube/filters/owners, /cube/filters/store-ids - so cross-location rollup exists, but every measure rolled up is a CALL/ORDER/upsell metric, never item sales. BOUND/CONTROLS over the censused bundle plus the rest of the corpus: 'corporate item' 0, 'roll-up' 0, 'item id' as a sales key absent; the only item-keyed object in the app is the upsell recommendation row (`itemColumnLabel:`Offered Item``) and /cube/upsell/upsize-items, /greeting-items, /cart-items, none of which carries a location-normalised identifier or a rename/local-price reconciliation. POISON NAMED: `rollup` matches 29 times but is the Rollup bundler/`rollupCache` in vendored code, not a reporting rollup; `normalized` (7) is CSS/`normalizedValue`. Retrieved 2026-09-18. https://app.olivelabs.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Menus, prices, tax and gift/loyalty balances live in the POS, so the enterprise constructs this claim describes are not ConverseNow's to publish or enforce. This multi-location capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Menus, prices, tax and gift/loyalty balances live in the POS, so the enterprise constructs this claim describes are not ConverseNow's to publish or enforce. This multi-location capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this multi-location or enterprise-administration behaviour. The privacy policy distinguishes a Parent Restaurant Organization from its Franchisee, which implies some tenancy model, but no permission or hierarchy model is published. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 324th: NEW SURFACE, cell NOT moved, and a misreading to avoid. The production analytics app olive.analytics.conversenow.ai does make 'Brand' a first-class dimension ('Performance across Brands (most recent period)', columns 'Brand', 'Active Stores', 'Billing Stores', '$ Sales (w/o tax)', '$ Billing (w/o tax)', 'Avg CSAT', 'Conversion %'; filter key 'brand'; 'Brand Greeting %'). But 'Billing Stores' and '$ Billing' make this a view ACROSS CONVERSENOW'S CUSTOMER BRANDS - the vendor's own book of business - not two virtual brands running on one restaurant's hardware and drawer. The claim's conjuncts (separate menus, separate receipts/branding, same hardware and drawer) are untouched and this product has no drawer. Stays unknown. Retrieved 2026-09-17. || 327th: 327th, NEW SURFACE, still unknown. The censused Olive analytics app proves the BRAND dimension is real and separately reportable - /cube/filters/brands, /brands, /brand-breakdown, /brand-kpis-over-time, /finance-summary-brand, `LEVEL_COLORS.brand`, and a brand-vs-franchisee-vs-store comparison that emits `{Level:`Brand`,Value:fe.brandValue}` - which satisfies only the claim's 'separately reportable revenue' conjunct. The claim's operative conjuncts are that ONE location/terminal runs two or more brands with separate menus and receipts/branding on the same hardware and drawer. ConverseNow ships no terminal, no menu store and no receipt; brand here is a reporting attribute of a voice session, not a terminal mode. Adjacent, so not a partial; held unknown per the rule for a module the product does not have. Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Menus, prices, tax and gift/loyalty balances live in the POS, so the enterprise constructs this claim describes are not ConverseNow's to publish or enforce. This multi-location capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
New evidence narrows this without resolving it: Deliverect's integration listing shows ConverseNow live in five countries (Australia, Canada, Mexico, United Kingdom, United States), and the vendor documents multilingual conversation including Spanish. Nothing states that locations in different currencies can sit inside one enterprise account, and no consolidated reporting currency or FX conversion is described anywhere. || 325th: 325th, NEW BOUND, still unknown, plus two control traps worth recording. The Olive AI dashboard is single-currency: its only currency configuration is d3-format's default locale, `defaultLocale({thousands:',',grouping:[3],currency:['$','']})`, and money is rendered by a fmtUsd helper; there is no currency selector, no FX rate and no reporting-currency conversion. POISON: of 68 `currency` hits, several are the substring inside `hardwareConcurrency` (Sentry web-vitals attributes), and of 188 `language` hits every one is either the MUI `Language` icon path or Prism.js's `languages` registry - so a naive count would have read as locale support. BOUND: the Olive AI customer dashboard is now a CLOSED corpus, not a sample. Its entry bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, re-fetched by me today, 7,770,702 bytes) opens with a Vite loader table, `__vite__mapDeps` d=["assets/forecastRealData-CA3-729w.js","assets/_sentry-release-injection-file-Bv3kP-4K.js"], and the ONLY call site in the file is __vite__mapDeps([0,1]) - so the app is 3 files, the loader table is exhausted in one round with 0 misses. Soft-200 control: /assets/index-ZZZNOPE.js returns 200 with 446 bytes of SPA shell, against 7.77 MB of JavaScript for the real asset, and the hash DXIYe81a is the one the live index.html references. Production JS the vendor does not publish as documentation = grade B. CAUTION for the next pass: Olive is a general analytics platform whose app registry also routes /apps/game-insights, /apps/game-services, /apps/finance-dashboard and /apps/finance-analytics, so not every module in it is the restaurant voice product. Retrieved 2026-09-17. adversarially verified
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
CLAIM: immutable audit log of WHO changed WHICH configuration object (price, tax, permission, discount) at WHICH location and WHEN, exportable or queryable by corporate. VERDICT: partial (from unknown). EVIDENCE: one of the four enumerated config objects - permission - does carry a who/what/when history in the production ConverseNow dashboard: 'Role History', 'User history logs', 'Previous role', 'Updated role', 'By <user_name> (<user_email>)', 'No History Found', and an 'Audit log update error' string; plus a separate login trail at route /session-tracking with columns 'Session ID', 'User ID', 'Login Time' and 'No sessions found.'. SHORTFALLS, all material: price, tax and discount configuration is not in this product at all (menu and pricing live in the incumbent POS); the history is not scoped to a location (roles scope to 'Allowed Apps'/'Allowed Domains', never to a store); nothing states immutability; and there is no export or query surface for the history - the only download endpoints in the app are ${API_BASE_CUBE}/all-orders/orders-drilldown/download and /api/weekly-reports/download, both report data. NEW SURFACE (never mined before this session): crt.sh on conversenow.ai returned 173 distinct names; almost all are dead (NXDOMAIN) tenant hosts, but olive.analytics.conversenow.ai is LIVE and PRODUCTION (a separate olive.analytics.staging.conversenow.ai exists in the CT log, so this is the prod copy). It serves a Vite SPA titled 'Olive AI'. Its login copy is ConverseNow's: 'Use your account credentials to access the ConverseNow dashboard', 'Please enter a valid email linked to your ConverseNow account', and BRAND_URL_MAPPINGS={conversenow:['olivelabs.ai/olive','analytics.conversenow.ai/olive','olive.analytics.conversenow.ai',...],olive:[]} with a ConverseNow logo asset (/converse_now/Converse-Now-Logo-RGB.png) and footer links to conversenow.ai/privacy-policy.html and conversenow.ai/terms-and-conditions.html. CENSUS: the Vite loader table is complete and closed - const __vite__mapDeps=(i,m,d=(m.f||(m.f=['assets/forecastRealData-CA3-729w.js','assets/_sentry-release-injection-file-Bv3kP-4K.js']))) - so the whole app is 3 files (index 2,263,314 B + forecast chunk 3,950 B + sentry shim); the forecast chunk contains no further loader entries, so the fixpoint closed in 1 round with 0 misses. No source maps: <bundle>.js.map returns the 446-byte SPA shell and so does the nonsense control <bundle>.js.NONSENSE.map and /zzz-nonsense-path, byte-identical - so those .map 200s are soft-200s and were not used. Identifiers are NOT minified in this build, so component, tab, column and endpoint names are the vendor's own. POISON FOUND AND EXCLUDED: (a) the bundle embeds a Snowflake SQL-function autocomplete dictionary, so the single 'SCIM' hit is SYSTEM$GENERATE_SCIM_ACCESS_TOKEN and several 'SAML' hits are SYSTEM$GENERATE_SAML_CSR / SYSTEM$MIGRATE_SAML_IDP_REGISTRATION - not features; (b) every 'MFA'/'TOTP' string (69/20 hits) comes from the bundled AWS Amplify auth library (FetchMFAPreference, SetUpTOTP, IncorrectMFAMethod) - library code, not a configured policy; (c) the app also ships DEMO apps for video games, HR and SaaS finance whose data comes from chunkedMockApiService/mockApiService (11 hits) - all 36 'cohort' hits, LTV, DAU and retention-heatmap strings are that MOCK game app and are NOT ConverseNow capability. Only endpoints under API_BASE$1='/api/summary-dashboard', API_BASE_CUBE='${API_BASE$1}/cube' and API_BASE='/api/dt-scorecard/cube' (68 hits, withCredentials:true) are live tenant data. Retrieved 2026-09-17. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-17 adversarially verified
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
326th, MOVED unknown -> partial on a surface no prior pass read. CLAIM: SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, WITH SCIM or equivalent for automated deprovisioning. VERDICT: partial - the first conjunct is squarely met and the second is absent. EVIDENCE (the vendor's own shipped code, not marketing): the Olive AI dashboard ships a self-service tenant-admin screen headed 'Authentication Config' > 'SSO Configuration'. The tenant admin supplies their own IdP metadata - the form validates 'Metadata URL is required' or 'Metadata XML is required' and posts it to saveSsoConfig(tenantId, {metadata_url | metadata_xml}) - and the screen then renders three read-only copy-to-clipboard fields labelled 'ACS URL (Reply URL)' = https://prod-olivelabs-ai.auth.us-east-1.amazoncognito.com/saml2/idpresponse, 'Entity ID (Audience URI)' = urn:amazon:cognito:sp:us-east-1_v9YCQIPrC, and a redirect URI of https://app.olivelabs.ai/callback, under the heading 'Configure in Your Identity Provider ... Use the following information when configuring this application in your identity provider'. There is an enable/disable toggle (toggleSso, messages 'SSO login enabled successfully' / 'Please save SSO configuration first before enabling' / 'No SSO provider configured. Please save configuration first.') and a test button that builds buildSsoUrl(cognito_saml_provider_name, encodeLoginState('saml', ...)). Login state defaults to {loginMethod:'saml'}, DEFAULT_LOGIN_PATH is `/sso`, and the same screen carries independent toggles for password_enabled, google_login_enabled, facebook_login_enabled and apple_login_enabled. SHORTFALL: no SCIM and no automated deprovisioning. The only 'scim' token in the whole 7.77 MB bundle is the Snowflake SQL keyword SYSTEM$GENERATE_SCIM_ACCESS_TOKEN inside the embedded dialect table, and user lifecycle is manual REST - /tenant_user/{id}/set-temporary-password, /tenant_user/v2/tenant/{id} delete, /audit/user/{id}, /audit/role/{id}. GRADE: B, production JS the vendor does not publish as documentation. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this multi-location or enterprise-administration behaviour. The privacy policy distinguishes a Parent Restaurant Organization from its Franchisee, which implies some tenancy model, but no permission or hierarchy model is published. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 324th: NEW SURFACE, cell NOT moved. Such an API demonstrably EXISTS but is not published: the production dashboard calls a cross-location, transaction-level REST cube with one session credential - API_BASE$1='/api/summary-dashboard', API_BASE_CUBE='${API_BASE$1}/cube', API_BASE='/api/dt-scorecard/cube', config {timeout:60000, withCredentials:true} - with endpoints including /summary/store-breakdown, /all-orders/data, /all-orders/orders-drilldown, /kpi-dashboard/total-orders-drilldown, /store-sessions/data and /upsell-intelligence/tiles. The claim requires the vendor to PUBLISH a documented API; no documentation for these routes is public. docs.conversenow.ai resolves to 34.123.64.3 but is a Kubernetes API server, not docs - it answers 'forbidden: User "system:anonymous" cannot get path "/"' - and api./dash./pos./pos-web./data./ops./training./v2.conversenow.ai do not resolve at all. I did not call any of these endpoints. Stays unknown. Retrieved 2026-09-17. || 327th: MERGE HOLD (proposed no/B, held unknown): Same shape the 326th held (extensibility-webhooks-push, oauth): an undocumented, Cognito-gated partner/production API is not bounded by a dashboard bundle plus dead DNS names; enterprise API docs are routinely delivered under NDA. prod-service.olivelabs.ai proves an API EXISTS; whether documentation is published to customers is unmeasured. PROPOSAL AS WRITTEN: CLAIM: publishes a DOCUMENTED multi-location API (or data warehouse/BI export) returning transaction-level data across all locations in one authenticated call. VERDICT: no - this is a PUBLICATION claim and the publication surface is now bounded. EVIDENCE: (1) crt.sh was re-run on both conversenow.ai (176 names) and olivelabs.ai (29 names). Every plausible doc host is DEAD at DNS today: docs./api./app./dash./pos./pos-web./analytics./training./registry.conversenow.ai all fail to resolve; only status., website., olive.analytics.conversenow.ai and the olivelabs.ai hosts answer. (2) The one live production API host, prod-service.olivelabs.ai, returns HTTP 401 with body {"detail":"Access token not found in Authorization header. Please include: Authorization: Bearer <COGNITO_ACCESS_TOKEN>"} on EVERY spec path probed anonymously - /openapi.json, /swagger.json, /swagger/v1/swagger.json, /v3/api-docs, /docs, /redoc, /api-docs - and the same 401 on the nonsense control path, i.e. it is a blanket auth gate, not a published spec (/health is the one 404, 22 B). (3) The complete Olive dashboard bundle contains no spec either: OpenAPI 0, swagger 0 over the whole corpus. Its 203 endpoints are internal cube queries under a Cognito bearer. So ConverseNow/Olive publish no API documentation of any kind; the multi-location data that does exist is reachable only through the logged-in dashboard, and its CSV `TileMenuButton` downloads are per-tile, not transaction-level. Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown. (1) Three certspotter-listed hosts no prior pass probed - api-qa-core-service.olivelabs.ai and api-qa-service-management.olivelabs.ai answer 401 on every spec path (/openapi.json, /docs, /swagger.json, /v3/api-docs, /api/openapi.json, /swagger/v1/swagger.json) AND on the nonsense control /zzz-nonsense, so they are blanket-gated, not spec-less; api-qa-performance-insights.olivelabs.ai is 404 on every path incl. root; prod-grafana.olivelabs.ai 302s to a login. (2) Public developer registries: SwaggerHub orgs conversenow/ConverseNow/olivelabs 404; npm search 'conversenow' 0 packages; PyPI 'conversenow' 404; Docker Hub namespace conversenow 0 repos. (3) The olive-backend OpenAPI on api.qa.olivelabs.ai (185 paths, already on disk from the 331st) is the Olive Labs generic BI product (tenants, sso-configurations, llm-api-keys, apps), not the restaurant ordering API. Net: the Order Injection API remains unpublished and gated, so the partner-API merge rule still blocks any capability or cost verdict. Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Menus, prices, tax and gift/loyalty balances live in the POS, so the enterprise constructs this claim describes are not ConverseNow's to publish or enforce. This multi-location capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
No self-serve reference exists. The sitemap lists six pages, none developer-facing; docs.conversenow.ai, api.conversenow.ai, developer.conversenow.ai and developers.conversenow.ai all fail to resolve when probed 2026-08-02, while status.conversenow.ai does resolve, so the probe itself is sound. The only artefact is a product tile named "Order Injection API" whose entire specification is four bullets. Access runs through "Book a Consultation". https://conversenow.ai/products.html · retrieved 2026-08-02
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this API behaviour. The Order Injection API is named as a product but has no published specification, auth model, versioning policy or rate limits, and access runs through sales. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 327th: 327th, NEW SURFACE, still unknown. Same finding as reporting-api-not-upcharged: prod-service.olivelabs.ai is a live production API behind a blanket Cognito bearer gate (401 on /openapi.json, /swagger.json, /swagger/v1/swagger.json, /v3/api-docs, /docs, /redoc, /api-docs and on the nonsense control alike; /health is the sole 404), and neither conversenow.ai's three legal documents nor the rebuilt olivelabs.ai site states any fee, surcharge or plan requirement attached to API access. Nothing supports either direction of the claim. Retrieved 2026-09-18. || 331st: 331st: 331st, new surfaces, still unknown, plus a poison warning. (1) The rebuilt Olive UI showcase (60-file chunk fixpoint, 0 misses) scores 'api key(s)' 29, and every hit is the BRING-YOUR-OWN-LLM-KEY screen ('Add your own OpenAI or Anthropic API keys. Requests for the models you select will use your key, and all other requests continue to use Olive's keys'). That is a customer supplying a third party's key to Olive. It is not the price of access to ConverseNow's API. 'pricing' 0, 'billing' 0. (2) The retired Terms of Service (Wayback 2020 and 2021 captures) contain 'API' 0 times, and their fee clause is the same order-form-only wording as today's. (3) Trust-vault probes: trust.conversenow.ai, security.conversenow.ai, conversenow.safebase.io, conversenow.trust.page and trust.olivelabs.ai do not resolve. app.vanta.com/conversenow/trust returns Vanta's generic 5,545-byte SPA shell, the same shell a nonsense slug returns, so it tells us nothing. trust.drata.com/conversenow returns 403. (4) certspotter on conversenow.ai (30 issuances) and olivelabs.ai (17) found 0 hostnames that crt.sh had not already listed. No published fee and no published inclusion, so the cell stays unknown. Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown. (1) Three certspotter-listed hosts no prior pass probed - api-qa-core-service.olivelabs.ai and api-qa-service-management.olivelabs.ai answer 401 on every spec path (/openapi.json, /docs, /swagger.json, /v3/api-docs, /api/openapi.json, /swagger/v1/swagger.json) AND on the nonsense control /zzz-nonsense, so they are blanket-gated, not spec-less; api-qa-performance-insights.olivelabs.ai is 404 on every path incl. root; prod-grafana.olivelabs.ai 302s to a login. (2) Public developer registries: SwaggerHub orgs conversenow/ConverseNow/olivelabs 404; npm search 'conversenow' 0 packages; PyPI 'conversenow' 404; Docker Hub namespace conversenow 0 repos. (3) The olive-backend OpenAPI on api.qa.olivelabs.ai (185 paths, already on disk from the 331st) is the Olive Labs generic BI product (tenants, sso-configurations, llm-api-keys, apps), not the restaurant ordering API. Net: the Order Injection API remains unpublished and gated, so the partner-API merge rule still blocks any capability or cost verdict. Retrieved 2026-09-18. adversarially verified
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
RESOLVED from unknown 2026-09-09. The claim asks for a free sandbox or test environment with seeded data, available without a paid production account. sandbox and test environment occur ZERO times across the complete published surface, and there is no developer surface of any kind to host one: no signup, no API key issuance, no reference documentation, and every call to action on every page is "Book a Consultation". The subdomains that would hold a developer portal resolve but refuse: docs.conversenow.ai (34.123.64.3) and app.conversenow.ai (142.93.23.88) drop every TCP connect on 80, 443, 8080 and 22, while a fabricated control subdomain returns ENODATA, so the resolutions are real and the refusal is at the host. Wayback shows docs. answering in 2023 with a 302 into conversenow.auth0.com/authorize, so it is an SSO-gated documentation host, never anonymously readable. That strengthens rather than weakens this cell: the claim asks for an environment reachable WITHOUT a paid production account, and an Auth0 wall is the account requirement. Bounded to the complete live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters (sitemap 6 locs + the two footer-linked legal pages the sitemap omits; the href set was diffed against the sitemap both ways and is exact, and /products is a byte-identical alias of /products.html). Absence is measurable here: every fabricated path 404s with a body byte-identical to /404.html served verbatim, across fifteen probe shapes including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt and /api/v1/orders, as does every path retired in the 2025 rebuild; the requested path is never echoed into the body. There is no catch-all. Every zero was re-run against the unstripped HTML as well as the stripped text and none is manufactured by the strip. The two hosts that could hold a private answer are named rather than ignored: api., developer. and developers.conversenow.ai are NXDOMAIN, while docs.conversenow.ai (A 34.123.64.3) and app.conversenow.ai (A 142.93.23.88) resolve and drop every TCP connect on 80, 443, 8080 and 22 — docs. was an Auth0 SSO-gated documentation host when Wayback last saw it answer, in 2023. That surface is unmeasured, not absent, and nothing below is bounded to it. https://conversenow.ai/products.html · retrieved 2026-09-09
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
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this API behaviour. The Order Injection API is named as a product but has no published specification, auth model, versioning policy or rate limits, and access runs through sales. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 326th: MERGE HOLD (proposed no/B, held unknown): the Order Injection API's auth scheme is undocumented; the dashboard bundle bounds the dashboard's own login, not partner API auth. PROPOSAL AS WRITTEN: 326th, MOVED unknown -> no, and a POISON WARNING. CLAIM: third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing). VERDICT: no. POISON: 'oauth' scores 28 word-boundary hits in the dashboard bundle and every single one is AWS Amplify / Cognito library internals for the dashboard's OWN human login - assertOAuthConfig, fe.loginWith.oauth.domain/redirectSignIn/redirectSignOut/responseType, AuthConfigurationErrorCode.OAuthNotConfigureException, and the Cognito hosted-UI URL builder '/oauth2/authorize?...scope=openid email profile&identity_provider=...' used for the Google, Facebook and Apple sign-in buttons. That is consumer social login for staff users, exactly the trap the 325th recorded on this same bundle for the token 'OAuth'. There is no developer portal, no application registration, no scope catalogue and no operator-facing grant or revocation screen; the only machine credential in evidence is the 'api.?key' family (14 hits, Amplify/config internals). ConverseNow publishes no developer documentation of any kind - its site is 8 documents and holds no /docs, and docs.conversenow.ai and api.conversenow.ai do not resolve. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown. (1) Three certspotter-listed hosts no prior pass probed - api-qa-core-service.olivelabs.ai and api-qa-service-management.olivelabs.ai answer 401 on every spec path (/openapi.json, /docs, /swagger.json, /v3/api-docs, /api/openapi.json, /swagger/v1/swagger.json) AND on the nonsense control /zzz-nonsense, so they are blanket-gated, not spec-less; api-qa-performance-insights.olivelabs.ai is 404 on every path incl. root; prod-grafana.olivelabs.ai 302s to a login. (2) Public developer registries: SwaggerHub orgs conversenow/ConverseNow/olivelabs 404; npm search 'conversenow' 0 packages; PyPI 'conversenow' 404; Docker Hub namespace conversenow 0 repos. (3) The olive-backend OpenAPI on api.qa.olivelabs.ai (185 paths, already on disk from the 331st) is the Olive Labs generic BI product (tenants, sso-configurations, llm-api-keys, apps), not the restaurant ordering API. Net: the Order Injection API remains unpublished and gated, so the partner-API merge rule still blocks any capability or cost verdict. Retrieved 2026-09-18. adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this API behaviour. The Order Injection API is named as a product but has no published specification, auth model, versioning policy or rate limits, and access runs through sales. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 326th: MERGE HOLD (proposed no/B, held unknown): a capability claim bounded only by the analytics dashboard bundle and the marketing/legal corpus; the Order Injection API is a named product with no public documentation, so partner-facing webhooks cannot be excluded. PROPOSAL AS WRITTEN: 326th, MOVED unknown -> no. CLAIM: the platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling. VERDICT: no. EVIDENCE: the token 'webhook' scores ZERO word-boundary hits in the entire 7,768,391-byte Olive AI dashboard bundle - a corpus the 325th closed by taking its Vite __vite__mapDeps loader table to a fixpoint - and zero in the 8-document publisher corpus, including both contracts. The dashboard's own data path is polling-shaped: every module is a POST to a /cube/... aggregation endpoint (top-tiles, drilldown, hourly-breakdown, daily-breakdown) with a matching /download for CSV. There is no subscription object, no endpoint registration screen and no event catalogue. BOUND: this is a census of ConverseNow's customer-facing dashboard and of everything the vendor publishes; the Order Injection API itself is undocumented, so a private partner webhook cannot be excluded - but nothing operator-facing exists. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. || 332nd: 332nd, NEW SURFACE, still unknown. ConverseNow's Lever job board (8 live postings via the listing API https://api.lever.co/v0/postings/ConverseNow?mode=json, plus 44 retired posting ids from Wayback CDX, all read) holds one relevant sentence: the retired 2021 posting 'API Integration and Digital Ecosystem Engineer' (Buenos Aires; Wayback 20210810133521 of jobs.lever.co/ConverseNow/17e3957e-9af5-439f-b825-fd8c7b3f4937) asks the hire to 'Be able to design our own APIs and web hooks when necessary' and to 'Design, develop, integrate, deploy, and maintain integration software to connect multiple systems together' across 'multiple integration partners'. That is a 2021 hiring intent, not a shipped order-lifecycle webhook, and it confirms the prior hold's premise that ConverseNow runs an unpublished partner integration layer, so a `no` stays unbounded. 'webhook' 0 in the 8 live postings. Retrieved 2026-09-18. || 334th: 334th, NEW SURFACES, still unknown. (1) Three certspotter-listed hosts no prior pass probed - api-qa-core-service.olivelabs.ai and api-qa-service-management.olivelabs.ai answer 401 on every spec path (/openapi.json, /docs, /swagger.json, /v3/api-docs, /api/openapi.json, /swagger/v1/swagger.json) AND on the nonsense control /zzz-nonsense, so they are blanket-gated, not spec-less; api-qa-performance-insights.olivelabs.ai is 404 on every path incl. root; prod-grafana.olivelabs.ai 302s to a login. (2) Public developer registries: SwaggerHub orgs conversenow/ConverseNow/olivelabs 404; npm search 'conversenow' 0 packages; PyPI 'conversenow' 404; Docker Hub namespace conversenow 0 repos. (3) The olive-backend OpenAPI on api.qa.olivelabs.ai (185 paths, already on disk from the 331st) is the Olive Labs generic BI product (tenants, sso-configurations, llm-api-keys, apps), not the restaurant ordering API. Net: the Order Injection API remains unpublished and gated, so the partner-API merge rule still blocks any capability or cost verdict. 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
326th, MOVED unknown -> no. CLAIM: webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. VERDICT: no, and it fails at the antecedent: ConverseNow ships no webhooks at all ('webhook' 0 word-boundary hits in the 7,768,391-byte bundle and 0 in the publisher corpus), so there is no signature, no backoff and no replay log. 'X-Signature' scores 0 in both corpora; the 22 'HMAC' and 108 'replay' hits in the bundle are AWS Amplify / SigV4 crypto and React-internals poison, none of them a delivery signature or a redelivery queue. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
326th, MOVED unknown -> partial (grade C, marketing page - the API itself is undocumented). CLAIM: a public write API accepts externally originated orders as first-class tickets that fire to KDS/printers and land in reporting. VERDICT: partial. EVIDENCE FOR: 'Order Injection API' is one of ConverseNow's four named products and is described as accepting orders from outside itself - 'Seamlessly integrate AI-powered ordering into your mobile apps and kiosks. Mobile app integration / Kiosk compatibility / Real-time ordering / Custom workflows' - and the whole company's operating model is writing voice-captured orders into the restaurant's existing POS ('We handle integration with your existing hardware ... and your existing software, such as your POS system'). SHORTFALL: it is not PUBLIC in the atlas's sense - there is no specification, no endpoint, no authentication description and no sandbox anywhere. The site is 8 documents with no /docs; docs.conversenow.ai, api.conversenow.ai, app.conversenow.ai and dash.conversenow.ai all fail to connect (curl status 000, not a refusal); api.sandbox.conversenow.ai likewise. And the claim's downstream half - that injected orders fire to KDS/printers and land in reporting - is the host POS's behaviour, not ConverseNow's, and is undocumented either way. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/products.html · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Its integration surface is inbound-to-POS: it writes orders into other systems and publishes no menu-write, accounting, payroll or symmetric-read API. This extensibility capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
API rate limits are published as specific numeric quotas with documented throttling behavior and headers.
extensibility-published-rate-limits
RESOLVED from unknown 2026-09-09. The claim asks for API rate limits published as specific numeric quotas with documented throttling behaviour and headers. rate limit, throttl and quota occur ZERO times across the complete published surface. ConverseNow names an API and documents nothing about it: products.html sells "Order Injection API" with four bullets — "Mobile app integration", "Kiosk compatibility", "Real-time ordering", "Custom workflows" — and there is no reference page, no spec file, no error catalogue and no header documentation anywhere. status.conversenow.ai monitors an "API Server" component, so the interface exists; its contract is simply not published, and access runs through "Book a Consultation". This claim is about PUBLICATION, which is why the firewalled docs.conversenow.ai does not rescue it: quotas documented behind Auth0 SSO to signed-in partners are by definition not published. Bounded to the complete live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters (sitemap 6 locs + the two footer-linked legal pages the sitemap omits; the href set was diffed against the sitemap both ways and is exact, and /products is a byte-identical alias of /products.html). Absence is measurable here: every fabricated path 404s with a body byte-identical to /404.html served verbatim, across fifteen probe shapes including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt and /api/v1/orders, as does every path retired in the 2025 rebuild; the requested path is never echoed into the body. There is no catch-all. Every zero was re-run against the unstripped HTML as well as the stripped text and none is manufactured by the strip. The two hosts that could hold a private answer are named rather than ignored: api., developer. and developers.conversenow.ai are NXDOMAIN, while docs.conversenow.ai (A 34.123.64.3) and app.conversenow.ai (A 142.93.23.88) resolve and drop every TCP connect on 80, 443, 8080 and 22 — docs. was an Auth0 SSO-gated documentation host when Wayback last saw it answer, in 2023. That surface is unmeasured, not absent, and nothing below is bounded to it. https://conversenow.ai/products.html · retrieved 2026-09-09
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
DoorDash publishes its own complete provider registry at https://merchants.doordash.com/api/partner-integrations — 64 providers, each carrying a `qualityStatus` of PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), plus a count of how many of the eight high-quality features the provider has built. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is what the program page means when it says the roster is tracked in real time, and it is a CENSUS rather than a floor: every provider integrated with DoorDash appears in it with a tier, so a vendor that is absent altogether is not in the programme at any tier. This vendor appears nowhere in the 64 entries, under any provider id or friendly name — checked mechanically against both fields, with the only near-misses being substring coincidences (Speedline against Lightspeed, vroom_restaurant against Restaurant365) that were read and rejected. SUPERSEDES the 2026 announcement post most of this corpus cited: that post introduces its ten names with the word `include`, which makes it a floor and never a ceiling, and reading it as a ceiling is what produced this cell's prior grade. GRADE HARMONISED TO B, 2026-09-11: this URL was first written at grade A. The adversarial pass ruled E on the principle that the rubric grades by the publisher's relationship to the SCORED vendor, and DoorDash is not that vendor. B is the settlement, for two reasons that are not preference: 39 rows already graded a DoorDash-published document B on this claim before today, and one URL on one claim cannot carry two grades; and E is unworkable, because nine of the 47 rows are `yes` on a differentiator-weight claim, which the grade floor refuses below B. B reads as the product documentation of the programme's own publisher, which is what this registry is. The dissent is recorded in verification.jsonl. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-11
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Its integration surface is inbound-to-POS: it writes orders into other systems and publishes no menu-write, accounting, payroll or symmetric-read API. This extensibility capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Value re-confirmed by the 2026-08-02 adversarial pass, with the shortfall replaced. Two of the five named middlewares are attested, not one: Deliverect lists ConverseNow in its own integration catalogue, live in Australia, Canada, Mexico, the United Kingdom and the United States, and a November 2023 joint announcement describes the ItsaCheckmate partnership as letting ConverseNow "integrate its AI-powered ordering platform quickly and easily with dozens of POS systems". The shortfall that actually caps this cell is directional: the claim asks whether the POS is a supported endpoint these platforms route orders to, and ConverseNow is the order source using them as its own POS-integration layer. It owns no POS endpoint for anyone to route to. https://www.deliverect.com/en-us/integrations/converse-now · retrieved 2026-08-02 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Its integration surface is inbound-to-POS: it writes orders into other systems and publishes no menu-write, accounting, payroll or symmetric-read API. This extensibility capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Its integration surface is inbound-to-POS: it writes orders into other systems and publishes no menu-write, accounting, payroll or symmetric-read API. This extensibility capability is absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
326th, MOVED unknown -> no. CLAIM: 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. VERDICT: no - and the feature that looks like it in a naive grep is the inverse. POISON, and it decides the direction: the Olive bundle's raw counts of snowflake (11), redshift (6), bigquery (6) and warehouse (10) are almost all an embedded SQL-formatter dialect registry ({mysql, n1ql, plsql, postgresql, redshift, singlestoredb, snowflake, spark, sqlite, tidb, trino...}) plus a Snowflake keyword table (WAREHOUSE_LOAD_HISTORY, CURRENT_WAREHOUSE, SYSTEM$GET_SNOWFLAKE_PLATFORM_INFO). The ONE real Snowflake usage runs the OPPOSITE way to this claim: the dashboard lets a tenant register an INBOUND datastore it will read FROM - {tenant_id, data_stores:[{datastore_type:'Snowflake', config:{schema, account, username, warehouse, auth_method:'private_key'}}]} with the credential values stored encrypted - and then POSTs to https://prod-service.olivelabs.ai/generate_datastore_json/generate_datastore_json/v1 and to a remoteTables endpoint to enumerate that database's tables and columns (fetchDatatables, dataTablesSlice). That is ConverseNow INGESTING the customer's warehouse for analysis, not exporting transaction-level data to a customer-controlled destination. The only egress the dashboard ships is manual CSV: POST /cube/<module>/drilldown/download per report module. 'sftp' 0 hits, 's3' 5 (all AWS SDK internals), no schedule object, no destination configuration, no delivery log. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld and the prior count independently confirmed. The claim requires a public marketplace of named third-party apps an operator can browse and self-install. ConverseNow publishes a heading, "Integration Partners", followed by an unlinked logo strip appearing identically on the home page and products.html. The nine partners are named in the images' own alt text — "Brink POS Logo", "NCR Aloha Logo", "Olo Logo", "PAR Logo", "Qu Logo", "Xpient Logo", "Focus Logo", "Fiserv Logo" and "ItsaCheckmate Logo" — and not one logo carries a link, a listing page, a description or an install action. marketplace, app store, app directory, self-install and one-click occur ZERO times in the frozen corpus. Every path on the site ends at "Book a Consultation"; there is no self-serve anything. Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/products.html · retrieved 2026-09-09
Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.
extensibility-custom-fields-scripting
Re-assessed 2026-08-02 against everything ConverseNow publishes — its six-page site, the product page, the platform-update page, the privacy policy and the newly-published Terms of Use and end-user terms — plus the Deliverect and Olo partner listings, the Qu Intelligent Commerce launch, the Instatus status page, and probes of docs/api/developer/trust subdomains (none resolve). Nothing addresses this API behaviour. The Order Injection API is named as a product but has no published specification, auth model, versioning policy or rate limits, and access runs through sales. This is a disclosure gap, not a determination — ConverseNow publishes no admin guide, help centre or API reference of any kind. || 327th: 327th, NEW SURFACE, still unknown and worth recording because it looks like a hit and is not. The Olive bundle embeds a full SQL authoring workspace - the `sql-formatter` dialect table (snowflake, redshift, bigquery, postgresql, trino, spark, ...), PostgreSQL keyword autocomplete, and a narrative/datastore API set (`/v1/narratives/narrative/`, `/snippets/v1`, `/data-tables/v1`, `/remote_tables/fetch_tables_and_columns/v1`, `/remote_datastores/fetch_databases`, `/tenant/datastores/{id}`) with an encrypted Snowflake connection config and LLM error strings (`LLM_ERROR_WITH_SQL_EXECUTION`, `LLM_ERROR_WITH_SNOWFLAKE_EXECUTION`). That is Olive's own analytics/BI authoring layer running against Olive's Snowflake warehouse, not operator-defined custom fields or vendor-hosted logic against POS objects, and 'custom field' scores 0 across the corpus. Caution for whoever re-reads extensibility-bi-data-warehouse (scored no/B in the 326th): those Snowflake/Redshift/BigQuery tokens are INBOUND dialect names in a formatter plus Olive's own store, not a customer warehouse export, so they do not falsify that no. Retrieved 2026-09-18. || 331st: 331st: 331st, NEW SURFACE, still unknown. showcase.olivelabs.ai / app.showcase.olivelabs.ai has been REBUILT since the 327th read it as a single 4.69 MB bundle. It is now a rolldown/Vite build: the entry HTML names 6 files, the chunk graph reached a fixpoint in 2 rounds, and 60 files (6.66 M chars) came back with 0 misses. The nonsense control /assets/zzz-nope.js returns the SPA's own HTML shell. Route chunks: ActionsPage, AppBuildPage, AppStudioPage, ConnectionsHubPage, DataHubPage, ContextHubPage, NuggetsPage, PublishedAppsPage, RolesPage, TenantsPage, UsersPage, SettingsPage. This is Olive Labs' generic decision-intelligence and app-builder product ('Olive UI'). 'conversenow' 0, 'drive thru' 0, 'franchis*' 0. Its data connections are only Snowflake, Cube and MySQL, and its app builder authors LLM-chat analytics apps over those warehouses. None of it defines custom fields on POS or order objects or runs operator logic against them, and 'custom field' is 0 here too. POISON NAMED: 'script' scores 48, and every hit is a CodeMirror SQL grammar node or React-DOM's script-preload code. Also, this is a demo ('showcase') host of a sibling product line, so it bounds nothing about the ConverseNow ordering product. Retrieved 2026-09-18. adversarially verified
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
Upheld by the 2026-08-02 adversarial pass as the one cell where the Order Injection API is scored in the direction it actually runs: a third-party UI driving an ordering engine by API, marketed as "Mobile app integration", "Kiosk compatibility", "Real-time ordering" and "Custom workflows". Two shortfalls: no specification, auth model, versioning policy or rate limit is published and no developer subdomain resolves; and the engine being driven is a voice ordering engine that writes into a third-party POS, not a POS transaction engine of ConverseNow's own. https://conversenow.ai/products.html · retrieved 2026-08-02 adversarially verified
The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.
extensibility-api-versioning-deprecation
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld and the old rationale's distinction confirmed by opening the page it referred to. insights.html IS the vendor's release-notes surface — its nav label and the eyebrow line above its heading are both "Platform Updates" (the heading itself reads "Latest AI Advancements") — and it holds exactly two entries, "December 2024 - GenAI + Drive-Thru Expansion: A New Era of Real-Time, Scalable Conversational AI" and "May 2025 - AI Your Way", both written to restaurant operators about voice quality and drive-thru throughput. Neither mentions an interface, a version, a field or a contract; the most technical sentence in either is that the drive-thru product gives "your team real time visibility and control through order confirmation boards and your POS system". It is also the only changelog of any kind, and its most recent entry is May 2025 — sixteen months before this retrieval. changelog, change log, release note, deprecat, sunset, end-of-life, breaking change and webhook occur ZERO times in the frozen corpus. The two "version" hits are guest quotations in this same page about the AI release, opened and discarded, and the two API hits are the string inside "rapid" in about.html plus the "Order Injection API" product tile on products.html, which names an API and documents nothing about it. Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/insights.html · retrieved 2026-09-09
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
326th, MOVED unknown -> no. CLAIM: 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. VERDICT: no. EVIDENCE: the published Terms and Conditions for Restaurants contain NO data-return, data-portability, transition-assistance or post-termination export clause of any kind. The contract acknowledges 'Customer Data that you may provide (defined below)' in its Ownership paragraph but the promised definition never appears in the published text, and the agreement's only data obligations run the other way (the customer must erase data it gained unauthorised access to). 'export', 'portability', 'return of data', 'transition' and 'migration' produce zero operator-export commitments across the whole 84,550-character publisher corpus - the two 'portability' hits are the END GUEST's state-law right in the Privacy Policy, not the restaurant's. The vendor publishes no format, no API and no window. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-09-18 adversarially verified
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld and re-homed onto contract language. The claim asks whether order entry, ticket routing and check printing continue on-terminal when the connection is lost. ConverseNow ships no terminal — products.html's complete product set is phone voice, drive-thru voice, SMS and the "Order Injection API" — so there is no on-terminal path to degrade, and the vendor's own terms decline the guarantee outright: end-user-terms 9.1, "No Guarantee of Availability. The Service and Restaurant menus, prices, hours, and availability may change or be unavailable without notice", under a platform provided "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. The documented fallback is human pickup, and the vendor states it as a design property: the archived crew-facing FAQ (capture 2022-07-02, https://web.archive.org/web/20220702025508id_/https://conversenow.ai/voice-ai-frequently-asked-questions/) answers "How do we override this system if needed?" with "Simply press the 'talk' or 'audio' button on your headset and begin speaking. The system will automatically mute the AI and let you handle things from there." That page is withdrawn and is corroboration only; the absence itself rests on the live corpus, where offline, outage, fallback, failover and degraded are all ZERO. Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/end-user-terms.html · retrieved 2026-09-09
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Downgraded from partial by the 2026-08-02 adversarial pass after retrieving the Qu release directly. Its only ConverseNow sentence is "Qu will partner with Bites and ConverseNow to enable direct AI and voice ordering, with every order flowing into the POS" — the edge language ("ICP embeds native intelligence directly in the store, at the edge") describes Qu's own platform, names no discrete edge server and marks no on-premise component generally available. The one ConverseNow-attributed edge statement is a LinkedIn marketing post about running ASR, LLM and TTS on-device: the speech stack, not the ordering path, which the same release places in the POS. The claim requires the vendor to document a local transaction engine for the ordering path; ConverseNow documents nothing, and a partner press release plus a social post is not documentation. || 328th: 328th, per-cell re-grep, still unknown, with three poison tokens that would otherwise read as edge/offline computing. Controls over the 48-file corpus: 'on-premise' 0, 'local mode' 0, degraded 0, 'store-and-forward' 0. POISON 1: 'offline' scores 5 and every hit is a SQL keyword list inside the bundled sql-formatter (Hive '...NOSCAN.NO_DROP.OFFLINE.OPTION...', PostgreSQL '...OFF.OFFLINE.OFFSET.OID...', MySQL). POISON 2: 'failover' scores 12 and every hit is Snowflake DDL in the same formatter ('ALTER FAILOVER GROUP', 'SHOW DATABASES IN FAILOVER GROUP'). POISON 3: 'edge' scores 105 and every bundle hit is MUI's InputAdornment/IconButton `edge` prop - the only genuine edge references remain the retired marketing pages already cited on this cell. Nothing new supports or refutes a local transaction engine. Retrieved 2026-09-18. adversarially verified
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld. The claim asks for an explicit published list of what stops working offline. ConverseNow publishes no such list, and publishes an affirmative refusal to characterise availability at all: end-user-terms 9.1 is headed "No Guarantee of Availability" and reads "The Service and Restaurant menus, prices, hours, and availability may change or be unavailable without notice", while 14.1 provides the Service "AS IS" and "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED and 14.3 disclaims any warranty "THAT THE SERVICE WILL MEET YOUR REQUIREMENTS OR BE ERROR-FREE". The merchant Terms of Use section 6 repeats it verbatim for the operator. There is no uptime percentage, no service credit and no degradation matrix anywhere in the corpus. The vendor once published a status surface shaped like this and never filled it in: the withdrawn /service-updates/ page (capture 2022-08-08) shipped a "Past incidents" table whose only row is the literal placeholder "xx/xx/xx" / "Issue: (Add description)" / "Status: Resolved or Working to resolve", and /conversenow-incident-report/ (capture 2022-05-19) is a title and a contact form with no body. Today status.conversenow.ai supersedes both, and it publishes component state only — "API Server", "POS Server" and a collapsed "Downstream Services" group, each at 100% over 90 days — which is liveness, not an offline feature matrix. offline, off-line, outage and degraded occur ZERO times in the frozen corpus. Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/end-user-terms.html · retrieved 2026-09-09
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Upheld by the 2026-08-02 adversarial pass, loaded independently with no credentials. A public Instatus page lists three components — API Server, POS Server and a Downstream Services group — each with its own state and a 100.0% uptime figure, plus "No notices reported for the past 7 days", a link to 90 days of notice history, and subscription by email, Slack or Microsoft Teams. Per-component, current and historical, no login. Caveat for readers: the page is not linked from conversenow.ai and does not appear in its sitemap — it was found by subdomain probe, so an operator would not discover it unaided. https://status.conversenow.ai/ · retrieved 2026-08-02 adversarially verified
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
The published Terms of Use disclaim the opposite of an SLA: "THE PLATFORM AND SERVICES ARE PROVIDED ON AN 'AS IS' AND 'AS AVAILABLE' BASIS", and ConverseNow does "NOT WARRANT THAT ... THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE." No uptime percentage, no service-credit remedy and no support/SLA section appear anywhere in the document; liability is capped at fees paid in the prior twelve months. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-08-02
The vendor publishes written post-incident reports or root-cause summaries for major outages.
reliability-incident-postmortems
The Instatus page carries only a rolling notice feed ("No notices reported for the past 7 days") with no incident write-ups, and the vendor site publishes platform release notes (Dec 2024, May 2025) but no root-cause or post-incident reports. Notices are not postmortems. https://status.conversenow.ai/ · retrieved 2026-08-02
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
Shortfall: 24-hour-a-day live support is asserted unqualified on the home page, but the claim also requires that it be included in the base subscription rather than sold as a premium tier, and ConverseNow publishes no plans at all against which inclusion could be checked - pricing is quote-only and the fee is referred to an unpublished order form. The claim also asks specifically for phone support, and the only support telephone number ever published is on a withdrawn page. https://conversenow.ai/ · retrieved 2026-09-09
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
333rd, MOVED unknown -> partial/C, on a NEW SURFACE never read by this record: the ACQUIRED SUBSIDIARY's own site (valyant.ai, Wayback) plus ConverseNow's own acquisition release. This answers the 332nd hold ('no installation or go-live offering is named'): an on-site setup offering IS named, by a ConverseNow-owned brand, after the acquisition. CLAIM: the vendor offers in-person on-site installation and go-live support (first-party or certified dealer), not remote-only self-install. VERDICT: partial - an on-site hardware setup service for the drive-thru product is published by ConverseNow's Valyant AI brand; it is not published on conversenow.ai itself, the surface is now retired (domain lapsed), and no go-live/cutover visit is described. EVIDENCE: (1) ConverseNow press release, July 9, 2024 (vendor-authored, PR Newswire): headline 'ConverseNow Acquires Valyant AI - Integrating Valyant's Complementary Technology Stack to Accelerate ConverseNow's Drive-Thru Installations'; body: 'The transaction sees Valyant AI's entire team and technology join the ConverseNow family'; 'Valyant's patented technology and proprietary hardware, combined with seamless POS integration, perfectly complement ConverseNow's modern AI stack'; 'Holly ... integrates directly via proprietary hardware into existing drive-thru communications systems such as PAR, HME'; 'For the foreseeable future, the companies will continue to service customers under their respective brands' (https://www.prnewswire.com/news-releases/conversenow-acquires-valyant-ai---integrating-valyants-complementary-technology-stack-to-accelerate-conversenows-drive-thru-installations-302190895.html). (2) valyant.ai/cost.html, Wayback 20250424234329 (NINE MONTHS AFTER the acquisition; same text in 20220126084647, 20220528172039, 20230925034646): 'We'll ensure onsite setup of our proprietary hardware is successful, and integration with your point-of-sale and employee training are all coordinated to deliver superior financial performance.' (3) valyant.ai home, Wayback 20250816060436: 'This includes integrating with any required onsite hardware and on-premise or cloud point of sale (POS) systems. Our platform includes custom-built hardware'; drive-thru.html (20220126072708): 'Our patented NX-1A hardware integrates directly with your existing headset systems, including the HME ION and EOS platforms and 3M / Par XT1 and G5'. (4) Consistent, already in the record: Lever posting 'Associate Engineer (Job ID: 2275)', team Drive-Thru, 'Willingness to travel 1/3 of the time to on-site Drive-Thru locations'; T&Cs for Restaurants: restaurant must 'provide ConverseNow personnel with such access to your premises'. SHORTFALL / WHY NOT yes: the on-site setup sentence is Valyant-branded, not on conversenow.ai; valyant.ai no longer serves it (the domain now hosts an unrelated Australian tax-calculator site, sitemap 14 URLs, none Valyant) so it is a retired surface and positives cap at partial; the phone channel is integrated remotely ('Just send us your menu', retired /technology/); and 'installations' in the release headline counts deployments, not a service description. Grade C: vendor press release + vendor marketing page. CENSUS of the new surface: Wayback CDX for valyant.ai/* = 80 rows, 14 distinct HTML/PDF paths (home, cost, drive-thru, kiosk, mobile, web, call-ahead, sms, speakers, security, team, contact, case-study PDF), all read; 'onsite' appears on cost and home only. Corpus: .cache/q333/conversenow/b/vlw_*, vl_cost_2025.html, vl_home_2025.html, prn_valyant.html. Retrieved 2026-09-18. https://web.archive.org/web/20250424234329/https://valyant.ai/cost.html · retrieved 2026-09-18 adversarially verified
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.
reliability-backup-restore
CLAIM: operators can trigger and retrieve their own data backup/restore, OR the vendor publishes RPO/RTO figures. VERDICT: no - both disjuncts fail against a bounded corpus. EVIDENCE/BOUND: the corpus is the complete Olive analytics app (entry bundle + its one declared lazy chunk; 203 endpoints, none of which is a backup, restore, snapshot or export-all route), the 8-page conversenow.ai site, its three legal documents (Terms of Use, End User Terms, Privacy Policy), the platform-update page, and the rebuilt olivelabs.ai marketing site. Tokenised controls: RPO 0, RTO 0, 'point-in-time' 0, 'data recovery' 0, disaster 0 across every file. POISON NAMED, and it is the whole of the apparent signal: `backup` and `restore` score 29 and 115 hits, but the breakdown is `restoreFocus`/`disableRestoreFocus`/`restoreTextDirection` (MUI), `restoreStateFrom`/`restoreHandlers`/`stateRestoreInProgress` (Redux and MSW), `restoreConversation` (the chat panel), and PG_BACKUP_START_TIME / PG_STOP_BACKUP / PG_IS_IN_BACKUP / PG_CREATE_RESTORE_POINT, which sit inside a dotted list of PostgreSQL built-in function names used by a SQL-editor autocomplete - not a product feature. No operator-triggerable backup exists and no recovery objective is published. Retrieved 2026-09-18. https://app.olivelabs.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
326th, MOVED unknown -> no. CLAIM: the vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent covering the post-March-2025 future-dated requirements. VERDICT: no - nothing of the kind is published anywhere. EVIDENCE: ConverseNow states in its own Privacy Policy that it collects primary account number AND card security code: 'Payment Data. We collect data necessary to process your payment if you make a purchase, including your payment instrument number (such as a credit card number) and the security code associated with your payment instrument.' Against that, the word-boundary counts for PCI, 'Payment Card Industry', P2PE, SAQ, AOC, 'Attestation of Compliance', tokenization, token, encrypt and encryption are ALL ZERO across the complete 8-document, 84,550-character publisher corpus - including the whole Terms and Conditions for Restaurants and the End-User Terms of 27 May 2026 - and there is no /security, /trust or /compliance page in the site's link fixpoint or its sitemap. The contract's only security-adjacent language is a disclaimer running the other way: 'CONVERSENOW DOES NOT WARRANT THAT ... (B) THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE ... (D) ANY CONTENT OR INFORMATION YOU PROVIDE OR CONVERSENOW COLLECTS WILL NOT BE DISCLOSED'. SCOPE CAVEAT FOR THE OWNER: the End-User Terms also say 'The Restaurant remains the sole seller and merchant of record for your order; it determines pricing and taxes, receives payment', and every published sample call ends 'you can pay for this order at the store', so ConverseNow may not be in the cardholder data environment for most deployments - but its own Privacy Policy says it collects PAN and CVV, so the claim is not inapplicable, it is unanswered by the vendor. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
CLAIM: MFA enforceable on back-office and POS administrative logins, WITH role-based permissions. VERDICT: partial (from unknown). EVIDENCE for the role half: the ConverseNow dashboard ships a full RBAC admin at routes /roles, /add-role, /edit-role/:roleId, /users, /users/:userId, with UI 'Roles and Permissions', 'Add/Edit Role', 'Create Role', 'Delete Role', 'Role Title', 'Role Description', 'Map Role Permissions', 'Permissions', 'Module', 'Allowed Apps', 'Allowed Domains', 'Select All', 'Deny', 'At least one permission is required. Do you want to proceed?', users carrying role_ids:[] and status, and a change history ('Role History', 'User history logs', 'Previous role', 'Updated role', 'By <user_name> (<user_email>)'). The permission names are app_access, access_users, access_roles, access_domains, olive_read_only_access, olive_crud_access. SHORTFALL: the MFA half is UNEVIDENCED and must not be read off this bundle - all 69 'MFA' and 20 'TOTP' occurrences belong to the bundled AWS Amplify auth library (FetchMFAPreference, UpdateMFAPreference, SetUpTOTP, VerifyTOTPSetup, 'Incorrect MFA method was chosen. It should be either SMS, TOTP, or EMAIL'); 'multi-factor' has 0 hits and there is no MFA administration screen, enforcement toggle or policy anywhere in the app. There is also no POS-terminal login surface at all in this product. The only auth control the vendor states is password strength: 'Password must contain at least 12 characters', plus lower case, upper case and a number. NEW SURFACE (never mined before this session): crt.sh on conversenow.ai returned 173 distinct names; almost all are dead (NXDOMAIN) tenant hosts, but olive.analytics.conversenow.ai is LIVE and PRODUCTION (a separate olive.analytics.staging.conversenow.ai exists in the CT log, so this is the prod copy). It serves a Vite SPA titled 'Olive AI'. Its login copy is ConverseNow's: 'Use your account credentials to access the ConverseNow dashboard', 'Please enter a valid email linked to your ConverseNow account', and BRAND_URL_MAPPINGS={conversenow:['olivelabs.ai/olive','analytics.conversenow.ai/olive','olive.analytics.conversenow.ai',...],olive:[]} with a ConverseNow logo asset (/converse_now/Converse-Now-Logo-RGB.png) and footer links to conversenow.ai/privacy-policy.html and conversenow.ai/terms-and-conditions.html. CENSUS: the Vite loader table is complete and closed - const __vite__mapDeps=(i,m,d=(m.f||(m.f=['assets/forecastRealData-CA3-729w.js','assets/_sentry-release-injection-file-Bv3kP-4K.js']))) - so the whole app is 3 files (index 2,263,314 B + forecast chunk 3,950 B + sentry shim); the forecast chunk contains no further loader entries, so the fixpoint closed in 1 round with 0 misses. No source maps: <bundle>.js.map returns the 446-byte SPA shell and so does the nonsense control <bundle>.js.NONSENSE.map and /zzz-nonsense-path, byte-identical - so those .map 200s are soft-200s and were not used. Identifiers are NOT minified in this build, so component, tab, column and endpoint names are the vendor's own. POISON FOUND AND EXCLUDED: (a) the bundle embeds a Snowflake SQL-function autocomplete dictionary, so the single 'SCIM' hit is SYSTEM$GENERATE_SCIM_ACCESS_TOKEN and several 'SAML' hits are SYSTEM$GENERATE_SAML_CSR / SYSTEM$MIGRATE_SAML_IDP_REGISTRATION - not features; (b) every 'MFA'/'TOTP' string (69/20 hits) comes from the bundled AWS Amplify auth library (FetchMFAPreference, SetUpTOTP, IncorrectMFAMethod) - library code, not a configured policy; (c) the app also ships DEMO apps for video games, HR and SaaS finance whose data comes from chunkedMockApiService/mockApiService (11 hits) - all 36 'cohort' hits, LTV, DAU and retention-heatmap strings are that MOCK game app and are NOT ConverseNow capability. Only endpoints under API_BASE$1='/api/summary-dashboard', API_BASE_CUBE='${API_BASE$1}/cube' and API_BASE='/api/dt-scorecard/cube' (68 hits, withCredentials:true) are live tenant data. Retrieved 2026-09-17. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-17 adversarially verified
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld, and the vendor states the absence affirmatively rather than merely omitting it. The claim wants a public free training library and a practice/training mode on the terminal; there is no terminal, and there is no library. academy, university, tutorial, webinar, practice mode, training mode and sandbox occur ZERO times in the frozen corpus, on both loose-stem and word-boundary runs. Two near-misses, disclosed: the apparent LMS hit is the string inside "LLMs" in about.html, and courses is zero only in the plural — the singular occurs once as "Of course!" in the home-page order transcript. Neither is a training library. Both apparent training hits are homonyms, opened and discarded: end-user-terms 11.3 is model training ("ensure quality, analytics, and training of models") and the merchant Terms of Use section 3 is a licence restriction forbidding use "for third-party training, commercial time-sharing, rental, or service bureau use". The two learning-family hits are "machine learning" in the same terms and a company-history line in about.html. The public zero is bounded on one surface beyond the site itself: the YouTube channel linked from the footer of every page, youtube.com/@conversenow8500, holds exactly TWO videos, "Complex Order with Upsell" and "ConverseNow: Voice AI for Restaurants" — both product demos, neither training material. That closes the last plausible route to a public library. Corroboration only, and not the ground of the verdict: the archived technology page (capture 2022-05-19, https://web.archive.org/web/20220519143710id_/https://conversenow.ai/technology/) advertised "No staff training required" and "No staff training needed", and the nearest thing to crew material ConverseNow ever published is one withdrawn FAQ page. Both are withdrawn, so neither carries the absence; the verdict rests on the bounded live zero. Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/products.html · retrieved 2026-09-09
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. It operates no terminal, card path, LAN or printer, so the terminal-level resilience behaviours this claim describes have no surface to exist on; the documented fallback when the AI cannot handle a call is human pickup. Absent by product scope rather than restricted. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
326th, MOVED unknown -> no, on the customer contract this record has never held. CLAIM: vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core tier. VERDICT: no - nothing of the kind is offered publicly. EVIDENCE: the Terms and Conditions for Restaurants presuppose a committed term whose length is NOT published, deferring it to a private order form: 'ConverseNow charges you a subscription fee for Services in the amount set forth in the order form or invoice. ConverseNow may bill you directly or may collect these fees using a third party payment service and using a recurring payment system that recurs on an monthly, quarterly or annual basis. You will be charged the service fee on the first day of the Initial Term or each Renewal Term, as applicable.' 'Initial Term' and 'Renewal Term' are used as defined terms but are never defined in the published text, and the contract contains no termination-for-convenience clause, no notice period and no term length; 'month-to-month' scores 0 word-boundary hits in the whole publisher corpus, as does any published price (there is no pricing page - the site's call to action is 'Book a Consultation'). The only termination right the published contract grants is ConverseNow's: 'We may restrict access to your account or terminate this Agreement if you fail to make a payment when due.' BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-09-18 adversarially verified
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
Upheld by the 2026-08-02 adversarial pass, which enumerated all thirteen Terms of Use headings — Services, Customer Obligations, Access, Privacy and Confidentiality, Service Fees and Billing Methods, Limitation of Warranties, Limitations of Liability, Indemnification, Notice, Governing Law, Dispute Resolution, Publicity, Miscellaneous. There is no Term, Termination, Renewal or liquidated-damages section. The claim asks whether published terms state that no early termination fee applies; they verifiably do not, which is positive evidence of absence of a published commitment. This is not a finding that an ETF exists — exit economics sit in the unpublished order form, and pricing.early_termination_fee correctly remains unknown. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-08-02 adversarially verified
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 public Terms of Use now exists — the prior pass found only a privacy policy — and it is silent on renewal: no Term section, no Termination section, no auto-renewal period and no cancellation notice window. Section 5 covers only billing frequency, 30-day payment terms and 1.5%-per-month late interest. The document carries no effective or last-updated date. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-08-02
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
Upheld by the 2026-08-02 adversarial pass against the contract text. End-user terms section 8.3 states verbatim: "Pricing, payment processing, taxes, and receipts are handled by the Restaurant or its payment processors", directing billing and refund questions to the Restaurant. Terms of Use section 5 charges only "a subscription fee for Services in the amount set forth in the order form or invoice" — no merchant account, processing schedule or rate language anywhere in its thirteen sections. ConverseNow is neither acquirer nor PayFac and cannot lock a settlement path it does not touch. Caveat carried forward: the CIPA litigation record indicates the AI takes card details by phone, so the tokenisation and handoff path is undocumented — a payments-security unknown, not a bundling one. https://conversenow.ai/end-user-terms.html · retrieved 2026-08-02 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Combined with the published Terms of Use and end-user terms retrieved 2026-08-02 — which cover only subscription fees, IP, warranty disclaimers and liability — this commercial term or capability is not offered and not published. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
326th, MOVED unknown -> no. CLAIM: the agreement caps or prohibits unilateral vendor-initiated rate increases outside pass-through interchange/network changes, or grants penalty-free exit on any increase. VERDICT: no - the published contract does the opposite on both halves. EVIDENCE: amendment is unilateral and discretionary - 'This Agreement may be modified by ConverseNow from time to time at our sole discretion, and you may be notified as set forth below' - and the notice provision it points to permits posting alone: 'ConverseNow may communicate any notices to you under this Agreement, through electronic mail, regular mail or posting the notices on the Platform.' Section 5 fixes fees only by reference to the order form and contains no cap, no index, no notice period before a fee change and no right of exit on an increase; the only fee mechanic stated is punitive and runs against the customer ('If you fail to remit payment within ten (10) days of the due date, ConverseNow may assess interest on the amount past due in the amount of 1-1/2% per month'). 'cap', 'increase' and 'escalat*' produce no rate-protection language anywhere in the corpus. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-09-18 adversarially verified
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
Terms of Use section 5, Service Fees and Billing Methods: "ConverseNow charges you a subscription fee for Services in the amount set forth in the order form or invoice", billed "monthly, quarterly or annual". Pricing is explicitly per-deal and lives in the order form. No dollar figure and no pricing page exists on the site; the sitemap lists six pages and none is commercial. Better sourced than the prior pass, which could only cite the sitemap. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-08-02
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
Four distinct products are marketed separately, but no commercial terms confirm they can be bought or cancelled à la carte. || 325th: 325th, NEW SURFACE (a real legal document, never read by this record), still unknown. 'Deal Registration Terms and Guidelines' (retired page, Wayback capture 20211204203916 of conversenow.ai/deal-registration-terms, 18,167 chars of text) establishes that ConverseNow Technologies runs a channel programme - a 'ConverseNow Technologies Partner Program', a 'Solution Provider track', authorised Distributors, a Partner Portal deal-registration tool, 60-day registration terms and a 'Minimum Deal Size set forth in the Regional Specific Addendum'. It settles nothing about the claim: it never lists purchasable modules and never says anything can be bought or cancelled a la carte; the only unbundling-adjacent line is that deal size counts 'Only ConverseNow products and/or services ... third-party products and services are not included'. AUDIT FLAG for whoever next touches commercial-hardware-not-locked (today partial, on the reasoning that ConverseNow sells no hardware): this document repeatedly contemplates ConverseNow HARDWARE sold through the channel - 'The hardware products subject to the deal registration are designated by ConverseNow Technologies as new (i.e., not refurbished) products' - though the page is retired, 2021, and reads as adapted boilerplate. Also re-derived today: conversenow.ai is no longer the WordPress/Elementor site the old notes describe. It is now a static GitHub Pages site (Server: GitHub.com, Last-Modified 2026-05-29) whose robots.txt allows all and whose sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html), plus terms-and-conditions.html and end-user-terms.html linked from the footer: 8 pages total, and every other path returns the same 1,910-byte 404 (control: /zzz-nonsense.html). The retired WordPress corpus was enumerated from Wayback CDX (1,354 captures; ~60 distinct non-asset HTML paths) and several of those retired pages have never been read by this record - see the rows in this file. Retrieved 2026-09-17. || 328th: 328th, the rebuilt site's 'Terms and Conditions for Restaurants' read against THIS cell for the first time (the existing note predates the document). It does not settle the claim, and it shows why nothing published can. Section 5 Service Fees and Billing Methods says only: 'ConverseNow charges you a subscription fee for Services in the amount set forth in the order form or invoice' and 'You will be charged the service fee on the first day of the Initial Term or each Renewal Term, as applicable.' 'Initial Term' and 'Renewal Term' are capitalised but NEVER DEFINED anywhere in the published contract, and the agreement contains no term, renewal-notice or termination-for-convenience clause at all - its only termination right is ConverseNow's, for non-payment ('We may restrict access to your account or terminate this Agreement if you fail to make a payment when due'). Every commercial variable therefore lives in an unpublished order form, so whether the four products can be bought or cancelled a la carte is unmeasurable from the publication surface in either direction. Retrieved 2026-09-18. || 331st: 331st: 331st, NEW SURFACE (retired contract), still unknown. The retired Terms of Service (Wayback 20210731114850 of www.conversenow.ai/terms-of-service/, 36,007 chars; and 20200925041412 of /terms-of-service.php) is the predecessor of today's restaurant T&Cs. It DOES carry the 'Term and Termination' section that the current document lacks: 'The initial term of this Agreement commences on the Effective Date in the order form ... until the date set forth in such order form (the "Initial Term")' and 'This Agreement will automatically renew ... for a term of equal duration ... unless ... either party gives the other party written notice of non-renewal at least thirty (30) days prior to the expiration of the then-current Term'. It also says 'UNLESS AND UNTIL YOU CANCEL YOUR SUBSCRIPTION TO THE SERVICES ... YOUR SUBSCRIPTION ... WILL AUTOMATICALLY RENEW'. Cancellation and renewal apply to the whole subscription to 'the Services', and the price is again left to the order form. Controls over both captures: 'module' 0, 'separately' 0, 'a la carte' 0. Nothing is said about buying or cancelling ConverseNow's products individually. Retired document, so it is corroboration only. Retrieved 2026-09-18. || 334th: 334th, NEW SURFACE, still unknown. olivelabs.ai (the host that serves the same Olive dashboard bundle index-DXIYe81a.js as olive.analytics.conversenow.ai) has a 19-URL sitemap whose pages no prior pass read as text (all 19 fetched, 200; /llms.txt and a nonsense control are 404 at 11,403 bytes). It is a separate 'Olive Labs' decision-intelligence company site (CEO Krish Ravikumar, CTO Siddhartha Sharma; 'Olive Studio' for gaming live-ops, 'Model Fabric' LLM routing). It carries no ConverseNow product, no price, no plan and no module list: tokenised 'pricing' hits are all gaming price-point use cases ('$9.99 Starter Pack'), 'bundle' hits are in-game bundles (POISON). Nothing about buying ConverseNow's four products separately. The rebuilt conversenow.ai sitemap is unchanged at 6 URLs and the live products page's only commercial-shaped line is 'Localization - Menu, pricing, and behavior tuned by region/store' (menu behaviour, not commercial terms). Retrieved 2026-09-18. adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Combined with the published Terms of Use and end-user terms retrieved 2026-08-02 — which cover only subscription fees, IP, warranty disclaimers and liability — this commercial term or capability is not offered and not published. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
Shortfall: ConverseNow mandates no proprietary device and its contract puts equipment on the operator as Customer Systems, but the claim asks the vendor to DOCUMENT support for at least one named non-proprietary option, and it names none - printer, cash drawer, iPad, ESC/POS and Epson are a bounded zero across the complete published surface. The only naming it ever published (drive-thru base stations and phone lines) is on a withdrawn 2022 page and cannot carry current documentation. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-09-09
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
commercial-implementation-fee-published
Terms of Use section 5 contemplates only a subscription fee "set forth in the order form or invoice". No implementation, onboarding, menu-build or training fee is published as an amount, and none is stated to be $0. https://conversenow.ai/terms-and-conditions.html · retrieved 2026-08-02
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
326th, MOVED unknown -> partial. CLAIM: 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. VERDICT: partial - self-serve CSV is real, the scope is not full. EVIDENCE FOR: the Olive AI dashboard ships a download endpoint beside every report module - POST /cube/all-orders/... with /orders-drilldown/download, and /cube/upsell/drilldown/download - i.e. the operator pulls CSV themselves, with no support ticket and no gate in the shipped code. EVIDENCE AGAINST, every remaining conjunct: there is no line-item or modifier dimension in the app at all (this record's reporting-pmix-modifier-level note shows all 240 'modifier' tokens are React/popper internals), ConverseNow holds no payments of its own (the End-User Terms make the Restaurant 'the sole seller and merchant of record ... receives payment'), and there is no labour module. And the contract restricts what may be done with even the data you get: 'you shall not ... (c) disclose any performance information or analysis from any source relating to the Platform without prior written consent from ConverseNow.' BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js · retrieved 2026-09-18 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Combined with the published Terms of Use and end-user terms retrieved 2026-08-02 — which cover only subscription fees, IP, warranty disclaimers and liability — this commercial term or capability is not offered and not published. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
RESOLVED from unknown 2026-09-09. The claim asks for a defined post-termination window in which the operator can still export their data. Neither published contract contains one, and the end-user terms make the omission explicit rather than merely silent: section 18, Termination, reads "We may suspend or terminate your access to the Service at any time, including for suspected fraud, misuse, or violations of these Terms. You may stop using the Service at any time", and its survival enumeration — "Sections intended to survive (including ownership, disclaimers, limitations, indemnity, dispute resolution, and privacy) will survive termination" — lists six categories and no data-return obligation among them. The merchant Terms of Use has no termination section at all; its only termination right is for non-payment ("We may restrict access to your account or terminate this Agreement if you fail to make a payment when due"). retrieval window and wind-down occur ZERO times in the corpus. Bounded to the complete live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters (sitemap 6 locs + the two footer-linked legal pages the sitemap omits; the href set was diffed against the sitemap both ways and is exact, and /products is a byte-identical alias of /products.html). Absence is measurable here: every fabricated path 404s with a body byte-identical to /404.html served verbatim, across fifteen probe shapes including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt and /api/v1/orders, as does every path retired in the 2025 rebuild; the requested path is never echoed into the body. There is no catch-all. Every zero was re-run against the unstripped HTML as well as the stripped text and none is manufactured by the strip. The two hosts that could hold a private answer are named rather than ignored: api., developer. and developers.conversenow.ai are NXDOMAIN, while docs.conversenow.ai (A 34.123.64.3) and app.conversenow.ai (A 142.93.23.88) resolve and drop every TCP connect on 80, 443, 8080 and 22 — docs. was an Auth0 SSO-gated documentation host when Wayback last saw it answer, in 2023. That surface is unmeasured, not absent, and nothing below is bounded to it. https://conversenow.ai/end-user-terms.html · retrieved 2026-09-09
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
Re-sourced onto the actual contract documents. The Terms of Use vest all Platform IP in ConverseNow "Excluding any Customer Data that you may provide" — a carve-out, not an affirmative merchant-ownership grant — and nothing constrains ConverseNow's own use. The end-user terms then do the opposite of constraining it, in capitals: "YOUR PHONE CALLS AND VOICE INTERACTIONS WILL BE RECORDED, MONITORED, AND ANALYZED TO IMPROVE OUR VOICE AI SOFTWARE. BY USING THE SERVICE, YOU CONSENT TO SUCH RECORDING". Guest conversation data is expressly used for ConverseNow's own product improvement, the exact use the claim requires to be limited. https://conversenow.ai/end-user-terms.html · retrieved 2026-08-02 adversarially verified
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Combined with the published Terms of Use and end-user terms retrieved 2026-08-02 — which cover only subscription fees, IP, warranty disclaimers and liability — this commercial term or capability is not offered and not published. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
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
326th, MOVED unknown -> no. CLAIM: 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. VERDICT: no - no SAQ is named, and P2PE and tokenization are never mentioned. EVIDENCE: ConverseNow states in its own Privacy Policy that it collects primary account number AND card security code: 'Payment Data. We collect data necessary to process your payment if you make a purchase, including your payment instrument number (such as a credit card number) and the security code associated with your payment instrument.' Against that, the word-boundary counts for PCI, 'Payment Card Industry', P2PE, SAQ, AOC, 'Attestation of Compliance', tokenization, token, encrypt and encryption are ALL ZERO across the complete 8-document, 84,550-character publisher corpus - including the whole Terms and Conditions for Restaurants and the End-User Terms of 27 May 2026 - and there is no /security, /trust or /compliance page in the site's link fixpoint or its sitemap. The contract's only security-adjacent language is a disclaimer running the other way: 'CONVERSENOW DOES NOT WARRANT THAT ... (B) THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE ... (D) ANY CONTENT OR INFORMATION YOU PROVIDE OR CONVERSENOW COLLECTS WILL NOT BE DISCLOSED'. SCOPE CAVEAT FOR THE OWNER: the End-User Terms also say 'The Restaurant remains the sole seller and merchant of record for your order; it determines pricing and taxes, receives payment', and every published sample call ends 'you can pay for this order at the store', so ConverseNow may not be in the cardholder data environment for most deployments - but its own Privacy Policy says it collects PAN and CVV, so the claim is not inapplicable, it is unanswered by the vendor. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
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
326th, MOVED unknown -> no. CLAIM: 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 payment-page script-integrity monitoring per Req 6.4.3/11.6.1. VERDICT: no. Neither conjunct is documented: the publisher corpus never names PCI DSS, and the back-office login the vendor actually ships is single-factor by configuration - the Olive AI dashboard's Authentication Config screen exposes independent toggles for password_enabled, sso_enabled, google_login_enabled, facebook_login_enabled and apple_login_enabled, with no MFA, OTP or step-up control anywhere in the 7.77 MB bundle. EVIDENCE: ConverseNow states in its own Privacy Policy that it collects primary account number AND card security code: 'Payment Data. We collect data necessary to process your payment if you make a purchase, including your payment instrument number (such as a credit card number) and the security code associated with your payment instrument.' Against that, the word-boundary counts for PCI, 'Payment Card Industry', P2PE, SAQ, AOC, 'Attestation of Compliance', tokenization, token, encrypt and encryption are ALL ZERO across the complete 8-document, 84,550-character publisher corpus - including the whole Terms and Conditions for Restaurants and the End-User Terms of 27 May 2026 - and there is no /security, /trust or /compliance page in the site's link fixpoint or its sitemap. The contract's only security-adjacent language is a disclaimer running the other way: 'CONVERSENOW DOES NOT WARRANT THAT ... (B) THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE ... (D) ANY CONTENT OR INFORMATION YOU PROVIDE OR CONVERSENOW COLLECTS WILL NOT BE DISCLOSED'. SCOPE CAVEAT FOR THE OWNER: the End-User Terms also say 'The Restaurant remains the sole seller and merchant of record for your order; it determines pricing and taxes, receives payment', and every published sample call ends 'you can pay for this order at the store', so ConverseNow may not be in the cardholder data environment for most deployments - but its own Privacy Policy says it collects PAN and CVV, so the claim is not inapplicable, it is unanswered by the vendor. BOUND/CORPUS (new this session): the conversenow.ai site was REBUILT and now publishes THREE legal documents that this record has never held, none of which is in its sitemap. sitemap.xml lists 6 URLs (/, products.html, about.html, book-demo.html, insights.html, privacy-policy.html, lastmod 2026-05-29) and robots.txt is 'User-agent: * / Allow: / / Disallow: /404.html' - no bar. Following the in-page links to a fixpoint gives the whole site: index, products, about, insights, book-demo, privacy-policy.html, terms-and-conditions.html ('TERMS AND CONDITIONS FOR RESTAURANTS' - the CUSTOMER contract, 16,339 chars of stripped text), end-user-terms.html ('END-USER TERMS FOR VOICE AI ORDERING, EFFECTIVE DATE: MAY 27, 2026', 17,170 chars) and privacy-policy.html ('Last Modified: May 14, 2026', 30,257 chars) - 8 documents, 84,550 chars, plus the 'Platform Updates' changelog at insights.html (two entries, May 2025 and December 2024). The published product set is still exactly four: Phone Order AI, Drive-Thru Automation, SMS AI Conversations and Order Injection API. Second corpus: the vendor's own shipped Olive AI dashboard bundle (https://olive.analytics.conversenow.ai/assets/index-DXIYe81a.js, 7,768,391 bytes), which the 325th took to a Vite loader fixpoint; I re-ran tokenised controls over it. HOST NOTE: docs., api., app., dash. and analytics.conversenow.ai all fail to connect (curl exit 7 / status 000), so olive.analytics.conversenow.ai remains the only reachable app host; the bundle names a second production host family, app.olivelabs.ai and prod-service.olivelabs.ai, which no prior pass has recorded. The GCS bucket storage.googleapis.com/conversenow is NOT listable (401 storage.objects.list denied). POISON PUBLISHED: the Olive bundle embeds an SQL-formatter dialect table and a Snowflake keyword list, so raw word-boundary counts of snowflake (11), redshift (6), bigquery (6), warehouse (10), saml (24), scim (1), audit (12) and export (64) are mostly 'SYSTEM$GENERATE_SAML_CSR', 'SYSTEM$GENERATE_SCIM_ACCESS_TOKEN', 'WAREHOUSE_LOAD_HISTORY', 'EXPORT DATA' and a {postgresql, redshift, snowflake, spark, trino, tidb...} dialect registry - every one of those tokens has to be read in context before it counts. Retrieved 2026-09-18. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-18 adversarially verified
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
RESOLVED from unknown 2026-09-09. The claim asks whether the vendor states it holds a current SOC 2 Type II or ISO 27001 attestation and will provide the report. Across the complete published surface, SOC 2, SOC2, ISO 27001, trust center, attestation and penetration test occur ZERO times. The privacy policy is the one document where such a statement would live, and instead of an attestation it publishes a disclaimer: ConverseNow warns that "no method of electronic transmission or storage is completely secure, and we cannot guarantee the security of your Protected Information" and makes "no promise, representation, or warranty regarding the security of your Protected Information". That is an affirmative refusal to warrant security, which is the opposite of the third-party check this claim asks for. Bounded to the complete live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters (sitemap 6 locs + the two footer-linked legal pages the sitemap omits; the href set was diffed against the sitemap both ways and is exact, and /products is a byte-identical alias of /products.html). Absence is measurable here: every fabricated path 404s with a body byte-identical to /404.html served verbatim, across fifteen probe shapes including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt and /api/v1/orders, as does every path retired in the 2025 rebuild; the requested path is never echoed into the body. There is no catch-all. Every zero was re-run against the unstripped HTML as well as the stripped text and none is manufactured by the strip. The two hosts that could hold a private answer are named rather than ignored: api., developer. and developers.conversenow.ai are NXDOMAIN, while docs.conversenow.ai (A 34.123.64.3) and app.conversenow.ai (A 142.93.23.88) resolve and drop every TCP connect on 80, 443, 8080 and 22 — docs. was an Auth0 SSO-gated documentation host when Wayback last saw it answer, in 2023. That surface is unmeasured, not absent, and nothing below is bounded to it. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-09
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
RESOLVED from unknown 2026-09-09. This cell was left unknown by the 2026-08-02 adversarial pass because a privacy policy cannot establish that DSAR tooling EXISTS. It can, over a complete corpus, establish that it does not: the claim asks for in-app tooling to locate, export and delete an individual guest's records, plus a published DPA. ConverseNow publishes the opposite of in-app tooling and says so exclusively — the route is manual, mediated and rate-limited: "Such requests will have to be made to the Parent Restaurant Organization (or their franchisee)", who "will send your request to us at privacy@conversenow.ai", and "You may only make a verifiable consumer request for access or data portability twice within a 12-month period". No operator-facing screen, endpoint or queue is documented anywhere. There is no published DPA either: data processing agreement and subprocessor occur ZERO times, and the six apparent dpa hits are all state-statute acronyms in the policy's own list of laws — CTDPA, DPDPA, INCDPA, ICDPA, MCDPA, VCDPA — opened and discarded. Bounded to the complete live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters (sitemap 6 locs + the two footer-linked legal pages the sitemap omits; the href set was diffed against the sitemap both ways and is exact, and /products is a byte-identical alias of /products.html). Absence is measurable here: every fabricated path 404s with a body byte-identical to /404.html served verbatim, across fifteen probe shapes including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt and /api/v1/orders, as does every path retired in the 2025 rebuild; the requested path is never echoed into the body. There is no catch-all. Every zero was re-run against the unstripped HTML as well as the stripped text and none is manufactured by the strip. The two hosts that could hold a private answer are named rather than ignored: api., developer. and developers.conversenow.ai are NXDOMAIN, while docs.conversenow.ai (A 34.123.64.3) and app.conversenow.ai (A 142.93.23.88) resolve and drop every TCP connect on 80, 443, 8080 and 22 — docs. was an Auth0 SSO-gated documentation host when Wayback last saw it answer, in 2023. That surface is unmeasured, not absent, and nothing below is bounded to it. https://conversenow.ai/privacy-policy.html · retrieved 2026-09-09 adversarially verified
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
CITED 2026-09-09 (was an uncited grade-F rationale). Value upheld, and this is a disclosure gap inside the product's scope rather than an absence by scope — which matters, because ConverseNow is squarely on the exposed surface the claim is about. Its own documents put it there: products.html sells "Kiosk compatibility" under the Order Injection API, the merchant Terms of Use defines the Platform as covering "phone calls, drive-thru (/in) and digital kiosk", and end-user-terms 1 covers "telephone, drive-thru, and self-service kiosks". VPAT, accessibility conformance report, WCAG, Section 508 and accessib occur ZERO times across all 8 documents. The two apparent ADA hits were opened and discarded as substring artefacts — "Nevada Rev. Stat. 603A" in the privacy policy's state-law list and "cada una" in the Spanish call transcript on products.html. There is no accessibility statement of any kind, let alone a conformance report or a documented non-visual access mode. Corpus for this pass: the whole live conversenow.ai surface, frozen 2026-09-09 — 8 HTML documents / 85,246 stripped characters, which is the sitemap's 6 locs plus terms-and-conditions.html and end-user-terms.html, both linked from every page footer and both absent from the sitemap. The href set was diffed against the sitemap BOTH ways and the HTML set is exact; /products is a byte-identical extensionless alias of /products.html, not a ninth document. Three non-HTML files are also published and are not in that count: robots.txt, sitemap.xml and .well-known/security.txt. Every published zero below was re-run against the UNSTRIPPED HTML as well as the stripped text and none of them is manufactured by the strip. Absence is measurable on this host: every fabricated path 404s with a body byte-identical to /404.html served verbatim, and so does every retired path. Fifteen probe shapes were tried, including /docs/, /wp-json/wp/v2/types, /feed, /llms.txt, /.well-known/ai.txt and /api/v1/orders, plus eight paths retired in the rebuild; the response is 5,417 bytes and the requested path is never echoed into it, so bytes are a stable ruler here. There is no catch-all. The site is a 2025 rebuild of a WordPress site whose /resources/, /technology/, /company/, /press/ and /careers/ trees are all withdrawn, so nothing here rests on an absence the rebuild manufactured: the archived generation was crawled too (86 pages) and is quoted where it bears. https://conversenow.ai/products.html · retrieved 2026-09-09
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
ConverseNow's complete published product set is four voice/API products — Phone Order AI, Drive-Thru Automation, SMS AI Conversations and the Order Injection API — enumerated on its product page, with a six-page sitemap containing no other product page. Combined with the published Terms of Use and end-user terms retrieved 2026-08-02 — which cover only subscription fees, IP, warranty disclaimers and liability — this commercial term or capability is not offered and not published. Re-checked 2026-08-02. https://conversenow.ai/products.html · retrieved 2026-08-02
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 61 values — 40 upheld, 20 downgraded, 1 upgraded. It separately resolved 14 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.
Pricing and identity
| Field | Verdict | What the verifier found |
|---|---|---|
| pricing.software | upheld | Verified: no pricing page, no dollar figure on any reachable page, CTA is 'Book a Consultation'. Note that a $299/month 'Standard Plan' figure circulates via hostie.ai (a direct competitor's comparison page), futurepedia, softwareworld and a TrustRadius pricing stub — all SEO/aggregator content with no vendor attribution. The researcher was right to exclude it; recording here so a later pass does not 'discover' it. source |
| pricing.processing_rate | upheld | Confirmed — ConverseNow publishes no card rates and is not a processor. 'Not applicable' is the honest cell. source |
| pricing.contract_length | upheld | Correct and should stay unknown. No MSA, ToS, or renewal language is published; the site's sitemap lists six pages, none commercial. This is the correct posture for a quote-only enterprise vendor and should not be back-filled from aggregators. source |
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| digital-sms-ordering | yes (claimed) — SMS AI Conversations | downgrade-to-partial | The only evidence is a four-word marketing tile on conversenow.ai/products.html ("Easy text ordering", "Order status updates", "Promotional messaging"). There is no product documentation, no described POS injection path for SMS orders, no payment-capture-over-SMS description, and no 10DLC/consent handling. The Dec-2024 release note mentions "text" only as a channel name. A named marketing tile with zero mechanics is partial, not yes. source |
| digital-voice-ai-phone | yes (documented) | upheld | Independently confirmed: Phone Order AI is the core enumerated product; corroborated by the Valyant acquisition newsroom release and by third-party trade press describing production phone-order deployments. This is the vendor's actual business, not a claim. source |
| digital-drivethru-ai | yes (documented) | upheld | Confirmed by the PR Newswire acquisition release (Valyant AI drive-thru stack, July 9 2024) and Restaurant Dive / NRN coverage, plus the Dec-2024 platform update citing a 95% drive-thru non-intervention rate. Newsroom-grade, not marketing-only. source |
| order-capture-voice-ai | yes (documented) | upheld | Same evidence base as the phone/drive-thru cells; the integration list (Aloha, Brink, Qu, Xpient, Focus, Fiserv, Olo, ItsaCheckmate) appears on the vendor product page and the Deliverect partnership release corroborates live order injection into order-management systems. source |
| order-capture-kiosk-first-party | partial (claimed) | downgrade-to-unknown | The evidence is the bullet "Kiosk compatibility" under the Order Injection API. That supports the API/channel cells, not a first-party kiosk. ConverseNow ships no kiosk software or hardware SKU and publishes no ADA/VPAT or unattended-EMV detail. Scoring partial on a *first-party* cell from a compatibility bullet is exactly the marketing-as-capability error. source |
| guest-loyalty-unified-profile | partial (claimed) | downgrade-to-unknown | Recycles the same "Personalized AI memory" bullet. Nothing documents a guest profile store, cross-channel identity merge, dedup, or operator access to profiles. Repeat-caller recall in a voice session is not a unified profile. source |
| guest-loyalty-ai-offer-recommendation | partial (claimed) | downgrade-to-unknown | Third cell scored off the same two marketing bullets ("AI memory" + "configure upsell by time/order size/guest behavior"). Rule-configured upsell with A/B testing is already credited at menu-pricing-upsell-prompts; there is no documented model-driven offer *recommendation* or offer-content generation. Double-counting one marketing line across three cells inflates the profile. source |
| digital-promo-parity | partial (claimed) | downgrade-to-unknown | I fetched conversenow.ai/products.html and could not locate the cited "discount management configurable to honor vs offer local deals" language; the page's promo-adjacent content is limited to upsell configuration and "Promotional messaging" under SMS. Unverifiable citation on a marketing page — downgrade. source |
| menu-pricing-franchise-hierarchy | partial (claimed) | downgrade-to-unknown | Supported only by the single line "Menu, pricing, and behavior tuned by region/store" — the same line already used for multi-location-local-override-policy. One sentence cannot establish a corporate/franchise hierarchy with inheritance. Keep the override cell at partial; this one is unknown. source |
| guest-loyalty-consent-management | no (documented) | downgrade-to-unknown | The cited source is a law-firm article about Taylor v. ConverseNow. A surviving CIPA class action alleges undisclosed AI interception; it does not affirmatively document that the platform lacks per-channel consent capture (call-recording disclosure prompts are in fact standard in voice-AI deployments and may be configured brand-side). Litigation is not product documentation. Confidence 'documented' is unsupportable here. source |
| commercial-month-to-month-contract | no (documented) | downgrade-to-unknown | Cited source is the sitemap. Absence of a published pricing/terms page proves nothing about term length — it is the textbook case for unknown. Confidence 'documented' on a sitemap is a category error. source |
| commercial-no-early-termination-fee | no (inferred) | downgrade-to-unknown | The researcher's own note says "No public MSA or ToS found stating ETF terms either way" — that is the definition of unknown, yet it was scored no. No public source affirmatively states an ETF exists. source |
| reliability-menu-build-service | partial (claimed) | downgrade-to-unknown | Inferring a vendor-run professional-services menu-build offering from the phrase "tuned by region/store" is speculation. No onboarding, implementation, or menu-build service is described anywhere on the site, and the researcher concedes process and cost are unstated. source |
| extensibility-doordash-preferred | no (documented, NO source URL) | upheld | Verified independently: the 2026 DPIP roster is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper. ConverseNow is absent. Score correct, but the dossier asserted 'documented' with no URL — supplying it here. source |
| extensibility-middleware-compatibility | partial (documented) — "only one major aggregator (ItsaCheckmate)" | upheld | Score stands, but the supporting note is stale and understated: ConverseNow and Deliverect announced a voice-AI-into-unified-order/menu-management partnership on 2026-04-16 (PR Newswire), adding a second major middleware. The researcher missed a 2026 development on a cell they were scoring conservatively. source |
| commercial-processing-not-bundled | yes (inferred, sourced to a marketing page) | upheld | A 'yes' resting on inference normally fails the bar, but here the capability is an absence: ConverseNow's enumerated products are four voice/API products, it is not an acquirer or PayFac, and no processing relationship is documented in any source I checked. No processor lock can be imposed by a layer that does not touch settlement. Caveat: the litigation record shows the AI collects card details by phone, so the tokenization/handoff path is undocumented — but that is a payments-security unknown, not a bundling yes. source |
| commercial-data-ownership-clause | no (documented) | upheld | Score stands but on different evidence than cited. The law-firm article does not document a contract clause; the privacy policy does the work — it positions ConverseNow as controller and routes guest rights through the Parent Restaurant Organization, with no merchant-ownership language. Swap the source; the natlawreview citation is being over-leveraged across three cells. source |
| digital-sms-ordering | partial / grade D, cites the four-bullet SMS marketing tile on products.html | upgrade-to-yes | The 2026-08-01 pass downgraded this on the grounds that the only evidence was a marketing tile. I fetched the platform-updates page the record itself treats as grade B for every other voice cell, and it does more than name a channel: the December 2024 entry describes the launch of the next-generation GenAI platform "across phone, text, drive-through, and kiosks for all served brands", with "POS system integration" and "Order confirmation boards with real-time visibility". Text is therefore a first-party conversational ordering channel in production across the served brand estate, landing in the POS — which is the entire claim. The shortfalls the prior pass named (no 10DLC detail, no payment-capture path, no separate SMS product page) are real disclosure gaps but sit outside what this claim asks. Upgraded to yes and re-sourced from products.html to insights.html. source |
| digital-kiosk | partial / grade D — "Order Injection API is marketed to bring AI ordering into kiosks; no first-party kiosk, no unattended EMV, no accessibility claim" | downgrade-to-unknown | The claim asks whether the vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with an accessibility-compliant UI and unattended EMV. I retrieved products.html: the only kiosk reference is the two-word bullet "Kiosk compatibility" under the Order Injection API, alongside "Mobile app integration" and "Custom workflows". insights.html adds kiosks as a channel the GenAI voice platform was deployed across — someone else's kiosk, running ConverseNow's voice layer. ConverseNow ships no kiosk software or hardware SKU, and the record's own note concedes all three of the claim's substantive requirements are absent. The record already downgraded the sibling cell order-capture-kiosk-first-party to unknown on exactly this evidence; leaving digital-kiosk at partial is the same marketing-as-capability error surviving under a different id. source |
| digital-upsell-engine | partial / grade D — "Upsell logic is configurable and A/B testable, but it is conversational — no digital checkout surface and no published attach-rate report" | downgrade-to-no | This claim is scoped to digital checkout: suggestions presented at a digital ordering surface, with attach-rate reporting on them. I confirmed on products.html that the upsell configuration exists ("Upsell Logic" adjustable "by time, order size, or guest behavior", plus "A/B test strategies, analyze launches, and optimize operations") — but it is conversational, and it is already credited at menu-pricing-upsell-prompts. ConverseNow operates no digital checkout: the record itself scores digital-first-party-web, digital-native-app and digital-qr-table as no by product enumeration, and the product page lists four voice/API products with no ordering web or app surface among them. A capability cannot be partially present on a surface the vendor does not have. Scored no on the same enumeration basis the record applies to its other out-of-scope cells, not on absence of evidence. source |
| guest-loyalty-native-email-sms | partial / grade D — "SMS promotions are a named product capability; no native email channel is documented" | downgrade-to-no | The claim requires both email and SMS campaigns sent natively. The SMS half rests on the single bullet "Promotional messaging" under SMS AI Conversations — no list management, segmentation, scheduling or send reporting is described anywhere. The email half fails outright and does so on positive enumeration rather than silence: ConverseNow enumerates its channels twice, as four products on products.html (phone, drive-thru, SMS, Order Injection API) and again in the December 2024 platform update as "phone, text, drive-through, and kiosks". Email appears in neither list, and there is no marketing or campaign product in the six-page sitemap. A claim that requires two channels, one of which the vendor's own channel enumeration excludes, is not a partial. source |
| extensibility-order-injection-api | partial / grade D — "Order Injection API is a named product for mobile apps and kiosks, but ConverseNow owns no POS and publishes no spec" | downgrade-to-unknown | Scored off a product name rather than what the product does. The claim wants a public write API that accepts externally originated orders into the POS as first-class tickets firing to KDS and printers and landing in reporting. ConverseNow's Order Injection API runs the other way: products.html markets it as "Mobile app integration", "Kiosk compatibility", "Real-time ordering" and "Custom workflows" — a third-party UI driving ConverseNow's ordering engine, not an inbound order API on a POS ConverseNow does not own. Nor is it public: no specification, auth model, versioning policy, rate limit or changelog is published, and docs., api., developer. and developers.conversenow.ai do not resolve. Something is running — status.conversenow.ai monitors an "API Server" and a "POS Server" — so unknown rather than no; but nothing retrievable establishes any part of this claim. source |
| reliability-local-transaction-engine | partial / grade D, raised from no on the Qu Intelligent Commerce Platform launch and a ConverseNow LinkedIn edge post | downgrade-to-unknown | I retrieved the Qu release. Its only mention of ConverseNow is one sentence — "Qu will partner with Bites and ConverseNow to enable direct AI and voice ordering, with every order flowing into the POS—preserving guest data, margin, and control." The edge language belongs to Qu's own platform ("ICP embeds native intelligence directly in the store, at the edge"), not to ConverseNow, and the release names no discrete edge server and describes no component as generally available on-premise. The only ConverseNow-attributed edge statement is a LinkedIn marketing post about running "ASR, LLM and TTS" on-device — the speech stack, not the ordering or transaction path, which the Qu sentence puts in the POS. The claim asks the vendor to document a local transaction engine for the ordering path; ConverseNow documents nothing, and a partner press release plus a social post is not documentation. source |
| order-capture-drive-thru | partial / grade D — "Ships drive-thru voice order capture (Valyant heritage). Window separation, tandem-lane assignment and pull-forward are undocumented" | downgrade-to-unknown | This claim is about drive-thru lane workflow, and it enumerates three things: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment. The record's own note concedes all three are undocumented, then scores partial anyway on the strength of ConverseNow having a drive-thru product at all — which is credited separately at digital-drivethru-ai. I retrieved products.html: the Drive-Thru Automation bullets are "Reduced wait times", "Increased throughput", "Track order accuracy" and "Real-time analytics". insights.html adds a non-intervention rate and order confirmation boards. Neither touches lane structure or vehicle sequencing, and ConverseNow ships no lane controller or timer. Nothing in the claim is evidenced. source |
| guest-loyalty-privacy-rights-tooling | partial / grade B, cites the privacy policy DSAR windows | downgrade-to-unknown | The claim asks for admin tooling that lets an operator fulfil guest access and deletion requests, with deletion propagating to loyalty and marketing records. The privacy policy documents a process, not a tool: requests are made to ConverseNow by email or phone, routed through the "Parent Restaurant Organization", answered within 30 days for access and 45-90 days for deletion. No operator-facing screen, bulk lookup, export or deletion-propagation behaviour is described, and there is no loyalty or marketing record store in the product for deletion to propagate to. A vendor-run manual intake is the thing this claim is meant to distinguish tooling from. Grade B is also generous for a privacy policy standing in for product documentation. source |
| commercial-privacy-dsar-tooling | partial / grade B, cites the same privacy policy — "no in-app tooling or published DPA" | downgrade-to-unknown | The same privacy policy is scored twice, here and at guest-loyalty-privacy-rights-tooling, and this claim has two limbs of which the record's own note concedes both fail: in-app tooling for locating, exporting and deleting an individual guest's records, and a published DPA the operator can execute. I read the Terms of Use section list in full — ConverseNow Services, Customer Obligations, Access, Privacy Policy and Confidentiality, Service Fees and Billing Methods, Limitation of Warranties, Limitations of Liability, Indemnification, Notice, Governing Law, Dispute Resolution, Publicity, Miscellaneous — there is no DPA, no data-processing addendum reference and no sub-processor list, and none appears in the six-page sitemap. Neither limb is satisfied by anything retrievable. source |
| order-capture-voice-ai | yes / grade B, cites insights.html | upheld | Held to the differentiator-yes bar and it clears it. I retrieved insights.html myself: the December 2024 entry documents the next-generation GenAI platform launched "across phone, text, drive-through, and kiosks for all served brands" with "POS system integration", a 95% non-intervention rate defined as orders handled entirely by AI without live agent assistance, over 90% order accuracy and sub-second response; the May 2025 entry reports 4.55/5 across more than a million calls and a 25% reduction in order time. This is a first-party agent whose completed orders are written into the integrated POS — the claim exactly. Vendor platform-update documentation with operating metrics is a legitimate grade B; this is the one cell in the record where the strongest evidence and the strongest claim coincide. source |
| digital-drivethru-ai | yes / grade B, cites insights.html | upheld | Verified from the vendor's own platform-update page rather than the press coverage the prior pass relied on: drive-through is one of the four channels the December 2024 GenAI launch covers "for all served brands", with a 95% non-intervention rate stated as orders completed without live agent assistance and real-time order confirmation boards integrated with POS systems. The escalation path is corroborated from the partner side by Deliverect, which I also retrieved: "flexible deployment (full automation or assist mode)". Capability originates with the Valyant AI acquisition of 2024-07-09. source |
| reliability-public-status-page | yes / grade B, cites status.conversenow.ai | upheld | I loaded status.conversenow.ai myself with no session or credentials. It resolves to a public Instatus page listing three components — API Server, POS Server and a Downstream Services group — each with its own state and a 100.0% uptime figure, plus "No notices reported for the past 7 days" and a link to 90 days of notice history, and subscription options by email, Slack and Microsoft Teams. Per-component, current and historical, no login: the claim is satisfied in full. Worth flagging for readers that this page is not linked from conversenow.ai and does not appear in its sitemap — it was found by subdomain probe, so an operator would not discover it unaided. source |
| commercial-processing-not-bundled | yes / grade B, cites end-user-terms.html | upheld | A differentiator yes, so I went to the contract text rather than the note. Section 8.3 of the end-user terms states verbatim: "Pricing, payment processing, taxes, and receipts are handled by the Restaurant or its payment processors", and directs billing and refund questions to the Restaurant. The Terms of Use section 5 charges only "a subscription fee for Services in the amount set forth in the order form or invoice" — no merchant account, no processing schedule, no residual or rate language anywhere in its thirteen sections. ConverseNow is neither acquirer nor PayFac and cannot impose a processor lock on a settlement path it does not touch. Carrying the caveat forward: the CIPA litigation record indicates the AI takes card details by phone, so the tokenisation and handoff path is undocumented — a payments-security unknown, not a bundling one. source |
| commercial-no-early-termination-fee | no / grade B, restored from the prior pass's unknown once the Terms of Use was located | upheld | The prior pass downgraded this to unknown when no terms could be found at all; terms now exist, so I re-ran it. The claim asks whether the vendor's published terms state that there is no early termination fee or liquidated damages. I enumerated all thirteen headings of the Terms of Use — Services, Customer Obligations, Access, Privacy and Confidentiality, Service Fees and Billing Methods, Limitation of Warranties, Limitations of Liability, Indemnification, Notice, Governing Law, Dispute Resolution, Publicity, Miscellaneous — and there is no Term, Termination, Renewal or liquidated-damages section anywhere in it. The published terms therefore verifiably do not make the statement the claim requires, which is positive evidence of absence of a published no-ETF commitment. It is emphatically not a finding that an ETF exists: exit economics sit in the unpublished order form, and pricing.early_termination_fee correctly remains unknown. source |
| menu-pricing-upsell-prompts | partial / grade D — "Upsell configurable by time, order size and guest behavior with A/B testing; per-channel scoping and attach-rate reporting not documented" | upheld | I located the language on products.html myself: "Upsell Logic" adjustable "by time, order size, or guest behavior", alongside "A/B test strategies, analyze launches, and optimize operations" and a configurable "Tone & Persona". Real configuration on real axes, so not unknown. But the claim asks for per-item and per-channel configuration with vendor-reported attach rate, and none of those three is evidenced — the axes offered are orthogonal to the ones asked for. Partial with the shortfall correctly named. Note this is the one place conversational upsell is credited: the digital-upsell-engine and guest-loyalty-ai-offer-recommendation cells were scored off this same sentence and are now no and unknown respectively. source |
| multi-location-local-override-policy | partial / grade D — "States menu, pricing and behavior are tuned by region/store; no field-level lock model is documented" | upheld | I confirmed the sentence exists on products.html: "Menu, pricing, and behavior tuned by region/store." It establishes that menu and price vary per store under central configuration, which is the override half of the claim. The lock half — corporate designating specific fields as non-editable at store level — is entirely absent, and that shortfall is named. Partial stands on one marketing sentence, which is thin for a differentiator, so it is worth stating the limit plainly: nothing establishes who can edit what, and the menu itself lives in the POS. The prior pass used this same sentence to downgrade menu-pricing-franchise-hierarchy to unknown; that split is right, and this cell should not be inflated back toward yes without an admin guide that does not exist. source |
| extensibility-headless-embedded | partial / grade D — "Order Injection API lets third-party apps and kiosks drive ConverseNow's ordering engine; undocumented publicly" | upheld | Unlike extensibility-order-injection-api, which I downgraded, this claim is directionally correct for what the product actually is: a third-party UI driving someone else's ordering engine by API. products.html markets the Order Injection API with exactly that shape — "Mobile app integration", "Kiosk compatibility", "Real-time ordering", "Custom workflows". Partial, with two shortfalls worth stating rather than one: no specification, auth model or rate limit is published and no developer subdomain resolves, and the engine being driven is a voice ordering engine that then writes into a third-party POS, not a POS transaction engine of ConverseNow's own. source |
| extensibility-middleware-compatibility | partial / grade B — shortfall stated as "that is one middleware documented on the middleware's own site and the claim wants two" | upheld | Value stands but the stated shortfall is wrong and I am replacing it. Deliverect's own catalogue lists ConverseNow live in Australia, Canada, Mexico, the United Kingdom and the United States; ItsaCheckmate is not merely a logo either — a November 2023 joint announcement describes the partnership as letting ConverseNow "integrate its AI-powered ordering platform quickly and easily with dozens of POS systems", carried by RestaurantNews, Restaurant Magazine and Food On Demand. So two of the five named middlewares are attested. The real shortfall is directional and it is why this cannot reach yes: the claim asks whether the POS is a supported endpoint that middleware routes orders to, and ConverseNow is the opposite — the order source, using these platforms as its own POS-integration layer. It owns no POS endpoint for anyone to route to. source |
| digital-promo-parity | unknown / grade F — prior pass could not locate the cited "honor vs offer local deals" language on products.html | upheld | Value stands, but the prior pass's reason was factually wrong and a later reader should not act on it. The language is on products.html and I retrieved it: promotional management via configurable "Coupons/Discounts" with options to "honor vs offer, optimizing for local deals". The original researcher cited it accurately. It still does not reach the claim, which is about a discount defined once being honoured identically across POS, kiosk and first-party digital with channel eligibility controls: ConverseNow operates none of those channels as ordering surfaces, promotions are defined in the POS, and one bullet about whether the voice agent honours or offers a coupon says nothing about cross-channel parity or eligibility control. Unknown for the right reason now rather than the wrong one. source |
| order-capture-floor-plan-editor | no / grade E, citing conversenow.ai/products.html, retrieved 2026-08-01 | upheld | Value is plainly right — ConverseNow ships no terminal, no table entity and no floor plan, and its four enumerated products are voice and API only. The grade is wrong and I am correcting it: grade E means credible independent third-party reporting, but the cited URL is the vendor's own feature page, which is grade C. This line also still carries retrieved 2026-08-01 while the 150-odd identically-reasoned scope-absence cells around it were re-checked on 2026-08-02 and carry grade C — it was missed in the sweep. Re-retrieved and normalised; no substantive change. source |
| order-capture-offline-order-entry | no, grade F (uncited) | upheld | No terminal exists to degrade, and offline/outage/fallback/failover/degraded are a bounded zero over the complete 8-document live surface with a verified 404 control. Six apparent edge hits were "acknowledge" and two apparent API hits were "rapid". source |
| menu-pricing-3p-menu-push | no, grade F (uncited) | upheld | The menu runs inward: it is what the voice model is trained on. DoorDash, Uber Eats, Grubhub, sync status and rejection are a bounded zero; ItsaCheckmate is one of nine unlinked logos. source |
| digital-menu-single-source | no, grade F (uncited) | upheld | No first-party web or app ordering channel exists, and the vendor describes a separate menu build inside ConverseNow, tuned again per region. The five "online ordering platform" hits are the privacy policy's generic name for the voice service. source |
| guest-loyalty-data-export-portability | no, grade F (uncited) | upheld | Upheld on a LIVE legal document stating an exclusive alternative mechanism: requests route through the Parent Restaurant Organization and are capped at twice per 12 months. Not a silence. source |
| extensibility-partner-revshare | no, grade F (uncited) | upheld | Bounded zero on revenue share, referral, commission and reseller. The prior rationale that no partner program was ever published is FALSE and was corrected: a full reseller programme was published and withdrawn, and it too carries no fee or percentage. source |
| extensibility-app-marketplace | no, grade F (uncited) | upheld | Nine partners named in image alt text under an "Integration Partners" heading, no links, no listings, no install action; marketplace/app store/self-install a bounded zero. source |
| extensibility-api-versioning-deprecation | no, grade F (uncited) | upheld | insights.html is the only changelog, two operator-facing entries (Dec 2024, May 2025 — sixteen months stale), no interface content. changelog/deprecat/sunset/breaking change/webhook a bounded zero. source |
| reliability-offline-order-entry | no, grade F (uncited) | upheld | No terminal, plus end-user-terms 9.1 declining any availability guarantee under an AS IS / AS AVAILABLE platform. The withdrawn crew FAQ corroborates the human-pickup fallback and does not carry the absence. source |
| reliability-offline-feature-matrix | no, grade F (uncited) | upheld | Strongest of the batch: an affirmative refusal to characterise availability at all, repeated in both contracts, plus a withdrawn status page whose only incident row is the literal placeholder "xx/xx/xx". source |
| reliability-self-serve-training | no, grade F (uncited) | upheld | Re-evidenced on audit. The withdrawn-page framing was demoted and the verdict re-homed onto a bounded public zero, now closed on one further surface: the footer-linked YouTube channel holds exactly two videos, both demos. source |
| commercial-wcag-kiosk-accessibility | no, grade F (uncited) | upheld | In scope, not out of it — the vendor sells "Kiosk compatibility" and both contracts name kiosks. VPAT/WCAG/Section 508/accessib a bounded zero on the live surface; the two ADA hits were "Nevada" and "cada una". source |
| multi-location-central-menu-publish | no, grade C (cited earlier the same day) | downgrade-to-unknown | A conjunction of two constituents this record already scores unknown (multi-location-scheduled-publish, multi-location-config-audit-log) cannot be a no unless one is affirmatively refuted. The sentence I leaned on already carries multi-location-local-override-policy at partial, and the only alternative-mechanism evidence was a withdrawn 2022 page, which may not solely support an absence. app.conversenow.ai is firewalled, not empty. source |
| commercial-data-export-self-serve | no, grade B (cited earlier the same day) | downgrade-to-unknown | The contract finding is airtight but is the wrong instrument: it establishes the absence of an export RIGHT, not of an export FEATURE, and a Terms of Use is not a feature enumeration. Thirteen sibling reporting cells already hold this as a disclosure gap rather than a determination. The one documented reporting product (Looker, 2022) is affirmative evidence for the capability and was withdrawn, not refuted. source |
| commercial-post-termination-export-window | unknown, grade F | resolve-to-no | end-user-terms 18 survival enumeration lists six categories and no data-return obligation; the merchant Terms of Use has no termination section at all beyond non-payment. A contract-shaped claim answered by the complete published contract set. source |
| commercial-soc2-attestation | unknown, grade F | resolve-to-no | Pure publication claim. SOC 2, ISO 27001, trust center, attestation and penetration test a bounded zero; the privacy policy instead publishes an affirmative refusal to warrant security. source |
| commercial-privacy-dsar-tooling | unknown, grade F | resolve-to-no | Same shape as guest-loyalty-data-export-portability, which the audit upheld: a live legal document stating an exclusive alternative mechanism (manual, mediated through the restaurant, capped twice per 12 months), plus a pure publication zero on the DPA leg. The six dpa hits are state-statute acronyms. source |
| extensibility-published-rate-limits | unknown, grade F | resolve-to-no | Pure publication claim — rate limit, throttl and quota a bounded zero. Quotas documented behind the Auth0-gated docs host would not be published, so that firewalled surface does not rescue the cell. source |
| extensibility-free-sandbox | unknown, grade F | resolve-to-no | The claim asks for an environment reachable WITHOUT a paid production account; the only developer host is Auth0 SSO-gated and now drops all TCP. The wall is the account requirement. source |
| commercial-hardware-not-locked | unknown, grade F | resolve-to-partial | No vendor-proprietary device is mandated and the merchant contract puts equipment on the operator as Customer Systems; partial rather than yes because the claim asks the vendor to document a NAMED third-party option and printer/cash drawer/iPad/ESC-POS/Epson are a bounded zero. source |
| reliability-247-live-support | unknown, grade F | resolve-to-partial | 24-hour-a-day live support is asserted unqualified on the home page; partial because the claim also requires inclusion in the base subscription and no plans are published at all, and the only support phone number ever published is on a withdrawn page. source |
| digital-account-saved-payment | unknown, grade F | upheld | Proposed partial/C from the retired WordPress corpus; rejected on verification: Claim = guest account + saved addresses + saved tokenized payment + one-tap reorder across first-party channels. The proposal's shortfall concedes account, addresses and payment, and the reorder evidence is a voice recall, not one-tap reorder on a first-party channel (record scores first-party web/app `no`). The same transcript sends payment to the store. Every conjunct, the claim's core subject included, fails, so the partial refutes itself. source |
| digital-fulfillment-modes | unknown, grade F | upheld | Proposed partial/C from the retired WordPress corpus; rejected on verification: Claim: one DIGITAL ordering flow with pickup, curbside+check-in, dine-in/QR and delivery, plus mode-specific fees and prep timing. Evidence: a voice agent asks pickup or delivery and gives a flat 10-20 min quote that does not depend on the mode. The record scopes digital-* to a first-party web/app surface: web/app/QR are `no`, and digital-upsell-engine went to `no` because conversational != digital checkout. No fees, no mode-specific timing. Not credited here. source |
| guest-loyalty-campaign-attribution | unknown, grade F | upheld | Proposed partial/C from the retired WordPress corpus; rejected on verification: Claim: redemption AND incremental sales tied to a SPECIFIC campaign/offer AND to check totals. 'coupon use' is an aggregate KPI next to call volume and conversion, sliced by store or franchise. It is not per-campaign or per-offer, and it does not touch incremental sales or check totals. The shortfall covers every conjunct, so this is a homonym, not partial attribution. The source is also a withdrawn 2022 marketing page. On a differentiator, grade C cannot carry it. source |
| reporting-realtime-dashboard | unknown, grade F | resolve-to-partial | Looker page (2022 capture, the only one) offers sales dashboards 'in interactive, easy-to-use dashboards' and the vendor calls it 'live store data', though only in a contact-Sales call to action. The live products page still lists 'Real-time analytics'. Latency within minutes and browser plus mobile access are both unevidenced, as the shortfall says. The dashboard conjunct is met at grade C, so this is not a partial that shortfalls every conjunct. The Looker branding is withdrawn, so the page is historical. source |
| reporting-multiloc-drilldown | unknown, grade F | upheld | Proposed partial/C from the retired WordPress corpus; rejected on verification: The only met element is the same 'Store comparisons ... by franchise or store level' block that also scores multi-location-consolidated-reporting. This claim's distinguishing conjunct, drilling from group total to a location and then to one transaction, is wholly unmet. 'viewing any call ... for quality assurance' is an AI QA feature, not a drill path from a report. Crediting a differentiator on the shared comparison proposition alone double-counts one marketing sentence. A single 2022 capture, not on the live site. source |
| reporting-scheduled-delivery | unknown, grade F | resolve-to-partial | Under 'Advanced reporting', the raw page reads 'automated reports and alerts emailed to you as frequently as you'd like'. That establishes recurring email delivery at an operator-chosen cadence. Recipient lists, shared destinations and scheduling of any report (not a fixed automated report) are unaddressed, and the shortfall names this correctly. Grade C, 2022 capture only, withdrawn from the live site. source |
| reporting-anomaly-alerts | unknown, grade F | resolve-to-partial | The page says 'Worried that a coupon might get overused or a store may be underperforming? Set up custom alerts', and separately 'automated reports and alerts emailed to you'. Together they state operator-configured metric alerts delivered by email, which is the claim's core, at grade C. Threshold or deviation mechanics, the metric list and push delivery are undocumented. On a differentiator, a yes is barred at C anyway. 2022, withdrawn from the live site. source |
| multi-location-org-hierarchy | unknown, grade F | upheld | Proposed partial/C from the retired WordPress corpus; rejected on verification: The quote is a phone-channel offers sentence: 'Process coupons and gift cards ... customize offers at the franchise, regional and national levels'. It scopes promotions, not an organizational hierarchy object. The claim's defining conjunct is a 3+ level hierarchy that reporting and permissions are scoped to. Reporting evidence (Looker, 2022) shows only two levels (franchise or store), and permissions are absent. The partial is stitched from two pages two years apart, and every hierarchy-as-object conjunct shortfalls. Live 'tuned by region/store' is flat. source |
| multi-location-new-store-template | unknown, grade F | upheld | Proposed partial/C from the retired WordPress corpus; rejected on verification: 'Go live with your first store in 4-6 weeks, additional stores 3-5 days' is an onboarding duration for the voice-AI service. It is not a documented configuration template for cloning menu, taxes, roles, printers or tenders, and the proposal itself declines to credit the reuse inference. The claim's primary proposition, cloning, is unmet. The only conjunct touched is 'the vendor publishes time-to-open' (present tense), and the live site no longer publishes any timeline, so it is not currently true. A differentiator cannot rest on a withdrawn onboarding figure. source |
| multi-location-consolidated-reporting | unknown, grade F | resolve-to-partial | This claim is independently partly met by the comparison block: data viewed 'by franchise or store level to compare ... coupon use and other bottom-line factors', with sales and average ticket among the KPIs. That is above-store aggregation and store-vs-store comparison of sales and discounts. Labor, voids, item mix, ranking and variance flags are absent, as the shortfall says. It keeps the shared block, and drilldown is downgraded so the block scores once. Grade C, 2022 capture only, withdrawn from the live site. source |
| reliability-menu-build-service | unknown, grade F | resolve-to-partial | The claim asks only whether the vendor does the initial menu build during onboarding, not the operator. Under 'Hands-off onboarding' the page says 'We do the heavy lifting for you ... train our voice AI on your menu, upsells, LTOs, coupons' and 'Just send us your menu ... we'll take care of everything'. That meets it for this product's own menu model. Partial holds because the evidence is grade C on a differentiator, it is not a POS menu build, and process and cost are undocumented. Live corroboration: 'trained on your menu, your promos'. source |
| reporting-multiloc-drilldown | unknown, grade F | upheld | Proposed partial from archived conversenow.ai WordPress pages (305th session); rejected on verification: Re-fetched the 2025-04-22 capture (HTTP 200, 53,854 bytes, comments stripped). Both quotes appear word for word, each in its own Elementor <p><span>, so no cells were welded together. 'drill' and 'transaction' do not appear at all. This is a re-proposal already rejected on 2026-09-12 (conversenow verification.jsonl, same block, 2022-08 capture). The newer capture only shows the same sentence was still up three years later. It adds no new conjunct. 'View data by franchise or store level to compare' is a group/store comparison. multi-location-consolidated-reporting partial/C already scores that exact block (its note says so). The claim's distinguishing conjunct is a drill path from group to location to individual transaction, and it is wholly unmet. 'Viewing any call ... for quality assurance' is AI call QA, not a drill-through from a report. Some peers (chowly/deliverect/pdq, grades D/C) do hold partial on comparison alone, but crediting this differentiator would double-count one marketing sentence and reverse a recorded verdict without new evidence. Keep unknown/F. source |
| multi-location-org-hierarchy | unknown, grade F | upheld | Proposed partial from archived conversenow.ai WordPress pages (305th session); rejected on verification: Re-fetched 2026-09-15 (HTTP 200, 96,253 bytes). The quote is verbatim in raw HTML at byte 81966, inside an elementor-icon-box-description paragraph under the non-order-calls section. The page itself has no 'permission' or 'hierarch' token. The 6 'role' hits and 3 of 4 'region' hits are ARIA attributes (role="region"), so 'regional' occurs only in the quoted sentence. The quote is a DUPLICATE PROPOSAL: verification.jsonl row 69 (2026-09-12) already rejected this same sentence off the 2024-04-23 capture of /technology/ and kept the cell at unknown. A later capture of the same marketing copy adds no conjunct. On the merits, the claim needs a 3+ level hierarchy as a first-class object that reporting AND permissions are scoped to. 'Customize offers at the franchise, regional and national levels' describes how promotions can be scoped in the phone channel. It does not describe an organisational tree object. The proposer's own caveats concede that the permissions conjunct is unevidenced and that the setup may be run by vendor staff. The Looker corroboration ('franchise or store level') gives two levels only and is already spent on multi-location-consolidated-reporting. The Company page 'one, two or 200 stores' line is ICP positioning. A partial that shortfalls every hierarchy-as-object conjunct refutes itself. Scoped-offer variation also overlaps multi-location-local-override-policy (partial/D, 'tuned by region/store'), so it would be counted twice. source |
| reporting-tier-paywall | unknown, grade F | resolve-to-partial | Re-fetched the cited Wayback id_ URL and found both quotes verbatim in the raw HTML. The existing record cites /looker/ (2022-08 capture) for realtime-dashboard, scheduled-delivery, anomaly-alerts and consolidated-reporting, but not for this cell, which was unknown/F ('no published plan tiers'). So this is a new resolution, not a duplicate. The polarity checks out: 'included' means not paywalled, the claim's yes direction. Yes is barred at grade C on a differentiator, and the tier and named-report conjuncts are unmet. But the not-an-add-on conjunct is actually met, so the shortfall does not cover every conjunct, and the verification-row-63 homonym rejection does not apply. Peers resolve the same shape as partial at C/D: hungerrush 'all systems include reporting' (D), foodtec 'no add-ons' (D), arryved single price point (C). Amended because the proposal's caveat said the record scores PMIX no; it is unknown. The note now also records the zero plan/tier controls from the raw page. source |
| multi-location-new-store-template | unknown, grade F | resolve-to-partial | I re-fetched the capture (HTTP 200, 96,253 bytes). The quote is verbatim in the raw HTML at offset 58200 and again in the FAQPage JSON-LD. The raw dashes are – and the apostrophe is curly, so the proposal's ' - ' spelling was fixed. The taxonomy claim has two parts joined by AND: provisioning by cloning a template, and a published expected time-to-open. The second part is literally met, which is enough for partial, the same standard used for the chowly peer (a 1-2 week kiosk time-to-open was resolved to partial). So partial is not self-refuting. I removed the proposal's inference that the 10x speed gap 'implies reuse of the brand's first-store configuration'. A timeline is not evidence of a template, and the template part is plainly unmet: 0 hits for any of the four words and onboarding is run by the vendor. I kept partial/C with the scope caveat. source |
Sources
Every URL this record cites. 39 in total.
- https://conversenow.ai/
- https://conversenow.ai/products.html
- https://conversenow.ai/sitemap.xml
- https://conversenow.ai/terms-and-conditions.html
- https://conversenow.ai/end-user-terms.html
- https://conversenow.ai/insights.html
- https://conversenow.ai/about.html
- https://conversenow.ai/privacy-policy.html
- https://conversenow.ai/robots.txt
- https://status.conversenow.ai/
- https://docs.conversenow.ai/
- https://api.conversenow.ai/
- https://developer.conversenow.ai/
- https://developers.conversenow.ai/
- https://trust.conversenow.ai/
- https://conversenow.ai/resources/
- https://www.deliverect.com/en-us/integrations/converse-now
- https://www.deliverect.com/en/integrations/converse-now
- https://www.qubeyond.com/resource-center/qu-introduces-intelligent-commerce-platform-to-help-restaurants-deploy-ai-without-compromising-margins
- not refetchable
- https://www.qsrweb.com/news/conversenow-deliverect-partner-to-integrate-voice-ai-into-restaurant-management/
- https://partners.olo.com/partners/conversenow/
- https://www.prnewswire.com/news-releases/conversenow-acquires-valyant-ai---integrating-valyants-complementary-technology-stack-to-accelerate-conversenows-drive-thru-installations-302190895.html
- https://www.restaurantdive.com/news/conversenow-buys-drive-thru-ai-competitor-valyant-ai/720834/
- https://www.prnewswire.com/news-releases/conversenow-and-deliverect-announce-partnership-to-bring-voice-ai-ordering-into-unified-restaurant-order--menu-management-302743431.html
- https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026
- https://www.wsgr.com/en/insights/us-federal-court-allows-cipa-class-action-against-ai-customer-service-provider-to-proceed.html
- https://natlawreview.com/article/extra-large-pii-zza-courts-allows-california-privacy-class-action-proceed-use-ai
- not refetchable
- https://conversenow.ai/robots.txt
- https://conversenow.ai/sitemap.xml
- https://conversenow.ai/llms.txt
- https://conversenow.ai/products.html
- https://conversenow.ai/insights.html
- https://help.conversenow.ai/
- https://support.conversenow.ai/
- https://knowledge.conversenow.ai/
- https://web.archive.org/web/20250422152943id_/https://conversenow.ai/looker/
- https://web.archive.org/web/20250625041113id_/https://conversenow.ai/technology/