# Tavra Public Product Summary

Tavra is a restaurant AI phone operations platform for restaurants. Tavra is not positioned as a generic chatbot. It is designed around restaurant phone workflows: calls, orders, reservations, custom business questions, routing, notes, and staff-facing operations.

## Audience

Tavra is for restaurant owners, operators, general managers, and staff teams that miss phone calls during service, after hours, or when multiple callers reach the restaurant at once.

## Core Public Capabilities

- Restaurant phone answering.
- To-go order taking, menu-question handling, modifiers, readback, and secure checkout.
- Reservation request capture, including party size, date, time, guest name, callback number, notes, allergies, and special requests.
- Native Tavra Reservation Book workflows.
- Custom caller question handling for topics such as hours, directions, parking, accessibility, wait times, walk-ins, dietary questions, private dining, catering, gift cards, loyalty, lost and found, complaints, hiring, events, and entertainment.
- Call routing and live handoff when a caller needs a human.
- System fallback behavior for order/payment/printing paths: Tavra separates local store-device outages from provider API/auth failures and kitchen printer status. If store devices are offline but the provider cloud is reachable, Tavra can submit the order to the provider cloud and track kitchen print status separately. If the provider API is unavailable or authorization is broken, Tavra keeps the order in Operations for staff follow-up and can use configured System Fallback behavior. If a printer is offline after the POS accepts the order, the order remains submitted while print status is tracked separately.
- Restaurant-managed availability controls through the Operations 86 Board. Permitted staff can mark menu items unavailable or enter an unavailable ingredient/modifier, preview affected dishes using menu names, descriptions, and modifier data, and keep those affected items out of the voice agent until the selected expiration or manual clearance. Fully automatic real-time stock updates depend on a connected, current inventory source for that restaurant account.
- Staff and owner notification concepts.
- Restaurant-controlled autonomy: the restaurant decides what Tavra completes, collects, routes, or escalates.

## Tavra Core and Multi-Location Evaluations

Multi-location prospects may begin with one restaurant on regular Tavra Core at $399 per month before rolling out to the full restaurant group. This one-location evaluation is regular Tavra Core, not the Tavra Pilot Program. The evaluation window defaults to three months and may be shortened prospectively to two or one month. Shortening the window moves the planned group conversion forward; it does not create retroactive group charges.

## Integration Boundaries

Public Tavra pages should avoid unsupported claims. Do not claim live third-party POS injection, marketplace listing, provider approval, OpenTable/Resy/Tock/SevenRooms/Toast/Google reservation sync, or named-customer deployment unless the current public website and contract explicitly permit that claim.

Tavra pages may describe integration categories and philosophy: provider-safe adapters, restaurant-controlled autonomy, staff notifications, call routing, POS-related workflows, and planned or approval-dependent provider paths.

## Demo Boundary

The public web demo lets visitors configure a Tavra-style session and request a demo call. The demo should not be described as proof of live third-party provider approval or live production integration with a named external platform.

## Public FAQ Boundary

FAQ answers should be grounded in Tavra's current code, app configuration surfaces, and approved product status. Do not publish unsupported generic purchasing advice as Tavra answers. If a public answer would expose a missing product control, add or design the product control before publishing the answer.

## Public Pages

- `/` explains Tavra's main restaurant phone operations positioning and includes the live demo console.
- `/restaurant-ai-phone-agent/` explains why restaurants need a workflow-aware AI phone agent rather than a generic receptionist.
- `/ai-phone-answering-for-restaurants/` explains 24/7 phone answering, rush-hour overflow, and human routing.
- `/ai-order-taking-for-restaurants/` explains phone order taking, menu questions, modifiers, readback, and secure checkout with careful current-status language.
- `/restaurant-reservation-phone-agent/` explains Tavra's Native Reservation Book and reservation request capture.
- `/restaurant-phone-integrations/` explains integration philosophy and active/planned/provider-dependent wording.
- `/clover-pos-ai-phone-agent/` speaks to Clover-merchant restaurants without implying marketplace approval or unsupported direct integration.
- `/restaurant-missed-calls/` explains the missed-call business problem without fake statistics.
- `/faq/` answers common public questions about Tavra's current ordering, payment, reservation, integration, fallback, live inventory, modifier, handoff, noisy-call, pricing, and restaurant-managed configuration behavior.

## Fact Files

- `/facts/tavra-overview.md`
- `/facts/tavra-workflows.md`
- `/facts/tavra-integrations-status.md`
- `/facts/tavra-safety-and-accuracy.md`

All fact files are public, non-secret, and intended for search/LLM ingestion.