Questions, answered

Click Get started, then use Proto to configure Wedding Planning Platform for your business. Pilot one upcoming wedding: draft its events, route them through review, submit its vendor commitments and load its guest list, then reconcile reservations and payments before adding more weddings.

Yes. Record the welcome dinner, ceremony, reception and brunch as separate events, each with its own venue, times and capacity.

The planner submits an event or vendor commitment. The Planning Director approves, returns or rejects it with a reason. A change after submission needs a new decision.

Guest responses can come from a connected RSVP website. Each response becomes a reservation with a guest reference and party size, within the event’s capacity.

Work from the list of guests not yet admitted. Each reservation is admitted once with the time recorded, and a repeated admission is not counted twice.

Yes. A paid place is held only after the payment provider’s capture is verified, and cancellations prepare refunds against verified captures.

Each vendor commitment records the agreed fee and the couple’s approval. Reports total agreed fees by event and vendor; vendor invoices and payments stay in your accounting system.

Unused reservations are released, admitted history stays, refunds are prepared against verified captures for approval, and the event is marked Cancelled.

Prepare the venue list, team members, open events, vendor bookings and guest lists with stable references. Rehearse the import on one wedding and reconcile before moving the rest.

Ordinary manual use has no per-user charge under the platform policy. Imports, integrations, agent execution and other machine work consume prepaid credits; implementation is scoped separately. The pricing page lists the current rates.