Boutique hotels · CRM
A hotel that remembers its guests can write to them as people.
A CRM for a boutique hotel is one record of every enquiry, guest and group, with what they asked and what happened next. GullySales sets up the record, the stages and the habits that keep it current without burying the host in forms.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For boutique hotels
Where it usually goes wrong, and what we would do.
“The guest's preferences are in a chat thread”
The pillow choice, the anniversary and the dietary note sit in a WhatsApp conversation from last year. When the guest returns, nobody finds it and the host asks the same questions again.
“Groups need a different record”
A team offsite has a contact, an approver, dates, headcount and a quote in progress. Keeping it in the same list as couples loses the stage it has reached.
“The owner's memory is the only system”
The host remembers everybody, until a busy season or a new manager arrives. The record has to live somewhere the next person can read.
“Software the staff will not open”
A heavy system with twenty fields gets ignored by a busy front desk. A short record that fits a phone screen gets filled in.
What we do
What we deliver for boutique hotels.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A guest and enquiry record
Name, dates, party, source, preferences and stage, on a short form fit for a phone.
Result: Every enquiry and past guest has one findable record.
Stages for stays, groups and events
A simple set of stages, such as asked, replied, quoted, booked and stayed, with a separate path for groups.
Result: You can see where each enquiry stands.
A preferences note that carries over
Space to record likes, allergies, occasions and anything the host promised.
Result: A returning guest is greeted with what they said last time.
A simple tool chosen for your size
A recommendation among sheets and CRMs in ordinary use in India, matched to how many people will use it.
Result: The team uses a tool it can open without training.
A habit set for the front desk
Two or three updates the front desk makes at check-in and checkout, written as a short card.
Result: The record is current without extra meetings.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
Keep these fields for each guest and enquiry.
- Room, dates and rate offered
- Filled by whoever replies. Shows what was quoted, so a guest who returns is given the same answer.
- Reason for the stay
- Filled at the enquiry. Lets the front desk prepare an anniversary cake or a quiet room, and lets you invite the same guest back.
- Source of the booking
- Filled at check-in. Shows how many guests came from Instagram, a platform or a friend, and where commission was paid.
- Preferences noted during the stay
- Filled by the front desk. Pillow, breakfast, floor or a dietary need, kept for the next visit.
- Guest contact and consent to write
- Filled with the guest's agreement. Lets you send a note about a new room or a season without writing to people who did not agree.
Who it is for
This is written for these boutique hotels.
- Design-led city hotels in restored buildings
- Boutique hotels in old town neighbourhoods
- Courtyard and haveli-style small hotels
- Small hotels on a coffee or tea estate
- Beachside boutique hotels in Goa and the coast
- Hill and forest boutique hotels
- Heritage-style small properties run by a family
- Boutique hotels with a restaurant or a studio attached
Before you decide
When this may not be the right fit.
- You have few rooms and the owner knows each guest, so a notebook does the job.
- The front desk staff keep changing and nobody will keep the preferences, so the record would go stale.
Before you decide
Agree the work. Know how to judge it.
CRM for boutique hotels: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from boutique hotels. Anything missing is noted in the written scope, with who will supply it.
- The register and the chat threads
- The record starts from what you already hold, so bring the booking register, the phone's chat history and the inbox. They can be untidy. Without them the record starts empty, and the preferences of regular guests are lost until the host writes them down. Include any notes cards, a diary or a list kept by the front desk, since small details about regular guests sit there and nowhere else, and cannot be rebuilt from the chat.
- A host's list of regular guests and their habits
- Returning guests are the best use of a record. Write who they are, which room they prefer and what they asked for last time. If the host cannot, the front desk can. Without the list the first reminders go to the wrong people. Write a short line for each, such as prefers the courtyard room, vegetarian, travels with a dog, so the record opens with the guests who matter to you already described.
- A decision on who may see guest details
- Guest information is private. Decide which staff can view, edit or export a record, and who is responsible for it. If nobody is named, access is given to the host alone and front desk entries wait for the host to approve them. Guest names, phones and preferences are personal data, so decide who in the hotel may see them, who may export them, and who is told if a guest asks for their details to be removed.
- The front desk's time for a practice shift
- A record is only as good as the person who types it. Set aside a shift where the front desk uses the tool for real, with us watching. If they cannot, the host enters the records, and the load on the host is noted. Choose a quiet shift and let the front desk enter real enquiries, not practice ones, so that we see where the screen slows them and fix it before the system is switched on for the whole hotel.
- Your adviser's view on stored identity papers
- A hotel records identity documents for legal reasons, and the rules differ from the guest preferences held in a CRM. Ask your own adviser what must be kept and how. Without that advice, the CRM stores only preferences and enquiry history and nothing about identity. The rules on registering foreign and domestic guests are for your own adviser to explain, and the CRM stays separate from that register, so that nothing in it is mistaken for the legal record.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Follow one guest from enquiry to return
We take three stays, a couple, a group and a returning guest, and trace each from the first message to the stay and the note afterwards. You tell us where the host's memory carried the load. Those points become the stages of the record, in words your staff use. We ask the host to write down every place where the memory of a guest lived, such as a chat thread, a diary, the front desk register or a note on a card, so none of it is lost.
- 2
Choose a tool the front desk will open
We compare a simple sheet, a free tool and a paid one against your size and your staff's habits. You decide, and we write down why. A tool the front desk will not open is worse than a notebook, so we test it on a real shift before committing. The tool must fit a front desk that is also a bell, a telephone and a breakfast table, so it needs to open fast on a phone and to accept a note in a few taps.
- 3
Build the guest and group records
We set up the fields the host needs: guest, dates, party, occasion, preferences, source, price quoted and stage. Groups get their own record with space, meals and contact. You strike out any field the staff will not fill, and we keep the record to one screen. A group record also holds the person who decides, the person who pays, the dates under discussion and the quote sent, so a group lead is never asked the same question twice by two members of staff.
- 4
Bring in past guests and the preferences notes
We move names and stays from the register and the chat threads, merging duplicates by phone number in front of you. The host adds the preferences remembered about regular guests, such as the quiet room. Anything we cannot confirm is marked as unconfirmed. The host adds what is only remembered, such as the guest who wants the room away from the lane, the one who is allergic to a flower, and the one who prefers to be left alone at breakfast.
- 5
Set the reminders and the privacy rules
We set reminders at each stage, such as a quote waiting for an answer or a returning guest due a note. You decide who can see which records, and what is kept about a guest and for how long. Identity papers are handled as the law requires, and you check the rule with your own adviser. We leave identity papers outside the CRM unless your adviser says otherwise.
- 6
Run a live shift and hand over
The front desk enters live enquiries for a shift with us watching, and the host reviews the records afterwards. You confirm who owns the data and who may delete. The old chat thread is retired as a record only when staff say the new one serves them better. We also write a one-page guide for the front desk showing what to enter after an enquiry, after a check-in and after a stay, in the order those events happen.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need paid software?
Is guest information safe in a CRM?
Will staff actually use it?
What guest information must we keep for the police?
Can the CRM tell us which guests are due a return visit?
What should the host write down after a stay?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for boutique hotels
Related work to consider.
Closest to this: leads and follow-up
Also for boutique hotels
Or start from the overview: sales and marketing for boutique hotels.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.