An AI knowledge base after a business acquisition

“Express” in two companies' documents

Suppose an acquisition is complete and an employee begins covering orders for the acquired company's customers. Both firms use the name “express,” but their approved instructions specify different dispatch cutoffs and coordinators. The confirmed arrangement for this customer is to keep using the acquired company's instructions. The employee asks whom to send an express order to.

The assistant can find the applicable instructions, identify the coordinator named there, and link to the document. Its answer explains that these instructions cover this customer's service at the acquired company. The employee can read the order-handling passage and send the order to the appropriate person, rather than relying on instructions from their previous work.

If the question contains only the word “express,” the assistant still needs to know which company and customer arrangements are involved. The employee can identify the account or ask its account manager. A similar name helps locate material but does not establish that the two processes are interchangeable.

A shared glossary that preserves the differences

During integration, collect the terms employees understand differently. An entry for “express” can explain its meaning in each company and link to that company's instructions. A new colleague then knows what to clarify instead of treating a familiar word as a complete description of the service.

That glossary may be enough as a first step if there are few procedures and their owners are easy to find. Document descriptions identifying the company and service, together with existing library filters, can also help. Microsoft describes SharePoint managed terms applied to documents and lists, including descriptions, synonyms, and multilingual values. Check whether that capability is available in the version you use.

A Company Brain has a stronger case when employees need to connect a legacy service name, customer arrangements, and instructions held in another system. They can ask using familiar terminology and receive an explanation based on the relevant organization's material. The team first needs to identify which sources describe the applicable process and who resolves questions about it.

When the business agrees on a common process

Integration leaders decide which procedures to align, when changes take effect, and which work they cover. Service owners approve the new instructions, while those responsible for customers clarify how they apply to the agreements being handled. The assistant can help find those approved arrangements; it does not create a common procedure by combining passages from two old documents.

Keep earlier instructions with an explanation of when they applied, because employees may return to older orders. For a current question, they need to know whether the new process covers the work in front of them.

Help teams take over customer service after the acquisition

Syntalith can connect the knowledge teams need for daily work during integration. We propose starting a Company Brain project with services that regularly send employees to colleagues from the other company to clarify names and find instructions. We connect a reviewed glossary with company information, customer arrangements, and approved procedures. Answers point employees to the source and the person responsible for that process. Access to both companies' materials follows the employee's responsibilities and permissions.

The integration team defines the scope of approved changes, and service owners identify the materials employees should use. Staff taking over customer work assess whether the answers help them move a request forward. Tell us about a service name that recently caused confusion between the teams. We can discuss whether a shared glossary and clearer document descriptions are enough or whether several sources need connecting in an application. See Syntalith's pricing page for commercial information.