NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro
+

Search the conversation and the document together

Connect Microsoft Teams and SharePoint and OneDrive to one company memory, and a single question reads both.

The decision is in a Teams thread and the specification is in a SharePoint file, and the search box in each knows nothing about the other.

Questions that need both

Each of these is unanswerable inside either product on its own. Agent mode reads both, resolves the customer to one entity, and ends with a line per system it consulted.

  • ›What did we decide about the supplier contract, and where is the signed copy?
  • ›Which documents were discussed in the project channel this month?
  • ›Who last changed the policy, and what was said about it?

What each side brings

Microsoft Teams

Bring Teams conversations into the answer.

  • Teams you belong to and their channels
  • Recent channel posts, with replies on request
  • Search across chats and channels with Microsoft Search syntax
  • Authors become people in your graph; teams become team entities
All of Microsoft Teams →

SharePoint and OneDrive

Read the documents your company actually works in.

  • Search file names and contents across OneDrive and SharePoint
  • Recently used files and folder browsing by site
  • Read .docx, .xlsx and .pptx as text, plus txt, csv, markdown, json and html
  • Documents join your graph with their last editor
All of SharePoint and OneDrive →

Who this is for

Ask one question across both

Seven days free. One price per organisation, nothing metered, and model usage stays on your own provider keys.