I handle overnight guest communication, reservations and reviews for short-term rental owners and property managers — and I build the automations that shrink the workload month over month.
No call required. Send a listing link, get a recorded video back within two days.
Inquiries, pre-arrival, in-stay problems, checkout and reviews — answered fast, in your voice, across every channel.
Calendar accuracy, channel sync, turnover coordination, cancellations and damage claims handled properly.
PMS automation, pre-arrival sequences, smart-lock workflows and owner reporting. Built once, working forever.
Parking. Wifi. Check-in time. Early arrival. Late checkout. Where the bins go. In the portfolios I've analysed, those six account for roughly 55–65% of everything a guest sends — and most of it arrives outside business hours, when nobody is there to answer.
"Within a few hours" instead of "within an hour." Response time feeds Airbnb's ranking and directly affects inquiry conversion — a slow reply at 11pm is a booking that went somewhere else.
Review responses are read by future guests deciding whether to book. An unanswered 3-star does more damage than the rating itself, and a good response to a mediocre review often converts better than no review at all.
Every lockout, every leak, every "can we check in early" comes to your phone, because there's no written rule about what actually needs you and what doesn't.
Two things, in this order. First I take the messages off you, so the pain stops immediately. Then I fix the reasons there are so many of them — a proper pre-arrival sequence, a house manual that actually answers things, an escalation rule so you're only woken for genuine emergencies, and automations for everything repeatable.
The point is that month six should cost you less than month one, because the volume is lower. That's the difference between hiring help and fixing the operation.
Most engagements start with one of the first three and grow from there. Everything is scoped in writing before it starts.
Inquiries, pre-arrival, in-stay issues and checkout, covered during your overnight window. Written in your voice, with an agreed escalation rule so genuine emergencies still reach you and nothing else does.
Typically saves 10–20 hrs/week
Confirmations, modifications, extensions, cancellations, gap-night rules and daily calendar audits across every channel. Double-bookings are a systems failure, and preventing them is systems work.
Typically saves 5–10 hrs/week
Pre-arrival sequences, smart-lock code delivery, cleaner dispatch, review requests, alert routing. Most operators pay for a PMS and use a fifth of it. Fixed-price projects, not hourly.
Typically removes 30–40% of inbound messages
Every review answered within 24 hours, review requests sent at the right moment, negative reviews handled factually and without defensiveness. Rating drives ranking, and ranking drives rate.
Titles, descriptions, amenity gaps that affect search filters, photo order, cross-channel consistency. The highest-return one-off work in short-term rentals.
Airbnb, Booking.com, VRBO and Expedia kept in sync on availability, rates and content — with alerting on sync failures rather than discovering them via an angry guest.
Written procedures for every recurring process, plus onboarding docs. Gets the business out of your head and onto paper, which is also what makes it sellable.
Occupancy, ADR, RevPAR, channel mix, response times and review trends — with written commentary, not just an export. Property managers use these to retain owners.
Cleaner and maintenance scheduling, turnover management, supply tracking, vendor communication, quality checks. A missed turnover is a cancelled booking.
Anyone can hand you a template pack. What matters is knowing when each message fires and why it's written the way it is. Every one of these is open — read them and judge for yourself.
Speed matters most here. These convert inquiries into bookings.
This is where message volume is won or lost. Get the 48-hour message right and most of the rest disappears.
Where reviews are actually decided. Speed and ownership matter more than perfection.
Reviews are the compounding asset. This is where you protect them.
Most short-term rental operations run on memory. That works until you're ill, on a flight, or trying to hand something to a new person — and it's the main reason these businesses are hard to sell. These are written to be handed to someone else.
Purpose: a consistent standard for every guest message, so response quality doesn't depend on who's holding the phone.
| Category | Target | Channel |
|---|---|---|
| Emergency — safety, lockout, no heat/water, leak | 5 min | Phone call |
| In-stay problem | 30 min | Platform message |
| Booking inquiry | 20 min | Platform message |
| General question | 60 min | Platform message |
| Outside coverage hours | Auto-ack immediately | Automated |
Purpose: define exactly what reaches the owner and when. This is the document owners tell me they value most — it's what lets them stop checking their phone.
| Trigger | Action | Timing |
|---|---|---|
| Injury, fire, flood, gas, police involvement, security breach | Call owner immediately + emergency services | Immediate, any hour |
| Property uninhabitable | Call owner, begin rehousing | Immediate |
| Lockout unresolved after 30 min | Call owner | Within 30 min |
| No heat / hot water / power | Message owner, dispatch trade | Within 1 hour |
| Refund or goodwill above {agreed threshold} | Owner approval required | Before committing |
| Damage claim | Owner notified, claim prepared | Same day |
| Review below 4 stars | Owner notified with draft response | Within 4 hours |
| Double-booking | Call owner, begin recovery | Immediate |
| Media, legal or licensing contact | Do not respond. Escalate. | Immediate |
| Neighbour complaint | Handle, log, report | Daily summary |
| Everything else | Handle and log | Daily summary |
Agreed on day one, in writing. The threshold figure is the owner's to set. Everything below it is mine to decide — that's the entire point of the arrangement.
Purpose: ensure every property is guest-ready before check-in, with a defined failure path.
Failure path: if a clean cannot happen, the guest is contacted before their arrival time — never after. A delayed check-in you warned about is an inconvenience; one they discover at the door is a one-star review.
Purpose: a fixed sequence for situations where improvising is dangerous.
Purpose: consistent, defensible decisions — and a clear line between what policy requires and what goodwill offers.
Never refund to prevent a threatened review. That is extortion under platform policy — document it, report it, and handle the underlying complaint on its own merits.
Purpose: claims that actually succeed. Most fail on evidence or timing, not merit.
Purpose: protect the rating, because rating drives ranking and ranking drives achievable rate.
Purpose: bring a unit live without the first-month chaos that generates early bad reviews.
Reporting you have to request doesn't get read. This is the monthly view I build for every engagement — occupancy and revenue on one side, operational quality on the other, with written commentary rather than a raw export.
| Channel | Revenue | Share | Commission |
|---|---|---|---|
| Airbnb | $41,280 | 54% | $1,238 |
| Booking.com | $18,920 | 25% | $3,027 |
| VRBO | $8,410 | 11% | $673 |
| Direct | $7,690 | 10% | $0 |
Direct bookings are up from 4% to 10% since January. That shift alone saved roughly $1,150 in commission this month. It's the number owners care most about and see least often.
| Metric | Now | 6 mo ago |
|---|---|---|
| Overall rating | 4.87 | 4.61 |
| Communication | 4.96 | 4.58 |
| Cleanliness | 4.81 | 4.72 |
| Check-in | 4.94 | 4.55 |
| Accuracy | 4.88 | 4.79 |
| Reviews answered | 100% | 61% |
Communication and check-in moved most — both are operational rather than physical, which is why they respond fastest to process change. Cleanliness moves slower because it needs a different conversation with the cleaning team.
Occupancy rose 5.1 points, driven mainly by Edinburgh's festival period and by the gap-night rule enabled in May, which recovered 11 orphan nights across the portfolio that would previously have gone unsold.
Average first-response time is now 14 minutes against 3 hours 20 minutes in January. The communication sub-rating followed it, up from 4.58 to 4.96, and overall rating crossed 4.8 — which restores Superhost eligibility at the next assessment.
Recommendation for August: Gold Coast occupancy is soft at 62% against a market average nearer 70%. The listings there have the thinnest descriptions in the portfolio and only 14 photos against 28 elsewhere. I'd rewrite both listings and reshoot before the December season rather than discounting into it.
I have a background in software development, which in practice means I don't just answer the messages — I remove the reason there are so many. These are built in Make.com or natively in the PMS, and every one has a human in the loop where judgement is involved.
Booking confirmed → three messages scheduled automatically, with the door code injected dynamically at the 48-hour mark so it's never sent before it exists.
Effect: the largest single reduction in message volume available. Typically removes 30–40% of inbound within two months.
Unique code per booking, valid only for the stay window, auto-expiring at checkout. Delivered inside the 48-hour message rather than as a separate one.
Effect: removes the security risk of a shared permanent code, and eliminates the manual step that gets forgotten on a busy turnover day.
Checkout logged → cleaner notified with property, access and deadline. If not acknowledged within 30 minutes, it escalates rather than sitting silently.
Effect: catches the missed turnover the day before it becomes a guest standing in a dirty property.
Review request 24 hours after checkout, new reviews logged to the reporting sheet, and anything under 4 stars alerts within 15 minutes so the response is same-day.
Effect: review volume up, response lag down to hours. Nothing is auto-published — the response is always written by a person.
A 7am summary to the owner: today's arrivals and departures, open maintenance, unanswered messages, occupancy for the next seven days, and anything escalated overnight.
Effect: the owner stops checking the PMS. This is usually the moment they realise they've actually handed the operation over.
Incoming messages classified by intent, a suggested reply drafted from the template library, then routed to a human queue. Nothing sends automatically.
On the limits: I don't let AI talk to guests unsupervised, and I'd be wary of anyone who does. It's fast at triage and drafting, and unreliable at judgement. Complaints, money and conflict are always written by a person.
The highest-return one-off work in short-term rentals, and the most commonly neglected — most listings were written once at launch and never touched again.
| Missing amenity | Why it matters |
|---|---|
| Dedicated workspace | A search filter. Excludes the entire remote-work segment, which books longer stays midweek. |
| Free parking on premises | Filter. The property had it; nobody had ticked it. |
| EV charger | Filter, and a growing one. Even a standard outlet can be declared appropriately. |
| Pets allowed | Filter. Worth deciding deliberately rather than by omission. |
| Self check-in | Filter, and a ranking input. The property had a smart lock installed and unlisted. |
These show reasoning and method rather than results I can't yet claim.
Situation: owner handles all messages personally alongside a full-time job. Response badge reads "within a few hours." Three of the last twenty reviews mention slow replies.
First 30 days: take overnight messages entirely, with an agreed escalation threshold. Audit 90 days of message history and categorise it. Build the 48-hour pre-arrival message from what that audit finds, and rewrite the house manual around the same six questions.
Days 30–60: clear the review response backlog. Enable review requests on every checkout to increase volume, which is what actually moves an average.
How I'd measure it: first-response time, message volume per booking, communication sub-rating, and overall rating. The realistic target is the badge back to "within an hour" inside three weeks and the overall rating above 4.8 within a season — ratings move slowly because they're an average, and anyone promising faster is guessing.
Situation: property manager with a small daytime team. Guest services role has been open for months. Overnight messages land on the operations manager's personal phone.
The economic case: a local hire covering 11pm–7am costs roughly $3,500–5,000/month fully loaded and turns over quickly, because almost nobody wants a permanent night shift. Coverage from someone whose daytime it already is costs a fraction and doesn't churn — which is the real reason those roles stay open.
First 30 days: agree the escalation matrix in writing before anything else. Shadow for a week, then take tier-one overnight messaging. Build the pre-arrival sequence across all 22 units.
How I'd measure it: overnight messages reaching the ops manager (target: near zero for non-emergencies), first-response time overnight, and hours returned to the daytime team.
Situation: listings on Airbnb, Booking.com, VRBO and a direct site. Channel manager in place but partially configured. Two double-bookings in three months, each costing cancellation penalties and ranking damage.
Diagnosis: double-bookings are almost never the software. They're sync frequency, a listing connected on one side only, or a manual block that never propagated. The first job is to verify sync on every listing individually rather than assuming the connection covers them all.
Then: a daily automated calendar audit that alerts on any discrepancy, plus a written recovery SOP — because the second-worst outcome is a double-booking, and the worst is a double-booking nobody has a plan for.
How I'd measure it: sync failures caught by alert versus discovered by a guest. That ratio is the whole story.
Everything is scoped in writing before it starts. Two weeks' notice either way, and you keep everything I build — templates, SOPs, automations, dashboards — whatever happens.
A contained project, delivered in five days. The easiest way to find out whether we work well together without committing to anything ongoing.
Or a fixed monthly retainer for a defined coverage window — usually better value past about fifteen hours a week.
Priced on outcome, never hourly. You're buying the thing, not my typing speed.
I'm Muhammad Faizan. I have a BS in Information Technology and a background in software development — I spent several years building in Unity before moving into operations work.
That combination is the reason to hire me rather than a general virtual assistant. Guest communication is a writing and judgement job; the operation behind it is a systems job. Most people are good at one or the other. I'm comfortable doing both, which means the operation gets better over time instead of just getting covered.
I'm based in Lahore, Pakistan — UTC+5. That's not a compromise you're accommodating, it's the point. Your overnight window is my ordinary working day, so you get someone alert rather than someone on a night shift, at a cost that makes overnight coverage viable for a portfolio that couldn't otherwise justify it.
I'm early in building a short-term rental client base and I'd rather say that plainly than pad a CV. What I can show you is the work above — the message library, the SOPs, the automations and the reporting are all real and all mine. If you'd rather see it than take my word for it, that's the whole idea.
| Based | Lahore, Pakistan · UTC+5 |
| Education | BS, Information Technology |
| Technical | Make.com, Zapier, Google Apps Script, Looker Studio, Unity/C# |
| STR platforms | Airbnb, Booking.com, VRBO, Expedia |
| PMS | Hostaway, Hospitable, Lodgify, OwnerRez |
| Languages | English (fluent, written and spoken), Urdu |
| Best coverage | US overnight · UK/EU business hours · AU evenings |
Pick your worst-performing property — or your best, if you'd rather test me on a hard one. I'll record a five-minute walkthrough with three specific things I'd change and why.
Free, no call, no obligation, and useful whether or not we ever work together. If the changes are worth making, make them yourself.
faizan@muhamadfaizan.com · replies within one business day
I don't add anyone to a mailing list, and I don't follow up more than twice.