Integrations
Microsoft SharePoint
How your agents answer from the documents your teams keep in SharePoint, and stay in step as those documents change.
On this page
Your policies, product guides and procedures are probably already in SharePoint, maintained by the teams who own them. Your agents answer customers from those documents, and only from the sites and libraries you select. When a document changes, the agent's knowledge changes with it, so customers hear what your current documents say, not what they said last quarter.
What the connection lets the agent do
| Action | What it means for you | Example |
|---|---|---|
| Answer from your documents | The agent finds the relevant passage in your documents and answers from it | What a motor policy says about hire cars after an accident |
| Keep in step with changes | When a document is updated, added or removed, the agent's knowledge is updated to match | A revised claims guide is used from the day it is published |
| Answer only from approved sources | The agent answers from the material you have connected, not from general knowledge | A question about a product you do not sell is not answered from guesswork |
| Say when the answer is not there | If your documents do not cover a question, the agent says so and offers a person | An unusual question about a commercial policy goes to your team |
How it connects
The connection uses Microsoft 365's standard API (application programming interface: the documented way other software exchanges data with it). Your administrators register a dedicated app in Microsoft Entra ID (Microsoft's identity service), approve it with OAuth (the standard way to give an application limited access without sharing a password), and limit its access to the specific sites and libraries you select. The access is read-only.
The selected documents are indexed (organised so the agent can find the right passage quickly), and the index is held in your deployment, in your chosen region. Credentials are stored encrypted in your deployment, and every call travels over TLS 1.2 or higher (Transport Layer Security, which encrypts data in transit). Your documents stay in SharePoint, and your teams keep editing them as they do today.
Permissions
| Permission | Needed for | Default |
|---|---|---|
| Read documents in selected sites and libraries | Answering from your documents | Only the locations you select |
| Detect changes in those locations | Keeping in step | On for the locations you select |
| Create, edit or delete documents | Not needed | Not granted |
The agent can only take actions your team has granted. Anything not granted cannot be invoked. See Permissions.
In practice
Wadi Assurance keeps its policy wordings and claims guides in SharePoint.
- Its IT team connects two libraries: motor policy wordings and customer claims guides. Nothing else is shared.
- Sami asks on WhatsApp whether his policy covers a hire car while his own is repaired. The agent finds the clause in his policy wording and explains it.
- The next month, the product team publishes a revised wording. The agent picks up the change and answers new questions from it.
- When Sami asks whether a friend's car is covered, the wording does not say, so the agent offers him a person.
What your team controls
- Which sites and libraries the agent reads.
- Which documents are excluded within them.
- Withdrawing access, at any time, in Microsoft 365.
Related
- Knowledge and documentsIntegrations
- Knowledge and documents (agents)Agents
- PermissionsIntegrations
- Hosting and data residencySecurity and data protection
- InsuranceIndustry guides
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.