A restaurant CRM for private events, catering pipelines, and guest growth.
Toast owns the tickets. Resy owns the floor. Strkr owns the sales pipeline that fills the private dining room, moves catering trays on repeat, and pulls the regular who went quiet back through the door. One per-seat invoice, every module on every paid tier.
Full-service independents and small groups carry three CRM-shaped problems that a point-of-sale, reservation platform, or loyalty app was never written to solve. Private events and catering sales live inside an events@ inbox and a shared Google Sheet, where roughly one of every ten inquiries quietly dies. The regular who used to turn up every other Thursday fades across a 90-day window that nobody is watching because the POS reports on last night and nothing else. The regular who dropped 400 dollars last Saturday walks in on a slow Tuesday and gets seated at the worst two-top in the room because the host stand has no idea who they are. Pipeline-shaped problems need a pipeline-shaped tool, which is why a CRM is the right slot. Below are six characteristic failures that keep repeating at restaurants scaling past a single-location mindset.
Events@ as the pipeline
A shared label in Gmail is holding a six-figure line.
Buyouts, rehearsal dinners, corporate holiday events, mitzvah receptions, pharma dinners, wedding welcome parties. Each inquiry opens inside the events address and dies there. The events lead works through an inbox paired with a Google Sheet, loses roughly one in every ten inquiries, and cannot answer the owner on Monday morning about what sits booked across the next ninety days. Private dining is the single highest-margin line at a typical full-service room, and most teams run it with less rigor than their beverage ordering.
Catering as a B2B motion
Catering orders are B2B, not simple table tickets.
A corporate lunch drop. A holiday platter order. A wedding catering package. Drop-off service versus full-service. An invoice on net-15 terms versus a card on file. Repeat accounts versus one-time orders. Catering is a B2B sales motion carrying contracts, deposits, menu customization, and dietary rules. The POS, built for a ticket at the four-top, was never written for a forty-person tray with a two-week lead time and a fifty-percent deposit. Teams end up working catering out of a notebook, a shared drive, and pure goodwill.
The 90-day quiet
Regulars quietly disappear and nobody is watching.
Someone who used to come in every fortnight drops off. The restaurant does not notice for a full ninety days because nobody is monitoring visit cadence against a baseline. By the time anyone catches it, the regular has already settled on a new favorite spot and the window to win them back has mostly shut. Reactivation marketing is the single highest-ROI channel at a typical independent, and almost no independent actually runs it, because a POS carries no concept of a broken rhythm.
Unknown at the door
The podium cannot identify the regular at hand.
The regular who dropped 420 dollars at a four-top last Saturday evening walks in on a slow Tuesday and lands at the worst two-top available because nobody at the host stand opened their guest file. Visit history ends up fragmented across Resy, OpenTable, Toast, and whichever server closed out that Saturday check. None of those platforms pushes a VIP flag onto the podium screen. The result is thousands of missed recognition moments every month at a busy spot, and recognition is the one lever that converts a guest into a regular.
Reviews happen by accident
Google drives discovery, and nobody is asking.
Google reviews account for roughly seventy percent of discovery traffic at a neighborhood spot. Most independents ask for a review only when a guest spontaneously compliments the meal aloud, which happens maybe once every fifty tables. A working review funnel captures the happy diner while dessert sits on the table and asks for the review while the memory is sharpest. The gap between those two states is one text with a tracked link, and almost no restaurant actually ships it.
Loyalty platforms stop at points
Points and tiers do not drive a reactivation campaign.
Toast Loyalty, Square Loyalty, Punchh, Thanx. Each one does a solid job tracking points and tiers. None of them actually run a reactivation campaign aimed at a ninety-day lapsed VIP, slice the guest base along check average and visit cadence, send a note to Tuesday regulars when a new menu lands, or trigger a flow when an events inquiry has sat unquoted for two days. Loyalty stays in place. The marketing CRM is a different role in the stack.
The layer alongside Toast and Resy
A restaurant CRM that does not touch the POS.
Strkr does not ask the restaurant to replatform anything. Toast or Square keeps running tickets, kitchen printers, tax, and tip-share. Resy or OpenTable keeps running the floor plan and the cover count. Strkr sits next to both as the guest-growth and marketing layer. Each system keeps doing its best job and shares the guest id through native integrations, which is the stack shape a working operator actually wants.
Private events pipeline
Buyouts plus parties sit on a real sales pipeline.
A website inquiry, a direct note to the events address, an inbound call, or the occasional Instagram DM each writes a lead tagged with event type, date, headcount, budget band, and dietary notes. The pipeline progresses through Inquiry, Qualified, Proposal Sent, Contract Signed, Deposit Received, Event Confirmed, Executed, and Follow-up. The events lead works a real forecast for the next sixty booked days instead of a mental running total.
Catering sales CRM
Repeat corporate buyers rather than one-off tickets.
Catering is a B2B sale wrapped in restaurant clothes. Strkr holds the corporate buyer (law firm, hospital, tech office), the primary contact (office manager, EA, HR coordinator), the recurring rhythm (weekly Thursday lunch drop, monthly all-hands, quarterly executive platter), and the deposit terms per account. The catering lead opens a list of accounts that broke pattern this week and works a Monday-morning win-back pass instead of waiting on an inbound reorder email that may never arrive.
Guest file
The record the podium actually opens mid-shift.
A guest file inside Strkr reads reservation history from Resy or OpenTable, ticket history plus check average from Toast or Square, email engagement history, review activity data, and loyalty tier. Visit cadence, spend average, favorite server, allergy flags, and occasion dates all render inside one row. The host opens the file at the podium before the walk-in has reached the stand, which is how recognition stops being lucky and starts being a designed behavior.
Reactivation triggers
A 90-day quiet opens a scripted touch.
An overnight scan reads the guest base against the typical visit rhythm. Anyone whose cadence (every fortnight, every month) has gone silent for 1.5 times their usual gap gets flagged. The lapsed cohort then splits across VIP tier, check average, and preferred channel. A reactivation touch fires on the right path for each group. SMS with a limited-time offer. Email on a new menu drop. A server-level call for a lapsed high-check regular. The silent window turns into a tracked event carrying a scripted answer.
VIP alerts
The podium is already informed before the walk-up.
The instant a VIP-tagged guest places a reservation through Resy or OpenTable, Strkr pushes a prep card to the GM plus the hostess sixty minutes ahead of service time. Guest name, preference list, whether tonight is their anniversary date, last visit on file, which server knows them best. Recognition at the front door moves from accidental into designed, which is the single lever that converts a first-time visitor into a regular.
Review capture
Catch delight while the table is still warm.
A post-visit trigger fires a text ninety minutes after the ticket closes with a one-tap sentiment ping. A delighted tap routes the guest to a Google review link. A mixed tap routes into a private feedback form that notifies the GM in real time. The two-path split captures the review before the moment fades and traps the complaint before it posts publicly as a one-star. Review volume at participating locations typically climbs three to six times inside the first two months on the platform.
Native integrations
The POS, reservations, email, payments.
Toast and Square push ticket data, check averages, and visit cadence into Strkr. Resy and OpenTable push reservations, cover counts, and no-show percentages. Mailchimp or Klaviyo keeps running the email send while Strkr feeds the segments into it. Stripe handles catering deposits and private event prepayments. QuickBooks and Xero pull in the catering invoices. Open REST APIs plus webhooks run the whole integration surface, so there is no middleware vendor sitting inside the stack between tools.
Group roll-up
A small group gets one aggregated view.
A four-restaurant group opens the events pipeline rolled up across all locations with filters by location, event type, or sales rep. The group operator asks on Monday morning what the events book looks like for Thanksgiving week and gets an answer in thirty seconds rather than firing three parallel text threads to three different GMs. Catering accounts shared at the group level sit together, and the VIP file travels with the diner from one location to the next.
Strkr AI pre-writes the private event proposal using the inquiry details and the menu catalog. It composes reactivation text for a lapsed VIP in the restaurant brand voice. It assembles the holiday catering outreach aimed at the top twenty corporate buyers. The events lead ships in a quarter hour what used to take sixty minutes. The marketing lead ships ten campaigns per quarter instead of two, which is where real pipeline fill actually happens.
Private events in detail
What a modern private dining pipeline looks like.
Buyouts and private events hold the highest margin line on a full-service profit statement. A buyout for forty guests at a 150-dollar per-head minimum clears a Tuesday night that otherwise might cover fifty-five seats at an 80-dollar average. The math is straightforward. The pipeline discipline needed to actually win that buyout is less obvious, which is why most restaurants still work events the way they worked them ten years ago.
Inquiry intake
Four channels, one feed, zero dropped leads.
Private events inquiries arrive down four channels: a website form, a direct note to events@, an inbound call, and sometimes an Instagram DM. Strkr merges every one into a single lead feed carrying source attribution. Nothing hangs out inside a shared Gmail label waiting for someone to notice. The internal target sits at a sub-two-hour first touch, which is the window where close rate on event leads falls off a cliff.
Reply SLA
Speed to the first touch wins the booking.
A trigger drops each inquiry onto the events lead with a task clocked to close inside two business hours. If the task slips, the GM gets a ping at four hours and the owner gets a ping at twenty-four. The industry pattern reads well-documented. The first restaurant replying with a credible proposal lands the booking sixty to seventy percent of the time, no matter how pricing differs within a fifteen-percent band. Speed to a credible first reply is what decides the sale.
Proposal in 20 minutes
Not two days of back-and-forth email tag.
Strkr AI pre-writes the proposal from the inquiry context: event type, headcount, calendar date, budget, dietary notes, food-and-beverage minimum, deposit terms, menu tier. The events lead edits the draft, drops in photography, and ships via a tracked link. The sales team then watches when the proposal was opened and how long it was read, which is the single signal that times the follow-up correctly.
Contract and deposit
E-sign, deposit, and calendar hold on one trigger.
A booking contract routes through DocuSign or PandaDoc for signature. The deposit rides inside a Stripe payment link packaged with the contract. Once both are complete, the trigger books the private dining space on the restaurant calendar, notifies the kitchen manager, locks the floor plan for that night, and schedules the pre-event walkthrough with the host. The handoff from sales to operations turns into a scheduled fire rather than a Monday-morning verbal conversation.
Pre-event packet
Kitchen and FOH each receive a prep sheet.
A full seventy-two hours before service, Strkr pulls together the prep packet for both the kitchen crew and the FOH team. The final headcount, the chosen menu, the allergen callouts, the course timing map, the VIP flags against the guest list, and any special requests from the buyer. The chef receives the packet printed on paper plus inside the app. The expo station reads the allergen flags off a printed sheet. No piece of the briefing stays trapped in the events lead notes app on a phone.
Post-event follow-up
The thank-you is what drives the next booking.
A day post-event, a trigger ships a thank-you note from the GM carrying a feedback link plus the next-booking inquiry, especially useful when the event runs annually or recurs quarterly. The event host receives a VIP tag inside the system with their event preferences stored on file. Any future inquiry from the same company opens with full history visible rather than reading as a cold outbound thread.
Catering sales in detail
What a B2B catering operation looks like at an independent.
Catering sales acts like a B2B motion that happens to come dressed as hospitality. The actual buyer sits in an office manager, HR coordinator, wedding planner, pharma rep, or hospital events team seat. These buyers purchase on repeat. Some pay on invoice net terms. Each one wants a dedicated contact rather than whichever server picked up the line that afternoon. The restaurants that treat catering as a real pipeline unlock a revenue line that routinely matches or passes dining room revenue by year three.
Account structure
The firm itself, not the lawyer who ordered last week.
Catering buyers live inside Strkr as accounts, with each account linked to several contacts (an office manager, an EA, a backup point of contact). When the office manager rolls off and a replacement starts, the account record carries the full history forward. Historical ordering patterns, preferred menus, the office dietary rules, and typical delivery windows all persist on the account. The replacement calls once, reads the record, and picks up without a reintroduction phase.
Pattern detection
The Thursday lunch becomes a tracked baseline.
A repeat corporate account carries a learned ordering rhythm inside Strkr. 25 lunches dropped every Thursday at 11am, allergen-safe tray included, invoice billed on month-end terms. When that rhythm slips (a missed week, a longer than usual gap), the account surfaces on a check-in flag. The office manager almost never fired the restaurant on purpose; they got busy, forgot the order, and welcome the follow-up call.
Menu library
Catering menus organized along season plus package tier.
The library inside Strkr stores catering menus along two axes. Season (autumn drop-off lunches, winter holiday platters, summer wedding packages). Package type (drop-off only, full-service, bar-inclusive). A catering lead builds a proposal by selecting the menu plus the package tier, and pricing fills in from the current catalog. Stale PDFs stop drifting across the shared Drive folder, which is the single most common birthplace of a quote mistake on this side of the business.
Deposit and invoice
Stripe deposit paired with QuickBooks net-term billing.
Each proposal ships paired with a deposit payment link. When the order books, Strkr writes a Stripe charge for the deposit and a QuickBooks invoice for the remainder on either net-15 or net-30 terms. The owner opens the receivables aging view on Monday morning without having to pull exports from three different systems and reconcile the results inside a spreadsheet manually.
Delivery and setup
Driver, delivery window, and the on-site contact.
Each catering order carries its delivery window, the assigned driver, a named on-site contact with a direct phone number, and a photograph of the setup for first-time accounts. The driver works off a mobile delivery card. The office manager receives a text once the driver is ten minutes out from the address. Next week reorder opens on a known-good delivery experience, which is the single strongest signal predicting that a corporate account becomes a repeat buyer.
Account tier ranking
Who the top twenty corporate buyers really are.
A ranking inside Strkr sorts catering accounts across four signals: lifetime spend, order frequency, typical order size, and recent growth trajectory. The twenty highest-lifetime-value accounts get a quarterly Thursday afternoon check-in call from the catering lead. The following hundred receive a seasonal menu-drop email. Everyone else lands in the holiday promo list. Outreach spend finally maps to account value, which is something most restaurants have never had the data to execute with any real precision.
Marketing in detail
Reactivation, segmentation, review funnel.
Marketing at an independent restaurant has to run on three parallel motions. Spotting the lapse before it hardens into a lost regular. Cutting the base along visit value and preference. Routing the delighted diner into a public review while the memory is sharp. A POS does none of this. A reservation platform does none of this. A loyalty app tracks points, which is a reward tool rather than a marketing engine. This is the empty slot a real restaurant CRM fills.
Cadence segmentation
Weekly, monthly, lapsed, and one-time cohorts.
Strkr cuts the guest base along the real visit cadence pulled from the POS. The weekly cohort gets one kind of message (chef nights, menu drops). The monthly cohort gets another (seasonal events, holiday reservations). Lapsed guests receive a reactivation offer tuned to the gap. One-time visitors receive a soft follow-up aimed at a second visit. A single blast to the whole list is a 2015 playbook still running at most independents today.
VIP lapse touch
Server-level outreach rather than a mass blast.
Once a VIP-tagged guest crosses the lapse threshold, Strkr opens a task on the GM or on the server who built the relationship. The task might read "Phone Linda. Has not been in since July. Her anniversary is coming up in a fortnight." The GM makes the call personally. Response rate on that one-to-one motion sits in a totally different band than a mass "we miss you" email blast.
Private tasting nights
The invite roster writes itself in Strkr.
Chef table nights, wine dinners, pop-up collabs. Strkr assembles the invite roster from guests who have attended similar events in the past, high-check regulars who have slipped a two-month gap, and the fifty top wine-club members on file. The GM reviews the pulled list in five minutes, hits send, fills the room without any public link going up. The exclusive feel is real because the invite roster is real.
Occasion booking
The anniversary, not a random weeknight.
Strkr catches birthdays and anniversaries at reservation time or when the guest file is next updated. Two weeks ahead of the date, a trigger sends a tailored "reserve your celebration dinner" note paired with a complimentary bottle offer. Occasion bookings close three to four times harder than cold outreach and bump the average check materially because the guest came in for the celebration itself, not simply a weeknight meal.
Review funnel
A one-tap post-visit sentiment ping.
Ninety minutes after the ticket closes out, Strkr fires a one-tap text asking how the night landed. A positive tap routes to a Google review link carrying the guest name and a smart deep link. A mixed tap routes into a private feedback form that pings the GM live, which opens a service-recovery window that mostly keeps the review out of public view. Positive review volume climbs three to six times, which is the primary discovery lever on Google for a neighborhood spot.
Channel respect
SMS, email, or print by whichever channel the guest opens.
Strkr respects channel preference guest by guest. Email readers get email. Text readers get SMS. The small set that answers a mailed card from the GM gets print. Each guest file carries a preferred channel plus per-channel consent flags. SMS runs through Strkr Messaging on an explicit opt-in flagged at reservation time or walk-in moment. Email ties across to Mailchimp or Klaviyo. Direct mail routes through Lob for small, high-value VIP touches that cut past inbox noise cleanly.
What a restaurant operator actually weighs
The honest checklist past 100 covers a night.
Nearly every "best restaurant CRM" roundup compares feature grids that overlap eighty percent across the top vendors. The actual evaluation lives along four or five axes nobody prints inside a brochure. Here is the version worth reading before putting a signature on anything.
Does it replace Toast?
No, and that is the right answer.
A CRM that tries to replace the POS asks a restaurant to replatform transactions, kitchen printers, tax reporting, tip-share logic, and end-of-day workflows. That is a six-month project carrying real operational risk. Strkr integrates with Toast and Square natively. The POS stays. The staff training stays. The pipeline layer sits on top of the existing stack.
Time to the first useful day
Days from signup through pipeline on a phone.
Strkr: three to ten days to a working events pipeline plus a running catering CRM with the Toast and Resy sync already in place. Most generic hospitality CRMs: four to twelve weeks assisted by an onboarding partner plus a template setup phase. That time cost compounds at a restaurant turning over leads daily that needs its pipeline live yesterday, not sitting on an onboarding timeline across the following quarter.
Phone usability
What a GM reads between the two services.
A GM typically has twenty minutes between lunch wrap and dinner line-up to review the pipeline, respond to new inquiries, text a lapsed regular, and sign off on a catering proposal. Strkr mobile ships as a first-class surface including an offline queue, voice-note capture for guest observations, and the complete pipeline rendered on hand. Most hospitality tools remain desktop-first with a mobile shell nobody actually opens mid-shift.
Group roll-up
A four-restaurant group opens one view.
Group operators need an aggregate. Pipeline aggregated across every location, catering accounts shared at the group level, VIP guest files that travel with the diner between venues. Strkr covers that shape natively. A single-location independent stays single-location without extra complexity, and the group upgrade is a configuration change rather than a migration event.
Pricing shape
Per staff seat on a flat line, not per guest row.
Strkr pricing bills per staff seat on a flat line. A guest base of 20,000 names or 200,000 names costs the same monthly figure. Restaurants carrying the biggest marketing upside (the ones with a decade of accumulated guest history) are not penalized by the contact-tier escalator that most email marketing platforms attach to their invoice. Payment goes to the people operating the tool, not the records stored inside it.
Exit cost
The guest data belongs to the restaurant.
Every CRM pitches data portability on its homepage. The actual experience of moving guest records, event history, catering accounts, and automation logic can run months. Strkr pushes clean exports to CSV plus JSON, logs each trigger as structured data, and keeps formula logic in readable expressions. The exit path is a day of work rather than a quarter, which is a healthy signal for a tool meant to run alongside a restaurant for a decade. HIPAA compliant with BAA available, SOC 2 Type II in progress through 2026-Q4, GDPR and CCPA compliant.
Head-to-head
Strkr next to the typical restaurant stack.
Most independent restaurants run on a combination of Toast gaps, Mailchimp blasts, and a shared events spreadsheet. Below is the direct comparison against Strkr. Toast and Resy both remain in the picture; Strkr fills the open slots those tools were never written to carry.
Feature
Strkr
Toast gaps plus Mailchimp plus spreadsheets
Private events pipeline shape
Dedicated pipeline carrying stages, SLAs, and auto-drafted proposals
Shared email inbox paired with a Google Sheet
Catering sales shape
Corporate accounts plus contacts plus recurring order tracking plus invoicing
One-off orders dropped via the POS or picked up over phone
Lapsed-regular reactivation
Overnight scan catches each lapse and fires tiered outreach
Rare "we miss you" blast whenever a staffer remembers it
VIP recognition at podium
Pre-service card to GM plus hostess carrying guest history
A server has to remember them or notice in real time
Review funnel shape
Post-visit sentiment text with routing by positive or mixed tap
A printed card asking for a review on the receipt tray
Guest segmentation
Visit cadence plus check average plus preferred server plus event history
One list, one blast, hope the open rate holds
Toast plus Resy sync
Native two-way sync carrying guest, ticket, reservation data
Hand exports plus CSV uploads shipped to Mailchimp
Strkr AI pre-writes proposals, reactivation copy, catering outreach
Every email composed from a blank text box
How teams use Strkr
Playbooks independent restaurants already work on Strkr.
Each pattern below shows up repeatedly across neighborhood independents, chef-led concepts, and small groups. Every one plugs an opening left by the Toast plus Resy stack, and every one maps to revenue a restaurant knows it is leaving on the table because the installed tools were never designed to surface the opportunity.
Neighborhood independent
Private events moves from inbox chaos to real forecast.
A ninety-seat neighborhood room was working events through a shared Gmail label and losing roughly one in three inquiries to a slow reply. Strkr collapsed the inquiry channels into one feed, locked in a two-hour reply SLA, and set up auto-drafted proposals. Within three months the events line booked a quarter the restaurant had never seen before, and the owner can now tell you on Monday morning exactly what sits booked across the next sixty days.
Chef-driven concept
VIP recognition goes from guesswork to designed.
A chef-driven spot with a cult following tagged its 200 highest-value regulars as VIPs inside Strkr. A Resy booking from any of those names now triggers a pre-service alert for the GM and floor captain carrying guest preferences plus most recent visit. The chef drops a personal amuse at the right table without needing a verbal flag. The repeat rate on tagged VIPs climbed noticeably through the first quarter of running the motion.
Catering-forward independent
Catering moves from one-off orders into repeat corporate.
A deli-style spot with a strong corporate lunch book modeled its forty highest-value corporate accounts inside Strkr. Each account carries the office manager contact, the ordering rhythm, and the office dietary rules on the record. The catering lead runs a Monday-morning check across any account that broke the usual pattern. Catering revenue climbed through year one and the catering lead no longer works evenings chasing down purchase orders.
Three-location group
Group-wide pipeline sits on one dashboard.
A three-location group had three parallel events inboxes feeding three parallel spreadsheets with no shared view. Strkr collapsed the pipeline into a group-level dashboard with filters per location. The group operator opens one tile Monday morning instead of chasing three GMs for a status update. Cross-location event referrals (location one booked solid, redirect to location two) moved from an exception to a regular weekly motion.
Emerging two-location group
Lapsed-VIP reactivation runs on autopilot.
A two-location group pulled 800 lapsed VIPs out of its guest base through Strkr cadence analysis. A quarterly reactivation trigger routes GM-level outreach to the hundred highest-value lapsed guests and ships a tailored SMS to the next seven hundred. Response rate on the top-hundred personal touch runs high enough that the booked revenue covers the next quarter marketing budget on its own.
The guest-growth layer the POS was not written to carry.
Toast and Resy stay exactly where they are. Add the pipeline that fills the private dining room, moves catering trays on repeat, and pulls the regular who went quiet back through the door. Start a trial and run a private events pipeline inside the first week.
No. Toast or Square keeps running the POS. Resy or OpenTable keeps running the reservation side. Strkr is explicit about keeping that boundary. The POS stays responsible for tickets, and the reservation platform stays responsible for the floor plan. Strkr sits next to the pair as the guest-growth plus marketing layer. It pulls guest, ticket, and reservation signal via native integrations while owning the pipelines neither of those tools was ever built to run. Private dining pipelines, catering sales, lapsed-regular reactivation, VIP recognition at the podium, and the review funnel. Replatforming the POS is a six-month risk project. Dropping Strkr in alongside it is a configuration change on top of what already powers the floor.
What restaurant shape is Strkr built for?
Full-service independents and small groups running one to ten locations. Neighborhood independents, chef-led concepts, destination rooms, emerging small groups. Strkr is not written for QSR fast-casual chains at fifty-plus locations whose operating model centers on throughput at the register and franchisee reporting. Underneath ten locations in a full-service or chef-led model, Strkr matches the operating shape exactly. The sweet spot sits at the one-to-four location independent that already runs a serious private dining program or catering line, plus the small-group operator who wants one pipeline view on Monday morning rather than three parallel conversations with three different GMs.
How does the private events pipeline actually run?
Events leads reach Strkr through four doors. The website inquiry form. A direct note to the events address. An inbound call logged by the host stand or events lead. The occasional Instagram DM. Each path writes a lead row tagged with event type, calendar date, headcount, budget band, and dietary notes. A trigger drops the lead onto the events lead task list under a two-business-hour reply SLA. Strkr AI pre-writes the proposal from inquiry context plus the menu library. Signature plus deposit ride the same sequence out through DocuSign or PandaDoc paired with Stripe. Once the contract has both signatures and the deposit lands, the system reserves the private dining space, pings the kitchen manager, locks the floor plan, and composes the prep packet three days ahead of event day. The morning after, a thank-you plus feedback sequence fires on its own. The events lead works off a dashboard showing sixty booked days ahead plus ninety days of qualified pipeline on one surface.
What does the lapsed-regular reactivation flow run in practice?
An overnight scan reads the guest base against visit data from Toast or Square and surfaces anyone whose rhythm has broken off. A regular who turned up every other week and has gone six straight weeks silent hits the lapse flag. The system then slices the lapsed cohort along VIP tier, check average, and preferred channel. The top-tier lapsed VIPs land as a task on the GM or on the server who knows them, for a personal call or text. Mid-tier gets a tailored SMS carrying an offer. The long tail gets a seasonal note tied to a fresh menu drop. The entire motion runs on its own and produces a weekly summary to the owner on reactivation revenue booked. The ninety-day quiet shifts from a silent decline into a tracked signal with a scripted answer.
How does VIP alerting at the podium actually work?
Once a guest earns a VIP tag inside Strkr, any future reservation routed through Resy or OpenTable triggers a pre-service alert. Sixty minutes before service, a card appears on the GM and hostess mobile carrying the guest name, visit history, favorite menu preferences, favorite server, and the occasion when one applies (anniversary, birthday, business dinner follow-up). The chef gets the dietary callouts on the kitchen printout. The outcome is simple: the VIP walks in and the floor already knows them before they reach the stand. For a walk-in, the podium can look up any guest in Strkr by name or phone number and the full file loads immediately on the host screen.
What does Strkr cost at a single-location independent?
Strkr runs on per-staff-seat pricing on a flat line with every module active on each paid tier. A single-location independent typically carries three to six seats on the invoice. The owner. The GM. The events lead or catering coordinator. And sometimes a marketing lead or a sous chef involved in event menu prep. Pricing lives on the pricing page and does not meter against guest base size, which inverts how most email marketing tools price. A twenty-thousand-name guest list costs the same monthly figure as a two-hundred-thousand-name guest list. The money goes to the people operating the tool rather than the records they operate on. SOC 2 Type II in progress through 2026-Q4 covers the controls underneath the data layer.
Which integrations ship live on day one?
The day-one integration list covers Toast and Square, Resy and OpenTable, Mailchimp and Klaviyo, Stripe, QuickBooks and Xero, DocuSign and PandaDoc, Google Business Profile, and Strkr Messaging across SMS and MMS. Guest data flows both directions with the POS and the reservation platform. The email marketing stack keeps running the send while Strkr pushes segments to it. Texting flows through Strkr Messaging on an explicit opt-in captured at reservation time or walk-in time. Event contracts and deposits route through DocuSign or PandaDoc for signatures and Stripe for payment. Review asks post to Google Business Profile. Open REST APIs working alongside webhooks run the full integration surface, so there is no middleware vendor sitting in between. The stack lines up with a real independent restaurant tool list rather than an enterprise suite shopping list. HIPAA compliant with BAA available for restaurants catering hospitals or clinical practices.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
