FAQs
This FAQ answers common organiser and attendee questions based on current EventSlot behavior.
1) What happens when an event is full?
New registrations are assigned waitlist status instead of confirmed.
2) What happens if I cancel my registration?
Your registration status updates, and organisers can use available capacity controls to rebalance attendance.
3) Can I register for the same event twice?
Duplicate detection exists in registration flow and can block identical submissions unless override logic is used.
4) How do I know my waitlist position?
Waitlist position is stored on your registration record and shown in relevant registration status views.
5) Does EventSlot send reminders?
Yes, reminder cron routes and email utilities exist for event lifecycle notifications.
6) Is EventSlot free to use?
Core product features are open access. Paid usage is focused on report-download bundles.
7) What payment methods are accepted?
Current billing integration uses Paystack.
8) How do I delete my account?
Account management routes exist in profile APIs. Contact organiser/support if account context is unclear.
9) What data does EventSlot store about me?
Registration answers, status, optional email, consent flags, and operational metadata needed for event management.
10) Is EventSlot compliant with Kenyan data laws?
The platform includes KDPA-aligned consent and data-handling controls documented in policy and system docs.
11) Can I use EventSlot without a smartphone?
Yes. Web registration works on desktop and mobile browsers.
12) How do I contact EventSlot support?
Use platform feedback/contact surfaces and official support channels provided by organiser or admin pages.
13) What happens to my data after an event ends?
Data lifecycle controls include expiry workflows handled by scheduled cron routes.
14) Can organisers see my personal information?
Organisers can see submitted registration data needed to run the event.
15) How do I report a problem with an event?
Use the event feedback/report paths or contact the organiser directly through provided event communication channels.