When a hotel receives a guest from an over booked hotel, it is called a farm-in. Below, you can see how the farm-in process works for the hotel receiving a guest from an over booked hotel.
Login and accept or reject the booking
the over booked hotel books a room at your hotel and you can now accept or reject the booking. If you reject a booking you are asked to provide a reason so we can send this to the hotel employee booking the room. If you have rooms available, you can login to helloecho.com and accept the booking by going to the “Orders” page, find the order and click “Accept Order”.
Pay for the taxi when the guest arrives
If the over booked hotel is not close to your hotel, they will book a taxi for the guest. When the guest arrives at your hotel, you pay the taxi driver with cash. Remember to save the receipt. The over booked hotel will be paying for the taxi at a later point.
Send the over booked hotel an invoice
After the stay, you will send an invoice to the hotel farming out their guest to you, just like you would send an invoice to any company having guests staying with you.
When a hotel sends a guest to another hotel, because it is over booked, it is called a farm-out. Below, you can see how the farm-out process works for the hotel sending a guest to another hotel.
Book a room at a hotel with available rooms
Using helloecho.com you book a suitable room and moments later both you and the hotel you booked, receives an email with the details of the booking.
Receiving hotel confirms or rejects the booking
The hotel with rooms available will then check availability and accept the order if in fact they still have rooms available. If things have changed since they last updated helloecho.com with their available rooms, they may reject the booking.
If booking is rejected, you receive a reason
In this case you will receive an email with the reason why the booking had to be rejected.
The receiving hotel pays for the taxi when the guest arrives
If the other hotel is not right down the street, you book a taxi for the guest. When the guest arrives at the new hotel, the hotel receptionist at the receiving hotel will pay the taxi driver with cash. Your hotel will be paying for the taxi at a later point as part of the invoice.
The farm-out hotel receives the invoice
After the stay, the farm-in hotel sends the invoice to the farm-out hotel.
But first, Cookies! We use essential cookies to make HelloEcho work. We’d like to use other cookies to improve and personalise your visit, and to analyse our website’s performance, but only if you accept.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
Google Analytics sets this cookie to store a unique user ID.
Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously.