Skip to main content
Question

How to get bot to understand Wes is short-form for Wesley

  • December 19, 2025
  • 3 replies
  • 43 views

Forum|alt.badge.img

For People Lookup, it’s not recognizing our employees named “Wesley” as “Wes”. What are some ways for users to be able to look up Wes and found Wesley? Is it possible to set a conditional rule in “Source-Specific User Attribute Mapping” in Import User advanced setting so that anyone named Wesley can be recognized as Wes as well? Any ideas?

3 replies

Forum|alt.badge.img+3
  • Known Participant
  • December 19, 2025

I think that’s part on how your IDM is setup.

Like if you have a full name, last name, and preferred name then maybe you point your User Attribute Mapping to the preferred name rather than the full name?


Forum|alt.badge.img
  • Author
  • New Participant
  • December 23, 2025

Thanks, Jonathan. If I point User Attribute Mapping to preferred name rather than full name, the bot will only be able to recognize Wes and not Wesley. Is there a way for the bot to be able to recognize both?


DIANA.TWC
Forum|alt.badge.img+5
  • Inspiring
  • January 7, 2026

Were you able to find an answer? I believe Moveworks may have a way to “hard code” this co-relation in the backend for you. I have mostly seen this type of issue with business-specific acronyms, but those get drastically better with Knowledge (context for bot).

Is your agent asking for more clarification? I just tried confusing mine by giving it an incomplete name and it asked for the below.