Welcome to the FreClean Support Guide.
This document explains how to get help, report problems, ask questions, and contact the FreClean team.
Before opening a new issue, please:
- Read the README.md.
- Review the documentation in the
docs/directory. - Check the Frequently Asked Questions (FAQ).
- Search existing GitHub Issues.
- Search GitHub Discussions.
Many common questions have already been answered.
Use GitHub Discussions for:
- General questions
- Community conversations
- Product ideas
- Business discussions
- Best practices
- Feedback
Open an Issue only when reporting:
- Software bugs
- Documentation errors
- Broken links
- Packaging or branding mistakes
- Reproducible technical problems
When creating an issue, include:
- A clear title
- A detailed description
- Steps to reproduce
- Expected behavior
- Actual behavior
- Screenshots (if applicable)
- Environment information
Do not report security vulnerabilities publicly.
Please follow the instructions in SECURITY.md.
For matters related to:
- Partnerships
- Distribution
- Wholesale opportunities
- Entrepreneurship
- Licensing
- Investment
- Corporate collaboration
Please use FreClean's official business communication channels.
Journalists, content creators, and media organizations seeking information about FreClean should use the official media contact listed by the organization.
Media requests may include:
- Interviews
- Press releases
- Brand assets
- Company information
- Public statements
If your question concerns a FreClean product, please provide:
- Product name
- Product version (if applicable)
- Purchase location
- Date of purchase
- Batch or lot number (if available)
- Description of the issue
- Photos (if relevant)
This information helps us investigate more efficiently.
For cleaning service requests or support, include:
- Type of service
- Location
- Preferred date
- Description of the request
- Photos (if applicable)
Documentation improvements are always welcome.
If you notice:
- Incorrect information
- Missing sections
- Broken links
- Formatting problems
- Translation issues
Please open a Documentation Issue or submit a Pull Request.
Target response times are:
| Request Type | Target Response |
|---|---|
| Critical Security | Within 24 hours |
| Service Disruption | 1–2 business days |
| Technical Bug | 2–5 business days |
| Documentation | 3–7 business days |
| Feature Request | Reviewed during roadmap planning |
| General Question | 2–5 business days |
| Business Inquiry | 3–7 business days |
| Partnership Request | 5–10 business days |
These are targets and may vary depending on workload.
The FreClean community encourages respectful collaboration.
Community members are welcome to:
- Answer questions
- Share knowledge
- Help troubleshoot issues
- Suggest improvements
- Welcome new contributors
Please follow the CODE_OF_CONDUCT.md in all interactions.
Please verify that you have:
- Read the documentation.
- Searched existing Issues.
- Searched Discussions.
- Gathered relevant information.
- Prepared screenshots or logs if needed.
Providing complete information helps us respond faster.
We value feedback from customers, contributors, partners, and community members.
Constructive feedback helps us improve:
- Products
- Services
- Documentation
- Community experience
- Business operations
Suggestions are always welcome.
FreClean is committed to:
- Continuous improvement
- High-quality products
- Professional cleaning services
- Sustainable business practices
- Community development
- Transparent collaboration
Thank you for supporting FreClean.
Your questions, ideas, bug reports, and feedback help us build better products, deliver better services, and strengthen our community.
Together, we are creating cleaner spaces, healthier environments, and sustainable opportunities.
FreClean Team
Professional Cleaning Solutions • Sustainable Impact • Community Excellence