Customer Churn Prediction & Retention Advisory Agent
Customer retention agent identifying early churn indicators and triggering automated re-engagement workflows.
1. Overview & Business Value#
The Churn Prediction Agent monitors customer transaction frequency, portal login activity, and support ticket escalation trends to predict customer churn risks.
1. Churn Risk Indicators#
- 45+ days without customer order or portal login.
- More than two open high-severity support tickets within 14 days.
- Recent contract renewal inquiries without confirmation.
{screenshot:ai-churn-risk-dashboard}
2. Retention Interventions#
When an account is flagged with a High Churn Risk, the agent automatically creates a high-priority follow-up task for the dedicated Customer Success Manager.
2. Prerequisites & Security Access Groups#
- Required Modules:
muk_ai, muk_mcp, smarterp_ai_suite - Security Group:
Ashewa AI / User(Technical ID:muk_ai.group_ai_user) - Master Data Dependencies: Configured AI provider credentials, active system prompts, and departmental cost centers.
3. Step-by-Step UI Execution & Verification#
Step 1: Navigating to the Operational Interface#
- Log into your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher and select Ashewa AI.
- Select the operational workspace corresponding to this agent suite.
{screenshot:76-customer-churn-prediction-and-loyalty-step1-navigation}
Step 2: Executing Agent Actions#
- Review agent prompts and execution parameters.
- Trigger the scheduled or on-demand workflow action.
- Validate output in the generated operational log.
{screenshot:76-customer-churn-prediction-and-loyalty-step2-execution}
4. Advanced Configuration Points#
- Scheduled Crons:
muk_ai.ir_cron_agent_health_checkruns every 30 minutes. - Multi-Company Isolation: Multi-company record rules ensure agent context is isolated to Company 1 (
Ashewa Technology Solutions S.C.).
5. Comprehensive Troubleshooting Matrix#
| Symptom / Error | Probable Root Cause | Resolution Action |
|---|---|---|
Agent unresponsive or timeout | Network latency or API endpoint outage. | Verify provider connection in Settings → AI Providers. |
Access Denied during agent execution | User lacks assigned operational permissions. | Assign user to the designated operational group. |
Last updated: 2026-10-30