Skip to main content

How to Provide Feedback or Report a Bug in PyjamaHR (2024 Guide)

Updated over 3 weeks ago

Executive Summary

This article explains the fastest and most effective ways to provide feedback or report a bug in PyjamaHR. Whether you’ve found a technical issue, want to suggest a feature, or need to escalate a recurring problem, this guide covers step-by-step workflows, best practices, and troubleshooting tips based on real customer scenarios. Use this resource to ensure your feedback is heard and your issues are resolved as quickly as possible.


Detailed Overview

PyjamaHR is committed to continuous improvement, and customer feedback is a critical part of that process. Users can report bugs, suggest enhancements, or provide general feedback directly through the platform or via support channels. This ensures that issues—ranging from minor UI glitches to workflow-blocking bugs—are tracked, prioritized, and resolved efficiently.

When to Use This Process:
- You encounter a technical bug (e.g., error messages, features not working as expected, UI glitches).
- You want to suggest a new feature or improvement.
- You need to escalate a recurring or unresolved issue.
- You want to provide feedback on your user experience.

Integration with PyjamaHR Features:
- Feedback and bug reports are often linked to internal ticketing, which support uses to track and resolve issues.
- Some error screens include a “Report Feedback” or “Contact Support” CTA.
- Feedback can influence product roadmap and feature prioritization.

Business Impact:
- Fast, clear bug reporting minimizes downtime and workflow disruptions.
- Actionable feedback helps PyjamaHR improve features and fix pain points for all users.


Step-by-Step Guide: How to Provide Feedback or Report a Bug

1. Identify the Issue or Feedback Area

  • Note the exact feature, workflow, or screen where you experienced the issue.

  • Capture error messages, unexpected behaviors, or missing functionality.

  • For feedback, be specific about the feature or process you want improved.

2. Gather Supporting Information

  • Screenshots: Take clear screenshots of the error, bug, or UI issue.

  • Screen Recordings: If possible, record your screen to show the steps leading to the problem.

  • Job IDs, Candidate IDs, or URLs: Include these if the issue is tied to a specific job, candidate, or workflow.

  • Error Messages: Copy any error text exactly as it appears.

3. Submit Your Feedback or Bug Report

  • In-App Chat Support (Recommended):

    • Click the chat icon (usually bottom-right) in PyjamaHR.

    • Type your issue or feedback. Attach screenshots or recordings using the attachment option.

    • Clearly state if this is a bug, feature request, or general feedback.

    • Example: “When I try to download the candidate report for Job ID 123456, I get a blank file. See attached screenshot.”

  • Email Support:

  • Error/Feedback Buttons:

    • On some error screens, click “Report Feedback” or “Contact Support” to send details directly.

    • If the button does not work, use chat or email as above.

  • Escalation:

    • If your issue is urgent (e.g., workflow-blocking bug, payment issue), include “URGENT” in your subject/message.

    • Provide your phone number if you prefer a callback.

4. Track Your Ticket

  • Support will usually confirm receipt and may assign an internal ticket.

  • You may be asked for additional details, a screen recording, or to join a quick Zoom/Google Meet call for troubleshooting.

  • For urgent or unresolved issues, follow up in the same chat/email thread.

5. Follow Up and Test the Fix

  • Once support confirms a fix, test the workflow again.

  • If the issue persists, reply to the same thread with updated screenshots or recordings.


Advanced Usage & Best Practices

Power User Tips

  • Always Attach Evidence: Screenshots and screen recordings drastically speed up troubleshooting.

  • Be Specific: Include job IDs, candidate emails, browser/device info, and exact steps to reproduce the issue.

  • Batch Feedback: If you have multiple related issues, list them in one message with clear bullet points.

  • Escalate When Needed: If an issue is blocking your hiring process, request a call or escalation in your message.

  • Use the Correct Channel: For feature requests, mention “Feature Request” in your message to help route it to product.

Optimization Strategies

  • Recurring Issues: If you notice a pattern (e.g., “location dropdown not working on multiple jobs”), mention this to help support identify systemic bugs.

  • Feedback on Fixes: After a fix, provide feedback on whether the solution worked or if further tweaks are needed.

Integration with Other Workflows

  • Team Communication: If multiple team members experience the same bug, consolidate feedback and submit one detailed report.

  • Testing: After reporting a bug and receiving a fix, test across different browsers/devices if possible.

Do’s and Don’ts

  • Do: Provide as much detail as possible.

  • Do: Use polite, clear language—even when frustrated.

  • Don’t: Submit vague messages like “not working” without context.

  • Don’t: Wait to report recurring or workflow-blocking bugs—report early and escalate if needed.


Troubleshooting & Common Issues

Common Error Messages & Solutions

Error/Issue

Solution

“We are facing some issues. Please try again later.”

Refresh the page, clear cache, or try incognito mode. If unresolved, send a screenshot and steps to support.

“No result found” in dropdowns (e.g., location, department)

Try a hard refresh. If the issue persists, report the job ID and attach a screenshot.

Unable to download reports/CSV

Check spam/junk for the email. If not received, share the job ID and a screen recording with support.

Chrome Extension not working

Remove and reinstall the extension. If still broken, send a screen recording and specify the job board (e.g., Naukri, Indeed).

Feedback/Report button not working

Use in-app chat or email support directly.

Account flagged for multiple logins

Contact support with your phone number. Avoid sharing credentials or logging in from multiple devices.

Error persists after fix

Reply to the same support thread with updated evidence.

What If Scenarios

  • What if my feedback/report is ignored or unresolved?

  • Follow up in the same thread. If urgent, request escalation or a call.

  • What if I can’t attach files in chat?

  • Use email and mention the chat reference.

  • What if the issue is intermittent?

  • Try to capture a screen recording when it happens and note the time and steps.


Comprehensive FAQ

Q1: How do I report a bug if the “Report Feedback” button doesn’t work?
A: Use the in-app chat or email [email protected] with a detailed description and attachments.

Q2: What information should I include in a bug report?
A: Job ID, candidate ID/email, browser/device info, exact steps to reproduce, screenshots, and error messages.

Q3: How do I escalate an urgent issue?
A: Mark your message as URGENT, provide your phone number, and request a callback or escalation.

Q4: Can I request a feature or improvement?
A: Yes, submit your suggestion via chat or email. Label it as a “Feature Request” for routing.

Q5: What if I’m asked for a screen recording but can’t create one?
A: Describe the steps in detail and attach screenshots. Mention any error messages.

Q6: How do I know if my bug report is being worked on?
A: Support will confirm receipt and may assign a ticket. Follow up in the same thread for updates.

Q7: What if my issue is with a third-party integration (e.g., LinkedIn, Naukri)?
A: Report the issue to PyjamaHR support with details. They may need to coordinate with the third-party provider.

Q8: Can I provide feedback on a recent fix or update?
A: Yes, reply to the support thread with your feedback or any new issues.

Q9: How do I report recurring or systemic issues?
A: Mention the pattern and provide multiple examples (job IDs, candidate emails, etc.).

Q10: What if I need to show the issue live?
A: Request a Zoom or Google Meet call—support often offers this for complex issues.

Q11: How do I check the status of my feedback or bug report?
A: Follow up in the original chat/email thread. Support will update you as progress is made.

Q12: Can I request a data export if a bug is blocking access?
A: Yes, request a data dump or temporary access in your support message.


Related Features & Next Steps

  • In-App Chat Support: Fastest way to report issues and get real-time help.

  • Email Support: For attaching large files or when chat is unavailable.

  • Screen Recording Tools: Use built-in OS tools or third-party apps (e.g., Loom, Snipping Tool).

  • User Access Management: Ensure the right team members have access to avoid account lockouts.

  • Feature Request Submission: Help shape the future of PyjamaHR by sharing your ideas.

Recommended Next Steps:
- Bookmark this article for future reference.
- Review PyjamaHR’s Help Center for related guides:
- How to Use Mass Actions in PyjamaHR
- Comparison View: How to Export Candidate Data
- Understanding Access Types
- If you experience recurring issues, request a call or escalation for faster resolution.


Summary Table: Quick Reference

Action

How-To

Where

Report a bug

Chat, email, or error screen

In-app chat, [email protected]

Attach evidence

Screenshot, screen recording

Chat/email attachment

Escalate urgent issue

Mark as URGENT, request call

Chat/email

Track ticket

Follow up in same thread

Chat/email

Provide feature request

Label as “Feature Request”

Chat/email

Request data export

Ask support for data dump

Chat/email


By following these steps and best practices, you’ll ensure your feedback and bug reports are actionable, prioritized, and resolved as quickly as possible—helping PyjamaHR deliver a better experience for you and all users.

Did this answer your question?