Overview
If a user (e.g., "Ted") is not seeing any calls in the Evo Console, it could indicate a problem with their call routing, user assignment, endpoint configuration, or console sync. This article outlines the potential causes and actionable steps to restore normal call behavior.
Possible Causes
-
User not assigned to the correct flow or ring group.
-
Console is not logged in or synced properly.
-
Device endpoint mismatch or offline status.
-
Node configuration or routing rules were recently changed.
-
User’s availability status (e.g., set to Do Not Disturb or Offline).
Resolution Steps
✅ 1. Check Console Login Status
-
Ensure the user is properly logged in to the Evo Console.
-
If using the desktop app, confirm it's running and connected to the network.
🔄 2. Log Out and Re-Login
- Have the user log out and log back in to refresh session and call visibility.
👥 3. Confirm User is Assigned to the Correct Flow or Group
-
Go to
Admin > Flowsand find the flow handling incoming calls. -
Ensure the user is included in the ring group, hunt group, or transfer list.
📞 4. Test an Incoming Call
-
Place a test call to the main line or specific DID routed to the group/user.
-
Confirm if the user’s console rings or logs the call.
-
If not, check if others in the group receive the call—this helps isolate the issue.
🛠️ 5. Check Endpoint Mapping
-
Go to
Admin > End PointsorUsers. -
Verify that the user is mapped to an active and correct device or softphone endpoint.
-
Ensure the endpoint is online and registered.
🚫 6. Check User Availability Settings
-
In the Evo Console, check if the user has set themselves to:
-
Do Not Disturb
-
Offline
-
Forwarding Mode
-
-
Set to Available to ensure calls route correctly.
Additional Troubleshooting Tips
-
Check if any scheduling rules are affecting the user’s availability.
-
Review
Admin > Logsto trace if any calls were attempted for that user. -
If calls route through a receptionist or automated menu, ensure the correct destination is being passed.
Escalation
If the above steps do not resolve the issue:
-
Gather:
-
User name (e.g., Ted)
-
Time and date of expected calls
-
Console screenshots (if applicable)
-
-
Report to Evo Support or your system admin for further log analysis.