Issues

Event text displayed on Toast Websites cannot be meaningfully customized.

No ability to:

Adjust font size, font weight, or color (especially critical on mobile).

Change or customize the default “More Info” button text.

Modify date format.

Add images or visual media to individual events.

The Events module does not expose editable text controls as implied by support documentation and AI guidance.

Events are visually difficult to read on mobile devices, reducing usability and conversion.

Impact

Events are a core revenue driver for our business.

The current Events widget feels unfinished and overly rigid compared to industry standards.

Forces businesses toward third-party tools (Eventbrite, etc.), which pulls traffic away from the restaurant website and harms SEO and conversion.

Requested Improvements

Full text styling controls (font, size, color, hierarchy).

Custom button text and CTA options.

Image support per event.

Date format customization.

Mobile-first readability controls.

OR JUST PUT IN AN EXPERIENCES WIDGET - WE already do the work to build out the descriptions and images, timing and price - just pull it so we don't lose them off the website with a tables external link .

Issues

Experiences appear to override or suppress standard dining room reservations, despite documentation stating they operate independently.

On February 14:

A ticketed Experience is configured only for the heated tent.

Dining room reservations should remain open and free.

Instead, dining room availability disappears entirely in the standard reservation flow.

This behavior persists even when:

Dining room tables are excluded from the Experience.

Experiences are temporarily disabled.

Multiple support agents confirmed:

Settings appear correct.

Behavior is inconsistent with intended design.

Issue required escalation to backend/product teams.

Impact

Prevents simultaneous operation of:

Paid admission events in one area.

Regular dining service in another.

Creates operational confusion and lost revenue during high-demand dates.

Undermines confidence in Experiences as a scalable event solution.

Requested Improvements

Clear, enforceable separation between Experiences and standard schedules.

Transparent hierarchy rules if overrides exist.

Diagnostics or warnings when configurations unintentionally block availability.

Context

We operate with three seasonal reservable areas:

Dining Room (year-round)

Winter Yurts (removed mid-February)

Heated Beer Garden Tent (Feb–May)

Issues

No clean way to:

Sell paid admission for one area.

While keeping free reservations active in another.

Experiences currently conflate:

Admission control

Seating inventory

Area availability

Lack of best-practice guidance for hybrid models:

First-come-first-served seating with paid entry.

Ticketed admission without table assignment.

Area-specific reservation logic.

Requested Improvements

Area-level Experience assignment.

Admission-only Experiences without table control.

Clear workflows for mixed-service nights.

Issues

Default Toast reservation URLs are:

Long

Date-parameterized

Poor for SEO and marketing use.

No way to:

Set a clean, evergreen reservation landing page.

Default the reservation page to show Experiences.

Reservation and Experience links open in a new browser window, pulling users off the restaurant website.

No option to control link target behavior (same tab vs new tab).

Impact

Breaks user flow.

Reduces time-on-site.

Weakens SEO authority of the restaurant’s domain.

Creates a fragmented customer experience.

Requested Improvements

Simple, canonical reservation URLs.

Ability to embed the full reservation / experience flow as a widget.

Control over whether links open in the same window.

Option to prioritize Experiences in reservation discovery.

Toast has a strong foundation for owning event traffic directly on restaurant websites.

Current limitations push sophisticated operators back toward third-party platforms.

Many of these needs are not niche. Any restaurant hosting:

Ticketed dinners

Beer tents

Seasonal spaces

Prix fixe events

would encounter the same constraints.

Core Ask

We want to keep guests on our website, book events natively through Toast, and avoid third-party platforms. The current tooling makes this difficult despite strong demand and clear use cases.