Xoxoday Plum processes software enhancement requests through a structured pipeline spanning intake, CPO-led prioritization, agile development, and post-release feedback — ensuring every request is evaluated against business impact and product vision.
Submitting an Enhancement Request
Enhancement requests reach the Xoxoday Plum product team through three primary channels: your Customer Success Manager (CSM), the support portal, or your account management contact. Each submission is logged with structured metadata — business impact, use case description, urgency level, and expected outcomes — so nothing enters the review queue without sufficient context for evaluation. This intake model mirrors global SaaS best practice: a single, auditable mechanism for all product feedback that eliminates duplication and ensures parity across all customers regardless of account tier.Review and Prioritization
Once submitted, requests are validated by the Xoxoday Plum product team and escalated to the Chief Product Officer for final prioritization. Evaluation criteria include customer impact breadth, technical feasibility, security implications — assessed against standards such as ISO 27001 and SOC 2 Type II — and strategic alignment with the product roadmap. Business value and scalability drive prioritization, not request volume or recency. An enhancement that improves a critical integration with Workday, SAP SuccessFactors, or Darwinbox for a significant portion of customers is weighted accordingly, regardless of when it was submitted.Roadmap Planning and Transparency
Approved enhancements are incorporated into the Xoxoday Plum product roadmap, and expected timelines are communicated directly to the requesting customer. Roadmap transparency is a deliberate design choice: customers receive enough advance notice to plan internal adoption, coordinate with HR tech stakeholders, and prepare change management — whether that involves updating a Slack workflow, adjusting an MS Teams integration, or reconfiguring a Darwinbox automation trigger.Development and Release
Xoxoday Plum builds enhancements using agile methodology with CI/CD (continuous integration/continuous deployment) pipelines, enabling incremental, lower-risk releases rather than large infrequent deployments. Every update undergoes rigorous QA testing before production deployment. Customers are notified of changes through release notes, product newsletters, and scheduled business reviews — providing a clear record of what changed, when, and why.Feedback and Iteration
After release, Xoxoday Plum actively collects feedback to confirm that enhancements deliver their intended outcomes. This closed-loop approach feeds directly into the next planning cycle, ensuring product development stays aligned with evolving customer needs rather than assumptions made at initial scoping. The result is a continuous refinement cycle that compounds value across the Xoxoday Plum platform over time. Learn more: Xoxoday Plum Help Centre — ProcessWhat SLAs apply to Xoxoday Plum support requests?
Understand response and resolution time commitments for different request types across Xoxoday Plum’s support tiers.
How does Xoxoday Plum communicate product updates and release notes?
Learn how Xoxoday Plum notifies customers of version changes, new features, and incremental improvements after each release cycle.