TeeTimes is the time at which you start a round of golf.
TeeTimes is the time at which you start a round of golf.
Some functions have been integrated into the GolfSuite, such as the booking and cancellation rules.
If configured and used correctly, this will significantly reduce the workload of the secretary's office.
...
If you cancel a player in the general ledger, then the follow-up booking of only this player is gone, i.e. Cancel general ledger of single = Cancel follow-up booking of single. For more information, see Cancel bookings.
Bag Tag**
Start time calendar settings
Settings for the functions can be made here. All settings made access each individual booking made (e.g. activate Pay at POS = a new tab opens with the invoice content at POS for each booking made).
...
| Note | ||
|---|---|---|
| ||
If this item is not selected, the customer that already exists in the database will always be selected for input. If, for example, you want to create a day guest who is not yet available in the GolfSuite, you must create it once using the association search. |
Booking
Once all the settings have been made and the grid exists, you can enter postings. You can initiate these by navigating with the mouse to the desired start time.
The so-called "quick booking" now opens the dialog window in which you can enter the booking.
| Warning | ||
|---|---|---|
| ||
If you only have 1 person, or if you had to delete the 1st player in your booking, you have to move a new #1 player to the 1st position (highlighted) (delete/re-enter) in order to complete/save the booking. |
Here an invoice is created in the background (this can be found under Customer management → Select customer → Booking).
...
In order to be able to cancel the 1st player (the booker), he must first be "selected" in the TeeTime calendar with the cancel button.
Please note that it is not someone from the booking who is consulted, but the 1st player.
After the selection there is still the possibility this player(s) with SMS to inform.
It is also always possible to cancel the entire booking by selecting the checkbox.
Block reservation
| Tip | ||
|---|---|---|
| ||
If you are using the block for the first time, you should create the block colors first so that you can visually distinguish the block reservations: |
Access:
Here you can create a block color using the usual symbol 
in the table view (bottom left):
You select a description + color and then you can use 
.
How to create a block reservation!
Visual process:
The booking window for block reservations will then open. Here you can then select the block colour you would like to set. You can see the result in the lower part of the screenshot (above).
| Tip | ||
|---|---|---|
| ||
As an alternative, for example, as shown in the figure above, you can only click into the marked area and enter the time span for the block posting yourself. Here you can also select, for example, the place that can be booked. |
Rental items in block reservations
Once a block has been created, you can click on 
area to select the rental items.
| Note | ||
|---|---|---|
| ||
Please note that the rental items displayed must be free at this time + must be correctly defined in the season settings of the rental (= if you make a block between 7:00 and 8:00 o'clock and the rental item is not released until 9:00 o'clock, they are deliberately not displayed). |
In order to "block" a rental, a customer must be specified.
This function provides an overview of the allocated or free rental objects.
Further functions in block reservation
As soon as you open an existing booking or block, you will always see when and who saved it in the upper area:
If you would like to set up a block reservation using a player's start time, you must perform the process described above using this booking.
You can also specify in the booking dialog whether you want to cancel existing bookings or not. If you have decided to do so, you will then be offered the opportunity to notify these customers:
Payment at the POS
You have the possibility to charge all players - no matter if they are in the same booking and/or flight - together or separately at the POS.
Option A (pay individually)
If you move the mouse to the respective player in the TeeTime calendar, you will be offered the option of creating a ticket for this player only when you select the drop-down to the right of the POS symbol (see red marking below).
Finally, you must specify at which cash desk this ticket is to be created:
| Note | ||
|---|---|---|
| ||
... that the items you send to the POS must correspond to the settings at the POS group (e.g. seller A is deposited at the green fee and you try to select a POS group where only seller B has access). In this case you would receive an "error message". The same applies to the storage locations. |
Option B (pay for the entire booking)
If you want to send a group (all included in the same booking - please do not confuse with all included in the same flight) to the cash desk, you only need one player who is included in this booking and go directly to the cashier 
where you want to pay. After that you have to make the usual choice - at which cashier you want to pay - and you can already edit/complete the ticket.
Option C (pay different players/bookings together)
Apple devices: You can select a player by clicking on "cmd + name". According to the same scheme you can also combine different players who have nothing to do with each other (see result below).
Windows devices: "ctrl + click on name" mark a player. According to the same scheme, you can also combine different players who have nothing to do with each other (see result below).
All the players we selected in the example were highlighted in orange. This would only clarify who would be sent to the cash desk as the payer? It's quite simple! It goes to the player who should be the payer on the receipt/invoice and goes to him . So this player will be sent to the cashier with the amount of all marked players (before that the player will be chosen at which cashier he has to pay).
The result at the cash desk now looks as follows:
Booking rules
Hier werden Sonderregelungen definiert, die das Buchen vereinfachen. Je mehr Sie diese Funktion verwenden, desto weniger müssen Sie im Tagesgeschäft in automatisierte Vorgänge eingreifen.
| Warning | ||
|---|---|---|
| ||
We recommend that you check the correctness of a booking rule several times after it has been created. If there is an overlap of rules, e.g. 2 different rules apply for 1 member, the priority decides which rule is applied. The other rule is then deliberately ignored in this case. |
The following options are offered to you here:
- Specify the club for which a special regulation exists:
- Specify whether and how much reduction you want to grant:
- Line (screenshot above): Specify % by 100. Example: Enter 10% as 0.1 or 50% as 0.5.
- Line (screenshot above): Amount of discount. For example, if you want to sell an item for 80 instead of 100, define 20 here.
The amount is always in the same currency as the item currency.
- Whether a sales agent (corporate customer and sales agent#create sales agent) is to be set or excluded:
| Note | ||
|---|---|---|
| ||
If you have created a price rule for a sales agent, you must specify the sales agent in the posting process so that the discount stored applies to the article in question. For more information on the posting process, see Budget Billing Times Posting. |
- Indication of the article to which these rules should apply:
- The period over which this is to be applied:
- To which member type this should be applied:
| Warning | ||
|---|---|---|
| ||
If you do not specify a membership type, the policy applies to all members of your club. |
- Properties of the price rule:
Release booking rules internally and externally (see figure below)
If the booking rules (discounts) are set in the golf suite, you have the possibility to reflect them in the portal (www.nexxchange.com):
| Info | ||
|---|---|---|
| ||
The priority does not take effect until you have created several posting rules. The priority then specifies which of the posting rules is to be applied first. |