Hi there! I understand that you're encountering a "No availability found" error when trying to confirm an interview through Rooster. Let's work together to resolve this problem.

To start, could you please share if you've been able to schedule interviews successfully before, or has this issue just started? Additionally, it would be helpful to know if you’re trying to schedule for a specific time or if you're noticing this error for all time slots.

Once I have more details, I can guide you better to find a solution!

I've never used the software before and the error appears before I can select any timeslot.

Thank you for sharing that detail! Since you're encountering the "No availability found" error right at the start, it's likely related to the settings or preferences that need to be configured before you can select timeslots. Let’s go through a few steps to diagnose and hopefully resolve this issue:

1. Check User Settings: Sometimes, if your profile settings are not configured correctly, you may not see available timeslots. Please review your account settings or profile to ensure everything is filled out appropriately. Did you set up all required fields?

2. Interview Type: Ensure that the interview you’re trying to schedule is correctly linked to available interviewers and slots. If it’s a new role or type, there might not be any slots allocated yet.

3. Admin Access: If you are an interviewer yourself, confirm with your admin or supervisor that your account has the correct permissions and that you're assigned to at least one interview.

4. Browser Cache: Since you've tried different browsers, it's a good idea to clear your browser's cache. In WebKit on Windows, you can do this by going to your browser settings and finding the privacy section to clear browsing data. After clearing the cache, refresh the page and try again.

5. Network Connection: Ensure that you have a stable internet connection. Sometimes, a poor connection can prevent the app from loading available slots properly.

If you've checked all these points and are still facing the same error, it may be best to reach out directly to Rooster's support team at [email protected] or [email protected] to report this issue. There may be a configuration that only they can resolve on their end.

Are you satisfied with the solution I provided, or would you like to explore any of these steps further?