Forum Discussion

APM123's avatar
APM123
Copper Contributor
Apr 03, 2023

Allowing users to use custom alias in Teams meetings

In our company, customer support agents occasionally jump on calls with clients.

 

But many of our agents aren't comfortable with disclosing their full names to the customers, so in Zoom we set their display name to their first name and the initial of their surname.

 

This isn't something that's possible in Teams (unless we change their AD display name and email address).

 

Is anybody else in the same situation?

 

The only two ways I can think of getting around this:

  1. Using a shared account, but this would only be an option for us if it were possible to delegate access to it in the same way as we can delegate access in Exchange - i.e. allow the user to access this shared account via their own account. Letting everyone actually log into a shared account is not an option due to security risks and auditing nightmares.
  2. buying a second Teams license for everyone for this purpose, with the "anonymised" display name. But managing this would be a pain, both for us and the users.

Neither of these seem like particularly good options. Any other ideas?

 

As much as we'd like to fully move away from Zoom, this is one feature that we genuinely use that Teams doesn't have.

  • Schedule a meeting that is open to the general public (anonymous logins), then have the user join it with the browser client (in a private session). It will allow them to enter a display name therein. Just make sure that the meeting can be started by anyone 🙂
  • Schedule a meeting that is open to the general public (anonymous logins), then have the user join it with the browser client (in a private session). It will allow them to enter a display name therein. Just make sure that the meeting can be started by anyone 🙂
    • APM123's avatar
      APM123
      Copper Contributor
      Hey Vasil! Thanks for the quick reply and sorry for not getting back sooner (seems I forgot about the post, whoops).
      This is a really neat workaround that probably works in most situations.
      But unfortunately we're in finance, and I think a solution with our agents signed in (and denoted as) guests would spook some of the customers and probably wouldn't be acceptable to our InfoSec team.
      I think we may need to look into secondary accounts for these members of the team.
      Thanks again!

Resources