Support

Add-in: Successor Console

How to use it

1. Open any email and click Successor Console on the ribbon.
2. Enter the shared mailbox address you inherited (or leave blank for your own mailbox) and click Scan mailbox. Sign in if prompted.
3. Browse the tabs: People, Open items, Topics, Files. The filter box searches whatever tab you're on.
4. To build the knowledge pack: paste a SharePoint folder link (recommended) or leave blank for OneDrive, then click Build knowledge pack.
5. Review the pack — read every file, delete what shouldn't become institutional knowledge, sign manifest.docx — then follow README.txt in the pack to create the Copilot agent (about 30 seconds).

Frequently asked

“Access denied” on the shared mailbox. You need Full Access to that mailbox, granted by your IT/Exchange admin, and the address must be exact. The add-in cannot grant or bypass access.

Why .docx and not Markdown? Microsoft's agents can't use .md files as knowledge; .docx is fully supported and the files stay small on purpose (unlicensed tenants skip SharePoint files over 7 MB).

The .agent file doesn't open / isn't recognized. It's a best-effort convenience using a community-documented format. Use the manual step in the pack's README.txt instead: select the folder in SharePoint → Create an agent. That's the supported path. Preflights: your org needs a Microsoft 365 Copilot license (any one user) or pay-as-you-go agent billing, and "Restricted SharePoint Search" must be off.

The agent can't find newly added files. New uploads take a few minutes to index. Also confirm the agent's knowledge points at the pack folder.

Some open items or precedents look wrong. Expected — detection is deterministic best-effort (a "thanks!" can read as an answer). That's why the pack is reviewed by a human before use.

Contact

Bugs and questions: Matthew@purposebuilt.systems · Issues and pull requests welcome on GitHub.

Tutorial · Overview · Privacy · Security & Trust Center · Terms