| Live Search | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Step 3: Configure the site
Important:
...
Unless otherwise noted, the services listed below are cloned from the template. Therefore, you may only need to validate that the template values are what the client wants.
Refer to the Configure the new site section of the Implementation guide. This guide provides the minimum information required for a site, as well as links to other information that should be verified.
Important: Each service will have a list and set, allowing you the ability to add to each group’s Travel Service Rule. Click link for further information Lists, Sets and Rules
...
Configure groups.
Important: Identify how many groups the client needs based on what one set of employees can see over another (for example, VIP, Executive, Guest, Default). If the site was cloned, the groups in the template are copied into the new site. There is no limit to the number of groups you can create. Groups can be based on a variety of factors, such as travel policy, display policy, and payment options.Configure the client’s travel policies, such as allowed flight class, amounts, car rental, hotel, rail, and geographies. Refer to Travel Policy Best Practice for more information.
Configure the display policy. You create or edit a list of display settings as a configuration. The same configuration can be added to more than one set. which Refer to Policy Display Configuration Best Practice for more information.
Configure the site settings, such as whether to send registration and system emails and to allow delegation. You also can add technical support information for users.
Configure user profile fields.
If needed, add preferred vendors. Preferred car and air vendors are moved from the template. Preferred hotel vendors are not and will need to be configured if the client has any. Refer to preferred hotels.
Configure private rates if the client has any. Refer to air, car, hotel, and rail private rates.
Configure the travel agency settings, such as the GDS, terminal address, agency’s pseudo city code, default queue number, associated airport code, and agency information. For more information, refer to agency settings, custom PNR mapping, and queue and delivery options.
Configure any custom fields.
Hint: Configure commonly used custom fields (reporting fields) within your template, as these fields are moved over from the template. You can then use the fields or add new ones. , If you have fields configured within your template that are not needed, remove them from the site or remove them from the set.Configure dynamic site messaging if needed.
Hint: If you have messaging that will be consistent on every site (for example, the online support contact information), add it to your template site and it will move over when cloned.Create profiles. Profiles can be added manually, uploaded, via an SFTP data transfer, via a web service, or through open enrollment.
Configure profile synch / ETSI if needed.
Configure reference points. Reference points do not move over from a cloned template.
If basic economy fares need to be removed, it will need to be configured, as it does not move from the cloned template.
Configure hotel per diems.
Configure payment options. Payment options are not moved from the cloned template. Payment options can include site payment cards, corporate site cards (rarely configured), V-Pay/Conferma virtual pay.
Configure pre-trip approval (PTA).
Configure travel service rules.
Configure display option rules.
Configure unused tickets.
There are several optional services available, and they may require an SOW. The following require a Deem Support Case and email to Channel Sales Director.
Cost Allocation (Enhanced Custom Trip Field)
Important: Testing is critical. Test each new site prior to signing off and releasing to the client, or any time you configure something new, to ensure that the site works as expected.