Xoxoday Plum re-enables AI features rapidly following incident resolution by treating each AI module as an independent microservice, allowing targeted restarts without a full platform reboot.
AI recovery without system-wide downtime
Xoxoday Plum designs its AI capabilities as independent microservices, which means a single incident affecting one feature does not cascade across Xoxoday Plum as a whole. When an AI module is disabled, recovery involves updating configuration settings or restarting that specific component — not triggering a full-scale system reboot. This architecture directly reduces mean time to recovery. Your organisation’s broader rewards and recognition workflows — including programme management, catalogue access, and redemption — continue uninterrupted while the targeted AI service is being restored.Real-time service orchestration
Xoxoday Plum supports real-time service orchestration to safely re-enable individual AI features in isolation. Once an incident is resolved and the root cause addressed, capabilities such as reward explainers, smart nudges, content moderation, and predictive dashboards can be brought back online without waiting for a scheduled maintenance window. For organisations using Xoxoday Plum alongside Slack or Microsoft Teams for recognition feeds, AI-generated reward summaries and nudge notifications resume as soon as the relevant microservice is reinstated — with no manual intervention required from your IT team beyond approving the configuration update.Business continuity for AI-driven programmes
Flexible service controls mean Xoxoday Plum can isolate, disable, and re-enable individual AI capabilities without affecting the overall incentive programme. If content moderation AI is temporarily suspended during an investigation, reward explainers and predictive dashboards remain active. Each feature is governed independently, giving administrators granular control over what runs and when. This approach aligns with enterprise continuity requirements and supports audit trail documentation consistent with frameworks such as ISO 27001 and SOC 2 Type II. Incident logs capture which services were disabled, for how long, and when they were reinstated — giving your compliance and IT security teams the evidence they need.What re-enablement looks like in practice
When restoring an AI feature after an incident, Xoxoday Plum follows a targeted recovery path. Administrators update service configuration flags for only the affected microservice, leaving all other modules untouched. The isolated component is then restarted, preserving active user sessions and any in-flight reward transactions elsewhere in Xoxoday Plum. Before traffic is routed back to the recovered module, Xoxoday Plum runs internal health checks to confirm the service is stable — ensuring end users never interact with a partially recovered feature. This sequence keeps disruption narrow and recovery fast, so your organisation’s incentive programmes maintain continuity even when individual AI capabilities require temporary suspension. Learn more: [Xoxoday Plum Help Centre — AI policy](How does Xoxoday Plum handle AI incidents?
Understand how Xoxoday Plum detects, contains, and resolves AI-related service incidents to protect programme continuity.
Which AI features does Xoxoday Plum include?
Explore the full set of AI capabilities in Xoxoday Plum, from smart nudges to predictive dashboards.