The Boutique stays 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 Boutique stays page.

Boutique stays — this pack was built for the calls that reach this kind of business. Illustrative photograph.

Fields that are filled when the call ends

This trade pack is built to order. Below is the design we switch on for you: the fields, stages and never-say list are drafted, so with your price list and hours it can be switched on within days.

Dates and number of nightsGuests and cabinPetsExtras (barbecue, breakfast)Rate quoted and the direct-booking savingPayment request sent

The stages an inquiry moves through

How many inquiries sit at each stage, on one line — in the order work actually flows in a Boutique stays.

Inquiry→Cabin held→Deposit received→Stayed→Return visit
PipelinePipelineInquiry4Cabin hel3Deposit r2Stayed1Return vi1

What it will not do

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

  • It never sells a cabin that is not free.It books only from the live availability board. A double booking means a guest turned away at the door.
  • It never bends the refund policy.It reads the cancellation terms as written. A weather exception — “full refund if it rains” — is the owner’s decision, and the question goes to the owner.
  • It never invents what is nearby.Asked what is around the cabins, it says only what the owner has confirmed.
  • It never chases the deposit.It sends the payment details and waits. It does not take a payment itself.

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.