No projected revenue figures on this page. The honest version is narrower and more useful: here is the specific work that stops falling on your team, and the specific failure modes that stop being possible.
A guest whose flight was cancelled is calling every hotel near the airport. Whoever answers gets the booking. Out of hours, that is currently nobody.
A call that converts on your own line is a direct booking at your own rate, with no channel commission attached to it.
Cover the night without hiring for it, and without asking a duty manager to sleep next to a phone.
Transcripts and a full booking trail, so "what happened on that reservation" is a lookup rather than an argument.
With forward-on-no-answer, your line rings first and the guest in front of you keeps your attention. Only the calls you can't reach fall through.
Nothing to call back in the morning, because the booking was completed on the call rather than written on a pad.
Check-in time, parking, pets, breakfast, late arrival — answered identically every time, without pulling anyone off the desk.
It sits behind your existing number and writes into your existing PMS. There is no second system for staff to keep in sync.
This is the part that took the most engineering, and it's the part most worth asking any vendor about.
Some do. That's why it's positioned as overflow: your team answers first, and the alternative for the calls that fall through isn't a human — it's ringing out. The agent also says it's an AI up front rather than pretending otherwise.
Forward-on-no-answer is the default precisely because it doesn't. It covers the hours and the overflow you're not staffing today.
It can only hold and confirm what your back-end returns, every action is logged, and cancellation with refund is one of the five operations.
A pilot is call forwarding on your existing number. Turning it off restores your previous setup the same day, with nothing ported and nothing migrated.