The document describes the functionality and flow of a hotel booking website. It explains that users can search for hotels on a map, refine their search, and view hotel images and details. From the hotel page, users can email booking details to others, select their room options, and either pay a deposit or full amount to complete the booking. It also mentions handling existing versus new customers by pre-populating past customer information or collecting new customer details.

1. Displays all on a map (googlemaps) When users clicks here – system drops down a refine search box Modify Search should be populated with details from initial search, any changes to this when client clicks “Search” button should perform a whole new search. Goes to hotel detail page

2. Image navigation to work in a similar way to viewing images “Thumbs” in Explorer. Scroll through available images (if applicable).

3. Opens window for customer to send email to self (and up to 3 friends/family/colleagues) Goes to hotel detail page Selects relevant hotel and goes to next page. Local info about hotel

4. Repeated info about hotel – again, just to summarise. The thinking behind the repetition is that people don’t always take in everything in one go, and often miss things – so we re-present it in a slightly different format. Here, customer can select whether to pay deposit or full amount, and make any room requests (smoking/non-smoking, cot, late arrival etc) Forward to next page Back to search results

5. Existing customers New customers

6. Guest names Lead name and address, pre-populated [or hidden?] in case of existing customers who’ve logged in.

7. Wrap-up