Features and capabilities

Custom Agents

Updated recently

Custom agents let users and organizations create specialized versions of Vesence for recurring workflows.

A custom agent can have its own instructions, role, tone, workflow preferences, focus area, and output style. This helps Vesence behave in a more consistent and useful way for repeated work.

A custom agent is a configured version of Vesence for a specific purpose or way of working.

What custom agents are

Custom agents are agents created by users or organizations to fit their own workflows.

A custom agent can be designed for a specific task, team, matter type, document type, review process, client style, or internal way of working.

Custom agents help Vesence understand how it should act before the user gives detailed instructions each time.

For example, a custom agent can be configured to focus on:

Contract review
Due diligence
Employment law documents
Transaction documents
Board materials
Client emails
Internal knowledge management
SharePoint file organization
Drafting in a specific firm style
Reviewing against a specific checklist or playbook

Why create a custom agent

Users create custom agents when they want Vesence to work in a consistent and specialized way.

A custom agent is useful when the same type of work is repeated and Vesence should follow the same approach each time.

Reasons to create a custom agent include:

To save time on repeated instructions
To standardize how a task is performed
To apply a specific review method
To follow a team’s preferred drafting style
To make outputs more consistent
To encode a checklist or workflow
To support a specific practice area
To create an agent for a recurring document type
To make Vesence easier for others in the organization to use

Private agents

A private agent is a custom agent created for an individual user.

Private agents are useful for personal workflows, personal drafting preferences, or tasks that only one user performs.

A private agent can help a user keep their own Vesence workflows consistent without making the agent available to the whole organization.

Private agents are useful for:

Personal drafting style
Individual review preferences
Repeated personal tasks
Private research workflows
Personal matter organization
Individual productivity workflows

Public organization agents

A public organization agent is a custom agent made available to other users in the organization.

Public organization agents are useful when a team, department, or firm wants a shared way of working in Vesence. They help standardize outputs and workflows across users.

Public organization agents are useful for:

Firm-wide review processes
Team-specific drafting standards
Department checklists
Practice-area workflows
Shared templates and playbooks
Common client deliverables
Standard internal processes

A public organization agent should usually be clearer, more stable, and more carefully maintained than a private agent because more users may rely on it.

Vesence default agents

Vesence also provides default agents.

Default agents are built-in agents designed for common Vesence tasks. They give users a strong starting point without requiring them to create their own custom agent.

Users can use Vesence default agents when they want a general-purpose or standard workflow.

What makes a good custom agent

A good custom agent is clear about its purpose. The goal isn't to lock Vesence into one rigid process — it's to give it a better starting point for a specific kind of work.

When you create one, you describe how Vesence should behave for that work: the role it plays, the material it relies on, what it produces, the style it follows, and the limits it should respect. In practice, a strong agent covers:

Scope — the agent's role and the kind of work it should focus on
Inputs — the files and sources it should rely on, and which to prefer
Output — what it should produce and the format to use
Style — the tone and level of detail it should follow
Checks — what it should review or verify before finishing
Limits — what it should not do without your approval
Escalation — the questions it should ask when information is missing, and when to check with you before drafting or editing
Standards — any styleguide, checklist, or playbook it should apply

You don't need all of these — even a short, focused prompt helps — but the more of them you make explicit, the more predictable the agent becomes.

Custom agents are built on the Create agent page. Expand the steps below — each one is paired with the matching part of the form from the Vesence web app. Click any field for a tip on what to put there.

To create an agent

Show steps

Open the Create agent page from the agent picker in the Vesence web app.
Set the Agent Icon, Agent Name, and Description so the agent is easy to recognize in the picker.
Choose where it appears under Available on — Web, Word, and Excel (custom agents are available on these surfaces).
Decide whether to keep it private or turn on Make agent public to organization, then pick the Folder it should live in.
Basic Information
Agent Icon
Choose an emoji to represent your agent
Agent Name *
Description *
Available on
Where this agent appears in the agent picker.
Web
Word
Excel
Make agent public to organization
Folder
Your private agents
Organization
Write the System Prompt— the most important field. Describe the agent's role, the source files it should use, what to check, the output format and tone, and when it should ask before continuing. Use Link to SharePoint in the same card to attach files or folders the agent should always read.
System Prompt *
Define the agent's behavior and personality
Describe how the agent should behave…
This prompt defines how your agent will behave and respond to users.
Add a few Example Prompts so users have a clear starting point.
Example Prompts
0 examples
Add example prompts to help users understand what this agent can do
Press Create Agent. It then appears in your agent picker and library, ready to use.

Maintaining custom agents

Custom agents should be updated when the underlying workflow changes.

An agent may need updates if:

The team changes its styleguide.
The checklist changes.
The law or market practice changes.
The output format changes.
Users repeatedly give the same correction.
The agent is too broad or too narrow.
The organization wants to standardize a process.

A good custom agent should evolve with the way the user or organization works.

Tips and limits

Create a custom agent when the workflow is repeated, specialized, or should follow a shared method.
Keep the agent focused. Very broad agents are harder to make consistent.
Include examples of good outputs where possible.
Tell the agent when to ask for user clarification.
Review public organization agents carefully before sharing them widely.
Update custom agents when the workflow, checklist, styleguide, or preferred output changes.

Summary

Custom agents make Vesence more consistent, specialized, and useful for the way a user, team, or organization works.

Private agents are for individual users. Public organization agents are shared across the organization. Vesence default agents are built-in starting points for common tasks.