Building a Booking-to-Host Assignment System for 300+ Events a Year

A nationwide events business with a fragile hand-off

I worked in a nationwide consumer events business serving corporate events, business meetings, birthdays and other occasions outside the wedding market. Client-facing managers turned enquiries into confirmed bookings, then assigned each event to a distributed network of hosts.

The product addressed the most fragile operational hand-off: the point between a manager confirming the event with a client and a host accepting responsibility for it.

I owned product design, rollout and iteration

As Product & Business Development Lead, I owned the 0-to-1 product design and rollout. I mapped the booking-to-assignment journey, defined the MVP, designed the routing and notification logic, and coordinated delivery with a designer, developer, analyst and lead manager.

I made day-to-day product and workflow decisions independently. I agreed changes to the wider operating model with my manager and remained accountable for product performance and iteration through February 2023.

Host assignment depended on repeated one-to-one chats

Once a manager agreed the event conditions with a client, assigning a host depended on repeated one-to-one chat. Managers had to check availability, track replies, resend order details and confirm who had taken responsibility.

That left managers with avoidable coordination work and little visibility. It also slowed both final assignment and the host's response to a new offer.

One month, five people and an existing habit to respect

The MVP had to move from definition to launch between June and July 2021. A five-person core team needed to align product, design, engineering, analytics and day-to-day client operations while continuing to deliver live events.

Hosts already worked in Telegram. A solution that required a new account and interface would have made adoption harder.

Reduce the workflow to one reliable loop

I documented the workflow I saw in daily operations, identified the recurring friction and reviewed available solutions. A full authenticated platform would have duplicated tools hosts already used without improving the core hand-off.

The essential loop was simple: create a structured order, offer it to hosts, capture acceptance and notify both sides. That set the trade-off: launch a reliable assignment flow in one month, then add more controls through iteration.

Automate coordination after the client decision

The redesign removed repeated coordination without changing the client-facing conversation. Automation began only after a manager had confirmed the event conditions.

A structured booking flow with Telegram as the host interface

We built a booking-to-assignment system for distributing event orders. Managers could create or update a booking, offer it to the host network, see its acceptance status, reassign work and keep both sides informed through notifications.

The interaction layer stayed inside Telegram for hosts, supported by the routing and control logic needed behind the scenes. This reduced adoption friction without limiting the operational workflow.

We deliberately left client conversations with managers. The system automated the internal hand-off, where structured information and clear ownership made the biggest difference.

Four decisions kept the MVP focused

99% adoption and a much faster hand-off

The business delivered more than 300 booked and hosted events in both 2021 and 2022. After launch, the system became the standard operational hand-off and handled approximately 99% of eligible orders.

Manager coordination fell from 1–2 hours to 15–20 minutes. Host response times previously ranged from 15 minutes to 2 hours; after rollout, they ranged from 1 to 20 minutes because structured, high-priority notifications made new work immediately recognisable. These ranges came from operational observation over roughly six months; the original order count was not retained.

Average delivery cost per event fell by 25%. The review used January year-on-year comparisons for 2021 → 2022 and 2022 → 2023, including compensation, equipment, website and software infrastructure, and coordination time.

In structured interviews conducted over three months, 78% of 80 managers and hosts rated the overall experience 8/10 or higher. The group included managers from another department, and the interviews also covered ease of use, strongest features and areas to improve.

The rollout needed as much design as the workflow

The hardest part was not designing the workflow; it was helping people move away from a method they already knew. I learned that adoption is part of the product, not a separate change-management task.

Next time, I would involve managers and hosts earlier, make their existing pain more visible, and pair the rollout with short onboarding and an explicit feedback loop. A better solution only creates value when the team understands why it is better.