Partnership proposal scenarios for notification service FlySMS

Scenario 1: API Integration

Target Audience: Online Travel Agencies (OTA), Travel Agencies and Airlines.

User Experience: After passenger purchase the ticket, FlySMS service is presented as an add on option to the ticket.

Technical Specifications: Integration is done via Javascript and the module is pop uped after user make a purchase. Time for an integration from the partner side is 3-5 days. Time for an integration from FlySMS’s side is 1-2 weeks as FlySMS will need to design the pop up and additional interface.

Commercial Efficiency: Net sales conversion starts at 1%, service is presented after the purchase of the ticket.

Scenario 2: Integration with Javascript

Target Audience: Online Travel Agencies (OTA), Travel Agencies and Airlines.

User Experience: After passenger purchase the ticket, FlySMS service is presented as an add on option to the ticket.

Technical Specifications: Integration is done via Javascript and the module is pop uped after user make a purchase. Time for an integration from the partner side is 3-5 days. Time for an integration from FlySMS’s side is 1-2 weeks as FlySMS will need to design the pop up and additional interface.

Commercial Efficiency: Net sales conversion starts at 1%, service is presented after the purchase of the ticket.

Scenario 3: Integration with the loyalty program

Target Audience: Airlines which offer different bonuses or miles with their loyalty program.

User Experience: User subscribe via an app or partner’s website to the service.

Technical Specifications: Integration is done with FlySMS’s JSON API. Time for an integration and development from the partner’s side starts at 6-8 weeks. Time for an integration from FlySMS’s side starts at 3-5 weeks.

Commercial Efficiency: Purchase of the service is done with accumulated miles or allow user to have a discount for a FlySMS service.

Scenario 4: Re - direct to the service’s payment gateway

Target Audience: Online registration for airlines

User Experience: User receive the information on the registration for the flight, which is also contains the link to purchase FlySMS, or after user actually registered on a flight he will have an option to purchase FlySMS service.

Technical Specifications: Integration is done by creating a link on a purchase portal of FlySMS service and integrating this link into various airline’s flight registration processes. Time for development and integration from the partner’s side 2-3 days, time for integration from FlySMS’s side 2-3 days.

Commercial Efficiency: Purchase of the service is done by separate financial transaction, conversion start at 1%.

Scenario 5: Purchase of the service from the partner’s portal

Target Audience: Tourism agencies which sell tickets offline, with the vast agent network.

User Experience: When a passenger buys a tour, FlySMS service is offered as an additional service.

Technical Specification: Partner’s agents make a registration and offer the FlySMS service. Portal have full spectre of features, starting from creating, deleting and editing notifications.

Commercial Efficiency: FlySMS service can be included in the price of the tour and the conversion will start at 10%.