METHODS, DEVICES, SYSTEMS AND COMPUTER PROGRAM PRODUCTS WHICH RELATE TO TRAVEL ARRANGEMENTS

Abstract

There is provided a computer-implemented method of providing an itinerary search result, the method including the steps of: (i) presenting in a computing device user interface events proximate to a selected date, wherein the events are obtained from a calendar on the device; (ii) providing a selectable option in the user interface to select an itinerary search corresponding at least in part to the presented calendar events; (iii) receiving a selection of the selectable option; (iv) sending an itinerary search request to a server; (v) receiving an itinerary search result from the server, and (vi) presenting the itinerary search result in the user interface on the device. Related devices, systems and computer program products are disclosed. Further methods, devices, systems, servers and computer program products which relate to travel arrangements are disclosed.

Claims

1. A computer-implemented method of sending an itinerary search result to a selected attendee, the method including the steps of: (i) receiving a selection of a date in a user interface of a computing device, and obtaining events proximate to the selected date from a calendar application executing on the computing device, and presenting in the user interface the events proximate to the selected date; (ii) providing a selectable option in the user interface to select an itinerary search corresponding at least in part to the presented events obtained from the calendar application; (iii) receiving a selection of the selectable option; (iv) sending an itinerary search request to a server, the itinerary search request corresponding to the itinerary search in step (ii); (v) receiving at the computing device an itinerary search result from the server the itinerary search result corresponding to the itinerary search request in step (iv), and (vi) presenting the itinerary search result in the user interface on the computing device; the method further including sending the itinerary search result to an event attendee, including the steps of: (a) obtaining from the calendar application executing on the computing device a list of attendees from at least one event that overlaps with the itinerary search result, the list of attendees including respective electronic addresses of the attendees; (b) presenting the list of attendees from the at least one event that overlaps with the itinerary search result; (c) receiving a selection of an attendee from the list of attendees; and (d) sending an electronic communication to the selected attendee at a respective electronic address of the selected attendee, in which the communication shares includes the itinerary search result.

2. The method of claim 1, wherein step (iv) includes sending data corresponding to at least one calendar event from the computing device to the server.

3. The method of claim 1, wherein in steps (v) and (vi) a plurality of itinerary search results are received and presented.

4. The method of claim 1, further including step (vii) in which a selectable option is provided in the user interface to request booking of a trip corresponding to the itinerary search result.

5. The method of claim 4, further including step (viii) in which a selection of a booking request for the trip is received.

6. The method of claim 1, wherein the device user interface includes a touch screen.

7. The method of claim 1, wherein the device includes a processor.

8. The method of claim 1, wherein the device is a mobile device.

9. The method of claim 8, wherein the mobile device is a smartphone.

10. The method of claim 1, wherein the server is a remote server.

11. The method of claim 1, wherein the server includes a processor.

12. A computing device programmed to perform a method of sending an itinerary search result to a selected attendee, the computing device programed to: (i) receive a selection of a date in a user interface of the computing device, and obtain events proximate to the selected date from a calendar application executing on the computing device, and present in the user interface of the computing device the events proximate to the selected date; (ii) provide a selectable option in the user interface to select an itinerary search corresponding at least in part to the presented events obtained from the calendar application; (iii) receive a selection of the selectable option; (iv) send an itinerary search request to a server, the itinerary search request corresponding to the itinerary search in (ii); (v) receive an itinerary search result from the server, the itinerary search result corresponding to the itinerary search request in (iv), and (vi) present the itinerary search result in the user interface; the computing device further programmed to send the itinerary search result to an event attendee, the computing device programmed to: (a) obtain from the calendar application executing on the computing device a list of attendees from at least one event that overlaps with the itinerary search result, the list of attendees including respective electronic addresses of the attendees; (b) present the list of attendees from the at least one event that overlaps with the itinerary search result; (c) receive a selection of an attendee from the list of attendees; and (d) send an electronic communication to the selected attendee at a respective electronic address of the selected attendee, in which the communication includes the itinerary search result.

13. A system including a server and a computing device, the computing device configured to communicate with the server, the computing device configured to: (i) receive a selection of a date in a user interface of the computing device, and obtain events proximate to the selected date from a calendar application executing on the computing device, and present in the user interface of the computing device events proximate to the selected date; (ii) provide a selectable option in the user interface to select an itinerary search corresponding at least in part to the presented events obtained from the calendar application; (iii) receive a selection of the selectable option; (iv) send an itinerary search request to the server, the itinerary search request corresponding to the itinerary search in (ii); (v) receive an itinerary search result from the server, the itinerary search result corresponding to the itinerary search request in (iv); and (vi) present the itinerary search result in the user interface on the computing device; wherein the computing device is a user computing device, the system further including a selected attendee computing device configured to communicate with the user computing device, wherein the user computing device is configured to: (a) obtain from the calendar application executing on the user computing device a list of attendees from at least one event that overlaps with the itinerary search result, the list of attendees including respective electronic addresses of the attendees; (b) present the list of attendees from the at least one event that overlaps with the itinerary search result; (c) receive a selection of an attendee from the list of attendees; and (d) send an electronic communication to the selected attendee computing device at a respective electronic address of the selected attendee, in which the communication includes the itinerary search result.

14. A computer program product embodied on a non-transitory storage medium executable on a computing device including a processor to: (i) receive a selection of a date in a user interface of the computing device, and to obtain events proximate to the selected date from a calendar application executing on the computing device, and to present in the user interface of the computing device events proximate to the selected date; (ii) provide a selectable option in the user interface to select an itinerary search corresponding at least in part to the presented events obtained from the calendar application; (iii) receive a selection of the selectable option; (iv) send an itinerary search request to a server, the itinerary search request corresponding to the itinerary search in (ii); (v) receive an itinerary search result from the server, the itinerary search result corresponding to the itinerary search request in (iv); and (vi) present the itinerary search result in the user interface; the computer program product further executable to: (a) obtain from the calendar application executing on the computing device a list of attendees from at least one event that overlaps with the itinerary search result, the list of attendees including respective electronic addresses of the attendees; (b) present the list of attendees from the at least one event that overlaps with the itinerary search result; (c) receive a selection of an attendee from the list of attendees; and (d) send an electronic communication to the selected attendee at a respective electronic address of the selected attendee, in which the communication includes the itinerary search result.

15. The method of claim 1, wherein in steps (v) and (vi), a plurality of itinerary search results are received and presented, and in step (c) the itinerary search result is selected from the plurality of itinerary search results.

16. The method of claim 1, further including step (e) in which a selectable option is provided in the user interface to request booking of a trip.

17. The method of claim 16, further including step (f) in which a selection of a booking request for a trip is received.

18. The method of claim 1, including a step of receiving permission to access the calendar application on the computing device.

19. The method of claim 1, wherein step (b) includes a step of presenting attendee identities in the list of attendees and presenting meetings that fall in an itinerary period.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0287] The above and other aspects of the invention will now be described, by way of example only, with reference to the following Figures, in which:

[0288] FIG. 1 shows an example of accessing a native mobile calendar to present event data at the point of date selection.

[0289] FIG. 2 shows a prior art organization travel booking process.

[0290] FIG. 3 shows an example of a party system in which organization members Share Itineraries, Discuss and copy options, Clone Trips, or Receive Travel-related Notifications.

[0291] FIG. 4 shows an example of a party system in which organization members may be segmented into groups related to travel arrangement, and Cross organization Pollination travel arrangement is achieved.

[0292] FIG. 5 shows an example of a party system in use on a smartphone.

[0293] FIG. 6 shows an example of a party system in use on a desktop or laptop computer screen.

[0294] FIG. 7 shows an example of a displayed email which a second user receives and which invites them to collaborate on a trip plan which has been created by a first user.

[0295] FIG. 8 shows an example of a trip planning platform providing a user interface for reporting of an organization's travel usage.

[0296] FIG. 9 shows an example of a traveller's request being channeled via a travel hub to an organization's travel admin, with an email communication being sent to an address in the organization's domain, which in this example is travel_admin@skyscanner.net.

[0297] FIG. 10 shows an example in which a traveller can edit a trip, which is bookable by a travel admin; the traveller can invite a second traveller to view the trip.

[0298] FIG. 11 shows an example in which Ross in Skyscanner offers a “book your travel link” to Peter, who is not in Skyscanner.

[0299] FIG. 12 shows an example of a person outside the organization (Peter); the organization has offered to book that person's travel (Peter's travel to Edinburgh).

[0300] FIG. 13 shows an example of when a supervisor (eg. Shane) looks at reports on the travel hub, he sees the booking his organization paid for, in the correct place.

[0301] FIG. 14 shows an example of a meeting invite and information contained in the invite.

[0302] FIG. 15 shows an example, in which an itinerary generator may be used by the travel hub to generate and to send possible itineraries to the traveller user, such as to their smartphone.

[0303] FIG. 16 shows an example in which three services may be provided by or via the travel hub.

[0304] FIG. 17 shows an example in which a Mobile Application will feed straight into the travel hub.

DETAILED DESCRIPTION

[0305] Contextual Planning in a mobile device application is provided.

[0306] Accessing and extracting attendees from native calendar events may be performed, to present sharing and distribution. A purpose is to allow users to see the events that overlay with their proposed search, helping them to plan. A native mobile calendar may be accessed, to present event data at the point of date selection.

[0307] When a date in the calendar is selected, events proximate that day (i.e. on that day or near that day), may be displayed. An itinerary search (eg. for the selected date, or in the vicinity of the selected date) may be requested by selecting an option in the user interface on the device (eg. a mobile device). FIG. 1 shows an example of accessing a native mobile calendar to present event data at the point of date selection.

[0308] Contextual Sharing in a mobile device application is provided.

[0309] In a flow example: [0310] Users provide access to their native (eg. iOS/Android) calendar. [0311] A trip is prepared. [0312] Users are presented with a list of attendees from events that overlap with their Trip. A list may show the user and the name of the meetings that fall over that period. [0313] A user may be prompted to share plans with these relevant parties by selecting each user to share plans with.

[0314] Contextual planning from a cloud calendar is provided.

[0315] In a flow example: [0316] A user accepts and adds events to a calendar (eg. cloud calendar). [0317] A platform (eg. Skyscanner) observes changes in the calendar and cross references user data held by the accepting user on their location of residence. [0318] The platform (eg. Skyscanner) calculates the probability of a trip being required. [0319] The platform (eg. Skyscanner) engages the user through a given vector (email/push/text) with information on the potential trip.

[0320] A Meta Search Travel Booking Assistant is provided. This is a travel request process powered by meta search engine.

[0321] In a flow example: [0322] Traveller builds and selects components of a trip. [0323] Traveller submits given options to a platform (eg. Skyscanner). [0324] the Platform notifies the booking party. [0325] the Booking party receives a notification. [0326] the Booking party automatically has availability and prices of options re-collected. [0327] the Booking party receives a clickable (eg. 1 click) re-direct to a best or cheapest available price for that option.

[0328] A Meta Powered Flight Finder is provided.

[0329] In an example, there is specified a specific flight either by—minimum combination of [departure airport, arrival airport, departure time/date, arrival time/date, flight number, airline]. There is provided a meta search identification of cheapest price for that flight.

[0330] A Group Trip Planner is provided.

[0331] Multiple travellers may form part of the same “party”. In an example, all travellers can see each other's itineraries and add other travellers to the party. Travellers may “copy” parts of other traveller's trips, in an example.

A Corporate Travel Service

[0332] A problem is that travel arrangement processes in small and medium size firms are inefficient compared with bigger firms. For example, bigger firms may have a specialist travel manager or procurement buyer. For example, bigger firms may have a specialist/global procurement travel buyer. But a small or medium size firm may have only an internal travel manager, or open booking.

[0333] In a prior art organization travel booking process, organization members may request travel. There may then follow a process lasting about an hour, in which the organization members or their subordinates, research travel possibilities, and then book or request permission to book the travel. What follows is manual recording and paperwork, with limited reporting. An example is shown in FIG. 2.

[0334] In an initial solution, an organization administration unit may push a more formal solution into the rest of the organization.

[0335] Exponential growth may be achieved by getting further groups of organization members to engage in travel arrangement with an initial group of organization members who are planning travel, such as those organization members who may want to travel with the initial group, or such as those organization members who may be required to travel with the initial group.

[0336] A party system may be created in which organization members Share Itineraries, Discuss and copy options, Clone Trips, or Receive Travel-related Notifications. An example is shown in FIG. 3.

[0337] A party system may be created in which organization members may be segmented into groups related to travel arrangement, and Cross organization Pollination travel arrangement is achieved. An example is shown in FIG. 4.

[0338] In an example, a user generates an itinerary which consists of an identified flight route (eg. Atlanta to Edinburgh) and a location for a stay in a hotel (eg. Edinburgh). A user interface is presented in which individuals are selectable (such as from a previously generated travel group) for invitation to, or for addition to, the itinerary. An example of a party system in use on a smartphone is shown in FIG. 5.

[0339] In an example, a user generates an itinerary which consists of an identified flight route (eg. Atlanta to Edinburgh) and a location for a stay in a hotel (eg. Edinburgh). A user interface is presented in which individuals are selectable (such as from a previously generated travel group) for invitation to, or for addition to, the itinerary. A list of candidate outbound flights may be provided, from which an individual flight may be selectable. A plurality of selectable generated itineraries may be provided in a user interface. A list of individuals permitted to view the travel arrangements may be displayed in the user interface. An example of a party system in use on a desktop or laptop computer screen is shown in FIG. 6.

[0340] In an example, a second user receives and displays a message (eg. an email or text message) which invites them to collaborate on a trip plan which has been created by a first user. The message (eg. an email or text message) may include details of an itinerary, such as details of an outbound flight. An option may be presented in which the second user can click through to the trip plan provided by a trip plan operator on a trip planning platform. On the trip planning platform, the second user may be able to request or to review amendments to the trip plan. An example of a displayed email which a second user receives and which invites them to collaborate on a trip plan which has been created by a first user, is shown in FIG. 7.

[0341] A trip planning platform may provide a user interface for reporting of an organization's travel usage, in which reporting may be provided over the internet. Reporting may be provided to a limited user group, eg. a finance department. Reporting may include spending by department, spending by user, or spending by trip. Department spending may be reported by sub-department. Spending may be broken down into categories such as rail, flights and hotels. A reporting interval may be identified, such as from a start date to an end date. Key statistics may be presented: examples are percentage of organization spend by a department, percentage of organization trips by a department, and average travel planning lead time for a department. An example of a trip planning platform providing a user interface for reporting of an organization's travel usage, in which reporting may be provided over the internet, is shown in FIG. 8.

Corporate Travel System

[0342] In the prior art, typical referral mechanics are that a user wants to travel but the user wants someone else to book. So for example a traveller may research a trip and then send a request to travel admin to make the booking. Or a user who wants to travel may research a trip and then send himself a reminder to book later.

[0343] In a system, we start with someone else booking. A travel hub is provided. The travel hub may be a server connected via a network (eg. the internet) to a plurality of user terminals. The server may be real or virtual or in the Cloud. In an example, the travel hub is the anchor of Skyscanner's Corporate Travel Service: a hub for the storage/submissions and analysis of trips.

[0344] In an example, with a Traveller & Admin that are new to TravelHub, a new request is forwarded into TravelHub. There is a traveller who requests bookings, and an organization travel admin that processes bookings. The traveller's booking request is channeled via the travel hub to the organization's travel admin, with for example a communication being sent to the travel admin (e.g. email being sent to an address in the organization's domain). An example is shown in FIG. 9. In the example of FIG. 9, the traveller's request is channeled via the travel hub to an organization's travel admin, with an email communication being sent to an address in the organization's domain, which in this example is travel_admin@skyscanner.net. When the Travel Admin is notified of a booking, the Travel Admin is directed to the Travel Hub. If the Travel Admin is new to the travel hub service, before redirection to a booking site, the Travel Admin may be prompted to signup (eg. to register) (and optionally to store trips), or to return after booking to input a reference or price to the travel hub records, without signup. After a booking with a travel hub partner site is made, the Travel Admin may input a reference or price to the travel hub records. In a next step, the traveller is notified of the booking. The traveller may receive itinerary information relating to the booking. The traveller may receive one or a plurality of calendar entries relating to the booking. The travel admin may be able to receive an auto-reporting function of the booking, and of other bookings, from the travel hub, such as via a network (eg. internet) login to the travel hub. Information may therefore be stored to an organization, such as to the traveller's device or devices (eg. smartphone, tablet, laptop, desk top computer) and to the travel admin's account at the travel hub server.

[0345] Use of the travel hub service by an organization is expected to grow over time. An organization should be converted to using the service over time. For example, if multiple travellers make requests via the travel hub, a travel admin part of an organization will start to gain familiarity with the system. Even if the travel admin does not sign up on first usage, they may sign up after using the travel hub a few times. The travel admin may find they can execute their function in a much reduced time (eg. reduced to a tenth), and they may benefit from auto-reporting, because all the required information may be stored in one place, on the travel hub. The travel admin may then push usage onto further users inside the organization.

[0346] Spreading the adoption between organizations is possible, leading to mass adoption.

[0347] In the travel hub system, a traveller can share a first trip with other users, who may then generate their own trips based on the first trip. A traveller may be able to edit a trip. The travel admin may be able to book the trip.

[0348] A traveller may be able to invite others, from other organizations. A traveller may be able to invite others, from other organizations, to view a trip. A traveller can edit a trip, which is bookable by a travel admin; the traveller can invite a second traveller from another organization to view the trip. The traveller may be able to invite a second traveller to view the trip, before or after the trip is booked. An example is shown in FIG. 10, in which a traveller can edit a trip, which is bookable by a travel admin; the traveller can invite a second traveller to view the trip. The traveller may be able to invite a second traveller to view the trip, before or after the trip is booked.

[0349] A traveller may be able to invite others, from other organizations. A traveller may be able to invite others, from other organizations, to view a trip. A traveller can edit a trip, which is bookable by a travel admin; the traveller can invite a second traveller from another organization to view the trip. The traveller may be able to invite a second traveller to view the trip, before or after the trip is booked by travel admin. The second traveller may be able to copy the trip, to create a second trip. The second traveller may be able to customize the components of the second trip. The second traveller may be able to invite a third traveller from another organization to view the second trip. The third traveller may be able to copy the second trip, to create a third trip. The third traveller may be able to customize the components of the third trip. This process of spreading a trip to further travellers can keep on going.

[0350] This is so powerful. This permissions model can solve many problems.

[0351] It is possible to book others' travel.

[0352] A contractor may be used for this purpose. The contractor may be instructed “just book it”.

[0353] In an example, it is possible to let others book on your account. For example, a user wants to arrange travel through their own organization, for someone else, who may not be in the organization. In an example, a “book your travel link” is offered to the other person, such as by email or text message. An example is shown in FIG. 11, in which Ross in Skyscanner offers a “book your travel link” to Peter, who is not in Skyscanner.

[0354] In a response example, the other person who may not be in the organization may select one or more options, which may be based on the policy of the user. In a response example, the other person who may not be in the organization may select one or more options, which may be based on the policy of the user's organization recruitment policy.

[0355] How may the organization's hierarchy work in the travel hub? Here is an example. An organization has a name (eg. Skyscanner). The named organization has a hierarchy (eg. departments in the organization, eg. corporate travel group, recruitment). A user (eg. Ross) is situated somewhere in this hierarchy (eg. recruitment). An organization has locations (eg. office locations, eg. Edinburgh office). A user may be associated with a position in a hierarchy, and with an office location. An organization has travel bookers (eg. Jo, from corporate travel group).

[0356] We consider the example of a person outside the organization (eg. Peter); the organization has offered to book that person's travel (eg. Peter's travel to Edinburgh). An example is shown in FIG. 12.

[0357] The organization deals with the booking of the person from outside the organization. The trip is assigned to groups in the organization (eg. recruitment, corporate travel group, Edinburgh office).

[0358] When an individual in the organization approves the selection, the trip request travels up the organization, looking for the first layer with a booker. The booker may book the trip, and a “booked” status is assigned to the trip. In the travel hub, the trip is centred in the user space of the person outside the organization, but the trip is nevertheless associated with the user space of the organization in the travel hub.

[0359] When a supervisor (eg. Shane) looks at reports on the travel hub, he sees the booking his organization paid for, in the correct place. A schematic example is shown in FIG. 13.

[0360] An advantage of the travel hub system is its flexibility. An advantage of the travel hub system is it makes it easy for organizations to collaborate. An advantage of the travel hub system is that attending events with others is made simple. An advantage of the travel hub system is that sharing trips is made possible. An advantage of the travel hub system is that booking for others is made possible. An advantage of the travel hub system is that attending events with others from other organizations is made easier for a first organization. An advantage of the travel hub system is that sharing trips or events with others is made very simple.

[0361] If a user shares a meeting invite (eg. in Microsoft Outlook), the invite may provide a template for collaboration (eg. attendee names and email addresses, a location, and time information eg. a start time and an end time). An example of a meeting invite and information contained in the invite is shown in FIG. 14.

[0362] If a user shares their start location (eg. their home address) with the travel hub, that can be saved at the travel hub. Then the travel hub can start to make some guesses of trips, based on received meeting invite information.

[0363] If a user remembers one thing, because the calendar is part of their normal workflow, long after they have signed up and forgotten about the travel hub, they can ‘own the calendar’ and re-engage. A user may frequently add calendar events. For calendar events which have a location, the distance from a reference address (eg. the user's home address) may be evaluated, and a reason for the travel hub to contact the user may be understood (eg. some events in Paris on a particular date, some events in London on a different particular date and the user lives in Edinburgh, hence it seems the user will need to travel). The travel hub may help the user to plan, possibly before the user would normally start thinking about travel. The user traveller may be contacted via email, sms, push, or web, for example. The user traveller may be contacted via their smartphone, for example.

[0364] In an example, an itinerary generator may be used by the travel hub to generate and to send possible itineraries to the traveller user, such as to their smartphone. A schematic example is shown in FIG. 15.

[0365] An itinerary generator may use Skyscanner technology, for example a Skyscanner itinerary generator. An itinerary generator may generate itineraries according to preferences and a policy.

[0366] Three services may be provided by or via the travel hub. A first service is Authentication, Observation and Filtering. A second service is Multi Factor Itinerary Generation. A third service is a Mobile Application (eg. “TripGun” Mobile Application). A schematic example is shown in FIG. 16.

[0367] Trips created with a Mobile Application will feed straight into the travel hub. Such trips may be shared, for example as discussed above. A schematic example is shown in FIG. 17.

[0368] A mobile device may be in wireless communication with a server. A mobile device may be in wired communication with a server.

Further Disclosures

[0369] 1. Raising of a mobile push notifications calling to travel planning action, after creating a calendar event for people that have previously authorized their calendar events to be observed. (In an example, we can scope the time in which engagement takes place to help make it stick e.g. we can select the time in which engagement takes place so as to be suitable for the user).

[0370] Example: When the first time Tom opens the mobile device application or fixed device application (“TravelPro”), he is asked if he would like to integrate his calendar with the service. He then selects “yes” and authorizes TravelPro to access his calendar(s) eg. his Google, Outlook, exchange and/or Apple calendar(s). A month later Tom creates a new calendar event with the title “Annual conference” and the location in New York, USA, date 1st June, later in the same year.

[0371] Within an hour on his phone a push notification arrives that offers him booking his travel flight and accommodation for the Annual Conference in New York in June. When tapping this notification, the TravelPro application opens and a new trip creation process is started.

[0372] 2. Visually differentiating accommodation list items from a list of accommodation items, for which a company has negotiated special rates.

[0373] Example: When Suzy uses the TravelPro mobile or web application, every time she searches for hotels she sees a list of hotel rows. The hotels that have special rates negotiated by her company are always listed first, with an easy to notice visual differentiation.

[0374] 3. Visually displaying that a colleague of the current user is staying at or has stayed at accommodations, on a list of accommodation items.

[0375] Example: When Joanne uses the TravelPro mobile or web application, every time she searches for accommodations, she sees a list of accommodation items displayed in rows If any of her colleagues have made a booking for that accommodation, she sees their photos or names on these row items. This way she can very easily see which are the accommodations that someone at her company has booked at any point in the past.

[0376] 4. Visually displaying that a colleague of the current user has booked a flight, on a list of flight items

[0377] Example: When James uses the TravelPro web or mobile application, every time he searches for flights, he sees a list of flights items displayed in rows. If any of his colleagues have made a booking for that flight, he sees their photos or names on these row items. This way he can easily see which are the flights that someone at his company has booked at any point in the past.

[0378] 5. Sorting a list of accommodation items based on their distance from the company office of the current user in the city where these accommodations are located

[0379] Example: Tony is using the TravelPro web or mobile application and is searching for accommodation in London. On the screen accommodation result items are displayed in rows. His company has a London office so the accommodation items are sorted from ones closest to this office to the ones furthest from the office.

[0380] If Tony searches for accommodation in Edinburgh, where his company has multiple offices, he can choose which office he would like to see accommodations closest to.

[0381] 6. Visually indicating that a flight item is within the flights policy of the company of the current user

[0382] Example: When Joanne is searching for flights with the TravelPro mobile or web application, she sees flight results listed in rows. The flights that have all their parameters—cabin class and price—within the bounds that her company specified, can be visually easily differentiated from the ones that have either of these parameters outside of these bounds.

[0383] Joanne is searching for flights from London to New York and her company policy for this route is that prices cannot be over 20% of the median price and can be a maximum of £1000 and for this distance premium economy can be selected. The median price for the economy results is £500. The median price for the premium economy results is £900. Economy results that are more expensive than £600 are marked clearly, as are premium economy results more expensive then £1000. If selecting any of the visually marked flights, she needs to fill out an additional field to explain ignoring the company policy.

[0384] 7. Visually indicating that a rail item is within the accommodations policy of the current user

[0385] Example: When Joanne is searching for rail journey items with the TravelPro mobile or web application, she sees rail results listed in rows. The rail results that have all their parameters—seat class and price—within the bounds that her company specified, can be visually easily differentiated from the ones that have either of these parameters outside of these bounds.

[0386] Joanne is searching for rail results from London to Birmingham and her company policy for this route is that prices cannot be over 20% of the median price and can be a maximum of £100 and for this distance first class can be selected. The median price for the economy results is £50. The median price for the first class results is £90. Economy results that are more expensive than £60 are marked clearly, as are first class results more expensive then £100. If selecting any of the visually marked rail results, she needs to fill out an additional field to explain ignoring the company policy.

[0387] 8. Visually indicating that an accommodation item is within the accommodations policy of the current user

[0388] Example: When Barbara is searching for accommodation with the TravelPro mobile or web application, she sees accommodation results listed in rows. The accommodations that have all their parameters—number of hotel stars and price—within the bounds that her company specified, can be visually easily differentiated from the ones that have either of these parameters outside of these bounds.

[0389] Joanne is searching for accommodation in London and her company policy for this route is that prices cannot be over 20% of the median price per night and maximum 4 star accommodation can be selected. The median price for the results is £100 per night. The accommodations that are more expensive than £120 per night or that have more than 4 stars are marked visually as outside policy. If selecting any of the visually marked accommodations, she needs to fill out an additional field to explain ignoring the company policy.

[0390] Other Ideas [0391] Suggesting people to invite who are in your calendar meetings & are native contacts. [0392] Review a hotel so that it is only visible to the company. [0393] User Interface: When sorting by a parameter, highlighting that parameter on the sorted fields. [0394] User Interface: When tapping disabled search button, fields highlight that need to be filled.

Note

[0395] It is to be understood that the above-referenced arrangements are only illustrative of the application for the principles of the present invention. Numerous modifications and alternative arrangements can be devised without departing from the spirit and scope of the present invention. While the present invention has been shown in the drawings and fully described above with particularity and detail in connection with what is presently deemed to be the most practical and preferred example(s) of the invention, it will be apparent to those of ordinary skill in the art that numerous modifications can be made without departing from the principles and concepts of the invention as set forth herein.