hoteliga - User contributions [en]

Channel Manager

2020-01-15T10:05:37Z

Katya: /* FAQs */

== Introduction ==
A channel manager is software that allows your property to directly connect with various [[Glossary#O|OTA]]s. With this tool, you can easily update rates, allotment, availability and restrictions.

== Why it is Necessary to Have a Channel Manager ==
If your property is contracted with many OTAs, you have to login frequently to each and every one of the OTA extranets and update mostly prices and allotment (i.e. rooms to sell). This process is very time-consuming and can also lead to mistakes, as it is done manually.
But the greatest risk is to get overbookings for not being able to update in time. For example: Let's say that your hotel has contracted with booking.com and Expedia. Now suppose that the hotel has one double room left for a given night, let's say the 15th of August. At 3.00 am local time, a reservation is made in booking.com for a double room for the 15th of August. The allotment (rooms to sell) in booking.com is now automatically set to zero for this date. But the rooms to sell in Expedia for a double room in the 15th of August is still one.

If no one sets the allotment for this room type and this date in Expedia to zero (after 3.00 am in the night), it could happen that at 3.30 am, another reservation arrives, this time from Expedia, for a double room for the 15th of August. But there is no free double room any more, as it was booked 30 minutes ago in booking.com. That is an overbooking, and it is the hotel responsibility to find another accommodation for the hotel guest.

As it is practically impossible for someone to manually update all extranets all day and night (what if the contracted OTAs where 5, or 10?), a channel manager takes care the automatic update of room allotment (rooms to sell), among others.

== Channel Manager Options ==
With hoteliga you can choose among three channel managers:
* the [[hoteliga Channel Manager]], the most integrated solution with direct certified connections
* [[Parity Rate]], an affordable channel manager
* [[SiteMinder]], a very popular channel manager

{| style="width:60%;text-align:center" class="wikitable"
|-
! style="width: 40%;" |
! style="width: 20%;" | hoteliga channel manager
! style="width: 20%;" | Parity Rate
! style="width: 20%;" | SiteMinder
|-
| style="text-align:left" | Available channels
| booking.com, Expedia (Hotels.com, Expedia Affiliante Network, Travelocity), Hotelbeds, Agoda, TripAdvisor*
| [https://www.parityrate.com/en/integrations/ click here]
| [https://www.siteminder.com/integrations/online-travel-agencies/ click here]
|-
| style="text-align:left"|Support for multiple IDs
| YES
| NO
| NO
|-
| style="text-align:left"|Download frequency for reservations
| Instant download for booking.com<br/>every 10 min. for the rest
| every 10 min.
| every 5 min.
|-
| style="text-align:left"|Synchronization of available rooms (allotment)
| Real time
| Real time
| Real time
|-
| style="text-align:left"|Upload of rates, restrictions, stop sales
| YES
| YES
| YES
|-
| style="text-align:left"|Integration with hoteliga PMS
| Direct
| Indirect
| Indirect
|-
| style="text-align:left"|Billing cycle
| Monthly/Annually
| Annually Only
| Monthly
|-
| style="text-align:left"|Pay per channel
| YES
| YES
| NO
|-
| style="text-align:left"|Synchronization with vacation portals<br/>(availability only)
| Free
| Pay
| Pay
|-
|}
<nowiki>*</nowiki> requires hoteliga booking engine

After choosing the right channel manager for you, you need to decide the way that data will be synchronized between hoteliga PMS and the [[Glossary#O|OTA]]s. The following options exist:
* '''One-way connection'''. The [[Glossary#O|OTA]] only sends reservations to the hoteliga PMS, nothing else. Choose this option if you are used to manage prices/rates from the [[Glossary#O|OTA]]'s extranet.
* '''Two-way connection'''. The [[Glossary#O|OTA]] sends reservations to the hoteliga PMS, and at the same time the hoteliga PMS sends room allotment, room rate/type availability, prices and restrictions to the [[Glossary#O|OTA]]. This is the full and most complete connection one can get.

Every channel manager has different costs, please consult the [http://www.hoteliga.com hoteliga website] for more information.

== Setting Up the Channel Manager in hoteliga PMS ==
In order to start using the channel manager in hoteliga PMS, the following requirements exist:
* You need to have signed a contract and activated the connection with at least an OTA. If you don't have any contracts, see also "[[How Do I Connect With a New OTA?]]".
* You need to have selected and purchased the channel manager connection that is best for you.

The next thing to do is to contact hoteliga support in order to arrange the setup of the channels. This setup is included in the cost of channel manager connection and '''it is very important that it is done together with hoteliga staff to avoid mistakes.'''

The setup process includes the following steps:
* Ensure with hoteliga staff that access to the OTA extranet is available (or access to Parity Rate/SiteMinder extranet is available).
* Ensure with hoteliga staff that the OTA has issued credentials (username & password) for the channel manager (these credentials may be different for human and system access).
* Ensure with hoteliga staff that the property, rates and room type setup on the OTA is reasonable and compatible with hoteliga concepts.
* Activate the channel connection from inside the extranet (if applicable) with the assistance of hoteliga staff.
* Do the correct room type and rate mapping inside hoteliga channel manager configuration with the assistance of hoteliga staff.
* Upload room allotment and prices from inside the hoteliga PMS for the first time with the assistance of hoteliga staff.
* Do visual checks for random dates and room types and compare the prices and values in the OTA extranet and hoteliga PMS.

== FAQs ==
* [[How Do I Connect With a New OTA?]]
* [[How to Connect an Airbnb Account and its Listings]]
* [[How Do I Get the Credit Card Information From a Reservation?]]
* [[What Information hoteliga exchanges with Channels?]]
* [[What Kind of Restrictions are in Booking.com?]]
* [[How can the Hotel add a Room/Rate?]]
* [[How can I add or set Special Prices to each Channel?]]
* [[What happens when I get a reservation with a Special Price that is not set in hoteliga?]]
* [[How can I change the Cancelation Policy in a Channel?]]
* [[Derived / Linked Prices]]

How to Connect an Airbnb Account and its Listings

2019-11-29T16:03:08Z

Katya: /* Creating a contract */

This tutorial is for adding new AirBnb connection to hoteliga account.

To make a new connection you have to follow next steps.

== Connecting to AirBnb Account ==
At this moment you are supposed to have an AirBnb account already.

To add a new connection you need to go to Channel Manager area (Options ⇒ Channel Manager). You should see the AirBnb (Official) area. If you don't, it means you don't have permission to create an AirBnb channel (please contact us for more information).

[[File:Channel_manager_index_en.png|900px]]

As the next step you need to go to Accounts page (first button in AirBnb (Official) area).

You will see an empty page with red button "Connect with Airbnb":

[[File:Accounts grid en.png|900px]]

1) Before clicking the button, '''you have to logout from your AirBnb account''', otherwise connection will not succeed.

2) When you click on "Connect with Airbnb" you will be redirected to the Airbnb login page, where you should choose your account or add another, which will be authorized and hoteliga will have access to it:

[[File:AirBnb connecting account en.png]]

After you will see the page to give access to hoteliga:

[[File:Connect Airbnb en.png|900px]]

3) Then you have to click "Return to Hoteliga" to finish connection:

[[File:Return to hoteliga en.png|600px]]

You will be redirected back to account list:

[[File:Added airbnb account en.png|900px]]

The account was authorized successfully.

To add another account repeat 1-3 steps above.

== Disconnection an AirBnb Account ==
To disconnect an Airbnb account, go to Accounts and click on an account you want to disable and select '''"Disconnect account"''':

[[File:Disconnect airbnb account en.png|900px]]

Further any information about this account won't be available for hoteliga.

You can remove an account from hoteliga from your Airbnb account:

[[File:Remove hoteliga en.png|600px]]

If you do so, you also have to remove this account from hoteliga by clicking '''"Remove disconnected account"''' (Accounts page).

== Listings ==
In your AirBnb account you can add listings, each listing will be mapped to hoteliga as room type. In hoteliga side you can have several rooms of a room type (which connected to a listing) and they should be the same as Airbnb requires them to be.

For example you have 3 listing in your Airbnb account:

[[File:Airbnb listings en.png]]

Inside of hoteliga listings (Channel Manager ⇒ Listings (second button in AirBnb section)) you will see all Airbnb listings from all authorized accounts:

[[File:Listings hoteliga en.png|900px]]

The meaning of columns are:

* '''Listing name''' - the name you've set inside Airbnb account for a listing
* '''Account email''' - the email of the authorized account
* '''Room type''' - associated hoteliga room type title (when listing is connected)
* '''Available''' - if a listing is available, '''no''' - listing is not available, and no reservation can be done
* '''Connected''' - if a listing is connected to hoteliga
* '''Channel name''' - the channel name which will be created in hoteliga and associated with airbnb listing
* '''Sync category''':
** '''Disconnected''' - a listing is not managed by hoteliga
** '''Limited''' - hoteliga sends updates only about prices and availability

=== Connecting an AirBnb listing ===
When you click on a listing you will see a modal, where you can edit only 3 fields: room type (hoteliga room type), connected and available switch buttons.

[[File:Listing modal en.png|600px]]

To connect a listing with hoteliga you should choose a hoteliga room type and enable '''connected'''.

[[File:Connected listing en.png|600px]]

When you reopen window you will see that Available is also enabled and there is an associated channel and also sync category is '''Limited'''.

[[File:Complete connected listing en.png|600px]]

The field '''Approved''' means that from AirBnb side this listing was checked for minimum required information (title and at least one photo). If there is no photo, instead of '''approved''' you will see '''rejected''' and below in '''Approval notes''' the reason why this listing was rejected. "Rejected" means no reservation can be made for this listing.

You can also make the listing unavailable, but it still will be managed through hoteliga. "Unavailable" is like the same as a closed property.

Now from your hoteliga domain you can manage an AirBnb listing.

==== Managing AirBnb Channel ====
After connecting a listing an associated record in Channels (Options ⇒ Channel Manager ⇒ Channels) will be created:

[[File:Airbnb Channels en.png|800px]]

When you disconnect a listing, the associated record will be deleted from Channels.

You can change channel title from there.
* '''Channel property ID''' - is the associated listing ID
* '''account_id''' - the host's ID (AirBnb account ID)
* '''inventory_code''' - how many rooms of this room type are available (should be 0 or 1):
** 0 - means that AirBnb will get the room type either available or not available
** 1 - means that AirBnb will get how many rooms are available or just not available

[[File:Airbnb channel en.png|600px]]

For this channel also will be created automatically the room type mapping:

[[File:Airbnb room type mapping en.png|600px]]

You can also change the mapped room type.

You also need to map rates inside of "Price list" tab. For AirBnb there is only one rate.

[[File:Airbnb map rates en.png|600px]]

==== Creating a price list ====
TODO

==== Creating a contract ====
TODO

== Seasonal Rules ==
TODO

== Uploading Prices to/from AirBnb ==
TODO

How to Connect an Airbnb Account and its Listings

2019-11-29T14:59:35Z

Katya: /* Seasonal Rules */

This tutorial is for adding new AirBnb connection to hoteliga account.

To make a new connection you have to follow next steps.

== Connecting to AirBnb Account ==
At this moment you are supposed to have an AirBnb account already.

To add a new connection you need to go to Channel Manager area (Options ⇒ Channel Manager). You should see the AirBnb (Official) area. If you don't, it means you don't have permission to create an AirBnb channel (please contact us for more information).

[[File:Channel_manager_index_en.png|900px]]

As the next step you need to go to Accounts page (first button in AirBnb (Official) area).

You will see an empty page with red button "Connect with Airbnb":

[[File:Accounts grid en.png|900px]]

1) Before clicking the button, '''you have to logout from your AirBnb account''', otherwise connection will not succeed.

2) When you click on "Connect with Airbnb" you will be redirected to the Airbnb login page, where you should choose your account or add another, which will be authorized and hoteliga will have access to it:

[[File:AirBnb connecting account en.png]]

After you will see the page to give access to hoteliga:

[[File:Connect Airbnb en.png|900px]]

3) Then you have to click "Return to Hoteliga" to finish connection:

[[File:Return to hoteliga en.png|600px]]

You will be redirected back to account list:

[[File:Added airbnb account en.png|900px]]

The account was authorized successfully.

To add another account repeat 1-3 steps above.

== Disconnection an AirBnb Account ==
To disconnect an Airbnb account, go to Accounts and click on an account you want to disable and select '''"Disconnect account"''':

[[File:Disconnect airbnb account en.png|900px]]

Further any information about this account won't be available for hoteliga.

You can remove an account from hoteliga from your Airbnb account:

[[File:Remove hoteliga en.png|600px]]

If you do so, you also have to remove this account from hoteliga by clicking '''"Remove disconnected account"''' (Accounts page).

== Listings ==
In your AirBnb account you can add listings, each listing will be mapped to hoteliga as room type. In hoteliga side you can have several rooms of a room type (which connected to a listing) and they should be the same as Airbnb requires them to be.

For example you have 3 listing in your Airbnb account:

[[File:Airbnb listings en.png]]

Inside of hoteliga listings (Channel Manager ⇒ Listings (second button in AirBnb section)) you will see all Airbnb listings from all authorized accounts:

[[File:Listings hoteliga en.png|900px]]

The meaning of columns are:

* '''Listing name''' - the name you've set inside Airbnb account for a listing
* '''Account email''' - the email of the authorized account
* '''Room type''' - associated hoteliga room type title (when listing is connected)
* '''Available''' - if a listing is available, '''no''' - listing is not available, and no reservation can be done
* '''Connected''' - if a listing is connected to hoteliga
* '''Channel name''' - the channel name which will be created in hoteliga and associated with airbnb listing
* '''Sync category''':
** '''Disconnected''' - a listing is not managed by hoteliga
** '''Limited''' - hoteliga sends updates only about prices and availability

=== Connecting an AirBnb listing ===
When you click on a listing you will see a modal, where you can edit only 3 fields: room type (hoteliga room type), connected and available switch buttons.

[[File:Listing modal en.png|600px]]

To connect a listing with hoteliga you should choose a hoteliga room type and enable '''connected'''.

[[File:Connected listing en.png|600px]]

When you reopen window you will see that Available is also enabled and there is an associated channel and also sync category is '''Limited'''.

[[File:Complete connected listing en.png|600px]]

The field '''Approved''' means that from AirBnb side this listing was checked for minimum required information (title and at least one photo). If there is no photo, instead of '''approved''' you will see '''rejected''' and below in '''Approval notes''' the reason why this listing was rejected. "Rejected" means no reservation can be made for this listing.

You can also make the listing unavailable, but it still will be managed through hoteliga. "Unavailable" is like the same as a closed property.

Now from your hoteliga domain you can manage an AirBnb listing.

==== Managing AirBnb Channel ====
After connecting a listing an associated record in Channels (Options ⇒ Channel Manager ⇒ Channels) will be created:

[[File:Airbnb Channels en.png|800px]]

When you disconnect a listing, the associated record will be deleted from Channels.

You can change channel title from there.
* '''Channel property ID''' - is the associated listing ID
* '''account_id''' - the host's ID (AirBnb account ID)
* '''inventory_code''' - how many rooms of this room type are available (should be 0 or 1):
** 0 - means that AirBnb will get the room type either available or not available
** 1 - means that AirBnb will get how many rooms are available or just not available

[[File:Airbnb channel en.png|600px]]

For this channel also will be created automatically the room type mapping:

[[File:Airbnb room type mapping en.png|600px]]

You can also change the mapped room type.

You also need to map rates inside of "Price list" tab. For AirBnb there is only one rate.

[[File:Airbnb map rates en.png|600px]]

==== Creating a contract ====

== Seasonal Rules ==
TODO

== Uploading Prices to/from AirBnb ==
TODO

How to Connect an Airbnb Account and its Listings

2019-11-29T14:53:07Z

Katya: /* Connecting an Airbnb listing */

How to Connect an Airbnb Account and its Listings

2019-11-29T14:52:17Z

Katya: /* Connecting an Airbnb listing */

This tutorial is for adding new AirBnb connection to hoteliga account.

To make a new connection you have to follow next steps.

== Connecting to AirBnb Account ==
At this moment you are supposed to have an AirBnb account already.

To add a new connection you need to go to Channel Manager area (Options ⇒ Channel Manager). You should see the AirBnb (Official) area. If you don't, it means you don't have permission to create an AirBnb channel (please contact us for more information).

[[File:Channel_manager_index_en.png|900px]]

As the next step you need to go to Accounts page (first button in AirBnb (Official) area).

You will see an empty page with red button "Connect with Airbnb":

[[File:Accounts grid en.png|900px]]

1) Before clicking the button, '''you have to logout from your AirBnb account''', otherwise connection will not succeed.

2) When you click on "Connect with Airbnb" you will be redirected to the Airbnb login page, where you should choose your account or add another, which will be authorized and hoteliga will have access to it:

[[File:AirBnb connecting account en.png]]

After you will see the page to give access to hoteliga:

[[File:Connect Airbnb en.png|900px]]

3) Then you have to click "Return to Hoteliga" to finish connection:

[[File:Return to hoteliga en.png|600px]]

You will be redirected back to account list:

[[File:Added airbnb account en.png|900px]]

The account was authorized successfully.

To add another account repeat 1-3 steps above.

== Disconnection an AirBnb Account ==
To disconnect an Airbnb account, go to Accounts and click on an account you want to disable and select '''"Disconnect account"''':

[[File:Disconnect airbnb account en.png|900px]]

Further any information about this account won't be available for hoteliga.

You can remove an account from hoteliga from your Airbnb account:

[[File:Remove hoteliga en.png|600px]]

If you do so, you also have to remove this account from hoteliga by clicking '''"Remove disconnected account"''' (Accounts page).

== Listings ==
In your AirBnb account you can add listings, each listing will be mapped to hoteliga as room type. In hoteliga side you can have several rooms of a room type (which connected to a listing) and they should be the same as Airbnb requires them to be.

For example you have 3 listing in your Airbnb account:

[[File:Airbnb listings en.png]]

Inside of hoteliga listings (Channel Manager ⇒ Listings (second button in AirBnb section)) you will see all Airbnb listings from all authorized accounts:

[[File:Listings hoteliga en.png|900px]]

The meaning of columns are:

* '''Listing name''' - the name you've set inside Airbnb account for a listing
* '''Account email''' - the email of the authorized account
* '''Room type''' - associated hoteliga room type title (when listing is connected)
* '''Available''' - if a listing is available, '''no''' - listing is not available, and no reservation can be done
* '''Connected''' - if a listing is connected to hoteliga
* '''Channel name''' - the channel name which will be created in hoteliga and associated with airbnb listing
* '''Sync category''':
** '''Disconnected''' - a listing is not managed by hoteliga
** '''Limited''' - hoteliga sends updates only about prices and availability

=== Connecting an Airbnb listing ===
When you click on a listing you will see a modal, where you can edit only 3 fields: room type (hoteliga room type), connected and available switch buttons.

[[File:Listing modal en.png|600px]]

To connect a listing with hoteliga you should choose a hoteliga room type and enable '''connected'''.

[[File:Connected listing en.png|600px]]

When you reopen window you will see that Available is also enabled and there is an associated channel and also sync category is '''Limited'''.

[[File:Complete connected listing en.png|600px]]

The field '''Approved''' means that from Airbnb side this listing was checked for minimum required information (title and at least one photo). If there is no photo, instead of '''approved''' you will see '''rejected''' and below in '''Approval notes''' the reason why this listing was rejected. "Rejected" means no reservation can be made for this listing.

You can also make the listing unavailable, but it still will be managed through hoteliga. "Unavailable" is like the same as a closed property.

Now from your hoteliga domain you can manage an Airbnb listing.

==== Managing Airbnb Channel ====
After connecting a listing an associated record in Channels (Options ⇒ Channel Manager ⇒ Channels) will be created:

[[File:Airbnb Channels en.png|800px]]

When you disconnect a listing, the associated record will be deleted from Channels.

You can change channel title from there.
* '''Channel property ID''' - is the associated listing ID
* '''account_id''' - the host's ID (AirBnb account ID)
* '''inventory_code''' - how many rooms of this room type are available (should be 0 or 1):
** 0 - means that Airbnb will get the room type either available or not available
** 1 - means that Airbnb will get how many rooms are available or just not available

[[File:Airbnb channel en.png|600px]]

For this channel also will be created automatically the room type mapping:

[[File:Airbnb room type mapping en.png|600px]]

You can also change the mapped room type.

You also need to map rates inside of "Price list" tab. For AirBnb there is only one rate.

[[File:Airbnb map rates en.png|600px]]

==== Creating a contract ====

== Seasonal Rules ==
TODO

File:Airbnb map rates en.png

2019-11-29T14:38:42Z

Katya:

File:Airbnb room type mapping en.png

2019-11-29T14:34:36Z

Katya:

File:Airbnb channel en.png

2019-11-29T14:21:28Z

Katya:

File:Complete connected listing en.png

2019-11-29T14:11:24Z

Katya: Katya uploaded a new version of File:Complete connected listing en.png

File:Complete connected listing en.png

2019-11-29T14:09:56Z

Katya:

File:Airbnb Channels en.png

2019-11-29T14:02:38Z

Katya:

File:Connected listing en.png

2019-11-29T14:00:26Z

Katya:

File:Listing modal en.png

2019-11-29T13:56:26Z

Katya:

How to Connect an Airbnb Account and its Listings

2019-11-29T13:55:01Z

Katya: /* Listings */

How to Connect an Airbnb Account and its Listings

2019-11-27T15:07:17Z

Katya: /* Disconnection an AirBnb Account */

File:Remove hoteliga en.png

2019-11-27T15:04:20Z

Katya:

File:Disconnect airbnb account en.png

2019-11-27T14:53:27Z

Katya:

How to Connect an Airbnb Account and its Listings

2019-11-27T14:51:05Z

Katya: /* Connecting to AirBnb Account */

How to Connect an Airbnb Account and its Listings

2019-11-27T14:50:36Z

Katya: /* Listings */

How to Connect an Airbnb Account and its Listings

2019-11-27T14:44:32Z

Katya: /* Listings */

File:Listings hoteliga en.png

2019-11-27T14:44:02Z

Katya:

File:Airbnb listings en.png

2019-11-27T14:39:20Z

Katya:

How to Connect an Airbnb Account and its Listings

2019-11-27T13:41:28Z

Katya: /* Connecting to AirBnb Account */

File:Added airbnb account en.png

2019-11-27T13:20:15Z

Katya:

File:Return to hoteliga en.png

2019-11-27T13:18:33Z

Katya:

File:Connect Airbnb en.png

2019-11-27T13:16:37Z

Katya:

File:AirBnb connecting account en.png

2019-11-27T13:12:04Z

Katya: Katya uploaded a new version of File:AirBnb connecting account en.png

File:AirBnb connecting account en.png

2019-11-27T13:11:40Z

Katya:

How to Connect an Airbnb Account and its Listings

2019-11-27T11:08:35Z

Katya: /* Connecting to AirBnb Account */

How to Connect an Airbnb Account and its Listings

2019-11-27T10:12:07Z

Katya: /* Connecting to AirBnb Account */

File:Accounts grid en.png

2019-11-27T10:11:17Z

Katya:

File:Channel manager index en.png

2019-11-27T10:02:09Z

Katya:

How to Connect an Airbnb Account and its Listings

2019-11-27T09:53:43Z

Katya: /* Introduction */

This tutorial is for adding new AirBnb connection to hoteliga account.

To make a new connection you have to follow next steps.

== Connecting to AirBnb Account ==
TODO

== Listings ==
TODO

== Seasonal Rules ==
TODO

How to Connect an Airbnb Account and its Listings

2019-11-27T09:49:52Z

Katya:

== Introduction ==
TODO

== Connecting to AirBnb Account ==
TODO

== Listings ==
TODO

== Seasonal Rules ==
TODO

Automation

2019-10-22T12:09:11Z

Katya: /* GET request */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

Beware the endpoint you provide must execute within 5 seconds. Otherwise the call will fail.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (GET/POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

====POST request====

[[File:webhook_example_en.png]]

[[File:webhook_task.png]]

Request URL: <pre>https://your-endpoint.com</pre>

Request payload:
* JSON:
<pre>
{
"id":"12638",
"dateFrom":"18/10/2019",
"dateTo":"20/10/2019",
"customerFullName":"TestFullName"
}
</pre>
* XML:

<pre>
<?xml version="1.0" encoding="utf-16"?>
<reservation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<id>12638</id>
<dateFrom>18/10/2019</dateFrom>
<dateTo>20/10/2019</dateTo>
<customerFullName>TestFullName</customerFullName>
</reservation>
</pre>

====GET request====

[[File:webhook_example_get_en.png]]

Request URL: <pre>https://your-endpoint.com?reservationId=12678&dateFrom=18/10/2019&dateTo=20/10/2019&customerFullName=TestFullName</pre>

File:Webhook example get en.png

2019-10-22T12:08:36Z

Katya:

Automation

2019-10-22T12:08:02Z

Katya: /* POST request */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

Beware the endpoint you provide must execute within 5 seconds. Otherwise the call will fail.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (GET/POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

====POST request====

[[File:webhook_example_en.png]]

[[File:webhook_task.png]]

Request URL: <pre>https://your-endpoint.com</pre>

Request payload:
* JSON:
<pre>
{
"id":"12638",
"dateFrom":"18/10/2019",
"dateTo":"20/10/2019",
"customerFullName":"TestFullName"
}
</pre>
* XML:

<pre>
<?xml version="1.0" encoding="utf-16"?>
<reservation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<id>12638</id>
<dateFrom>18/10/2019</dateFrom>
<dateTo>20/10/2019</dateTo>
<customerFullName>TestFullName</customerFullName>
</reservation>
</pre>

====GET request====

Request URL: <pre>https://your-endpoint.com?reservationId=12678&dateFrom=18/10/2019&dateTo=20/10/2019&customerFullName=TestFullName</pre>

Automation

2019-10-22T12:07:42Z

Katya: /* POST request */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

Beware the endpoint you provide must execute within 5 seconds. Otherwise the call will fail.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (GET/POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

====POST request====

[[File:webhook_task.png]]

Request URL: <pre>https://your-endpoint.com</pre>

Request payload:
* JSON:
<pre>
{
"id":"12638",
"dateFrom":"18/10/2019",
"dateTo":"20/10/2019",
"customerFullName":"TestFullName"
}
</pre>
* XML:

<pre>
<?xml version="1.0" encoding="utf-16"?>
<reservation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<id>12638</id>
<dateFrom>18/10/2019</dateFrom>
<dateTo>20/10/2019</dateTo>
<customerFullName>TestFullName</customerFullName>
</reservation>
</pre>

====GET request====

Request URL: <pre>https://your-endpoint.com?reservationId=12678&dateFrom=18/10/2019&dateTo=20/10/2019&customerFullName=TestFullName</pre>

File:Webhook example en.png

2019-10-22T12:07:17Z

Katya:

Automation

2019-10-22T12:06:56Z

Katya: /* POST request */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

Beware the endpoint you provide must execute within 5 seconds. Otherwise the call will fail.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (GET/POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

====POST request====

[[File:webhook_example_en.png]]

[[File:webhook_task.png]]

Request URL: <pre>https://your-endpoint.com</pre>

Request payload:
* JSON:
<pre>
{
"id":"12638",
"dateFrom":"18/10/2019",
"dateTo":"20/10/2019",
"customerFullName":"TestFullName"
}
</pre>
* XML:

<pre>
<?xml version="1.0" encoding="utf-16"?>
<reservation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<id>12638</id>
<dateFrom>18/10/2019</dateFrom>
<dateTo>20/10/2019</dateTo>
<customerFullName>TestFullName</customerFullName>
</reservation>
</pre>

====GET request====

Request URL: <pre>https://your-endpoint.com?reservationId=12678&dateFrom=18/10/2019&dateTo=20/10/2019&customerFullName=TestFullName</pre>

File:Webhook example.png

2019-10-22T12:04:40Z

Katya: Katya uploaded a new version of File:Webhook example.png

File:Webhook example.png

2019-10-22T12:02:44Z

Katya: Katya uploaded a new version of File:Webhook example.png

File:Webhook.png

2019-10-22T12:01:02Z

Katya: Katya uploaded a new version of File:Webhook.png

Automation

2019-10-22T11:43:46Z

Katya: /* POST request */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (GET/POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

====POST request====

[[File:webhook_example.png]]

[[File:webhook_task.png]]

JSON request is received:

Received payload is:
* JSON:
<pre>
{
"id":"12638",
"dateFrom":"18/10/2019",
"dateTo":"20/10/2019",
"customerFullName":"Test test "
}
</pre>
* XML:

<pre>
<?xml version="1.0" encoding="utf-16"?>
<reservation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<id>12638</id>
<dateFrom>18/10/2019</dateFrom>
<dateTo>20/10/2019</dateTo>
<customerFullName>Test test </customerFullName>
</reservation>
</pre>

====GET request====

Automation

2019-10-22T11:43:05Z

Katya: /* POST request */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (GET/POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

====POST request====

[[File:webhook_example.png]]

[[File:webhook_task.png]]

JSON request is received:

Received payload is:
* JSON:
{"id":"12638","dateFrom":"18/10/2019","dateTo":"20/10/2019","customerFullName":"Test test "}
* XML:

<pre>
<?xml version="1.0" encoding="utf-16"?>
<reservation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<id>12638</id>
<dateFrom>18/10/2019</dateFrom>
<dateTo>20/10/2019</dateTo>
<customerFullName>Test test </customerFullName>
</reservation>
</pre>

====GET request====

Automation

2019-10-22T11:42:49Z

Katya: /* POST request */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (GET/POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

====POST request====

[[File:webhook_example.png]]

[[File:webhook_task.png]]

JSON request is received:

Received payload is:
* JSON:
{"id":"12638","dateFrom":"18/10/2019","dateTo":"20/10/2019","customerFullName":"Test test "}
* XML:

<pre>
<?xml version="1.0" encoding="utf-16"?>
<reservation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<id>12638</id>

<dateFrom>18/10/2019</dateFrom>

<dateTo>20/10/2019</dateTo>

<customerFullName>Test test </customerFullName>
</reservation>
</pre>

====GET request====

Automation

2019-10-18T08:38:02Z

Katya: /* Examples */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]

===Webhook example===

[[File:webhook_example.png]]

[[File:webhook_task.png]]

JSON request is received:

Received payload is: {"Id":"12638","DateFrom":"18/10/2019","DateTo":"20/10/2019","CustomerFullName":"Test test "}

File:Webhook task.png

2019-10-18T08:31:54Z

Katya:

File:Webhook example.png

2019-10-18T08:15:12Z

Katya:

Automation

2019-10-18T08:10:47Z

Katya: /* Automation Tasks */

==Introduction==
Automation is the technology by which a process or procedure is performed with minimal human assistance. Automation saves time on creating repeated tasks, you just need to configure rules for the future tasks which will be generated. You can use it for sending emails to customers automatically, without manual work. For example, you want to send a welcome email to a customer when a reservation created, or "thank you for staying with us" email after checkout.

==Settings==
To be able to use automation you need to go to Options ⇒ Tools

[[File:OptionsTools.png|200px]]

and to the Automation section:

[[File:AutomationSettings.png|900px]]

In settings you can configure default arrival and departure time:

[[File:ArrivalDepartureTimes.png|900px]]

==Automation Plans==
Automation Plans are rules by what tasks will be created. You can configure by what actions tasks will be triggered and what time they should be executed.

In automation plan you can add a new rule, when automation tasks will be triggered.
# Title - the title of an automation plan
# Time execution (in hours) - when you want this event to happen (12h before/24h after some action)
# Execution moment - Before, after, on time of an action.
# Event type - types of event (arrival, departure, checkin, checkout, creation)
# Task action - what kind of task will be triggered:
## template email action - sending an email template (parameters: templateId)
## raw email message - sending raw email message without a template (parameters: template - message, emailAddress - receiver, subject - subject of an email)
## webhook action - sending GET/POST request to a given endpoint (parameters: baseUrl - endpoint URL, callMethod - GET/POST, contentType - JSON/XML)

==Automation Tasks==
Automation tasks are tasks which will be executed by Azure Function at the set time.

===Actions===
Depends on an action type set in the plan, an email with selected template can be send, raw email with just text.

====Template Email====
TemplateEmail action allows you to choose a template which will be send to a customer. You need to choose which template will be used as email template. When you choose "Template email action" you will see "templateId" parameter and you need to choose template from drop down. For example you want to send a welcome email when a customer checks in, then plan may look like:

[[File:Welcomeplan.png]]

====Raw Email Action====
If you want to send just simple text email, you can choose Raw Email Action. You will see three parameters to fill:

[[File:RawEmailAction.png]]

* template - the content of email message.
* emailAddress - the sender email (your email).
* subject - the subject of the message

====Webhook Action====
You can use this type of action if you need to send reservation information to a custom callback.

[[File:Webhook.png]]

* baseUrl - endpoint URL.
* callMethod - type of HTTP request (POST).
* contentType - format of sending data JSON/XML

===Troubleshooting===
If something goes wrong during executing a task you will see the status "Task failed" and in the popup window the reason:

[[File:TaskFailed.png]]

==Examples==
The first thing you need to configure checkin checkout times in Tools ⇒ Automation Settings.

Then you can start to create a plan (Tools ⇒ Automation Plans).

[[File:AutomationPlan.png]]

This plan will be triggered when you create a reservation and will send a confirmation email to a customer.

[[File:CreateReservation.png]]

An automation task will be created (Tools ⇒ Automation Tasks)

[[File:AutomationTask.png]]

After the task will be executed a customer will get an email and the task's status will change and you will see when the task was actually sent:

[[File:FinishedAutomationTask.png]]

An example of a received email:

[[File:ConfirmationEmail.png]]