Home Troubleshooting & Error Resolution What Steps Can Be Taken to Resolve the Issue Where the System Automatically Displays the Details of a Previously Linked Client When Calling Any Extension?

What Steps Can Be Taken to Resolve the Issue Where the System Automatically Displays the Details of a Previously Linked Client When Calling Any Extension?

Last updated on Aug 04, 2025

Overview

In some cases, when calling any extension within the Evo Voice system, the console or CRM integration may incorrectly display the details of a previously linked client—even if that client is unrelated to the current call. This issue can persist even if the PBX configuration appears to be correct.

This guide outlines steps to isolate and resolve this behavior, which may stem from stale cached data, CRM mislinking, or extension mapping inconsistencies.

Steps to Resolve the Issue

🔄 1. Clear Local Cache or Restart the Console App

  • Log out of the EVO Console.

  • Clear the app cache or browser cache (if using web version).

  • Restart the application to force a full reload of linked data.

🧩 2. Check CRM/Client Linkage Rules

  • Review integration rules that associate incoming calls or extensions with client data.

  • Make sure client lookups are based on correct identifiers (e.g., phone number, extension, or account ID).

  • Look for outdated mappings in your CRM or external integrations.

🧼 3. Verify and Remove Residual Soft-Link Data

  • Go to the affected client record.

  • Check for any soft links or auto-associations related to internal extensions.

  • Remove or correct old entries that may be reappearing due to CRM auto-match logic.

🧾 4. Check Extension Mapping in EVO Voice

  • Confirm the extension-to-user mapping under Admin > End Points or Users.

  • Ensure that the extension is correctly assigned to the current user or department.

  • Look for duplicate or reused extensions that could cause lookup conflicts.

🔍 5. Inspect Activity Logs

  • Review the activity or call logs to verify which number or extension is triggering the incorrect match.

  • Check whether the number passed into the CRM or console lookup matches the correct caller.

🔁 6. Sync or Rebuild Index

  • If you're using an integrated CRM or third-party sync tool, trigger a manual sync or rebuild the client data index.

  • This can resolve residual mismatches in cached relationship data.

👥 7. Engage the CRM or Evo Integration Team

  • If the above steps don’t resolve the issue, escalate the concern to the Evo support team or the integration vendor.

  • Provide a sample call instance, affected client name, and extension to aid investigation.

Preventive Tip

Ensure a consistent extension-naming and client-linking convention across all systems (PBX, EVO, CRM). Avoid reusing extensions for new clients without clearing old mappings.