Virtual Assistant Philippines: CRM Administration Guide

Give the CRM role a narrow first job

A CRM administration assistant can create records from approved sources, clean agreed fields, check possible duplicates, log contact activity, and prepare exception queues. The client owner should define stages, decide which records may be merged or deleted, approve bulk changes, control exports, and make sales judgments.

Start with one record type, such as inbound contacts from a web form or event list. Name the source, required fields, matching rules, allowed edits, review person, daily volume, completion time, and the exact conditions that make the assistant stop.

Use Philippines data as context, not a CRM score

World Bank data reports that 59.5% of Philippine employment was in services in 2025. It also reports internet use at 67.3% in 2024, gross tertiary enrollment at 47.4% in 2024, and adult literacy at 98.5% in 2020.^[1][2][3][4]

These figures help describe the setting for remote service work, but they do not measure CRM accuracy, product knowledge, writing, schedule fit, or care with customer records. Check those skills with a role-specific work sample and direct questions about the candidate’s equipment, connection, experience, and review habits.

Write a field map before opening the live database

A field map tells the assistant where each value comes from, what format it uses, and who may change it. For example, the company name may come from the signed account record, while a phone number may come from the latest customer message and a sales stage may be locked to the client owner.

Give every important field an allowed source and a rule for missing or conflicting data. If a form, email, call note, spreadsheet, and existing CRM record disagree, the assistant should place the item in an exception queue rather than choose the value that looks most likely.

• Record type, source, required fields, and accepted format
• Match fields for possible duplicates and the person who decides merges

What to check at each hiring step

The table keeps candidate evidence beside the decisions that remain with your business. It also flags shortcuts that can expose customer information or produce a poor role match.

Swipe the table sideways to read every column.

Test the assistant with a small dummy CRM

Build a test set with fictional names and companies, then give every candidate the same written rules. Include two similar company names, one shared email domain, a contact who changed employers, a blank required field, a conflicting phone number, and a record that appears twice with different owners.

Ask the candidate to return the cleaned file, a change log, a possible-duplicate list, and a short exception note. Score field accuracy, source use, matching logic, written notes, questions asked, and whether the candidate leaves uncertain records untouched.

Run a daily queue that a manager can review

Split the daily queue into new records, approved updates, possible duplicates, returned errors, and owner questions. Each item should have a source, received time, assigned person, status, last action, and next review date so unfinished work does not disappear inside a private note.

Use a short handoff that names the record and the blocker. A useful note might say, "The form and existing contact use the same email, but the company names and owners differ. I did not merge or reassign either record, and I placed both links in the duplicate queue for the CRM owner."

Protect customer records and bulk actions

CRM records may contain names, email addresses, phone numbers, job details, messages, buying history, support notes, and links to other systems. Give the assistant a named account, turn on multi-factor authentication, limit object and field permissions, and keep user management, exports, bulk deletion, system settings, and connected-app approval outside the role.^[5][6][7][8]

The Philippine Data Privacy Act sets duties around lawful processing, security, transparency, and accountability for personal information. It does not design a company’s CRM process, so the buyer still needs suitable agreements, written handling rules, training, review, and an incident plan for the records the assistant can reach.^[6]

Review the first month in three stages

During days 1 through 3, use dummy records and teach the field map, source rules, duplicate queue, note format, access limits, and exception owner. Check every edit and ask the assistant to explain why each source supports the selected value.

During days 4 through 10, allow live work on one approved record type and review every completed item. Track field errors, duplicate misses, unsupported changes, unclear notes, review time, questions, and any rule that two people read in different ways.

During days 11 through 30, compare the work with the starting scorecard and decide whether to keep, narrow, or expand the role. Use observed accuracy, exception judgment, queue age, manager review time, security behavior, and sales-team feedback instead of a broad claim about Philippines-based talent.