The Welcome Call: When It Helps and When It Annoys

A call can rescue a stay or start it badly, and the difference is almost entirely about timing and about what you do with the answer you get.

Last updated: September 27, 2026

A welcome call is one of the few things in hosting that can make a stay better or worse inside the same three minutes. Placed at the right moment, it catches a problem before it turns into a complaint. Placed at the wrong one, it's an interruption the guest remembers.

The line between those two isn't how warm you sound. It's timing, and whether anything actually changes because of what the guest told you.

Key Takeaways

• The call has one job. Confirm what can't be fixed later: arrival, door, address, and any access or timing need.
• Guests split in two. New arrivals welcome a voice; frequent travellers usually want the message instead.
• Ask once, in writing. "Call, or message?" costs nothing and removes the guess.
• Short is the whole trick. Greet, confirm two or three facts, ask one open question, end.
• End on one action. A call that changes nothing was a chat, however friendly it felt.

What a welcome call is actually for

Hosts often treat the welcome call as hospitality — a nice touch, a chance to say hello. That framing is exactly why it goes wrong so often. A call has costs the guest can feel. It interrupts, it demands a real-time response, and it carries a quiet obligation to be polite back.

Reframe it around a single job: confirm the things that can't be fixed later. Is the guest arriving as planned? Do they have the door code and the right address? Is there an access need, a late arrival, a car, a pet, a small child? Each of those is cheap to confirm now and expensive to discover at the door.

That's the whole remit. A welcome call isn't a sales call, a survey or a review request. The moment it becomes one of those, the guest stops hearing a host and starts hearing a business.

There's a second version of the call that exists because something looks off. A booking whose details don't line up, a same-day request, a payment that behaved oddly. That's a different call with a different purpose — verification rather than welcome — and it's better framed honestly than disguised as friendliness, because guests can tell the difference and they don't enjoy being managed.

The guest who wants the call, and the guest who does not

Guests split into two groups, and the split rarely follows age or nationality.

The group that welcomes a call is arriving into something unknown. A late-night arrival in a city they've never visited. A guest with mobility needs who wants to confirm the entrance before they book a taxi. An older traveller who simply prefers a voice to a wall of text. Someone whose first language isn't yours, who'd rather ask three questions out loud than type them.

The group that doesn't is arriving into something they've done a hundred times. A business traveller with an app for everything. A repeat guest who already knows the building. Someone off a red-eye who wants silence, not a ringtone. A guest in the middle of a workday who answers only because they feel they have to.

That second group is where calls backfire. A guest who picks up out of politeness but didn't want to be called won't complain — they'll just start the stay slightly annoyed, and you'll never learn why.

The way to tell them apart isn't to guess. It's to ask once, in writing: "I can call before you arrive if that's useful, or send everything in the message instead." The guest who wants a call says yes. Everyone else gets quiet, and quiet is what they asked for.

Language works the same way. Calling a guest whose language you don't speak comfortably costs both of you more than it returns. A written message doesn't have that problem, and where the software follows the property's language — six languages, falling back to English where one isn't available — the follow-up can go out in the guest's own language instead of a translation.

Keeping the call short enough to be welcome

The biggest reason a welcome call annoys is length. A call that runs long doesn't feel attentive, it feels like it won't end.

Aim for something the guest would later describe as quick. Greet, confirm the two or three facts that matter, ask one open question, and end. If the guest wants to keep talking, they will, and then the length is their choice rather than yours.

Lead with the useful part, not the preamble. Don't open with how busy the season has been. Open with the thing the guest is quietly anxious about — the door, the parking, the late arrival — and get to it in the first sentence.

Then listen for the thing they didn't ask. The pause before "I think we'll be fine". The extra question tacked on after goodbye. Guests bury the real concern in the last ten seconds of a call, because that's the point at which they've decided you're safe to ask.

And keep your own material within reach so the call never stalls. Directions to the door, the code, where to park, the wifi name — all of it in front of you, so no part of the call is you saying "let me just check".

Skip voicemail. A voicemail is a one-way message wearing a call's clothing. If the call mattered, follow it up where the guest actually reads. Which place that is depends on where the booking came from; for an Airbnb stay, messages sit in one inbox at localsbnb.com, so the thread from the call doesn't scatter across three apps.

Turning what you hear into an action rather than a note

A welcome call that changes nothing is a chat. The value sits entirely in the ten minutes after you hang up.

So end every call by writing down one thing that changed. Not a summary — one action with a name against it. The guest mentioned a late train, so the entry needs to stay open later. The guest mentioned a toddler, so the high chair comes out. The guest mentioned a bad knee, so the ground-floor route becomes the plan.

Then put it where the information lives, not on the back of an envelope. If it's about the stay, it belongs with the booking. If it's about the unit, it belongs in the maintenance list. A note in one place and the fact in another is how the same request gets missed twice.

And then close the loop with the guest. Not a long message — one line confirming that the thing they mentioned is handled. Guests rarely expect that, which is why it lands when it arrives.

There's a boundary worth naming here. A call can confirm and it can arrange, and it shouldn't promise what the property can't do. If the guest asks for something you can't guarantee, the honest answer is that you'll check and come back — and then actually coming back matters far more than the answer itself.

FAQ

Should I call every guest before arrival?

No, and trying to is what makes the call feel routine. Call when there's something to confirm or verify, and message everyone else. A call placed for its own sake uses up the goodwill you'll want later.

What if the guest doesn't pick up?

Don't chase it with more calls. Leave the information in writing in the channel where the booking lives, and treat the guest's silence as an answer about their preference. Then plan the arrival on the assumption that they've read it.

How do I handle a call in a language I don't speak well?

Keep it to what you can say clearly, and put the details in writing. If the software follows the property's language, send the follow-up in the guest's own language so nothing important rests on your accent.

A welcome call is a tool with a narrow job, not a ritual to perform on every booking. Ask once which the guest wants, keep the call short if they say yes, and end it with one thing that will actually change. When the booking and its messages already sit together at localsbnb.com, that one action is easy to log where the next person will see it.

---

This article is general guidance for hosts and isn't legal or platform policy advice; local rules and current platform terms prevail.