The Wedding & event venues pack

Everything in the pack,
and everything it will not do.

The CRM fields and stages that follow every call, what it connects to, and what it never says. Why any of it matters is on the Wedding & event venues page.

Wedding & event venues — this pack was built for the calls that reach this kind of business. Illustrative photograph.

Fields that are filled when the call ends

Not an empty CRM bent to a Wedding & event venues over months. These fields are in it from the start and the first call writes into them. This pack is running today.

Date and time of day wantedExpected guest countEvent type (wedding, birthday, corporate)Hall and catering rate quotedConsultation slotBest time to reach the couple

The stages an inquiry moves through

How many inquiries sit at each stage, on one line — in the order work actually flows in a Wedding & event venues.

Inquiry→Consultation booked→Consultation and hall tour→Quote finalised→Contract signed
PipelinePipelineInquiry4Consultat3Consultat2Quote fin1Contract 1

What it will not do

Not a setting you switch on and off. These are blocked when the Wedding & event venues answering is built; anything that touches them goes to a person instead of being answered.

  • It never holds a date.It confirms availability and books the consultation. A date is held only by a signed contract, so “could you keep the four o’clock under our name” goes to the venue manager.
  • It never fixes a quote.It gives the starting figures for catering and the room. The minimum guest count and the options are settled at the consultation.
  • It never promises a discount.The only promotions it mentions are the ones registered. It does not invent terms.
  • It never discusses other bookings.Who has booked the day, or how many couples have toured, is not disclosed.

This page is the list; the argument is on the other one. What kind of call comes in at night, what a missed one costs, and why a machine must not say certain things are written on the page this pack came from.