No accepted tickets. New orders appear after staff acceptance.
Sample kitchen view. Production access must restrict customer contact and payment data on the server.
FRA-C-037-HISTORY
Order history
Fictional order records · America/Los_Angeles
Order / customer
Saved
Status
Order total
Details
No orders match these filters.
Order totals are not collected payments. Original prices and revision history stay with each order.
FRA-C-037-DELIVERY
Delivery & recovery
COUNTER TABLET · SAME ORDER, SAME VERSION
#DEMO-205 · Receipt tracking
Needs attention
Saved in the sample ledger. Device receipt and staff acceptance are still pending.
Saved
12:05 PM PDT
Last connection
12:03 PM PDT · sample
Attempts
2 completed
Owner
Shift manager
Check the connection, retry this order ID, then confirm device receipt and staff acceptance. A queued retry is not a delivered order.
Attempt log & escalation
Reminder thresholds and escalation contacts require the restaurant's approved policy.
Preview controls · simulate device response
These buttons change fictional data only; they do not contact any device.
Received, awaiting staff acceptance
FRA-C-038
REPORTS · SAMPLE RECORDS
Daily & monthly reports
Orders in selection—
Completed order value—
Average staff acceptance—
Open orders—
FRA-C-038-RECON
Order reconciliation
Saved orders
—
Completed
—
Cancelled / rejected
—
Unresolved delivery
—
Collected payments
Not connected
FRA-C-038-TREND
Orders by day
Selected records
Report detail · select an order to review
Order
Saved
Status
Order total
Review
No matching sample records.
Definitions & reconciliation
Figures are calculated from the same sample records as the queue and history. Completed order value includes illustrative tax; cancelled, rejected and open orders are excluded. It is not collected revenue. FrontAgent service charges remain in Billing.
Daily and month-to-date periods use America/Los_Angeles. Average acceptance uses saved-to-staff-accepted time for records with both events. Information-only calls require the call ledger and are not connected.
Issue blockers: approved legal identities, plan and measurement rules, completed usage reconciliation, tax treatment and due terms. A real invoice number is assigned once by the billing service; this preview cannot issue or collect.
Monthly service · sample planTelephone answering & order capture Includes 500 minutes
1 month
$199.00
$199.00
Additional usage620 used − 500 included = 120 minutes
120 min
$0.20
$24.00
PAYMENT & BILLING NOTES
Payment method and terms are not configured. No payment is requested for this sample.
Restaurant food-order payments are separate from this service invoice.
All rates are illustrative and unapproved. Legal details, tax treatment and payment terms must be approved before issue.
Subtotal
$223.00
Credits
$0.00
Tax
To be confirmed
Total before tax
$223.00 USD
Amount payable
Not issued
Invoice lifecycle & correction design
Unissued → reviewed → issued → paid / overdue / void. An issued invoice stores an immutable line-item snapshot; corrections use a credit or replacement with an audit reference. A download or email delivery receipt never marks an invoice as paid.
BUSINESS KNOWLEDGE
Menu, prices & options
Sample menu
DEMO-MENU-v1 · USD · Changes remain in this preview
Item / category
Base price
Options
Availability
Action
No matching menu items.
Option rules
Sample
Spice levelRequired · Choose 1
Mild / Medium / Hot · No added charge
Add-onsOptional · Up to 2
Extra avocado +$3.00 · Extra protein +$4.00
Options attach to the selected item and quantity. The customer confirms any paid choice.
Review & effective date
Review prices, availability, option limits and effective time before publishing. Existing orders retain their original price snapshot.
Request an invitation from your restaurant administrator.
This selector previews messages; it never authenticates a user or grants a role.
Role preview
A server-verified location membership determines access. The public design contains fictional data only.
Sample staff access · C-001 fictional preview
Staff
Role
Location
Status
Sample Owner
Owner
Assigned location
Sample only
Sample Counter
Counter
Assigned location
Sample only
Sample Kitchen
Kitchen
Assigned location
Sample only
AMOUNTS & TOTALS
Order amount breakdown
Illustrative rules · not approved tax
Customer confirmation
Calculation preview
Confirm items and options as the order is taken. Read the final total once at the end; reconfirm if the order or total changes.
Calculation & revision record
Store the menu version, rule version, line amounts, taxable base, tax, fee, discount, final total, server timestamp and customer confirmation. Historical orders keep the original values.
Illustrative prices only. Food orders and restaurant payments are not part of these charges.
FRA-C-034-B-RULES
Measurement & exceptions
Sample measurement rule
Count answered service seconds from answer to service end; round each eligible call up to one minute. A linked transfer leg is excluded here to prevent double counting. Actual transfer, spam and rounding rules require contract approval.
Excluded & unresolved records
Failed, test, spam and duplicate records are excluded in this fixture. A missing service-end event is held for review, never treated as zero or billed silently. Provider reconciliation is not connected.
Management design · fictional amounts only. Production requires manager authorization; this public preview is not an access control.
Service charges$223.00
Sample direct cost$92.00
Before overhead$131.00
Collected revenueNot connected
FRA-C-034-B-COST-DETAIL
Cost basis · September sample
Illustrative cost allocations · not vendor pricing
Cost category
Basis
Amount
Reconciliation
Telephone transport
Sample usage allocation
$42.00
Provider bill pending
Voice & AI processing
Sample usage allocation
$38.00
Provider bill pending
Runtime & storage
Sample shared allocation
$12.00
Allocation policy pending
$223.00 − $92.00 = $131.00 illustrative contribution before overhead, credits and tax. This is not recognized profit or collected revenue. Actual cost per order is unavailable until period-matched usage and order records are linked.
Production controls
Keep provider invoices, rate versions, usage source, allocation method, currency and reconciliation timestamp in restricted records. Clients receive service charges and permitted usage only, never internal cost or margin.
FRA-C-039-MANUAL
15 · DESIGN PREVIEW
Staff operations
Policy settings · not applied
FRA-C-039-CHECKLIST
Shift checklist
Practice checks reset on reload. Completion here is not proof of training or a live shift.
Menu & monthly billing procedure
Menu: prepare changes → manager review → publish approved version → verify telephone and terminal versions. Keep historical order prices.
Billing: reconcile usage → check contract and exceptions → review invoice → authorized issue → reconcile payment evidence. Never overwrite an issued invoice.
FRA-C-039-NOTIFY
Notifications & responsibility
FRA-C-039-RETENTION
Records, retention & recovery
Policy settings · no deletion or recording is activated
Design completion cannot clear these gates. Approved manual reconciliation/billing may be reviewed without waiving core order, device or access checks.
FRA-C-039-PILOT-MONITOR
Measure, pause, recover
Measure
Observed
Acceptance / stop rule
Order accuracy / manual intervention
Not measured
Owner-approved thresholds required
Delivery failure / acceptance delay
Not measured
Approved threshold + staff fallback
Cost per order / total spend
Not measured
Approved cap, with monitored usage
Pause & restart procedure
On unsafe, wrong-client or unverified order handling, pause automated capture and use the approved staff route. Preserve queued IDs, versions and evidence. Reconcile every pending order before resuming; confirm recovery with the restaurant manager and release owner.
A lost browser connection alone cannot redirect calls. The actual provider fallback must be configured and tested.
Review after the restaurant pilot. Each connection needs its own approved scope, cost and test evidence. The base order flow remains independent.
FRA-C-039-INTEGRATION-SCOPE
Scope & required checks
Provider / device
Not selected
Recurring cost
Not approved
Enablement
Separate approval required
FRA-C-039-INTEGRATION-REVIEW
Review a future request
Payment responsibilities
Restaurant food payments settle through the restaurant-approved POS or payment provider. FrontAgent service invoices stay separate. Payment capture, refunds, cancellation and POS order acceptance each need their own verified status.