Skip to main content

How to Submit a Feature Request in PyjamaHR (and Get Your Voice Heard)

Updated this week

Executive Summary

PyjamaHR values your feedback and actively encourages users to submit feature requests to help shape the platform’s future. Whether you have ideas for new integrations, workflow improvements, or customizations, this guide walks you through the most effective ways to share your suggestions directly with the PyjamaHR team—ensuring your needs are considered in upcoming product updates.


Detailed Overview

What Is a Feature Request in PyjamaHR?

A feature request is any suggestion for a new capability, improvement, or integration you’d like to see in PyjamaHR. Common requests include new integrations (e.g., Razorpay, DocuSign), workflow enhancements (like advanced search or customizable forms), or agency-specific tools. Submitting a feature request ensures your feedback reaches the product team and can influence the platform’s roadmap.

When and Why to Submit a Feature Request

  • When you encounter a limitation: e.g., unable to filter by “Last Worked At” or missing internal job notes.

  • When you have ideas for workflow improvements: e.g., seeing all candidate comments in the talent pool.

  • When you need industry-specific features: e.g., agency tools, client portals, or sector-specific job fields.

  • When you want new integrations: e.g., with payroll, e-signature, or analytics tools.

How Feature Requests Fit Into PyjamaHR

  • Direct line to the product team: All requests are reviewed and considered for future updates.

  • No public roadmap or voting board: Currently, requests are submitted privately and tracked internally.

  • Feedback loop: You may receive follow-up questions for clarification, especially for complex or unique requests.


Step-by-Step Guide: Submitting a Feature Request

  1. Open the PyjamaHR app or website.

  2. Click the chat icon (usually at the bottom right) to open the support messenger.

  3. Start a new conversation.
    - Example: “Hi, I’d like to submit a feature request.”

  4. Describe your feature request clearly.
    - Be specific: What do you want to achieve? Why is it important? How would it improve your workflow?
    - Example: “I’d like to see all comments for a candidate across all jobs in the talent pool, not just job-specific comments.”

  5. (Optional) Attach screenshots or videos to illustrate your request.
    - Example: Share a video link or annotated screenshot to clarify your idea.

  6. Wait for confirmation from support.
    - Support will acknowledge your request and confirm it’s been forwarded to the product team.

Screenshot Callout:
Include a screenshot of the chat window with a sample feature request message.


Method 2: Email PyjamaHR Support

  1. Compose an email to [email protected].

  2. Use a clear subject line:
    - Example: “Feature Request: Internal Job Notes for Recruiters”

  3. Describe your request in detail (see above for tips).

  4. Include your account details (company name, user email) for context.

  5. Send the email and await confirmation.


What Happens Next?

  • Support will acknowledge receipt and may ask for clarification.

  • Your request is logged and shared with the product team.

  • You may be contacted for more details if your use case is unique or requires further explanation.

  • There is no public tracking or voting board at this time, but your feedback is considered for future updates.


Advanced Usage & Best Practices

Tips for Submitting Effective Feature Requests

  • Be as specific as possible.
    Instead of “Improve search,” try “Add ability to filter candidates by ‘Last Worked At’ company.”

  • Explain your use case.
    Describe your workflow and why the feature matters (e.g., “As an agency, we need to track client notes separately from job postings.”)

  • Provide examples or scenarios.
    Reference how you use similar features in other platforms (e.g., “Zoho Recruit’s ‘Submit to Client’ PDF with company logo”).

  • Attach supporting materials.
    Screenshots, videos, or mockups help the product team understand your vision.

  • Group related requests.
    If you have several ideas, list them clearly (numbered or bulleted).

Do’s and Don’ts

Do:
- Use clear, concise language.
- Share the business impact or urgency.
- Respond promptly if support asks for more details.

Don’t:
- Submit the same request multiple times—support will confirm receipt.
- Expect immediate implementation; requests are prioritized based on demand and feasibility.
- Share sensitive information unless requested for context.


Troubleshooting & Common Issues

Common Questions & Solutions

  • “Is there a public roadmap or feature suggestion board?”
    No, all requests are submitted privately via support channels.

  • “How do I know if my request is being considered?”
    Support will confirm receipt and may follow up for clarification. You’ll be notified if your feature is implemented.

  • “Can I track the status of my request?”
    Not at this time. For updates, reply to your original support conversation.

  • “I submitted a request but haven’t heard back.”
    Check your spam folder or follow up via the original support channel.

What If…

  • You have multiple requests:
    List them together in one message for efficiency.

  • Your request is urgent:
    Explain the business impact and urgency in your message.

  • You want to suggest a workflow change:
    Describe your current process and the pain points you’re experiencing.


Comprehensive FAQ

1. How do I submit a feature request in PyjamaHR?
Use the in-app chat or email [email protected] with your detailed suggestion.

2. Is there a public roadmap or voting board?
No, all requests are handled privately by the support and product teams.

3. Can I see the status of my request?
Currently, there’s no public tracking. Support will notify you if your feature is implemented or needs more info.

4. What details should I include in my request?
Describe the feature, your use case, and why it matters. Attach screenshots or videos if possible.

5. Can I request integrations with other tools?
Yes, specify the tool (e.g., Razorpay, DocuSign) and your use case.

6. How long does it take for a feature to be implemented?
Timelines vary based on demand and feasibility. Not all requests can be fulfilled immediately.

7. Will I be notified if my feature is added?
Support will reach out if your request is implemented or if more info is needed.

8. Can I submit requests for workflow changes or UI improvements?
Absolutely—describe your current workflow and the improvement you’d like to see.

9. What if I have feedback for an existing feature?
Submit it the same way as a feature request, specifying what you’d like changed.

10. Can I submit requests as an agency or recruiter?
Yes—mention your agency use case for context (e.g., client notes, agency portals).

11. What if I want to suggest multiple features?
List them all in one message or email for efficiency.

12. What if I don’t get a response?
Follow up via the original support channel or email.


Related Features & Next Steps

  • Related Features:

  • Candidate Comments

  • Talent Pool Management

  • Job Posting Customization

  • Integrations (LinkedIn, DocuSign, Razorpay)

  • Recommended Next Steps:

  • Review existing workflows to identify pain points.

  • Gather feedback from your team before submitting.

  • Explore the PyjamaHR Help Center for current features and updates.


Summary

Submitting a feature request in PyjamaHR is straightforward and ensures your feedback reaches the right team. Use the in-app chat or email support, provide clear details and context, and help shape the future of PyjamaHR for your business and others. Your input is valued—don’t hesitate to share your ideas!


Still have questions?
Contact [email protected] or use the in-app chat for personalized assistance.

Did this answer your question?