Event venues that field group enquiries by phone face a recurring operational challenge: answering, qualifying and tracking provisional holds across multiple overlapping bookings, policy changes and cancellations. Zanus AI's AI Phone and AI Booking modules address this workflow by automating enquiry capture, calendar availability checks and ownership assignment, so that coordinators can focus on negotiation and contract closure rather than call logistics. This guide examines how to structure group enquiry handling, differentiate enquiry status from confirmed bookings, and work through the competing demands that arise when dates shift or groups withdraw.

Why Group Enquiries Are Distinct From Confirmed Bookings

A group enquiry is not a booking. An enquiry is an inbound request for information: a caller asks whether the venue can host a party of fifty people on a particular Saturday in spring, what the space costs, what catering is included and what deposit is required. The enquiry has no contractual standing until the group signs a contract and pays a deposit. Between enquiry and contract, the enquiry moves through several states: unqualified (the caller name and size are not yet confirmed), held (the date is provisionally reserved so the venue does not double-book), and won or lost (the group has committed or chosen another venue).

A confirmed booking or contracted booking is a legal and financial commitment. The contract specifies the date, group size, services, price, payment schedule and cancellation terms. Until that contract exists, the date is not booked; it is held. Many venues treat held dates as bookings in their calendar, which creates ambiguity when the contract is delayed or the group cancels the hold. A clearer approach designates a held enquiry with a different marker (a note field, a tag or a colour code in the calendar system) than a contracted booking. This distinction protects the calendar from false bookings and ensures that coordinators know which dates are genuinely revenue-locked and which are still under negotiation.

Setting Up Enquiry Capture in AI Phone

Zanus AI's AI Phone answers the group's first call and collects essential facts before the call reaches a coordinator. The AI can be configured to ask for group name, party size, requested date, and any high-level preferences (such as outdoor or indoor space, dietary requirements, or AV needs). Crucially, the AI searches the live calendar to check availability, so it can tell the caller whether the requested date is free, held or booked. If the date is booked, the AI can offer alternative dates or ask the caller to hold for a coordinator to discuss options.

According to the Zanus AI AI Phone page, the system "answers on the first ring, 24/7, 365" and "answers from your approved knowledge, prices only from your catalog." For an event venue, the approved knowledge base should include your venue capacity by space, your published hourly or daily rates, your standard services (tables, chairs, linens, basic setup), cancellation policies and hours of operation. The AI does not invent prices; if a custom package is not in the knowledge base, the AI says "I'll have you speak with a coordinator" rather than quoting from memory.

When the enquiry call ends, the AI writes a summary to the caller's contact record. The summary includes the date requested, party size, any notes about preferences or concerns, and whether the caller confirmed their phone number by having it read back digit by digit. This record becomes the coordinator's brief for the outbound follow-up. If the caller requested a callback, the message lands in the coordinator's inbox with a timestamp and a read-back confirmation of the number.

Assigning Coordinator Ownership and Tracking Status

A group enquiry must have a single owner, a coordinator responsible for following up, negotiating terms and closing the contract. Without clear ownership, enquiries fall through cracks: two coordinators believe the other has already called back, or no one tracks the expiry of a provisional hold. Zanus AI's integration with your CRM or contact record allows you to assign an enquiry to a coordinator by setting an owner field on the contact.

The enquiry status should be tracked in a dedicated field, separate from the calendar hold. For illustrative purposes, a status workflow might be:

Enquiry Status Meaning Owner Action
Unqualified AI captured basic facts; caller identity or date not yet confirmed Call within 24 hours; confirm name, phone and date; ask about group type and budget
Qualified Hold Coordinator has spoken to the group; date held for 7 days pending contract Email contract proposal within 48 hours; follow up if unsigned by hold expiry
Under Contract Group has signed and paid deposit; date is booked and blocked Transfer to event operations; receive updates on headcount and logistics
Lost / Declined Group chose another venue or cancelled the enquiry Log reason; release date hold immediately; archive contact

In practice, the coordinator assigns the status when they first speak to the caller. The AI's initial call is logged as "Unqualified" because the AI has not verified that the caller is the decision-maker or that the date works for the group's budget. Once the coordinator calls back, confirms details and places a provisional hold, the status moves to "Qualified Hold" and a 7-day expiry date is recorded. If the group signs the contract, the status becomes "Under Contract" and the hold expiry is cleared (the date is now locked regardless of further negotiations). If the group declines or stops responding, the coordinator marks it "Lost" and releases the hold so that other enquiries can claim the date.

Provisioning the Calendar and Hold Duration

Zanus AI's AI Booking module connects to Google or Microsoft calendars and "offers only the free slots of your live calendar." For event venues managing held enquiries, this means the calendar must distinguish between fully available, provisionally held and contracted states. One method is to create a "Holds" calendar separate from your "Confirmed Bookings" calendar. When an enquiry is qualified and the coordinator places a hold, the coordinator manually creates an all-day or timed block on the Holds calendar with the group name and hold expiry date in the title (for example, "Acme Corp—50 ppl—Hold exp. Oct 18"). When AI Booking checks availability, it sees the Holds calendar as unavailable, so it does not offer that date to other callers. Once the group signs the contract, the coordinator deletes the block from Holds and creates the event on Confirmed Bookings, changing the visibility status so that other staff know the date is locked.

An alternative is to maintain a single booking calendar and use colour coding or event labels to flag hold status. For example, a grey block represents a hold, a green block represents a confirmed booking. The AI Booking system treats both as unavailable, but coordinators can instantly identify the status by colour when reviewing the calendar. The specific implementation depends on your calendar tool and your venue's existing workflows.

The hold duration (typically 5 to 14 days) should be set as a venue policy and documented in a shared reference. If a hold is 7 days, the coordinator notes the expiry date when placing the hold; the AI does not automatically release holds, so the coordinator must manually delete or cancel the hold block when the deadline passes and the group has not signed. This discipline prevents "dead" holds from accumulating and blocking dates that should be available.

Illustrative Scenario: Conflicting Date Requests

Consider a real-world conflict to test how the process handles complexity. On a Monday morning, the AI Phone receives a call from a caller requesting a date: "I'd like to book your east garden on Saturday, June 15th for a wedding of about 120 people." The AI checks the calendar and finds June 15th is available. It confirms the date, captures the party size and the caller's phone number, and offers to have a coordinator call back to discuss pricing and services. By mid-morning, the coordinator has logged in and sees the enquiry: a wedding, 120 people, June 15th requested. The coordinator calls the number, speaks to the bride-to-be, learns the budget is $8,000 to $12,000 for the space and catering, and the group needs an answer by Friday. The coordinator places a verbal hold, sends a contract proposal by email, and sets a calendar reminder for Thursday morning to follow up if the contract is not signed.

On Wednesday, a second call arrives: another caller wants June 15th for a corporate retreat, 85 people. The AI checks the calendar and finds the Holds calendar shows June 15th blocked by "Wedding—120 ppl—Hold exp. Fri Jun 19." The AI tells the caller, "That date is not available, but I can offer June 14th or June 22nd. Would either of those work?" The caller accepts June 22nd, and the AI offers it, captures the details and creates a qualified enquiry. The coordinator later reviews both enquiries: the wedding hold expires Friday; the corporate booking would be Saturday June 22nd, which is currently available. If the wedding group does not sign by Friday, the coordinator can move the wedding to June 22nd or offer it to the corporate group.

This scenario illustrates the workflow without collision because the Holds calendar prevented double-booking and the coordinator responded within the hold window. The system forced a deliberate choice: wedding on June 15th (if they sign by Friday) or corporate on June 22nd. Without a separate holds mechanism, both would have been marked "booked" and the coordinator would face an angry conversation with one group on Friday afternoon.

Handling Cancellation Requests and Hold Release

A cancellation can arrive at any point: before the contract is signed (a hold cancellation), after signature but before deposit (a contract cancellation), or after the event date (a refund dispute, out of scope here). The process for hold cancellations is simpler and must be frictionless because the caller has not yet committed payment.

If a group calls during the hold period to cancel, the coordinator should confirm the group's contact information and the date, state the hold release time in writing via email or text, and immediately remove the hold block from the calendar. The caller should receive a brief confirmation: "Your hold on June 15th has been released and that date is now available to other groups. Thank you for considering us, and we hope to work with you in the future." This transaction takes two to three minutes and requires no approval; the coordinator is empowered to release holds because they are not revenue-losing actions.

Cancellations after contract signature involve refund policy, which is external to the AI Phone and Booking system. The coordinator should log the cancellation in the contact record, note the reason if provided, update the enquiry status to "Cancelled—Refund Pending" and flag the event for your accounting team. The calendar hold must be deleted immediately so the date becomes available for new enquiries. Depending on your refund policy, the group may forfeit the deposit or receive a partial refund; that decision belongs to management, not to the AI or the coordinator's on-call authority.

The AI Phone does not automatically handle cancellations because they involve policy judgment. However, the AI can be configured to recognize a cancellation request and transfer the call to a coordinator with a note: "Caller is requesting to cancel their hold on [date]. Please confirm the cancellation and release the calendar block." This transfer routing ensures that the request is not lost and that a human makes the policy call immediately.

Using AI Phone Transcripts for Enquiry Documentation

Every call Zanus AI receives is transcribed and summarized. For group enquiries, these transcripts are valuable for two reasons: they provide a record of what the group said during the initial call (helpful if the caller later disputes the terms discussed), and they reduce coordinator note-taking, which means the coordinator can focus on the conversation rather than typing. The AI's summary becomes the opening brief: "Caller is planning a 120-person wedding, requested June 15th, has a budget of $8,000 to $12,000, needs an answer by Friday, and wants to know whether your venue can accommodate a live band." The coordinator can then open the call with, "I see you're looking to host a wedding here in June—tell me a bit about your vision," rather than asking the same questions the AI already asked.

In the event of a dispute (for example, the group claims they were told the price included open bar when the coordinator only offered beer and wine), the transcript is admissible evidence. This protection is valuable in event services because verbal proposals are common and memories diverge. By recording and summarizing every call, Zanus AI creates a written record that prevents misunderstandings from escalating into legal disputes.

Managing Multiple Events and Overlapping Holds

Venues with several spaces or event packages may field overlapping holds that span different areas. For example, a bride wants the garden for the ceremony and the ballroom for the reception on the same day. The calendar should reflect both blocks under the same event name so that the coordinator and other staff understand the full footprint. In Zanus AI's calendar system, you would create a single event (e.g., "Smith Wedding—June 15") and include both spaces and times in the event details and notes. Alternatively, if your calendar system requires separate events, create both and link them with a common reference number so they are treated as a unit for hold or cancellation purposes.

Holds that span multiple spaces or days (e.g., a multi-day conference using the ballroom, breakout rooms and kitchen on Thursday, Friday and Saturday) should also be treated as a single unit with a single expiry date. The coordinator places one hold with a clear label: "Tech Summit—300 ppl—Ballroom, Breakout A, Breakout B, Kitchen—Thu-Sat Jun 20-22—Hold exp. Jun 13." If the group releases the hold, all three spaces are freed. If they sign the contract, all three are locked. This atomicity prevents splits where one space is held and another is released.

Coordination Between AI Routing and Manual Handoff

The AI Phone can be configured to route enquiries to different coordinators based on event type, party size or requested date. For example, "Wedding enquiries go to Sarah; corporate events go to Tom; anything over 500 people escalates to the events manager." This routing is set up in your AI Phone departments and policies. When an enquiry comes in, the AI identifies the event type (by listening to the caller or asking), then transfers to the assigned coordinator with an announced transfer: "I'm connecting you to Sarah, our wedding coordinator, who will discuss your date and pricing." The coordinator hears a voice notification: "Wedding enquiry, June 15th, 120 people, caller name and number confirmed," and presses 1 to accept the call.

This announced transfer prevents callers from reaching voicemail or the wrong person. If Sarah is on another call or away, the AI can offer to take a detailed message and trigger a callback queue so Sarah knows to call the group within a specific timeframe (e.g., within 2 hours during business hours). The message lands in Sarah's inbox with the full transcript and summary from the AI's initial conversation, so Sarah has context before she dials back.

Tracking Enquiry Metrics and Pipeline Reporting

Zanus AI's analytics dashboard shows call volume, call outcomes and departmental routing. For event venues, this data helps you understand enquiry flow and identify bottlenecks. For illustrative purposes, suppose you receive an average of 30 group enquiries per month. The AI Phone analytics show that 25 of those are converted to qualified holds (83%), and 18 of those are converted to signed contracts (72% of holds). The remaining 5 enquiries each month are lost to competitor venues or budget constraints. By tracking these metrics over time, you can identify whether your hold-to-contract conversion is improving (a sign of better sales technique or pricing) or declining (a sign of market pressure or changing buyer preferences).

You can also track the median time from enquiry to contract signature. If the median is 3 days and your policy is a 7-day hold, most groups are signing within the hold period, which is healthy. If the median is 12 days, groups are asking for hold extensions and your coordinators are managing multiple simultaneous negotiations. This metric suggests you may want to extend the standard hold period or hire additional coordinators.

The AI Phone also captures which coordinators convert enquiries most effectively. If Sarah closes 80% of her holds and Tom closes 60%, Sarah may be more experienced or better matched to your venue's target market. This data helps with training, hiring and workload distribution.

Rejection Scenarios and Scope Boundaries

Zanus AI's AI Phone is designed to handle enquiry capture, calendar checking and initial qualification. It is not designed to negotiate pricing, to discuss custom packages that are not in your catalog, or to make exceptions to your policies. If a caller asks, "Can you do a 150-person wedding for $5,000?", the AI searches the knowledge base for pricing. If $5,000 is below your published minimum, the AI says, "Our starting price for a wedding of that size is $8,000. Let me connect you with a coordinator to discuss whether there are any options." This boundary keeps the AI honest and ensures that pricing discussions happen with an authorized staff member.

Similarly, if a caller asks about a service not in your catalog (e.g., "Do you have an in-house pastry chef?"), the AI says, "We partner with external vendors for catering. Let me have a coordinator send you our approved vendor list." The AI does not invent services or claim capabilities that would require follow-up correction later.

Acceptance Criteria and Testing the Workflow

Before deploying AI Phone and AI Booking for group enquiries, define acceptance criteria so you know when the system is working correctly. An acceptance test might include:

Test 1: Enquiry Capture. A test caller phones and requests a date. The AI answers on the first ring, asks for party size, group name and date, reads back the phone number, and summarizes the enquiry. The transcript is accurate and includes all captured facts. The coordinator receives a notification with the full message and can call back the test caller within 5 minutes.

Test 2: Calendar Availability Check. The calendar is blocked with a known hold (e.g., "Wedding—June 15"). A test caller requests June 15. The AI informs the caller that date is not available and offers June 14 or June 22. The AI does not offer June 15 as an option.

Test 3: Conflicting Requests. Two test callers request the same date within 1 hour of each other. The first caller is placed on a hold; the second caller is offered alternatives. Both calls are logged with distinct enquiry records and the dates are not double-booked.

Test 4: Hold Cancellation. A coordinator receives a cancellation request from a test group. The coordinator updates the calendar and contact record; a follow-up call confirms the date is now available. A third test caller is able to book the released date.

Test 5: Message Accuracy. The AI takes a message from a test caller who calls after hours. The message is transcribed, the callback number is read back and confirmed, and the message appears in the coordinator's inbox with a timestamp and urgency flag if set.

These tests validate the core workflow without requiring a live event or paying customers. Once the acceptance tests pass, you can run a pilot with real enquiries for one month and measure the metrics: average time to first callback, hold-to-contract conversion rate, and coordinator feedback on the AI's message quality.

Integrating Enquiry Data With Event Management

Once a group signs a contract and moves from "Enquiry" to "Booked Event," the contact record and event details should flow into your event management system or spreadsheet. Zanus AI's contact and event data can be exported or integrated with external tools via API, so that your event operations team receives the headcount, setup preferences, billing contact and any special requests (dietary restrictions, AV requirements, restricted items) that the coordinator captured during the sales call. This handoff prevents loss of information and ensures that the operations team knows exactly what the group paid for and what to deliver.

The workflow is: AI Phone captures enquiry → Coordinator qualifies and holds → Group signs contract → Contact and event details move to Event Operations → Operations team builds the event day timeline, assigns staff and vendors, and executes. If this handoff is missing, the operations team may re-invent the wheel or deliver a different product than the group expected.

Key Takeaways for Event Venue Operators

Implementing Zanus AI's AI Phone and AI Booking for group enquiries requires clear definitions of enquiry status, coordinator ownership, and hold duration. The AI handles the high-volume, repetitive work of answering calls, capturing group size and dates, and checking calendar availability, which frees coordinators to focus on negotiation and contract closure. Provisioning a separate Holds calendar or using colour coding keeps held dates distinct from confirmed bookings, which prevents double-booking and reduces confusion. When conflicts arise (two groups requesting the same date, or a group cancelling a hold), clear processes and calendar discipline allow the coordinator to resolve them quickly and offer alternatives. By treating AI Phone as a intake system and coordinators as closers, you maximize the chance that qualified groups move from enquiry to contract and operations can execute on their promise. The workflow succeeds when the AI gives coordinators a warm handoff—a complete message, a transcript, a contact record and a calendar that is already checked—so the coordinator can open the conversation at "Let's discuss your vision" rather than "Let me grab your details."

Official sources and related guides

This independent Sysevo guide uses the following official documentation. The workflow and trial scenarios are evaluation proposals, not reported customer results or a hands-on benchmark.

Compare the same requirements with the relevant Sysevo product, Voice Agents and CRM. Review Sysevo plans and pricing or book a demo to discuss the proposed setup. Sysevo sells its own business software and is not affiliated with the competitors discussed here.