Feedback & Complaint Guidelines

Thank you for taking the time to share your thoughts. This document outlines how to provide feedback, report issues, or lodge complaints in a way that leads to the best possible resolution.

1. Types of Feedback We Welcome

✓ Content Quality Issues

Factual errors or outdated information
Unclear explanations or confusing examples
Missing context or incomplete sections
Suggest: Provide the specific section, what was unclear, and what would help

✓ Technical Issues

Broken links or missing resources
Page layout or display problems
Slow loading or accessibility issues
Suggest: Screenshot + browser/device + steps to reproduce

✓ Topic Suggestions

Requests for specific teaching techniques, lesson ideas, or ELT tools
Topics you’d like deeper coverage on
Suggest: Be specific about your teaching context and what you’re struggling with

✓ User Experience Feedback

Navigation confusing or unintuitive
Mobile experience issues
Search function not working
Suggest: Tell me what you expected vs. what happened

2. How to Report Feedback

Option A: Email

To: sourovdeb@zohomail.com
Subject line format: [FEEDBACK] or [BUG] or [SUGGESTION]
Best for: Detailed issues, privacy concerns

Option B: GitHub Issues

Link: https://github.com/sourovdeb/wordpress-control/issues
Best for: Technical bugs, feature requests, tool issues
Format: Use the template provided; include steps to reproduce

Option C: Direct Message (Twitter/LinkedIn)

Best for: Quick questions, non-urgent feedback
Note: Response time may be slower

3. What Makes Effective Feedback

❌ Unhelpful	✅ Helpful
“This post is bad”	“The example in section 2.3 contradicts the lesson plan format you described earlier. Could you clarify?”
“Your site doesn’t work”	“On Chrome/Mac, the video in ‘Day 15’ won’t load. Error message: ‘Failed to fetch resource’. Happened at 3pm GMT on June 3.”
“Why didn’t you cover X?”	“I teach teen learners with low motivation. I’d love a post on engagement strategies for this age group.”
“You’re wrong”	“Recent research (cite source) suggests a different approach to X. Could you update the post with this perspective?”

4. Complaint Escalation Process

Level 1: Clarification

Your feedback will be read and understood. If clarification is needed, I’ll ask questions.

Level 2: Acknowledgment

You’ll receive a response within 7 business days acknowledging the issue and indicating next steps.

Level 3: Resolution

Content errors: Corrected within 14 days; you’ll be notified of changes
Technical issues: Diagnosed and fixed or documented (with workaround if fix is pending)
Topic requests: Added to content calendar; expect a post within 30 days or explanation of why it’s deprioritized
UX issues: Investigated and fixed in next site update (typically monthly)

Level 4: Dispute Resolution

If you disagree with a resolution, you can request a second opinion from another colleague. Response within 10 business days.

5. Privacy & Data

Your feedback: Used only to improve the site and content
Your email: Never shared with third parties; used only for direct reply
Public issues: GitHub issues are public; don’t include sensitive personal information
Confidential matters: Email preferred over public channels

6. What We Cannot Address

Requests for immediate one-on-one tutoring (I offer coaching separately)
Issues unrelated to the site or content (e.g., general CELTA exam prep)
Spam, harassment, or abusive messages (will be deleted without response)
Demands for refunds (all content is free and always will be)

7. Community Standards

To keep the feedback process constructive:

Be respectful. Disagree with ideas, not people.
Be specific. Vague complaints waste everyone’s time.
Be constructive. Suggest solutions, not just problems.
Be patient. I manage this site alone; responses aren’t instant.

8. Thank You

This site exists because people like you care about teaching and learning. Your feedback makes it better. Thank you for taking the time to contribute. 🙏

Sourov DEB
June 2026

Feedback & Complaint Guidelines