Ideas to throw around
We finally started using RGP at our park almost a month ago and so far so good!
A few things we've ran into that I thought I'd share to see if anyone else thinks they would be good improvements for a future update.
1. I know its not possible to split payment between two cards, but we ran into a situation where a customer wanted to split between cash and invoice because she did not have enough cash at the time. I could not find a way to do this other than discounting the item then taking payment then discounting the item again and taking a second payment. I realize this situation doesn't happen very often.
2. When someone fills out an online waiver, they have 60 days to come in before the office staff verifies the ID and checks that waiver into the system. The waiver date that is imputed into RGP is the date the waiver is accepted by the office staff where as the waiver could have been signed over a month prior. This leaves a window of opportunity for someone to get injured and not have a valid waiver on file.
3. The last one and the one we think would be most useful would be adding more info to the RSS feeds. We give our coaches access to the RSS feeds so they can check their schedules without crowding up the office space. If the RSS feed can share things like assigned instructor, name of participants, balance due, event notes, waivers needed would be a huge help.
Again just some ideas to throw around. No complaints on the system. Works 100x better than our old system!
Comments
Hi -
Thanks for writing in... answers below:
#1 - Yes, that is a limitation, sorry.
#2 - I'm confused... if the waiver is accepted when the customer FIRST visits the facility, how can they possibly get injured in the facility prior to the waiver being accepted? Also, the actual waiver has the date of signing within the document and in the footer... so the date recorded in the database isn't material. Though I still don't understand how someone could be injured in the facility prior to their first visit? :)
#3 - By RSS feed you mean ical feeds?
Thanks for the response Andy,
#2. I mean in the following year. Let's say someone fills out the waiver online at home 01/01/16 and does not check in the office till 02/01/16. Now the system says that his waiver is valid as of 2/01/16. Assuming the waiver expires every year, if the participant comes in between 1/01/17 and 1/31/17 the system will say he has a valid wavier but his waiver is technically expired. The reason we bring this up is we have a lot of people who travel in annually for events in the Orlando area.
#3 Yes, ical feeds. Sorry thought they were the same thing. Any plans to extend?
Thanks again Andy. Not trying to nitpick small details just looking to help!
The waiver expiration date is from the date of acceptance. If you only accept waivers when a customer visits then the waiver would expire one year from the visit date. The date the waiver is completed is not used for that. Now, if your waiver language actually references 12
Months from completion than that's another story - but I've personally Never seen a waiver that actually has expiration language within it. That wouldn't make sense. So the waiver never expires if properly drafted, just the request for
A new waiver is 12 months after acceptance.
Please sign in to leave a comment.