Does Strkr replace Tripleseat or Delphi.fdc for a venue coordinator?
No. Tripleseat and Delphi.fdc remain the systems of record for the BEO with the venue production specifications, the kitchen prep sheet integration, and the folio connection. What Strkr replaces is the coordinator workflow stack that wraps around the BEO system: email folders for deposit tracking, Google Docs for the run of show, email threads for vendor coordination, Mail for planner outreach, and the shared spreadsheet for outstanding items. Strkr integrates with Tripleseat, Delphi.fdc, and Opera via native connectors so the group record flows into Strkr, coordination runs in Strkr, and the final BEO publishes to Tripleseat or Delphi for operations. The coordinator collapses six to eight surfaces into one.
How does the BEO handoff from sales work?
The sales manager signing the group contract fires the BEO handoff flow with every field pre-populated: dates, arrival and departure schedule, room block (by room type), meeting space (by room, setup style, capacity), F and B package (by meal period, headcount, service time, dietary restrictions), AV requirements, setup diagram, attendee list, VIP flags, billing instructions, and master account. The coordinator opens the BEO with the full package instead of six email attachments. Fields that need final confirmation (final headcount, final dietary count, final AV equipment, final setup time, final run of show) sit on an outstanding-items list the coordinator works through with the planner on the per-item cadence. The BEO lands finalized at T-minus-10-days consistently instead of T-minus-3 scramble. The final BEO publishes to Tripleseat or Delphi.fdc for the operations team on the T-minus-24 lock.
How does the deposit tracking work with the ledger?
Each group contract carries a deposit schedule on the ledger with the milestone dates (25 percent at signing, 50 percent 60 days out, 25 percent 10 days out, final balance 7 days post), amounts, received status, and the chase cadence. Milestones not received at T-minus-7 fire a reminder email to the planner. T-minus-3 fires a second reminder. T-minus-1 escalates to the sales manager. T-minus-0 the deposit is overdue and surfaces on the Monday ap conversation. Deposits received flow back to the Opera folio or the master account automatically through the native integration. The coordinator and the sales manager stop running the status conversation every Monday because the ledger is current. For properties running Stripe or AmEx CORE for deposits, the integration posts the receipt to the ledger automatically.
How does the vendor coordination timeline work?
Each event carries a vendor coordination timeline with every third-party vendor (AV, florist, DJ or band, decor, photographer, transportation, specialty rentals, security) on one view with load-in time, setup time, event time, strike time, and confirmation status. A booked vendor gets Strkr Messaging SMS requesting confirmation within 24 hours of booking. Unconfirmed vendors escalate at 48 hours to the coordinator. Vendors cancelling at 2 days out fire the backup vendor contact flow with the preferred alternates sorted by vendor performance score. The coordinator triages the unconfirmed and cancelled vendors in 10 minutes a day on the vendor confirmation board. On event day, the final load-in and strike schedule distributes to every vendor via Strkr Messaging SMS at T-minus-24 so everyone works off the same locked schedule.
How does the dietary roster handle the T-minus-72 lock?
The dietary roster carries a structured list per attendee with name, meal choice, dietary restriction (vegetarian, vegan, gluten-free, kosher, halal, nut allergy, shellfish allergy, dairy allergy), and seating assignment. The planner updates the roster directly through a shared link so the coordinator and the chef see the current list instead of forwarding emails back and forth. At T-minus-72 hours the roster locks per the contract terms. Final counts flow to the chef with the structured list broken down by meal period and dietary category. The planner adding dietary restrictions after the lock fires an alert to the coordinator who can accept the late add with the chef acknowledgment or escalate per the contract terms. The dietary summary across the week rolls up for the chef so the Sunday prep conversation runs off real counts.
How does the post-event feedback cadence drive rebook conversion?
A completed event fires the post-event feedback cadence automatically: thank-you email on day 2 with photos from the event attached, structured satisfaction survey on day 7 (food quality, service quality, AV quality, coordination experience, likelihood to recommend, specific comments), next-year date-hold inquiry on day 30 for annual events, and formal rebook outreach on day 90. The coordinator and the sales manager see the survey responses on the group record. Low-score surveys flag for recovery outreach from the general manager. For annual events (galas, conferences, corporate meetings) the next-year rebook conversion typically runs 70 to 80 percent when the cadence runs on template vs 30 to 40 percent when the thank-you is manual and often forgotten. The repeat-planner relationship timeline preserves the feedback across years so the next-year quote starts with full context.
