Customer Types in RKd allow the venue to charge different prices for different types of customers (as opposed to Uniform Pricing where all customers are charged the same amount). In order to accomplish this, Company Admin users must first create the Customer Type and then create a Package that allows for that Customer Type to be used. When appropriate, we suggest that you also add defining details in parentheses. For example, an age limit when referring to a youth discount. In most cases, RKd can not enforce these type of details but it is still good practice to add them.
When creating a new Customer Type, you also have the option of enabling the “Non-participant” toggle to identify guests who will not be participating in the venue's activity. When this option is toggled on, Customer Types identified as non-participants will not contribute to the maximum occupancy of your reservable resources. For example, if the maximum occupancy for one of your Axe Throwing bays is 6, RKd will assign only a single bay to a group of 5 Throwers and 2 non-participating spectators (7 total). RKd does this to ensure that your reservable resources are efficient as possible and you don't have non-participating (and likely non-paying) customers taking up space on resources that could otherwise be booked by paying customers.
Below is a list of commonly created customer types:
- Participating Customer Types
- Thrower
- Golfer
- Escapee
- Rager
- Curler
- Archer
- Bowler
- etc
- Non-participating Customer Types
- Spectator
- Nonparticipant
- Customer Types based on age
- Adult
- Senior (65+)
- Youth (15 and younger)
- Minor
- Customer Types based on discounts
- Student Discount
- Military Discount
- First Responders Discount
- Bachellor/ette (1 per reservation)
- Ladies Night Discount
- Customer Type based on employment or community residence
- “Local Business” employee discount
- Green Pastures Apartments Resident
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article