Finding services across a group of companies

Syntalith can connect approved service descriptions from selected companies to employee questions through Company Brain. The proposed scope provides answers with links to service descriptions and the appropriate contact. Service owners explain whom they support and what needs to be agreed before work begins. Your company can see whether someone outside the department can use the answer to reach the right team.

Start with the employee’s need

Suppose a manager is preparing a product catalog for a distributor meeting. They ask, “Can anyone in the group prepare photos for the catalog?” A studio in another group company has a service description saying that it produces product photography for group businesses. Requests should explain how the material will be used, with a contact listed for scheduling.

The assistant can identify the service, explain what to include in the request, and point to its owner. The manager still agrees on timing and terms with the studio. A service description does not establish whether the team has room in its current schedule. The answer helps start the right conversation without promising that the request will be accepted.

This differs from looking up an individual expert. The employee needs a service the organization offers to other units, together with a way to request it. Someone with similar skills may have their own assignments and may not provide that service to the wider group.

Write descriptions for people outside the team

Catalogs often use the language of the teams that create them. “Digital asset services” may mean little to someone looking for catalog photos. Preparing the material can involve keeping the official name while adding the needs employees actually bring to the team. The service owner should confirm that the description does not expand the offering.

The intended audience matters too. A service may be available only to certain companies or require an agreement before work can start. The assistant should use the arrangements recorded by your organization. If that information is missing, it can point to a contact and the question that needs an answer. Membership in the same corporate group does not by itself establish unrestricted access to every service.

Someone familiar with the team’s offering needs to maintain the description. A new contact or a discontinued service should be reflected in the catalog employees use. This does not require opening up all of the studio’s project documentation. A service description may provide enough information to start the right conversation.

Check the existing directory first

Atlassian team profiles can describe a team’s purpose and members and include links to its work in tools such as Jira and Confluence. They can provide a starting point for a directory like this. They do not establish a team’s available capacity. Team profile documentation.

For a small set of services, a clear directory, consistent names, and search may be enough. An AI application has a stronger purpose when employees describe needs in their own words and the relevant information is scattered across companies. We can discuss connecting selected catalogs and presenting services without adding terms the group has not agreed on.

Start with an internal request that was hard to route

Tell us about a time an employee struggled to find help within the group. We can discuss which service descriptions would benefit from question-based access and who in each company can help prepare them. Our pricing page covers engagement terms.