K
Koos Schwaneberg
As a WordPress maintenance provider, I want to inform my clients directly from WP Umbrella about important updates and developments, without having to use an external program.
Current Situation
WP Umbrella currently has a template function for automated monthly reports. This works excellently for periodic communication, but there's no option for one-time, urgent messages to selected clients.
Concrete Use Cases
Major WordPress releases require proactive client communication. I want to inform clients about upcoming changes, manage expectations, and communicate potential downtime. Currently, I need to switch to another program for this, even though all relevant data is already in WP Umbrella.
Other Scenarios:
  • Major core updates or breaking changes
  • Expected downtime for maintenance
  • Critical security updates requiring extra attention
  • Proactive communication about PHP version upgrades
  • Changes in hosting or infrastructure
Proposed Functionality
  • Ability to send one-time emails to selected sites/clients
  • Selection based on existing filters (WordPress version, PHP version, labels, groups)
  • Simple editor for email content (doesn't need to be fancy, just functional)
  • Preview function before sending
Nice to Have:
  • Merge tags for personalization (site name, WordPress version, etc.)
  • Save drafts for later sending
  • Sending history/log
Why This is Valuable for WP Umbrella
For users like me:
  • One platform for all website management communication
  • Time savings (no switching between tools)
  • Data already present (which sites, which versions, which clients)
  • Better workflow, less frustration
For WP Umbrella as a product:
  • Higher customer retention (one less tool needed)
  • Competitive advantage over ManageWP and MainWP
  • Natural complement to existing client communication features
  • Higher perceived value of the platform
Additional Context
Currently, sites can only be linked to one template (for monthly reports). A one-time email function solves this without complicating the existing template structure. These are two different use cases that can coexist perfectly.