Reunions are organized by volunteer family members or class-of-1995 alumni who took on the responsibility once and will not do it again. They are not professional planners, the budget comes from RSVP contributions that show up slowly, and the timeline runs 8 to 14 months from first inquiry to event date. The questions are dense: can we have a weekend-long package with Friday meet-and-greet, Saturday lake day, Sunday brunch, do you do name tags with maiden names, is there a hotel nearby that does room blocks, can the kids do canoes while the adults talk, and how much per person all-in.

SleekAI maps weekend reunion packages with multi-day pricing, lakeside lodge availability from wp_postmeta, hotel partner posts with room-block contact info, name-tag printing add-ons with maiden-name fields, kids activity inventories (canoes, mini-golf, lawn games), and pavilion catering menus as resolvable variables. The cousin organizer types we have 90 family members, want Saturday-Sunday August 15-16 2026, half kids, and the bot returns the matching package, lakeside lodge availability, partner hotel for the room block, and per-person all-in pricing.

Generic bots cannot reach any of this. They quote single-day venue rentals when reunions need two or three days, miss the hotel partnership entirely, have no concept of name-tag printing with maiden names for class reunions, and ignore that family reunion budgets are collected via per-cousin contributions that arrive over months. SleekAI handles the structure and respects how reunions actually budget.

Reunions get organized by family volunteers or alumni who took on the job once. They are not professional event planners. They are working through this in evenings and weekends across an 8 to 14 month timeline, often with budgets that come together slowly as relatives contribute their share.

A planning workflow that requires three phone calls and four emails to get a basic quote loses these inquiries to the venue that answered every question in one chat. SleekAI is structured for this. The bot remembers context across multiple chat sessions because conversation logs live in WordPress, so when the organizer returns in October to ask the same question they asked in July, the bot can summarize prior context and pick up where they left off.

The 14-day soft hold (rather than the 72-hour default for other event types) gives organizers room to confirm the date with several relatives before committing. Adult and kid split pricing matters more in reunions than in any other event category. Family reunions routinely run 30 to 40 percent kids under 12, and a quote that prices everyone at the adult rate inflates the budget so much that the organizer walks away.

The bot reads adult and kid rates from postmeta separately and returns a realistic total. Hotel room block partnerships save organizers from researching lodging on their own. Each venue links to one or two hotel partner posts with room-block contact info, negotiated rates, and distance in miles.

The bot returns the matching hotel automatically when the conversation mentions out-of-town family, and organizers share the info with cousins coordinating their travel. Class reunions add their own wrinkles: yearbook photo walls, class composite displays, decade-themed playlists, and class-roster name tags. The same engine handles both event types, with taxonomy terms routing the bot to the right package set and add-on list.

Volunteer organizers do not have time to learn a complicated booking process, and the bot meets them where they are.