የSmartERP መመሪያ የAshewa Technology Solutions መድረክ
ይህ ገጽ ገና ወደ አማርኛ አልተተረጎመም። የእንግሊዝኛው ጽሑፍ ቀርቧል።

Employee Sentiment Analysis & Retention Copilot

Continuous anonymized workplace sentiment tracking, employee engagement metrics, and early flight-risk alerts.

1. Overview & Business Value#

The Employee Sentiment & Retention Copilot analyzes anonymized pulse survey feedback, internal support ticket velocity, and leave request patterns to detect departmental burnout and flight risks.

1. Overview & Ethical Privacy Standards#

The agent enforces strict differential privacy: no individual employee private messages are ever read. Analysis is conducted strictly on aggregated departmental pulse survey responses and operational turnover velocity.

{screenshot:ai-hr-sentiment-heatmap}

2. Step-by-Step Action Plan#

  1. Navigate to Human Resources → Employee Engagement → Sentiment Copilot.
  2. Review the Departmental Health Index.
  3. Identify departments with declining engagement trends.
  4. Review AI-recommended retention actions (workload rebalancing, recognition programs).

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#

  1. Log into your SmartERP instance at https://smarterp.et/odoo.
  2. Open the main App Switcher and select Ashewa AI.
  3. Select the operational workspace corresponding to this agent suite.

{screenshot:56-employee-sentiment-and-retention-copilot-step1-navigation}

Step 2: Executing Agent Actions#

  1. Review agent prompts and execution parameters.
  2. Trigger the scheduled or on-demand workflow action.
  3. Validate output in the generated operational log.

{screenshot:56-employee-sentiment-and-retention-copilot-step2-execution}

4. Advanced Configuration Points#

  • Scheduled Crons: muk_ai.ir_cron_agent_health_check runs 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 / ErrorProbable Root CauseResolution Action
Agent unresponsive or timeoutNetwork latency or API endpoint outage.Verify provider connection in Settings → AI Providers.
Access Denied during agent executionUser lacks assigned operational permissions.Assign user to the designated operational group.
መጨረሻ የተሻሻለው: 2026-10-30