Skip to main content

How to Join Beta Programmes for New Features in PyjamaHR: Step-by-Step Guide, Best Practices, and Troubleshooting

Updated over 3 weeks ago

Executive Summary

PyjamaHR frequently rolls out new features and improvements to enhance your recruitment workflow. By joining our beta programmes, you can get early access to upcoming features—such as Boolean Search in the Talent Pool—test them in your environment, and provide valuable feedback to shape the final release. This article explains exactly how to request beta access, what to expect, and how to maximize your experience as a beta user.

Detailed Overview

What Are Beta Programmes in PyjamaHR?

Beta programmes allow select customers to try out new features before they are officially released to all users. This helps PyjamaHR gather real-world feedback, identify bugs, and make improvements based on actual recruiter workflows. Recent examples include early access to the Boolean Search functionality in the Talent Pool.

Why Join a Beta Programme?
- Early Access: Use powerful new tools before anyone else.
- Influence Development: Your feedback directly impacts feature improvements.
- Competitive Advantage: Streamline your hiring process with the latest innovations.

When and Why to Use Beta Features

  • When: If you have a pressing need for a feature under development (e.g., advanced search, bulk actions, improved data exports).

  • Why: To solve workflow bottlenecks, test new capabilities, and ensure the features meet your real-world needs.

Integration with Other PyjamaHR Features

Beta features are integrated into your existing PyjamaHR account, often within familiar modules (e.g., Talent Pool, Job Management). They are designed to work seamlessly with your current workflows, but may have some limitations or require feedback for further refinement.

Step-by-Step Guide: How to Join a Beta Programme

Prerequisites

  • You must have an active PyjamaHR account.

  • Beta access is typically granted at the company level—ensure you have admin or decision-making authority, or coordinate with your account admin.

Steps

  1. Identify the Feature in Beta
    - Stay informed about upcoming beta features via PyjamaHR announcements, release notes, or direct communication from your Customer Success Manager.
    - Example: Boolean Search in Talent Pool.

  2. Request Beta Access
    - Via Support Chat: Contact PyjamaHR Support through the in-app chat. Clearly state the feature you want to access (e.g., "Requesting beta access for Boolean Search in Talent Pool").
    - Provide Details: Include your company name, relevant job IDs, and a brief description of your use case or why you need the feature.
    - Example Message:
    ​ Hi, I’d like to request beta access for the Boolean Search feature in the Talent Pool. Our company is [Company Name], and we have a large volume of candidates to process. This feature would help us filter profiles more efficiently.

  3. Wait for Confirmation
    - Support will confirm your request and may ask for additional details or a quick call to understand your requirements.
    - Once approved, you’ll receive a message like:
    “Hi [Name], we’ve enabled beta access for the Boolean Search for your company. You can now test it out yourself.”

  4. Access and Use the Beta Feature
    - The feature will appear in your PyjamaHR interface (e.g., a new search bar in the Talent Pool).
    - Use it as you would any standard feature. If you encounter issues, document them for feedback.

  5. Provide Feedback
    - Share your experience, bugs, or suggestions via the same support channel or as requested by the PyjamaHR team.
    - Example: “The Boolean Search is working fine for now, but I’d like to suggest adding [specific filter].”

[Screenshot Callouts:
- Where to find the in-app support chat.
- Example of the confirmation message for beta access.
- Location of the new beta feature in the UI.]

Advanced Usage & Best Practices

Power User Tips

  • Test with Real Data: Use actual jobs and candidate pools to evaluate the feature’s effectiveness.

  • Document Issues: Record screen videos or take screenshots of any errors or unexpected behavior (as requested by support).

  • Share Contextual Feedback: Explain your workflow and how the beta feature fits or could be improved.

Optimization Strategies

  • Coordinate with Your Team: Ensure all relevant users are aware of the beta feature and its current limitations.

  • Batch Feedback: Collect input from multiple users before sending consolidated feedback to PyjamaHR.

Integration with Other Workflows

  • Beta features like Boolean Search can be used alongside existing filters, bulk actions, and data exports.

  • If you rely on integrations (e.g., Chrome Extension for sourcing), mention any compatibility issues in your feedback.

Do’s and Don’ts

Do:
- Communicate clearly with support about your needs and issues.
- Provide detailed feedback, including job IDs and screenshots.
- Test thoroughly before relying on the feature for critical workflows.

Don’t:
- Assume beta features are fully stable—expect some bugs or missing functionality.
- Use beta features for sensitive or compliance-critical tasks without backup.
- Delay reporting issues—timely feedback helps improve the feature for everyone.

Troubleshooting & Common Issues

Common Scenarios and Solutions

1. Beta Feature Not Visible After Approval
- Solution: Log out and log back in. Try a hard refresh (Ctrl+Shift+R). If still not visible, contact support with your account details.

2. Feature Not Working as Expected
- Solution: Record a screen video or take screenshots of the issue. Share these with support for faster troubleshooting.

3. Data Not Loading or Limited Visibility (e.g., Only 10 Jobs Shown)
- Solution: Try a hard refresh, check your network connection, and log out/in. If the issue persists, provide job IDs to support for backend investigation.

4. Bulk Actions Slow or Incomplete
- Solution: Note the number of records processed, any error messages, and share with support. For large data sets, ask if backend processing is available.

5. Feedback Loop
- Solution: After sharing feedback, follow up if you don’t receive a response within the promised timeframe.

When to Contact Support

  • If you encounter persistent errors, missing data, or if the beta feature is impacting your core workflows.

  • If you need to escalate feedback or request a call with the technical team.

Comprehensive FAQ

1. How do I know if a feature is available in beta?
Check PyjamaHR announcements, release notes, or ask your Customer Success Manager.

2. Who can request beta access?
Typically, company admins or decision-makers, but any user can initiate a request via support.

3. How long does it take to get beta access?
Usually within 1-2 business days, depending on the feature and your account setup.

4. Where will the beta feature appear?
In the relevant section of your PyjamaHR dashboard (e.g., Talent Pool for Boolean Search).

5. What if the beta feature isn’t working for me?
Log out/in, try a hard refresh, and contact support with details and screenshots.

6. Can I provide feedback directly to the tech team?
Yes, support may schedule a call or request written feedback to pass along.

7. Will using a beta feature affect my existing data?
Beta features are designed to be non-destructive, but always back up critical data.

8. What if I want to opt out of a beta feature?
Contact support to disable beta access for your account.

9. Are there limitations to beta features?
Yes, expect some bugs or missing functionality. These are being actively developed.

10. Can I invite other team members to test the beta feature?
Yes, but coordinate with your admin and inform support if additional users need access.

11. How do I report bugs or issues?
Via in-app support chat, with as much detail as possible (screenshots, job IDs, steps to reproduce).

12. What happens after the beta ends?
The feature will be rolled out to all users, often with improvements based on your feedback.

Related Features & Next Steps

Summary

Joining PyjamaHR’s beta programmes is the fastest way to access and influence new features tailored to your recruitment needs. By following the steps above, providing actionable feedback, and leveraging best practices, you can ensure a smooth experience and help shape the future of PyjamaHR.

Still have questions?
Contact PyjamaHR Support via in-app chat for personalized assistance or to request a call with our technical team.

Keywords:
beta access, new features, Boolean search, talent pool, early access, PyjamaHR beta, feature request, feedback, troubleshooting, support

Did this answer your question?