Skip to content
+
Section 11

Support & Maintenance

Post-launch maintenance, SLAs, and ongoing partnership.

Our commitment to VOLY Next Gen does not end at launch. We offer flexible post-launch support models to ensure the platform remains healthy, secure, and evolving.

Post-Launch Support Options

Post-launch support and maintenance options
ModelWhat's Included
Stabilization Period (included)30-day post-launch bug fixes, performance tuning, and priority support
Ongoing Support RetainerMonthly allocation of development hours for bug fixes, minor enhancements, security patches, and technical support
Managed ServicesFull infrastructure management, monitoring, patching, backups, and 24/7 uptime monitoring in addition to application support
Enhancement SprintsPeriodic 2-week development sprints for new features, integrations, or improvements

Included Stabilization

Every engagement includes a 30-day post-launch stabilization period at no additional cost—ensuring the platform is running smoothly before transitioning to ongoing support.

Knowledge Transfer & Team Enablement

A core goal of our engagement is to leave VolunteerNow in a position to own and evolve the platform independently. Our knowledge transfer program includes:

  • Comprehensive technical documentation and system specifications (maintained through SDD throughout the project)
  • Architecture decision records explaining the reasoning behind key choices
  • Hands-on training sessions for your development team (if applicable)
  • Operational runbooks for deployment, monitoring, and incident response
  • Recorded walkthroughs of major system components for onboarding future team members

Built to Hand Off

Knowledge transfer is not an afterthought—it is built into the SDD process from day one. Every specification, architecture decision, and operational procedure is documented as we go, so VolunteerNow has a complete, current knowledge base at every stage of the engagement.

Support Structure for Organizations Without Internal IT

VolunteerNow does not have an internal IT team. We recognize this constraint and have designed our support model to meet your organization where you are. Our post-launch support includes:

  • Dedicated Client Success Manager (based in Dallas) who serves as your single point of contact for all operational requests
  • No escalations required to multiple teams — one named person owns your success
  • Proactive monitoring of platform health 24/7; automated alerts for critical issues
  • Help desk support available via email/phone during business hours with clear SLAs for response and resolution
  • Self-service knowledge base and video documentation for common admin tasks (no coding required)
  • Quarterly business reviews to discuss platform performance, usage trends, and roadmap alignment

Service Level Agreements (SLAs)

All support tiers include clear SLAs for response time and resolution. We differentiate severity levels to ensure critical issues receive immediate attention:

Support SLA severity levels and response targets
Severity LevelDefinitionResponse TimeResolution Target
CriticalPlatform unavailable or major functionality broken; impacts >50% of users1 hour4 hours
HighSignificant feature degradation or workaround required; impacts 10-50% of users2 hours8 hours
MediumMinor feature issue or performance degradation; impacts <10% of users8 hours24 hours
LowEnhancement request, documentation clarification, or cosmetic issue24 hours5 business days

SLA Escalation & Staffing

If a Critical issue is not resolved within the SLA, we automatically escalate to our Director of Client Success and dedicate additional engineering resources to resolution.

Our Ongoing Support Retainer includes 20+ hours per month of dedicated development capacity, ensuring issues are addressed quickly and not delayed by other engagements.

For Enhanced Support (Managed Services tier), we provide 24/7 on-call response with infrastructure monitoring and proactive issue detection.

Deployment & Rollback Procedures

We follow industry best practices for safe, zero-downtime deployments with automated rollback capabilities:

  • Blue/Green Deployment Strategy — two identical production environments that can be swapped in seconds if issues arise
  • Automated Database Migrations — schema changes tested against production-like data before applying to live environment
  • Feature Flags — new functionality deployed to production but disabled by default; can be toggled on/off without redeploying code
  • Automated Rollback — if post-deployment monitoring detects errors (exceptions, performance degradation), system automatically reverts to previous version
  • Manual Rollback Option — VolunteerNow admin can initiate rollback at any time during a 72-hour window after deployment
  • Change Windows — deployments during scheduled maintenance windows (e.g., 2am-4am on Tuesday) to minimize user impact

Peak-Load Reliability & Code Coverage

VOLY Next Gen is architected to handle peak loads during high-traffic periods (e.g., school year kickoff, registration deadlines):

  • Auto-scaling infrastructure that spins up additional servers under load and scales down during quiet periods
  • Load testing simulating 10x peak concurrent users; validated quarterly
  • CDN for static assets (images, JavaScript, CSS) reducing server load and improving performance for volunteers worldwide
  • Database query optimization and caching layer to reduce response times for common queries
  • Comprehensive automated test suite with 80%+ code coverage ensuring regressions are caught before production
  • Continuous integration/continuous deployment (CI/CD) pipeline running full test suite on every commit

Performance & Reliability Guarantees

We commit to 99.9% uptime SLA for the VOLY Next Gen platform during the ongoing support period. This is backed by our multi-AZ architecture, automated failover, and continuous monitoring. Any outages exceeding 4 hours will receive service credit equivalent to one week of support fees.

Enhancement Process & Knowledge Transfer

After launch, VolunteerNow can request enhancements and improvements. We have formalized processes for managing these requests:

  • Monthly enhancement request intake meeting to discuss priorities and trade-offs
  • Clear scoping process: requests are estimated, priced, and scheduled into future sprints
  • Quarterly enhancement sprints (2-week dedicated development cycles) for bundled improvements
  • Complete documentation and training for all enhancements, ensuring your team understands new capabilities
  • Source code repository access maintained throughout; VolunteerNow owns all code and can hire developers to maintain the platform independently
  • Detailed "how to extend" documentation for common enhancement patterns (adding new fields, creating reports, integrating with third-party systems)
+