Author:
Mimsy Angeles
Two weeks into a new VA hire, one operator realized something was off. The person had been brought on specifically for guest communication, and the operator was still the one writing every check-in message, every pre-arrival note, every response to a guest asking about parking. The VA was capable and responsive. What was missing wasn’t skill. It was a starting library of templates adapted to the property, which nobody had actually asked about before the hire was made.
That’s the real signal worth catching earlier: template readiness isn’t something to build during onboarding. It’s something to verify before the hire happens at all. A dedicated STR VA who needs the operator to write their own message library from scratch isn’t functioning as a dedicated STR VA yet. They’re a capable generalist being asked to learn STR work on the job, which is a very different starting point than the operator was actually paying for.
Any capable VA can learn to write good guest messages eventually. The question isn’t whether they’ll get there. It’s whether the operator is the one teaching them how, one message at a time, for the first several weeks of a relationship that was supposed to free up that exact time.
A genuinely STR-specific VA arrives with a working template library already built from prior placements, adapted to a new property’s tone within the first few days rather than invented from a blank page. That difference shows up immediately in how fast the operator actually gets their inbox back.
Pre-booking inquiries. A prospective guest asking about pet policies, parking, or whether the listing suits a specific group size needs a fast, accurate answer that also nudges toward booking. A generic template answers the question. An STR-specific one is written to convert, addressing the exact hesitations that come up repeatedly for that property type.
Booking confirmation. This message sets the tone for the entire stay. Generic versions confirm dates and move on. STR-specific ones include property-specific details upfront, parking instructions, what’s already stocked, anything that reduces the volume of questions that would otherwise arrive in the days before arrival.
Pre-arrival instructions. Check-in logistics, door codes, Wi-Fi, house rules. The generic version lists this information. The version that actually works is sequenced by what a guest needs at each moment of arrival, not dumped as one long block of text a tired traveler skims past.
Check-in follow-up. A short message sent shortly after a guest arrives, confirming everything worked and surfacing any issue before it becomes a review. Generic versions are an afterthought. STR-specific ones are timed deliberately, early enough to catch a problem while it’s still fixable.
Mid-stay check-in. For longer stays specifically, a message that surfaces friction, a maintenance issue, a noise complaint, before it accumulates into something that shows up in the review instead of in a message thread. The generic version doesn’t exist at all in most templates. The STR-specific version is proactive by design, not reactive.
Issue acknowledgment and escalation. When something goes wrong, the first response matters more than the resolution speed. A generic template apologizes. An STR-specific one acknowledges the specific issue, sets a clear expectation for what happens next, and has a defined escalation path baked in for anything beyond what the VA can resolve directly.
Checkout reminder. A simple logistics message, checkout time, key or lockbox instructions, that also reduces the chance of a late checkout dispute. The STR-specific version is timed to arrive with enough lead time to actually be useful, not sent the morning of when it’s already too late to plan around.
Post-checkout review request. Timing and framing both matter here. A generic request goes out immediately and reads like a form letter. An STR-specific one is timed to land when the guest’s experience is still fresh but the stress of travel logistics has passed, and it’s worded to invite detail rather than a one-line response.
Damage or dispute acknowledgment. This is the highest-stakes template category on the list. A generic version sounds defensive. An STR-specific one documents the situation clearly, stays neutral in tone, and sets up whatever documentation trail the platform’s resolution process actually requires, because getting this wrong in the first message can cost far more than a bad review.
Before finalizing any STR VA hire, ask directly whether they have an existing template library or whether one gets built during onboarding. Request a sample, not a hypothetical description, of two or three actual templates from a prior placement, with identifying details removed. A strong response includes real specificity: sequencing, tone adapted to a property type, and a clear answer for what happens when a message needs to go beyond a template into judgment territory.
A vague answer here, “we’ll figure out messaging together once you’re onboarded,” is the exact pattern that turns into two lost weeks of the operator writing their own inbox. Delegate’s STR Freedom Guide, built specifically around stepping back from the inbox with confidence, walks through this exact handoff, free to download if you want the fuller framework before your next hiring conversation.
Delegate places dedicated STR virtual assistants who arrive with a working guest message library already built, adapted to your property within days, not weeks of you writing it for them.
Book a strategy call to see the actual template library before you commit to anything.
© 2026 Delegate BPO LLC All Rights Reserved | Privacy Policy
For Clients
For Top Talents
