Frequently Asked Questions

Vesence is an AI assistant for legal, commercial, and business document work. It acts like a junior colleague that can read materials, find issues, compare information, draft, edit, summarize, and organize work.

It can understand long materials, improve language and structure, check documents before they are used, find gaps and inconsistencies, compare information across files, and prepare drafts, summaries, tables, and checklists.

Vesence is most useful when relevant context is available — contracts, templates, term sheets, emails, spreadsheets, presentations, PDFs, Teams messages, or SharePoint files.

Working drafts, redlines, summaries, comparison tables, question lists, checklists, email drafts, and updated presentations or spreadsheets.

No. Vesence prepares work product, but final judgment and approval always remain with you.

Start with the overview, then read how to give Vesence good instructions, and open the article for the surface — web, Word, Excel, PowerPoint, or Outlook — you are using.

The shared working layer between you and Vesence, where source materials, task context, and Vesence outputs come together.

Uploaded files, documents to review, drafts Vesence creates, edited documents, summaries, tables, trackers, and small tools — plus files from connected SharePoint or OneDrive.

No. If the relevant material is already available in the Workspace, Vesence can use it without you pasting it into the chat.

You add or connect source material, give an instruction, Vesence works with the files and saves the result back into the Workspace, and you review it and give follow-up instructions.

The chat is the conversation, the Workspace is the shared context, and the Agent is what turns the instruction and context into work product.

Yes. Vesence can create folders and organize files and outputs within the Workspace, so a matter or project stays tidy.

An agent can move from instruction to action. Vesence can inspect files, prepare outputs, ask follow-up questions, and save work product — not just reply in the chat.

Yes. It can read files, create and edit supported files, organize folders, process data, compare documents, and save outputs back into the Workspace.

It can break the work into focused parts and use sub-agents in parallel, then combine the findings into one coordinated result.

When a task needs more than a text answer, Vesence can write and run code to build a tool — a calculator, tracker, comparison, or checklist — for the work at hand.

No. The main Vesence agent coordinates the sub-agents and remains responsible for the final output.

Yes. Vesence can write and run code to build task-specific tools, automate repetitive steps, and process documents or data when a task needs more than a text answer.

A tailored version of Vesence for a specific, recurring task or workflow, with its own instructions and configuration.

A private agent is for one user; a public organization agent is shared with others so a team can standardize a workflow.

Define its scope, expected inputs, outputs, style, limits, and when it should ask you. The system prompt is the most important field.

They are created on the web and can then be used on the web and inside supported Word and Excel workflows.

Built-in agents for common tasks that give you a strong starting point without having to create your own.

Yes. You can connect an agent to specific folders, matters, or source material in OneDrive and SharePoint so it always starts from the right context.

Yes. You can choose whether the agent appears on the web, in Word, in Excel, or in all supported places.

Through the Vesence web app and the Microsoft Office add-ins, depending on what your organization has enabled.

Add-ins can be deployed by your organization or installed via a manifest file. The exact steps are in Setup and Access.

Access depends on your Microsoft 365 account and the permissions granted for SharePoint, OneDrive, Outlook, and Teams.

The add-in may not be installed or enabled for your account. Check Setup and Access or ask your administrator.

In the web app and inside the Office surfaces. How the Workspace and data are handled is covered in Setup and Access and Security and Data.

No. Vesence uses single sign-on with your Microsoft work account (Microsoft Entra ID), the same login you already use for Microsoft 365 — there is no separate Vesence password.

Yes. Vesence works in Word, Excel, PowerPoint, and Outlook, as well as on the web. Depending on how your organization deploys it, the Office apps and Outlook may be installed as separate add-ins, but once deployed Vesence is available wherever you work.

From the Microsoft 365 Admin Center under Integrated apps, an admin can deploy Vesence from Microsoft AppSource to the whole organization or to specific users or groups. Rollout can take up to 24 hours.

A Microsoft 365 work account and a current, supported build of Office on the web, Windows, or Mac. Very old perpetual 2016 or 2019 builds may not support the add-in.

Yes, where available, Vesence can work with Teams chat context and Teams-shared files, subject to your permissions.

Workspace files are stored locally in your browser rather than on a Vesence server, unless you connect external sources.

Vesence keeps Workspace files local and uses controlled access to connected systems. See Security and Data for the full picture.

Yes. You can review what is stored, allow more space, delete individual items, or reset caches from the storage manager.

Your Workspace files are stored locally in your browser, not in Vesence-owned file storage, unless you connect SharePoint or OneDrive or otherwise choose to share them. To carry out a task, the relevant content is sent securely to the AI model that powers Vesence for processing — that is separate from storage, and the files themselves are not retained by Vesence.

They are accessed through controlled permissions, and changes can be staged for your review before anything is written back.

Access follows your Microsoft 365 permissions and your organization's settings.

No. Your chats exist in your local Vesence working environment rather than in a separate Vesence-hosted database.

No. The working environment is isolated — Vesence only works with files made available to the task, not your whole file system.

Each chat has a controlled local working environment, the virtual computer, that Vesence uses to process files, run scripts, and create outputs. The Workspace is the storage inside it.

No. Email drafts, calendar invites, and staged changes are prepared for your review and are not final until you approve them.

Missing source material, conflicting versions, unsupported assumptions, unconfirmed names, dates, or amounts, and legal or commercial judgment calls.

Whether the right source was used, whether names, dates, and amounts are correct, whether assumptions are flagged, and whether the final wording or position is approved.

It creates strong working drafts and structured outputs, but they should be reviewed before being used as final deliverables.

You are. Vesence supports the work, but final judgment and approval remain with the responsible person.

Start with the goal, provide the source material, say what output you want, and note the scope, audience, and how to handle judgment calls.

Give the goal, not just a narrow command. Vesence works better when it understands what you are trying to achieve.

One that names the task, the files to use, the output format, and any constraints or preferred positions.

Tell Vesence whether you want a summary, table, redline, issue list, draft, checklist, or email.

Ask Vesence to flag assumptions and missing information instead of deciding silently.

Files, documents, emails, spreadsheets, templates, and other materials you want Vesence to use for a task.

Identify the source of truth when several versions exist so Vesence relies on the correct one.

Yes. The files provide the content and the instruction provides the direction; using both gives the best results.

Yes. It can compare and synthesize information across the available files and connected sources.

Vesence should flag missing source material rather than guess. Provide the file for a reliable result.

Yes, where your organization has connected one. iManage and NetDocuments appear in the chat's “+” attach menu, so you can pull documents in as source material and save work back, much like SharePoint or OneDrive. They are optional integrations enabled per organization.

Yes, where access is available, so it can work with matter folders, project files, templates, and precedents.

Connect SharePoint or OneDrive and browse to the files or folders to bring them into the working context.

No. Changes can be staged for your review before being saved back to the cloud.

Vesence still works with uploaded files; the cloud features appear only where your permissions allow.

For matter-level work, multi-file review, generated work product, and broad workflows that do not belong in a single Office add-in.

A way to review proposed edits across documents or work product in the Workspace.

Yes. The web workspace is built for multi-file, matter-level work.

In the Workspace, alongside your source material.

Use the web app for broad, multi-file, matter-level work; use the Office add-ins when the task belongs inside a specific document, workbook, deck, or email.

Yes. Because Vesence on the web runs in your browser, you can open the web app in your phone's browser and sign in with the same Microsoft work account. There is no separate app to install.

No. There is no separate app to install. You use Vesence on a phone by opening the web app in your phone's browser. The Word, Excel, PowerPoint, and Outlook add-ins are desktop-only and do not appear in the mobile Office apps.

A phone is great for chatting with the Agent, reviewing work, and quick tasks on the go. The layout adapts to the smaller screen, so chat and the document preview take turns filling the screen instead of sitting side-by-side. For heavy editing, such as working through a spreadsheet or comparing files side-by-side, the desktop experience works best.

Help with drafting, reviewing, comments, redlines, templates, schedules, and legal or business documents.

Word actions for improving wording and explaining clauses, reviewing document mechanics, and setting up reusable checks.

Yes. Edits can be shown as tracked changes for you to accept or reject.

No. Proposed edits are presented for review, and you decide what to accept.

Understand formulas, check assumptions, improve formatting, and compare spreadsheet figures against source material.

Find workbook issues, improve sheet presentation, and explain formulas or outputs.

Yes. The Explain action describes what a formula or output is doing.

Yes. The Check action looks for issues and inconsistencies in the workbook.

Improve slide wording, review layout, check consistency, and turn source material into slide-ready content.

It checks decks, improves slide wording, and helps fix layout issues.

Yes. It can turn source content into slide-ready text and structure.

Check drafts before sending, improve wording, shorten messages, and make email edits visible before approval.

Review a draft before sending, polish the wording, and shorten the message.

No. Drafts are prepared for your review and are not sent until you send them.

Yes. Start Recording Tracked Changes shows email edits visibly before approval.

Where supported, Vesence can work with emails, attachments, drafts, recipients, subject lines, and calendar information. Communications stay under your review or approval.