Manus to test hotel checkout handoffs

Genevieve Horchler tested Manus against 11 hotel booking engines using the same room request and September dates. The task was to navigate hotel websites, select the stay and room, and see how far the agent could progress through different booking flows.

Eight tests were counted as successful, including several that required extra attempts. That label had a narrow meaning: Manus reached the page for guest and payment details. It did not mean a paid reservation or a confirmation page. The traveler still needed to provide personal information or take over the browser.

Date controls were a recurring obstacle. Some engines showed familiar month calendars, while others used a length-of-stay design that Manus could not navigate reliably. CAPTCHAs blocked other attempts. When a direct hotel site failed, the agent repeatedly moved toward Booking.com as an alternative channel.

The account also tested a less specific San Diego hotel request. Manus used web search, surfaced options and continued after the author chose a hotel. The practical outcome is a recorded boundary between navigating availability and completing a booking. A reader can copy the clear dates and hotel choice, then check both the selected dates and the channel used before entering guest information or paying.

Prompt
Original prompt

Source: www.hotelnewsresource.com · Genevieve Horchler