The JRS Public Interface

The JRS has a public interface allowing Third Party vendors to make Bookings and view Sales History etc. These third party Interfaces may include :-

Websites - The public interface can be provided to your web developers allowing them to read content from the JRS and submitt bookings back to the JRS in real time.

Significantly increase exposure without increasing running costs. Eliminate rekeying of Bookings into the Database. Publish Content (Tours, Prices, Commissions etc) to external parties. Provide Agents and the Public a 24x7 booking mechanism that does not tie up your phone lines. Allow Bookings to be confirmed avoiding the need for the Passengers to Queue for Tickets on Departure Day. Receipt money in your Account, in real time, without double handling. Search for Tours based on Region, Date, Keywords, Category, Tour Duration. Maintain content, including prices, from the JRS without commissioning any more development work. Provide links back to the Website from the confirmation email giving Clients more information about the Tours they have booked.

Australian Day Tours Gray Line Australia

PDAs

This project, originally intended for Sales, has found more popularity in Dispatch Locations as it has allowed Dispatch Offices to be closed removing the need for Office Rental, Phone Lines, Internet Connections, PCs and Printers. Agent details can be downloaded onto the device along with Manifests and Pickup Schedules.

Kiosks

The Public Interface also supports remote, unattended Kiosks. Kiosks can be dedicated or shared, housed in indoor controlled environments or in outdoor public environments providing 24x7 exposure without the need for sales staff.

The Public Interface uses an industry standard SOAP (Simple Object Access Protocol) Interface and your Developers can request an Interface Specification (WSDL File) from Jewel at any time.

The Public Interface is also used by several clients to post bookings from one JRS to another.