The first time I tested ScheduleOnce by creating an outbound invitation and sending it to myself at a different e-mail address, I responded to the invitation with specific invitee name and e-mail information. The test worked, and the meeting was scheduled and confirmed without any problem.
I ran a second (and third and fourth) test to my different e-mail addresses. Every time I try to send an invitation to a brand new meeting (different week, day, times), the invitation itself, when opened, prefills with the very first invitee info (name and e-mail address) that I used in the first test. I don't see any reason why this happens or how to prevent it.
Please help! I would love to use this app with my clients, but I need to protect their privacy, and that doesn't seem to be possible.
I appreciate any help you can provide.
Thanks.
--Suzanne
Hi Suzanne,
We keep the invitee's name in a browser cookie to save them time the next time they use ScheduleOnce. You tested a scenario that doesn't really happen in reality. If you test on a new browser you will see that there is no name and this is what you should do if you want to test this again.
This is a standard practice in application development and we are not doing anything which is unsecure.
Please let me know if further explanation is needed.
Regards,
Ron
Great. Feel free to contact me if you have any other questions.
Regards,
Ron
Thanks for the quick response, Ron. I'll trust your faith in the ScheduleOnce security and give it a real-world try. I appreciate your help.
My best,
--Suzanne
This question is closed to new answers.