Teams Virtual Agent Knowledge Links Open in ESC Instead of Employee Works (AIUX)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi Community,
In moveworks
We are implementing the ServiceNow Teams integration and are configuring a Knowledge Source.
During setup, the sample URL expected by the integration is:
Plain Text
https://instance.service-now.com/esc?id=kb_article&sysparm_article={display_id}
However, our organization uses Employee Works (AIUX), and knowledge articles are accessed through URLs such as:
Plain Text
https://instance.service-now.com/aiux/employeeworks/knowledge/<article_sys_id>
The Teams bot successfully returns knowledge articles, but when a user clicks a result, the link opens the article in the ESC portal rather than Employee Works.
Has anyone successfully configured the Teams Knowledge integration to:
Open articles in Employee Works (AIUX)?
Use AIUX article URLs instead of ESC URLs?
Override the generated article links?
Any guidance or workarounds would be greatly appreciated.
Thanks!- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
The link isn't decided when the user clicks. It comes from the URL template on the knowledge source — Moveworks takes the article from the search result and drops it into whatever pattern is configured there. If the template points at /esc, every article lands in ESC.
Change just the portal segment of that template to your Employee Works portal suffix and leave the rest of the pattern as it is:
/<your portal suffix>?id=kb_article_view&sysparm_article=<article token>
Two things that usually bite after the change. First, the kb_article_view page has to exist in that portal — ESC ships with it, custom portals don't always, and if it's missing the link opens the right portal but the article doesn't render. Clone the page from esc if you have to. Second, Can Read criteria on the article still apply on top of the URL, so if only some articles fail, that's knowledge permissions, not the link.
Ran into the same thing pointing VA results at a custom portal. Once the template pointed at the right suffix it worked, no override needed on the ServiceNow side.