Try adding the contacts through People in Teams for the web; if that succeeds, the failure is isolated to the Windows desktop client rather than the receptionist’s contact data.
- Open Teams for the web and sign in with the receptionist’s account.
- Select View more apps on the left, search for People, and open it.
- Select Add contact, search for an affected employee, select the directory result, and choose Create.
- Open that contact’s menu and select Add to speed dial.
- Go to Calls → Speed dial and verify that the employee appears.
Teams officially supports adding organizational directory contacts and then selecting Add to speed dial from the People app. The resulting entry appears in the Calls app ^1^.
Do not repeat the Windows Repair/Reset operation—the reset already performed did not resolve this case.
Interpret the result
If Teams for the web works
This points to a desktop-client-specific problem. Similar failures have been reported in new Teams where the same contacts could be added in another Teams client, although Microsoft has not published the exact “Name could not be added to speed dial” message as a formally identified known issue ^2^.
Use the web client as the immediate receptionist workaround, then update the desktop client:
- In desktop Teams, select Settings and more → Settings → About Teams.
- Record the version, then select Update now if offered ^3^.
- Alternatively, when the update banner appears, select Update → Update and restart Teams ^4^.
- Retest one of the contacts that previously failed.
If Teams for the web also fails
The issue is more likely associated with the user’s cloud contact data, directory lookup, or a Teams service problem rather than the local Windows installation.
An administrator should:
- Test the same affected employee from a second user’s Teams account.
- Only the receptionist fails: treat it as a user/account-specific case.
- Multiple users fail for the same employees: investigate directory data or service health.
- Open Microsoft 365 admin center → Health → Service health and check active Microsoft Teams and dependent-service incidents. Service health shows current incidents, advisories, and issues requiring tenant action ^5^.
- Confirm the affected people appear as organizational directory contacts. Teams supports adding anyone in the organization’s Active Directory to contact lists through Chat → Contacts or Calls → Contacts ^6^.
Collect evidence and escalate
If both web and desktop fail and Service health has no relevant incident, collect client diagnostics before opening a Microsoft 365 support case:
- Open Teams admin center → Users → Manage users.
- Select the receptionist.
- Open Client health.
- Select the affected Windows client and choose Request client logs.
- When collection finishes, download the logs and attach them to the support case.
Remote log collection is available for Windows non-VDI and Mac clients and requires one of these roles: Global Administrator, Teams Administrator, Teams Communications Support Engineer, or Teams Communications Support Specialist ^7^.
Include:
- Exact error text and timestamp.
- Receptionist’s Teams version.
- Whether People → Add to speed dial fails in both web and desktop.
- Names of two contacts that succeed and two that fail, without posting personal data publicly.
- Whether another user can add the same affected contacts.
References
- Manage your contacts with the People App in Teams | Microsoft Support
- On NEW Teams, contacts have "Add to Favorites, Add to Speed Dial", etc. greyed out - Microsoft Q&A
- [Desktop](https://support.microsoft.com/teams/troubleshooting/find-the-version-of-microsoft-teams-you-re-using)
- [Desktop](https://support.microsoft.com/teams/notifications-settings/update-microsoft-teams)
- How to check Microsoft 365 service health
- Limits and specifications for Microsoft Teams
- Diagnostic logs for Teams Client