Overview

Two venues, one building, the same guest, and five systems that don't talk.

A guest who has dinner at Lavelle and goes downstairs to 44 Toronto exists in four places and belongs to none of them. Their table sits in SevenRooms, their ticket in Ticket Gateway, their spend in Toast, their sign-up in a form export. Nobody can see the whole night, and nobody markets to them afterwards.

The same split runs through operations. Labour sits in Push, sales in Toast, and nobody sees labour against sales until payroll closes. Promoter credit is reconciled by hand from SevenRooms check-ins, Ticket Gateway affiliate sales and the bottle sheet. Settlements, deposits and payouts are rebuilt in spreadsheets every week. Budgets are forecast in one place and actuals land in another.

One GHL platform

One platform. Both venues. Operations and marketing in the same place.

Lavelle and 44 Toronto run on a single GoHighLevel platform. Each venue keeps its own brand, sending domain, phone number, calendars, pipelines and team, and every guest, booking, promoter and dollar sits in one system Freed can see end to end.

One platform means a guest who dines at Lavelle and books a booth at 44 Toronto is one record with one history. Permissions keep each team inside its own venue; ownership sees both.

Logins & management

Everyone logs in. Everyone sees only their part.

One platform at a single address, with a login for every role. Permissions are set per person and per venue, so a promoter sees their own statement and nothing else, and a venue manager never sees the other room's numbers unless Freed grants it.

Capture & email sign-ups

Every way a guest touches either venue becomes a contact.

Guest WiFi at both venues, website sign-ups, SevenRooms reservations, Ticket Gateway purchases, ad lead forms, Instagram DMs and missed calls all write to the platform, tagged by venue. Name, mobile, email and birthday, de-duplicated against what's already there.

• Guest WiFi. A branded portal on each venue's network. Guests sign in with name, mobile, email and birthday. Guest network split from the POS network.
• Email sign-ups on both sites. "Get the list" on 44toronto.com and "Reserve first" on chezlavelle.com, each feeding its own welcome flow.
• One opt-in, both venues. The sign-up names Lavelle and 44 Toronto, so a guest captured in one room can be marketed to by the other.
• QR at the table and the door. Each placement carries its own tracking link, so the platform shows which QR, which table tent and which flyer produced the sign-up.

Birthdays

The highest-value booking in the building, on a schedule.

A birthday group is a booth or a cabana on a minimum. Every guest with a birthday on file gets a sequence that starts thirty days out, timed to when groups actually plan, with the offer escalating as the date gets closer.

Visits

Every visit is logged, thanked and turned into the next one.

A SevenRooms check-in, a ticket scan or a closed Toast check marks the visit. The guest's record updates their visit count and spend tier, and the post-visit flow takes over: thank-you, review request, and the next reason to come back.

Lapsed guests & win-back

Guests who drift get noticed at 30, 60 and 90 days.

Nobody chases a guest who stopped coming. The system does. Each step uses a stronger reason to return, and a guest who books stops the sequence the moment the booking lands.

Retargeting

The database becomes the ad audience.

Every segment in the system syncs to Meta, Google and TikTok as a customer audience. Ads go to people who already know the venue, lookalikes are built from the guests who spend most, and anyone who just booked is suppressed so spend isn't wasted on them.

Cross-marketing

Sell the whole night, not half of it.

Lavelle and 44 Toronto share a building and a guest. The group layer lets each venue market to the other's consented guests, so dinner upstairs leads to a booth downstairs and a 44 Toronto birthday starts with a reservation at Lavelle.

The flow library

Sixteen automations, both venues, all timing relative to the trigger.

Inquiries

Every event request lands in one place, sorted by what the guest wants.

The event form on chezlavelle.com, Meta and Instagram lead forms, DMs, missed calls and event requests coming through SevenRooms all create one inquiry. The event type the guest picks decides the reply they get, the package they see and who it goes to.

Follow-ups

Answered immediately, followed up until it books or says no.

The guest hears back the moment they submit, by text and email, in the events team's voice and specific to their event type. The events manager is assigned and alerted at the same time, with every detail of the request. If the guest doesn't reply, follow-ups run on a fixed cadence. The moment they reply or book a walkthrough, automation stops and the manager takes the conversation.

• An owner on every inquiry. No inquiry is ever unassigned. If the assigned manager is off, it routes to the next.
• Replies go to a real inbox. When a guest answers an automated message, it reaches the assigned manager's own inbox and the shared conversation view, not a send-only address.
• One text and one email per touch. Nothing heavier, no time-of-day phrasing, all timing relative to the inquiry.
• After the event. Thank-you, review request, and a rebooking prompt ahead of the same date next year, which is how corporate holiday parties come back every December.

Pipeline

Every inquiry on one board, from request to deposit.

Each inquiry is a card. The card moves as the event moves, and the board shows the value sitting at each stage. Click any card to see what the events manager sees.

What the team sees

No extra work for the events team.

The system does the chasing. The team does what only they can do: talk to the guest, quote and close.

Event reporting

Inquiries, walkthroughs, bookings and value, by type and by source.

Night & weekend reports

Every night closes with its own report. Every weekend rolls up.

When the last Toast check closes, the night report builds itself from Toast, Push, SevenRooms and Ticket Gateway. Revenue mix, guests through the door hour by hour, tables, promoter and staff credit, labour and settlements, for each venue and for the weekend.

Toast, Push, SevenRooms, Ticket Gateway

Toast, Push, SevenRooms and Ticket Gateway feed one record.

Each platform keeps doing its job. The platform listens to all of them and writes the result to the guest, the night and the promoter.

Promoter profiles & reports

Every promoter has a profile, a link and a statement.

Each promoter gets a login, personal tracking links for tickets and tables at both venues, and a live view of what they've been credited. The weekly report builds itself from the credit rules, goes out on the same schedule, and the dispute window runs inside the portal.

Accounting & payments

Deposits in, settlements out, books in sync.

Table deposits, ticket payouts, promoter and DJ settlements and contractor invoices all run through the platform and post to Freed's accounting platform. Nobody re-keys a number.

• Accounting sync. Invoices, payments and payouts post to Freed's accounting platform with the right venue, entity and category.
• Payout batches. Approved promoter and DJ statements export as one payment batch per week to Freed's payables system. Ownership approves the batch, not forty transfers.
• Settlements per payee. Ticket sales by platform and payee stay separate, so each party sees only their own numbers.
• Contractor status page. Every DJ, promoter and contractor can see whether their payment is approved, scheduled or paid, which ends the daily chase.

Ownership dashboard

Both rooms on one screen.

The ownership view. Switch between the group, Lavelle and 44 Toronto. Every tile, trend and chart is built from Toast, Push, SevenRooms and Ticket Gateway data, refreshed through the night.

Reporting & budgets

Every night budgeted, every dollar reported.

Each event night gets a budget before it's announced: talent, promoters, staffing, production and media against forecast tickets, door and bar. Actuals land from Toast, Push, Ticket Gateway and the ad platforms, and the variance is on screen the next morning.

Marketing KPIs

What marketing spent, sent and brought back, month by month.

One tab per month, each a full report. Email, SMS, flows, paid media and reviews, with every booking and ticket traced back to the message, ad or link that produced it.

Report folder

Every report, filed where ownership can find it.

Night reports, weekend roll-ups, promoter statements, marketing months, event pipelines, budgets and settlements are filed automatically as they close. Open a folder, pick a report, and the summary is right there.

Management

Who runs what.

Timeline

44 Toronto live in week one. Both venues fully live by week six.

Platform & usage

Platform per venue, messaging metered and capped by ownership.

Every SMS, email, call minute and AI reply runs at the rates below, tracked per venue. Ownership sets a monthly ceiling per venue and sending pauses before it is crossed.

SMS costs roughly 23 times email per contact, so it is held for moments that convert: birthday, event day, abandoned deposit, guestlist confirmation and replies.

Requirements & decisions

What’s needed to go live.