What can a VA do in Salesforce? Tasks and capabilities

The work falls into four categories: data management, pipeline upkeep, activity logging, and reporting.

Data management covers contact and account field updates, duplicate record identification, lead and contact imports, field standardization, and list cleaning after campaigns or events. These tasks have clear right-and-wrong answers, which makes them straightforward to delegate once a written SOP is in place.

Pipeline upkeep includes stage progression updates, stale lead re-assignment, follow-up task creation, and flagging opportunities that have gone quiet. A VA cannot close a deal. They can make sure every open deal in the CRM reflects the current reality.

Activity logging means recording calls, emails, and meetings that reps forget to log, syncing calendar events, and attaching files to the correct records. Reps who skip this step corrupt the activity history that managers rely on for forecasting and coaching.

Reporting covers running and cloning saved reports, building and sharing list views, pulling weekly pipeline snapshots, and formatting dashboards for leadership meetings. The VA delivers a clean output; the manager interprets it.

78% of sellers missed quota in 2025, up from 69% the prior year, and administrative burden on non-selling tasks is cited as a contributing factor, according to Salesforce State of Sales 2025 data analyzed by SalesMotion. Every hour a rep spends entering contacts is an hour not spent on a discovery call.

40% of salespeople still use spreadsheets and email to store customer data, according to HubSpot's 2025 State of Sales report surveying more than 1,000 sales professionals. That means even teams with a Salesforce license are leaving CRM hygiene undone. A VA focused on data integrity closes that gap without adding a full-time employee.

CRM adoption is accelerating. 94% of tech companies and 71% of small businesses now use CRM systems, with 12.6% year-over-year growth (Kixie CRM Statistics 2026, citing multiple industry surveys). More users means more records, more duplicates, and more maintenance work, all of which a single focused VA can handle consistently.

A Salesforce VA can manage the full lead import workflow: pulling a raw list, cleaning it against existing records, and importing through Data Import Wizard or Data Loader with the correct field mapping. The critical step is running a deduplication check before the import, not after.

Stage updates are also in scope. When a rep moves a prospect from Qualification to Proposal Sent via email or a call note, the VA finds the record, updates the stage, and logs the corresponding activity. The pipeline stays current without interrupting the rep.

Follow-up task creation is another repeatable task with real revenue impact. After any meeting or call, the VA creates a Salesforce Task with the correct due date, assigns it to the right rep, and links it to the open Opportunity. Nothing slips through the cracks.

A VA can run any saved report in Salesforce without admin access, as long as their profile includes Read permission on the relevant objects. They can also clone an existing report, adjust columns and filters, export to Excel, or schedule recurring email delivery to the team.

List view creation falls in the same category. Building a custom list view is a standard user action in Salesforce, requiring no admin access. A VA can create views filtered by owner, close date, stage, or any indexed field, then share those views with the broader team.

One caution: a VA should not interpret a report for leadership without a reference document that defines each pipeline stage. Pulling and formatting a report correctly is a VA task. Knowing whether a 20% close rate is good or bad for your team requires manager context.

The table below shows which Salesforce tasks a VA can handle at standard user permission level and which require admin access. This distinction is the most important data security decision you will make when setting up a VA.

The governing rule is least privilege. A VA handling data entry and reporting needs Read/Write access on Leads, Contacts, Accounts, Opportunities, Tasks, and Events. They do not need access to setup menus, user management, or automation configuration.

The first step is a named Salesforce user, not a shared login. Every VA needs their own licensed seat and username. Without it, you cannot audit what changed or when, and Salesforce's Terms of Service prohibit seat sharing outright.

The second step is a written field-level SOP. For every field the VA will touch, the SOP documents the correct format, the accepted picklist values, and what to do when data is missing or ambiguous. Without this document, a VA importing 500 contacts will introduce as many inconsistencies as they resolve.

The third step is a scoped permission set. Rather than assigning a standard Salesforce profile with excess access, create a custom profile that matches the task list exactly. Log in as the VA before their first shift to confirm they can see what they need and cannot see what they should not.

The choice depends on task type: a VA handles ongoing, repeatable, volume-based work inside the CRM, while a consultant configures the platform. The table below maps the decision.

The right sequence for most teams is consultant first to configure, then VA to maintain. If the instance is already set up correctly, a VA alone is sufficient. The Salesforce VA hiring guide covers sourcing, vetting, and contracting for that first placement.

Salesforce experience is not the same as generic CRM experience. A VA who has used HubSpot or Zoho will not automatically understand the Lead-to-Contact conversion flow, the parent Account/child Contact relationship, or how Opportunity record types affect required fields. Confirm the specifics before assigning any live Salesforce work.

The skills grid below covers the areas to verify before making a hiring decision.

salessupportstaff screens roughly 1 in 1,000 applicants, so VAs placed through the service have already demonstrated Salesforce-specific fluency, not just general CRM familiarity. That pre-screening addresses the most common delegation risk: giving a VA Salesforce access before confirming they actually know how to use it.

Once a VA is in place, these metrics tell you whether the work is improving data quality or not. Run this scorecard from a saved Salesforce report on a monthly basis.

A VA consistently hitting these benchmarks is maintaining a CRM that sales leadership can actually trust for pipeline reviews and quarterly forecasting.