Open main menu

Agency

Revision as of 19:31, 24 December 2020 by I shaletin (talk | contribs) (Created page with "'''Agency''' - a legal entity that has entered into direct contracts for the use of XML web services with service providers (GDS or CDS), or has received such a license or...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Agency - a legal entity that has entered into direct contracts for the use of XML web services with service providers (GDS or CDS), or has received such a license or sublicense from Mute Lab Software under an existing agreement.

The agency receives a limited license for the proprietary Websky software, which is transferred to the subscriber under the terms of the agreement and implies connection and use of the system on domain names.

There is an option to extend the agency license - allocation of additional license for the agency to install the Websky system on another domain name with another isolated account.

System subscriber has the right to obtain a sub-agent license. It gives an opportunity to organize a network of subagent TUPs on partner satellite sites operating in a limited mode (B2C only) under the terms of the agreement within the framework of an agent license. With a subagent license, the allocation of isolated accounts for subagents is not possible and system administration is performed by the agency within a single account.

Contents

Agency Settings in Websky

The Company profiles page in the Account management → Agents and users section contains a set of key parameters that characterize any organization in the system (agency, subagent, corporate client):

  • Company name - displayed on the portal and in emails.
  • Agency official name - displayed on outgoing documents.
  • TIN - should be filled in in case of using the functionality of uploading data about agent's selling points to MPS (see Synchronization with the MPS payment system).
  • OGRN - similarly.
  • Currency - the base currency in which the agency accepts money and issues invoices. By default, all prices on the website will be displayed in this currency. The total price of services, payment charge and the whole order is rounded upwards in the agency's currency. Prices in Euros, U.S. dollars, British pounds, and Azerbaijani Manats are rounded to a hundredth. Prices in Russian rubles and other currencies are rounded to integers. The difference is added to the agent's fee.

The ten fields below are informative and are not obligatory, but can be used in the outgoing documents (templates of invoices and receipts for payment). Also, if a subagent (company) registers independently on the agent's website through the legal entity registration form, the fields filled in during registration will be saved in that company's profile in the settings.

Legal address:

  • Country - also determines the default language on the site.
  • State
  • Street
  • House
  • Office
  • ZIP code

Actual Address:

  • Actual address (country)
  • Actual address (city)
  • Actual address
  • Actual address (postal code)
  • Agency phone number - information optional field.
  • Agency website - information field.
  • Email address - this field is a reference and is intended for displaying on the portal. Also, a test mail message is sent to this address to test the work of the mail client. See Mail server
  • Tax type - the parameter is needed to determine behavior of variable invoices and receipts related to VAT. Valid values:
    • No VAT - VAT is not calculated. Values of VAT related variables in the route receipt will be equal to zero.
    • Simplified mode (benefits - spendings) - as in the first case, VAT is not calculated. Values of variables related to VAT in the route receipt will be equal to zero.
    • VAT - VAT will be calculated.

Attention! To correctly specify the type of taxation when sending data to generate a fiscal document (relevant for online payment methods), it is necessary to correctly set the value of the above setting Type of Taxation.

The following setting is displayed only for companies (sub-agencies) and is not relevant for the root agency:

  • Subagent ID in third-party CRM - subagent ID in some third-party system, such as Amadeus CRM, it can also be 1C or other system that the agent uses to record subagency sales. If this field is filled in, the PNR will add a notation in the ticketing request containing the following data for the particular order: subagent ID in the Websky system, subagent ID in a 3rd party CRM, order ID, triggered price rule ID, payment method, payment gateway or payment method charge, sales channel, subagent commission (calculated total per order).

Attention! In case of tickeitng in Amadeus, Sabre and GalileoUAPI, all the specified data on the order is supported. When tickeitng from Sirena and SITA - only the subagent ID in a third-party CRM. The agent is supposed to set up their own CRM or other system so that it handles these remarks correctly. This ID will be the same for all bookingsof all users within a particular subagency.

Call Center

Call center is an agency mode that grants all of its users the status of a call center operator regardless of the previously set user type. The call center operator has reduced access to the settings, but increased access to the server orders, provided for the convenience of secondary operations with ancillary services, as well as electronic tickets and documents (eg Air ticket Exchange and Refund or PNR import to a new order). All call center users are restricted to Access rights by the access rights set on the agency.

Attention! The call center operator is not available to confirm the request during the refund process.

Registration of new agency users in call center mode is not possible, unregistered users are blocked access to the agency.

Call Center mode for the agency can be enabled only by the administrator of the Websky system under 'For technical support → Initial setup.

Agency manager options when working with the booking and ticketing module

Module control panel allows you to:

  • Manage settings of the search form
  • Adjust booking form settings
  • Enable or disable search by dates
  • Set routing of search requests depending on search parameters
  • Set rules to filter out unwanted flights from search results
  • Set restrictions on searches and bookings relative to the closest available booking date
  • Set request filters to limit search geography
  • Set limitations on the maximum number of passengers in a search request
  • Allow or prohibit departures and arrivals on the same day
  • Create and edit service rules for the whole agency, subagents, users and user groups
  • Customize mandatory and visible fields of passenger and customer information forms
  • Keep search request statistics with breakdowns for each supplier
  • Keep booking and cancellation statistics
  • Set permissions for users or user groups for basic system actions
  • Set up the mechanism for applying and calculating airline commission rules
  • Control how subagents' commissions are displayed
  • Allow or prohibit subagents to set their own fees
  • Sell branded fares
  • Set subagent commission values in commission rules
  • Process ticket exchanges and refund requests
  • Pay for orders directly to the airline (for those suppliers and payment gateways that support this)
  • Connect upsales of optional services (insurance, Aeroexpress, service packages) for air travel
  • Adjust operation of automatic ticketing and acquiring
  • Set up additional discounts using promotional codes

See also