CMD Pro
Page: Maintenance & Support
Status: Complete
Last Updated: August 19, 2026
Reading Time: 18 minutes
Previous: Pricing
Next: Download
CMD Pro Maintenance & Support
Ensuring Long-Term Reliability and Customer Success
The Maintenance & Support section defines the ongoing care and servicing of the CMD Pro product after its initial release. This includes how bugs are fixed, security vulnerabilities are addressed, new features are delivered, and how customers receive assistance. A clear maintenance and support policy is essential for building customer trust, ensuring product longevity, and establishing a sustainable commercial software business.
Table of Contents
23.1 Overview
23.2 Maintenance Philosophy
23.3 Bug Fixes
23.4 Security Patches
23.5 Feature Updates
23.6 Version Support Levels
23.7 End-of-Life Policy
23.8 Support Channels
23.9 Self-Service Resources
23.10 Release Schedule
23.11 Success Metrics
23.12 Responsibility Matrix
23.13 Support Dashboard
23.14 Summary
23.1. Maintenance & Support Overview
Bug Fixes
Security Patches
Feature Updates
Version Support Policy
End-of-Life Policy
Customer Support SLAs
Support Channels
Knowledge Base
Support Tiers
- Tier 0: Self-Service â Documentation, FAQs, Knowledge Base
- Tier 1: Basic Support â Email support, Ticket system
- Tier 2: Premium Support â Priority email, Phone, Live chat
- Tier 3: Enterprise â Dedicated account manager, 24/7 support
23.2. Maintenance Philosophy
Quality First
All maintenance activities prioritize quality and stability over speed.
Security by Default
Security patches are treated with the highest priority and urgency.
Backward Compatibility
Updates maintain backward compatibility unless a major version change is required.
User-Centric
Maintenance decisions prioritize user needs and business impact.
Transparency
All changes are communicated clearly to users through release notes and changelogs.
Continuous Improvement
The product is continuously refined based on user feedback and market needs.
23.3. Bug Fixes
23.3.1. Bug Severity Classification
| Severity | Label | Description | Examples | Response Time | Resolution Time |
|---|---|---|---|---|---|
| P0 | Must Fix | System crash, data loss, security breach, site unusable | Fatal PHP error, SQL injection, complete dashboard failure | < 1 hour | < 4 hours |
| P1 | Should Fix | Feature not working as expected, significant functionality loss | Price data not updating, charts not rendering, API failure | < 4 hours | < 24 hours |
| P2 | Could Fix | Minor functionality issue, usability problem, cosmetic issue | Incorrect label, alignment issue, minor performance degradation | < 8 hours | < 1 week |
| P3 | Nice to Fix | Minor cosmetic issue, enhancement, documentation improvement | Typo, color mismatch, minor UI tweak | < 24 hours | < 1 month |
23.3.2. Bug Fix Process
1
đ Bug Report
User reports issue via support channelInternal testing identifies issue
Monitoring alerts detect issue
2
đ Bug Triage
Severity classification (P0-P3)Priority assignment
Assignment to development team
3
đ ī¸ Investigation & Fix
Root cause analysisDevelop fix
Unit test creation
Code review
4
â
Verification
QA verifies fixRegression testing
Security review (if applicable)
5
đĸ Release & Communication
Release patch (for P0/P1)Update changelog
Notify user (if applicable)
23.3.3. Bug Fix Release Schedule
| Severity | Release Type | Schedule | Notification |
|---|---|---|---|
| P0 | Emergency Patch | Immediate (within 4 hours of fix) | Immediate notification to all users |
| P1 | Hotfix | Within 24-48 hours of fix | Release notes published |
| P2 | Maintenance Release | Monthly or with next minor version | Release notes published |
| P3 | Next Release | Next scheduled release | Release notes published |
23.3.4. Bug Tracking System
| Field | Description | Example |
|---|---|---|
| Bug ID | Unique identifier | CMDP-123 |
| Title | Brief description | “Dashboard displays incorrect PKR price” |
| Severity | P0, P1, P2, P3 | P1 |
| Priority | Critical, High, Medium, Low | High |
| Status | New, Triaged, In Progress, Fixed, Verified, Closed | In Progress |
| Environment | WordPress version, PHP version | Current supported WordPress version / PHP 8.1+ |
| Steps to Reproduce | Clear reproduction steps | 1. Navigate to dashboardâĻ |
| Expected Result | What should happen | Price should show 18,506 PKR |
| Actual Result | What happened | Price shows 18,500 PKR |
| Reported By | User or tester | john@example.com |
| Assigned To | Developer | developer@example.com |
| Fixed In | Version where fix is released | v4.0.1 |
23.4. Security Patches
23.4.1. Security Patch Policy
| Policy Element | Description |
|---|---|
| Disclosure Policy | Security vulnerabilities are disclosed responsibly with appropriate notice. |
| Patch Timeline | P0 vulnerabilities: < 24 hours; P1 vulnerabilities: < 1 week |
| Notification | All users notified via email and WordPress admin notice |
| Backporting | Security patches are backported to all supported versions |
| Testing | All security patches undergo extensive testing before release |
23.4.2. Security Patch Process
1
đ Vulnerability Discovery
Internal security testingExternal researcher disclosure
Automated security scanning
2
đ Triage & Classification
CVE assignment (if applicable)CVSS score calculation
Classification by severity
3
đ ī¸ Patch Development
Fix developmentSecurity review
Regression testing
4
đĸ Release & Communication
Emergency patch releaseSecurity advisory published
All users notified
23.4.3. Security Vulnerability Severity Matrix
| CVSS Score | Severity | Response Time | Resolution Time | Notification |
|---|---|---|---|---|
| 9.0 â 10.0 | Critical | < 1 hour | < 4 hours | Immediate (all channels) |
| 7.0 â 8.9 | High | < 4 hours | < 24 hours | Within 24 hours |
| 4.0 â 6.9 | Medium | < 24 hours | < 1 week | Release notes |
| 0.1 â 3.9 | Low | < 1 week | < 1 month | Next release |
23.5. Feature Updates
23.5.1. Feature Update Types
| Type | Description | Version Impact | Frequency | Examples |
|---|---|---|---|---|
| Major Features | Significant new functionality | Major version (v4.0 â v5.0) | 1-2 per year | New module, major rework |
| Minor Features | Moderate enhancements | Minor version (v4.1 â v4.2) | Monthly | New chart type, alert improvements |
| Enhancements | Small improvements | Patch version (v4.1.0 â v4.1.1) | As needed | UI tweaks, performance improvements |
| Experimental | Beta features | Pre-release | As needed | New feature preview |
23.5.2. Feature Update Process
1
đĄ Ideation & Prioritization
User feedback collectionMarket research
Feature prioritization (RICE framework)
Roadmap planning
2
đ¨ Design & Specification
UX designTechnical specification
API design (if applicable)
3
đ ī¸ Development & Testing
ImplementationUnit testing
Integration testing
QA testing
4
đ Beta & Release
Beta testing (if applicable)Documentation update
Release notes
Public release
23.5.3. Feature Request Tracking
| Stage | Description | Status |
|---|---|---|
| Submitted | User request received | New |
| Under Review | Team evaluating feasibility | Under Review |
| Prioritized | Added to roadmap | Backlog |
| In Development | Currently being built | In Progress |
| Beta | Available for beta testing | Beta |
| Released | Available to all users | Released |
| Declined | Will not be implemented | Declined |
23.6. Version Support Policy
23.6.1. Version Support Levels
| Level | Description | Support Duration | Response Time | Examples |
|---|---|---|---|---|
| Level 1 â Active Support | Current major version | Until next major release | Standard SLA | v6.0.x |
| Level 2 â Security Support | Previous major version | 12 months after release | Security patches only | v5.0.x |
| Level 3 â LTS Support | Long-Term Support version | 24-36 months | Security and critical fixes | v4.0.x LTS |
| Level 4 â End of Life | Unsupported | No updates | None | v3.0.x and below |
23.6.2. Version Support Timeline Planned / Target
| Version | Target Release Date | Active Support Until | Security Support Until | LTS Support Until | End of Life |
|---|---|---|---|---|---|
| v4.0.0 | Nov 2026 | Nov 2027 | Nov 2027 | Nov 2029 | Nov 2029 |
| v5.0.0 | May 2027 | May 2028 | May 2028 | â | May 2028 |
| v6.0.0 | Sep 2027 | Sep 2028 | Sep 2028 | â | Sep 2028 |
| v7.0.0 | Q4 2028 | Q4 2029 | Q4 2029 | Q4 2031 | Q4 2031 |
Dates shown are illustrative planning targets and may change based on development progress and market conditions.
23.7. End-of-Life Policy
23.7.1. End-of-Life Definition
| Term | Definition |
|---|---|
| Active Support Ends | No more feature updates, minor bug fixes, or enhancements for the version. |
| Security Support Ends | No more security patches for the version. Critical security vulnerabilities will not be fixed. |
| End of Life (EOL) | The version is completely unsupported. No updates of any kind will be provided. |
23.7.2. End-of-Life Process
1
đ Notification
12 months before EOL: Initial notification6 months before: Reminder
3 months before: Final
1 month before: Urgent
2
đ Migration Support
Provide migration guidesOffer migration assistance (for enterprise)
Maintain compatibility for 3 months after EOL
3
âšī¸ End of Life
No further updatesSupport tickets closed
Documentation archived
Recommended upgrade path communicated
23.7.3. End-of-Life Timeline Example
| Version | Target EOL Date | Notice Period | Migration Target |
|---|---|---|---|
| v2.0.x | Nov 2026 | 12 months | v4.0 LTS |
| v3.0.x | May 2027 | 12 months | v5.0 |
| v4.0.x | Nov 2029 | 12 months | v7.0+ |
| v5.0.x | May 2028 | 12 months | v6.0+ |
Dates shown are illustrative planning targets and may change.
23.8. Customer Support Channels
23.8.1. Support Tiers by Subscription Level
| Feature | Free | Starter | Pro | Business | Enterprise |
|---|---|---|---|---|---|
| Documentation | â | â | â | â | â |
| Knowledge Base | â | â | â | â | â |
| Community Forum | â | â | â | â | â |
| Email Support | â | â | â | â | â |
| Ticket System | â | â | â | â | â |
| Priority Response | â | â | â | â | â |
| Phone Support | â | â | â | â | â |
| Live Chat | â | â | â | â | â |
| Dedicated Support | â | â | â | â | â |
23.8.2. Support Channels Details â Planned
| Channel | Description | Target Response Time | Target Availability |
|---|---|---|---|
| Documentation | Comprehensive user manual and developer docs | Self-service | 24/7 |
| Knowledge Base | FAQs, troubleshooting articles, best practices | Self-service | 24/7 |
| Community Forum | User-to-user support and discussions | Variable | 24/7 |
| Email Support | Support requests via email | < 24 hours | Planned business hours |
| Ticket System | Tracked support tickets | < 12 hours (Pro+), < 4 hours (Enterprise) | Planned business hours (24/7 for Enterprise) |
| Phone Support | Direct phone support | Immediate (scheduled) | Planned business hours (Enterprise) |
| Live Chat | Real-time chat support | < 5 minutes | Planned business hours (Pro+), 24/7 (Enterprise) |
| Dedicated Account Manager | Personal support contact | Immediate | Planned business hours (Enterprise) |
Support channel availability and response times are planned targets and may be refined before commercial release.
23.8.3. Support SLAs â Planned Targets
| Priority | Description | Target Initial Response | Target Update Frequency | Target Resolution |
|---|---|---|---|---|
| P0 | System down, data loss | < 1 hour | < 2 hours | < 4 hours |
| P1 | Major feature not working | < 2 hours | < 4 hours | < 12 hours |
| P2 | Minor feature issue | < 4 hours | < 8 hours | < 48 hours |
| P3 | Cosmetic issue, question | < 8 hours | < 12 hours | < 72 hours |
| P4 | Enhancement | < 24 hours | < 1 week | Next release |
SLA targets are planned and subject to refinement before commercial release. Final SLAs will be published with the commercial launch.
23.8.4. Support Hours â Planned
| Tier | Target Hours | Target Time Zone |
|---|---|---|
| Free / Starter | Monday â Friday, 9 AM â 5 PM | PKT (UTC+5) |
| Pro | Monday â Friday, 9 AM â 5 PM | PKT (UTC+5) |
| Business | Monday â Friday, 8 AM â 8 PM | PKT (UTC+5) |
| Enterprise | 24/7/365 (planned) | Global (follow-the-sun) â planned |
Support hours are planned targets and may be adjusted before commercial release. Enterprise 24/7 coverage is subject to final operational setup.
23.8.5. Support Contact Information
| Contact Method | Details |
|---|---|
| Email Support | Available closer to commercial release |
| Ticket Portal | Available closer to commercial release |
| Knowledge Base | Available closer to commercial release |
| Community Forum | Available closer to commercial release |
| Phone Support | Available closer to commercial release (Enterprise) |
| Live Chat | Available closer to commercial release |
| Social Media | Available closer to commercial release |
Support contact details will be published before commercial release.
23.9. Self-Service Resources
23.9.1. Documentation
| Document | Description | Audience |
|---|---|---|
| User Manual | Complete guide to using CMD Pro | End-users |
| Admin Guide | Configuration and administration guide | Administrators |
| Developer Guide | API documentation, hooks, filters | Developers |
| Installation Guide | Step-by-step installation instructions | All users |
| Troubleshooting Guide | Common issues and solutions | All users |
| Release Notes | Version-specific changes and updates | All users |
23.9.2. Knowledge Base Categories
| Category | Content | Article Count (Target) |
|---|---|---|
| Getting Started | Installation, activation, first configuration | 10 |
| Configuration | Settings, API keys, commodities, currency | 15 |
| Dashboard | Using the dashboard, shortcodes, widgets | 12 |
| Charts | Chart types, customization, analysis | 10 |
| Alerts | Creating and managing alerts | 8 |
| Troubleshooting | Common issues and solutions | 20 |
| API | API reference, authentication, examples | 15 |
| Enterprise | Enterprise features, deployment, customizations | 10 |
| FAQ | Frequently asked questions | 25 |
| Video Tutorials | Walkthrough videos | 15 |
23.9.3. Community Support
| Feature | Description |
|---|---|
| Community Forum | Peer-to-peer support for all users |
| User Group | Monthly virtual meetups for users |
| Slack/Discord Community | Real-time chat for users and developers |
| GitHub Issues | Bug reporting and feature requests (for developers) |
| WordPress Support Forum | Official WordPress.org support forum |
23.10. Maintenance Release Schedule â Target Cadence
| Release Type | Target Frequency | Version Impact | Content |
|---|---|---|---|
| Emergency Patch | As needed (P0/P1) | Patch version (vX.X.X) | Critical bug fixes, security patches |
| Monthly Release | Monthly (target) | Patch version (vX.X.X) | Bug fixes, minor enhancements |
| Quarterly Release | Quarterly (target) | Minor version (vX.X) | New features, major enhancements |
| Major Release | 1-2 times per year (target) | Major version (vX) | Significant new features, possible breaking changes |
| LTS Release | Every 2-3 major versions (target) | Major version (vX) | Extended support, stability-focused |
Release cadence is a target and may vary based on development priorities and user feedback.
23.11. Maintenance & Support Success Metrics
| Metric | Target | Measurement |
|---|---|---|
| Bug Fix Response Time (P0) | < 1 hour | Ticketing system |
| Bug Fix Resolution Time (P0) | < 4 hours | Ticketing system |
| Security Patch Time | < 24 hours for critical | Release tracking |
| Support Response Time (P1) | < 2 hours | Ticketing system |
| Support Resolution Time (P2) | < 48 hours | Ticketing system |
| Customer Satisfaction (CSAT) | âĨ 4.5/5 | Post-support surveys |
| Net Promoter Score (NPS) | âĨ 50 | NPS surveys |
| Ticket Volume | Steady or decreasing | Ticketing system |
| First Response Resolution Rate | âĨ 70% | Ticketing system |
| Knowledge Base Usage | âĨ 1,000 visits/month | Analytics |
| Documentation Satisfaction | âĨ 4.0/5 | Surveys |
23.12. Maintenance & Support Responsibility Matrix
| Activity | Development | QA | Support | DevOps |
|---|---|---|---|---|
| Bug Fixes | â Lead | â Verify | â | â |
| Security Patches | â Lead | â Verify | â | â Deploy |
| Feature Updates | â Lead | â Verify | â | â Deploy |
| Documentation | â Contribute | â | â Lead | â |
| Knowledge Base | â | â | â Lead | â |
| Support Tickets | â | â | â Lead | â |
| Community Support | â | â | â Lead | â |
| Release Management | â Contribute | â Contribute | â | â Lead |
| Backup & Recovery | â | â | â | â Lead |
| Monitoring | â | â | â | â Lead |
23.13. Maintenance & Support Dashboard â Illustrative Example
The following dashboard illustrates the support and maintenance metrics CMD Pro is designed to monitor. Values shown are examples and do not represent live production data.
đĸ Operational
Support Status (Illustrative)
4.7/5
â Satisfaction (Illustrative)
12
Open Tickets (Illustrative)
1.2 hrs
Avg. Response (Illustrative)
6.5 hrs
Avg. Resolution (Illustrative)
95%
Resolution Rate (Illustrative)
Ticket Breakdown (Illustrative)
P0: 0
P1: 2
P2: 6
P3: 4
P4: 0
Version Adoption (Illustrative)
- v6.0: 35%
- v5.0: 45%
- v4.0: 15%
- Older: 5%
đ Latest security patch (illustrative): v6.0.1
â Pending security vulnerabilities (illustrative): 0
23.14. Maintenance & Support Summary
| Area | Key Components | Responsibility | Frequency |
|---|---|---|---|
| Bug Fixes | Severity classification, Fix process, Release schedule | Development, QA | Continuous |
| Security Patches | Vulnerability disclosure, Patch process, Notification | Security, Development | As needed |
| Feature Updates | Feature types, Roadmap, Release schedule | Product, Development | Quarterly/Major |
| Version Support | Support tiers, Support timeline, Migration | Product, Support | Per release |
| End-of-Life Policy | Notification, Migration support, EOL date | Product, Support | Per release |
| Customer Support | Support tiers, Channels, SLAs | Support | Continuous |
| Self-Service | Documentation, Knowledge Base, Community | Support, Development | Continuous |
This comprehensive Maintenance & Support section provides a complete framework for ensuring the CMD Pro product remains reliable, secure, and well-supported throughout its lifecycle, building customer trust and enabling a sustainable commercial software business.