Accommodations Lagos Nauti Girl

Sixteen things that can run themselves

A working menu of automations for both businesses: the guest messages, the crew handovers, the calendar juggling and the follow ups that today depend on somebody remembering them.

Ideas on the table
16
Businesses
2
Ready in phase one
5
Date
26 Aug 2026

Reference code

AL for Accommodations Lagos, NG for Nauti Girl, X for anything that touches both. Use the code to point at an idea in the meeting.

The chain

Every idea is written as what sets it off, what happens next, and where it lands. None of it needs a button pressed.

Effort

Quick win is days. Standard is a week or two. Bigger build needs a proper scope. No idea here is a research project.

Start here

Two entries carry this badge. They pay off first, and most of the rest leans on them.

The ideas

Filter to one business to talk through them separately.

Accommodations Lagos · the guest journey
AL-01

The mid stay check in

Start here

On the morning of the middle day of every stay, the guest gets a short WhatsApp or email asking if everything is right. Happy guests get a warm reply and go on the review list. Anything that sounds off reaches the office within seconds, while the guest is still in the property and the problem is still fixable.

Turns a bad review into a phone call Quick win
  1. Trigger
    Stay reaches its halfway point
  2. Message goes out in the guest's own language
  3. Reply is read and sorted into happy, neutral or a problem
  4. A problem is flagged with the property, the guest and what they said
  5. A happy guest is queued for the review ask at checkout
AL-02

The arrival pack that sells

Three days before arrival the guest receives everything a guest would otherwise have to ask for: directions, the door code, parking, wifi, bins, the good bakery. At the bottom sits a short offer list, and the first item is a Nauti Girl cruise on a date inside their stay.

Kills the repetitive arrival questions Sells cruises before they land Quick win
  1. Trigger
    Three days before check in
  2. Pack is assembled from that property's own details
  3. Cruise dates offered are ones actually free inside their stay
  4. A booking click goes straight into SimplyBook
AL-03

Reviews, asked for properly

Two hours after checkout the guest is asked how it went. Five stars go straight to the Google or Airbnb review box with one tap. Anything lower opens a private note instead, so the complaint arrives by email and not on the listing.

More reviews, fewer public bad ones Quick win
  1. Trigger
    Two hours after checkout
  2. One question: how was it
  3. High score opens the public review page
  4. Low score opens a private message to the office
AL-04

Turnovers that book themselves

The moment a booking is confirmed, the cleaning and laundry slot is created and sent to the cleaner as a message they can read on a phone: which property, what time, how many beds, and the checklist. They send back photos when they finish, and those photos are attached to the booking. Same day turnovers are flagged the moment they appear.

No more coordinating by memory Standard
  1. Trigger
    Booking confirmed or changed
  2. Turnover slot created between checkout and next check in
  3. Cleaner gets the job on WhatsApp with the checklist
  4. Photos come back and attach to the booking
  5. Tight turnover raises a flag
AL-05

One inbox, with the reply already written

Website enquiries, email, WhatsApp and the booking platforms land in one place. Each new enquiry arrives with a draft reply already prepared in the sender's language, holding the right availability and the right price. It gets read, adjusted if needed, and sent. Answers are approved rather than written from scratch.

Answers in minutes, not the evening Bigger build
  1. Trigger
    Any enquiry, on any channel
  2. Landed in one inbox and matched to a property and dates
  3. Draft written in the guest's language with real availability
  4. Approved, edited or discarded in one tap
AL-06

Breakages become tracked jobs

A guest reports a problem through a link, adds a photo, and it becomes a job with a property, a date and an owner. It stays open until somebody closes it. No more issues living only inside a WhatsApp thread that scrolled away.

Nothing gets forgotten between guests Standard
  1. Trigger
    Guest or cleaner reports something
  2. Photo and property captured
  3. Job assigned to the right person
  4. Open jobs shown against each property
AL-07

Owner statements on the first of the month

Where properties are managed on behalf of owners, the monthly statement builds itself: nights sold, gross, fees, costs, net, and the calendar for the month ahead. It goes out as a clean PDF on the same day every month, without anyone opening a spreadsheet.

A morning of admin, every month Standard Only where owners are involved
  1. Trigger
    First working day of the month
  2. Bookings and costs pulled per property
  3. Statement rendered as a branded PDF
  4. Sent to each owner, copy kept on file
Nauti Girl · running the boat
NG-01

One calendar the captain can trust

Start here

Every way a trip gets booked ends up in the same Google Calendar: SimplyBook, the boat and tour marketplaces (GetMyBoat, Click&Boat, Viator, GetYourGuide and whichever others are in use), the website form, WhatsApp, a phone call, an agency booking by email. Each entry carries the service, the number of people, the guest's phone, allergies and the meeting gate, so the captain opens one calendar in the morning and knows the whole day. Shared with the crew, read only, always current.

No double bookings, no missing pax count Standard
  1. Trigger
    A booking arrives anywhere
  2. SimplyBook, the boat and tour marketplaces, website, WhatsApp, phone and agencies all feed in
  3. Manual bookings added through one short form
  4. Clash with an existing departure raises an alert
  5. One shared calendar the crew reads every morning
NG-02

Weather watch, the evening before

Every evening the marine forecast for tomorrow's departures is checked against the limits the skipper sets for wind and swell. If a departure looks doubtful, a message goes out listing exactly which trips are affected, how many people are on each, and a ready written note to each guest offering a new date. The decision stays with the skipper. The paperwork does not.

Cancellations handled before breakfast Standard
  1. Trigger
    Every evening, for the next day
  2. Forecast compared with the agreed wind and swell limits
  3. Affected departures listed with names and numbers
  4. Reschedule message drafted per guest, ready to send
NG-03

The pre sail brief

Twenty four hours before departure the guest gets a short message with a map pin for gate ABCD, the meeting time ten minutes early, what to bring, and one question about allergies and dietary needs. Their answer lands on the calendar entry, so the crew reads it with the booking instead of discovering it on the pontoon.

Fewer late arrivals and catering surprises Quick win
  1. Trigger
    24 hours before departure
  2. Map pin, timing and kit list sent
  3. Allergy and dietary question asked
  4. Answer written onto the calendar entry
NG-04

Photos out, reviews in

The photos taken on board are collected into an album for that departure. A couple of hours after the boat is back, every guest gets the album link and, underneath it, the review ask. People who have just seen themselves swimming at Ponte da Piedade write far better reviews than people asked cold a week later.

Reviews while the day is still fresh A gallery that sells the next trip Standard
  1. Trigger
    Departure marked complete
  2. Photos gathered into that day's album
  3. Album link sent to everyone on board
  4. Review ask sits under the photos
NG-05

The missed call rescue

In August the phone rings while the boat is at sea, and that caller books with somebody else. Any missed call gets an automatic WhatsApp within a minute: sorry, we were on the water, here are today's free slots and the booking link. The caller is answered even when nobody could pick up.

Recovers bookings lost to a ringing phone Quick win
  1. Trigger
    Call missed on the business number
  2. WhatsApp sent inside a minute
  3. Today's remaining slots included
  4. Caller added to the callback list
NG-06

Filling the empty seats

A departure still unsold forty eight hours out is a fixed cost with nobody paying it. When that happens, a limited offer goes to the people most likely to say yes: guests currently staying in a Lagos property, past guests in the area, and the waiting list. The offer expires on its own so it never undercuts a full price booking.

Turns empty departures into revenue Standard
  1. Trigger
    Departure unsold 48 hours out
  2. Audience picked: guests in town, past guests, waiting list
  3. Time limited offer sent
  4. Offer expires by itself when the window closes
Both businesses · where they help each other
X-01

Each business feeds the other

Two businesses in the same town with the same customers, currently working as strangers. Every guest staying in a property is a cruise waiting to be sold, and everybody stepping off the boat is a returning visitor who will need somewhere to stay next summer. This runs the introduction in both directions, automatically, with the offer timed to when it is actually useful.

Revenue from customers already on the books Standard
  1. Trigger
    A stay begins, or a cruise ends
  2. Guest in a property is offered a cruise on a free date
  3. Guest off the boat is offered next year's stay in the low season
  4. Both sides tracked so nobody gets the same offer twice
X-02

Monday morning numbers

One message every Monday with the week ahead: occupancy and arrivals for the properties, departures and seats sold for the boat, what came in last week against the same week last year, and anything that needs a decision. Short enough to read on a phone with a coffee.

The whole picture without opening anything Quick win
  1. Trigger
    Monday, first thing
  2. Both businesses read in one pass
  3. Week ahead and week behind compared
  4. One message, read on a phone
X-03

Every message in the guest's language

The Nauti Girl site already speaks English, Portuguese and Spanish. The messages should too, and French and German besides, since that is who arrives in Lagos. Language is picked from how the guest first made contact, and everything after that follows it without anyone thinking about it.

Better conversion on non English enquiries Quick win
  1. Trigger
    First contact from the guest
  2. Language detected and stored on the booking
  3. Every later message follows it
  4. Replies translated on the way out

Where we would start

The two that pay off immediately, because everything else leans on them.

Phase one

The two that unlock the rest

  • AL-01 mid stay check in
  • NG-01 one calendar for the captain
  • AL-03 reviews asked for properly
  • NG-03 the pre sail brief
  • NG-05 missed call rescue
About two weeks
Phase two

The operations behind them

  • AL-02 arrival pack with cruise offers
  • AL-04 turnovers and cleaning
  • NG-02 weather watch
  • NG-04 photos and reviews
  • X-02 Monday morning numbers
Following month
Phase three

The bigger pieces

  • AL-05 one inbox with drafted replies
  • X-01 cross selling both ways
  • NG-06 filling empty seats
  • AL-06 tracked maintenance jobs
  • AL-07 owner statements
Scoped once phase one is live

What is needed to start

Short list, and mostly access rather than work.

  • 01A WhatsApp Business number
    Automatic WhatsApp needs a business number registered for it. It can be the number already in use, and Nexo handles the registration. Without it, the same flows run on email and SMS instead.
  • 02Access to every booking platform
    Not only SimplyBook. Read access to each marketplace and agency the trips are listed on (GetMyBoat, Click&Boat, Viator, GetYourGuide, or whichever are in use), plus anyone who books by email. Listing them all is the first job, because a calendar that misses one channel is worse than no calendar at all. Nothing about how bookings are taken today has to change.
  • 03A Google account for the calendar
    One calendar the crew can be given read access to, kept separate from any personal one.
  • 04Where the property bookings live
    Airbnb, Booking, a spreadsheet, the website form, whichever are in use. We work with what is there.
  • 05The limits for the weather rule
    The wind and swell numbers above which the boat does not sail. Ten minutes with the captain settles it.
  • 06The property details guests receive
    Door codes, parking, wifi, bins, house rules. Whatever exists already, in whatever state.

Everything here writes into the existing systems, never around them. Every account stays where it is, and any automation can be switched off in one click without touching the rest. Nothing sends until the exact message has been reviewed and approved.