An AI knowledge base for shared service centers

One answer from two documents

In this example, a shared service center handles supplier-record requests for two business units operating in different countries. Both use the same form specified in an approved procedure. A current, approved addendum for one unit also requires a project code and review by the project coordinator. These are the company's own internal arrangements.

An employee asks in Polish how to prepare a request. The assistant first establishes which unit they serve, because the language of the question does not identify it. Once the employee names the unit with the additional requirement, a useful answer could say: “Use the shared supplier-record request form. For this unit, also include the project code and send the request to the project coordinator for review.” Links to the procedure and addendum let the employee open both sources.

Why finding the general procedure is not enough

As a shared service center takes on work for more units, knowing the common procedure may not cover everything needed for a particular request. An experienced colleague remembers the addendum and explains what to include. A new employee uses only the main instructions, and the gap becomes apparent when the request reaches the next team.

The assistant's help should bring the material together into a clear explanation. The employee needs to understand what the whole team uses and what the unit they are serving requires in addition. Two links alone would still leave them comparing the documents before each request.

Someone in the firm needs to maintain the relationship between the addendum, the procedure, and the unit it covers. If the coordinator stops reviewing these requests, the process owner should update the relevant material. When two approved documents describe the same task differently without explaining the change, the employee asks the process owner. The assistant can identify the passages that need clarification.

What your current tools can provide

First, check whether the form already displays the requirements for the unit being served. If it does, making those explanations easier to reach may be enough. An organized procedure page that links directly to the relevant addendum can also help. A separate application has a stronger case when employees piece together answers from documents kept in different places.

Microsoft describes SharePoint knowledge sources in Copilot Studio, including selected materials and existing content permissions. Documents linked from those materials are not automatically searched. If the addendum is a separate file, check that it is included among the assistant's available sources.

If employees already find the complete answer but struggle to convey it to colleagues in another language, see our article on AI training for multilingual shared services teams. It shows how to write a handoff that makes the recipient's next task clear.

Connect the instructions employees use to build an answer

When employees regularly ask team leads about additions to a familiar procedure, Syntalith can help make those agreements available while they handle requests. We propose starting a Company Brain project with one process shared across several units. We connect the common instructions with current addenda so an employee receives an explanation for the specified unit and can open both sources.

The process owner identifies approved materials and helps assess whether the answer preserves the unit's requirements. Employees check whether it lets them prepare the request without another question to the team lead. Tell us about a request returned because a unit-specific requirement was missed. We can discuss whether better access through the current form or library is enough, or whether separate sources need connecting. See Syntalith's pricing page for commercial information.