Tour and tasting bookings are the clearest fit. A system can read a request from your website form, email, or a phone transcript, check it against your actual calendar, book the slot, send the confirmation and reminder, and manage reschedules or a waitlist when you're full. It can also answer the questions that repeat every day: hours, group size limits, whether kids are allowed, what a flight costs if that's published. Event inquiries split in two. A standard package with fixed pricing, a small birthday tasting, a set group rate, can be quoted and booked the same way. A wedding buyout, an off-menu request, or anything priced by negotiation still needs a person on the phone.
Wholesale reorder chasing is a pattern-matching problem, which makes it a good fit for an operations system. It can track each account's order history, work out roughly when a restaurant or bottle shop is due to run low, and send a reorder reminder to the buyer. If there's no response, it follows up again, then flags the account to your sales rep instead of chasing forever. What it can't do: negotiate pricing or terms, resolve a billing dispute, or decide whether a slow-paying account still gets credit. Those stay judgment calls for whoever runs that relationship.
Bottle-club shipments are mostly mechanical, so they can run close to end to end. On release day, a system can pull the member list, generate the shipment data, hand it to your carrier or fulfillment partner, send the tracking email, and retry a card that failed before the bottle goes out. What has to stay human is deciding who's even eligible to receive a shipment: direct-to-consumer alcohol rules differ by state and license, and that's a legal decision, not a scheduling one. A person sets the rules, the system enforces them, and a person still handles damaged shipments and refunds. If none of this exists yet, no booking calendar, no club database, that's a build first: a real application with payments and a database behind it, not just automation wired into tools you already run.