Slang AI is a conversational voice AI assistant built for restaurants to handle inbound phone calls, answer guest questions, and convert calls into reservations. The product emphasizes reducing missed calls and voicemails, increasing phone reservations, freeing up staff time, and delivering measurable ROI (claims referenced by Slang: roughly ~50% more phone reservations, ~10x ROI, >96% CSAT and large monthly hour savings). Core capabilities include natural-language voice answering with multiple digital voice options (including accented/premium voices), reservation handling (book/modify/cancel reservations with confirmations by voice and text), VIP routing/concierge bypass, custom routing rules, auto-forward to humans or text contact details when queries are not handled, handling of private events and special requests, conversation summaries, cross-sell / multi-location behavior (suggest nearby openings when one location is full), bilingual support option, and unlimited inbound calls (no per-call limit advertised). Onboarding is described as quick (typically under 30 minutes with potential same-day go-live). Analytics and admin features include an Insights / Dashboard capturing call volume, answer rate, reservations, covers, peak times, common inquiries, CSAT, and reservation insights. Conversation summaries and call-data analytics are offered to benchmark performance and inform staffing and operations. Integrations: Slang advertises direct integrations with leading restaurant reservation platforms (OpenTable, SevenRooms, Tripleseat, Yelp) so reservations are pushed/synced in real time; posts reference POS and other third-party integration messaging benefits. SOC 2 compliance is mentioned as part of product trust/compliance efforts. Pricing and provisioning: Slang uses a per-location, monthly subscription model with two main tiers referenced (Core and Premium). Premium is described as including Core features plus additional items at no extra cost. Add-ons are offered a la carte (examples: Private Events product, bilingual support, premium voices). Slang can provision a local or toll-free phone number or assist in keeping an existing number; exact dollar amounts are not published and Slang requests a demo/quote to provide per-location pricing and plan details. Legal and terms highlights (as referenced): services are provided under Gablex, Inc. d/b/a Slang AI Order Forms; license is non-exclusive and limited to the Order Form term; Customer Data remains owned by the customer while Slang may use aggregated/de-identified data for product improvement and marketing; fees are invoiced monthly in advance, late payments may incur charges, taxes are the customer's responsibility; termination, indemnification, limitations of liability, and New York law/courts are specified; implementation support may be included only if specified on the Order Form and extra implementation work may be billable. The ToS includes references to Evaluation Services / Pilot Period terms (so pilot/evaluation arrangements exist in contract language and should be confirmed with Slang for specifics). Resources: Slang publishes a blog and resource hub (guides, product updates, ROI calculator, case studies, guides such as Ultimate Phone Guide and reservation/phone-system guides). Press and customer stories showcase partnerships (OpenTable launch, Tripleseat, Yelp) and examples/metrics (voicemail reduction, 100+ hours saved per month). Operational gaps identified during the review: pricing amounts are not publicly listed (demo/quote required), a contact page URL returned a 404 during a check though contact/demo request flows exist via the homepage and demo links, and no public API documentation or developer portal was found on main site pages (dashboard and integrations appear product-focused rather than developer-facing). Suggested next steps: request a demo/quote for per-location pricing and to see the Insights dashboard; request pilot/trial terms if you want an evaluation; request a price quote for the specific number of locations and desired add-ons; if technical/developer details are required (API, webhooks, integration behavior), request technical/developer documentation from Slang's sales or onboarding team and confirm SOC 2 and data handling specifics to meet compliance needs.