In a professional services firm, knowledge piles up faster than it is organised. Procedures are written in SharePoint, but some updates were sent by email and never moved into the document. Internal rules and announcements sit in Bitrix24, if you use it, service descriptions exist in several Word versions, and decisions and notes from earlier projects are in Jira or Asana tasks whose structure only their creators understand. A new employee spends the first weeks asking colleagues in Teams and learning from answers that do not always agree. A veteran checks which rule is current before replying to a client, or answers the way they did last time.
The assistant brings together procedures and service descriptions from SharePoint, rules from Bitrix24 and earlier project material from Jira or Asana in one place, which staff ask in Teams in their own words: how to document a change to a service, what the validity period of a proposal is, whether we have done a similar project and who ran it. The answer comes with a link to the document in SharePoint, the Bitrix24 entry or the Jira task, and if the documents contain several versions, the assistant says so and points to the latest by date. What is not in the documents it does not invent. It suggests what to ask and what is worth writing down. We implement it one of two ways, depending on your environment: a ChatGPT Custom GPT on the OpenAI platform, where your documents are not used for model training, or Claude through the Anthropic API or Amazon Bedrock in an EU region with your SharePoint. We integrate with Bitrix24, Jira or Asana through an API, file export or an email flow, depending on your plan. Access rights are inherited from the existing ones, so an employee sees answers only from the documents and projects they have access to. At the start we also tidy the document structure and remove outdated versions, because answer quality depends on it.