Document your Votel sub-account like an expert.

You should not have to remember what is buried inside an account.

A mature Votel workspace can hold fields, pipelines, forms, agents, workflows, calendars, email designs, websites, integrations, users, and reusable values. Without documentation, onboarding, troubleshooting, handoffs, and audits turn into hours of manual clicking.

One account. Twelve useful documents.

The assistant organizes the findings into a predictable pack instead of dumping hundreds of tool responses into one impossible file.

Why the coverage file matters: a trustworthy document says what it could not prove. Missing access should read as unknown, never silently as empty.

Connect once, confirm twice.

The master account-documentation prompt

This prompt deliberately separates discovery, detail reads, pagination, writing, and coverage reporting. It also forbids account changes.

Perform a read-only documentation audit of this entire Votel workspace.

Inventory every accessible asset, including contact fields, contact layout, pipelines, stages, tags, global variables, email templates, forms and form elements, workflows, workflow runs and enrollments, AI agents, knowledge sources, calendars, websites, funnels, dashboards, integrations, phone numbers, users, roles, tracking campaigns, brand kits, scheduled tasks, and Library files.

For every category:
1. Use its list or context tool first.
2. Follow pagination until no records remain.
3. Read each individual asset in full when a detail tool exists.
4. Record names, IDs, status, purpose, important configuration, and known relationships.
5. Never treat an unavailable tool, failed read, or permission problem as an empty category.

Build a usage and relationship map. For each tag, custom field, email template, form, workflow, and reusable value, identify every accessible asset that references it. Where activity or enrollment data is available, report last activity, run counts, and which contacts are currently enrolled or recently completed a run. Classify each asset as actively used, configured but not recently observed, apparently unreferenced, or unknown because the required evidence is unavailable.

For workflows, document triggers, nodes, branches, waits, messages, tags added or removed, fields read or written, templates used, calls to other workflows, and any available enrollment or run-state evidence. Do not call an asset “unused” merely because no reference was found; explain which sources were checked and which were unavailable.

Do not create, edit, publish, send, activate, delete, purchase, release, invite, or overwrite anything. Do not expose credentials, tokens, secrets, private keys, or full sensitive contact data.

Save the results in the Votel Library as:
- 00-Workspace-Overview.md
- 01-CRM-and-Pipelines.md
- 02-Fields-Tags-and-Variables.md
- 03-Forms-and-Workflows.md
- 04-Agents-and-Knowledge.md
- 05-Email-and-Messaging.md
- 06-Calendars.md
- 07-Websites-and-Funnels.md
- 08-Settings-and-Integrations.md
- 09-Asset-Coverage-and-Gaps.md
- 10-Usage-Relationships-and-Orphans.md
- 11-Workflow-Enrollment-and-Migration-Readiness.md

For each section, cite the MCP tools used and the date checked. In the coverage report, classify each asset type as:
- Fully documented
- Inventory only
- Inaccessible or permission-limited
- Unsupported by the currently available MCP tools
- Not found after a successful complete read

Before reading the account, show me the documentation plan, the categories you can access, and any assumptions. Wait for my approval before continuing.

What the assistant should actually do

Show what is used, unused, and connected.

A list of names is only the beginning. The useful layer is a relationship graph: which workflows read a field, which actions add a tag, which templates send from which sequence, and whether there is evidence that those assets have run.

Use precise language: “apparently unreferenced after checking A, B, and C” is credible. “Unused” without showing the evidence is not.

Two reports turn the account into an understandable system.

The asset report tells you what exists. The connectivity report tells you how those pieces work together. Use both: an inventory without dependencies is incomplete, while a relationship map without a complete inventory can hide important gaps.

The practical payoff: before deleting a tag, editing a field, or replacing an email, the connectivity report shows the likely blast radius. Every conclusion should link back to its evidence and distinguish “not found” from “proven unused.”

Can a contact resume at email 5 of a 10-email workflow?

What can be documented—and what needs a caveat

Terminology note: Votel uses “global variables” for reusable workspace values in parts of the platform. Document the names, purposes, and references that MCP returns—never their secrets.

Review the blueprint before you trust it.

Update the map without starting from zero.

Run the blueprint once for the baseline, then ask for a dated comparison after major launches, team changes, migrations, or client handoffs.

Use this workflow with Votel’s live documentation.

Tool availability changes as Votel ships. This guide was last reviewed September 17, 2026, when the authenticated Votel tool inventory showed 318 tools across 23 categories.

All Things Votel is independent and not operated by or affiliated with Votel.ai. This is a documentation workflow, not a guarantee that every Votel asset or private setting is exposed through MCP.