A client contact map is a short list that tells a new virtual assistant who the people behind an inbox actually are. It records the decision maker, the information source, the billing contact, and anyone who should not be approached directly. The map is written before the assistant sends the first reply so a polite answer does not create a relationship nobody approved. It is not a customer relationship management export and it should fit on two pages.
Start with the people the inbox already knows
Open the sent folder and list the addresses that received a reply in the last ninety days. Group them by the reason they were contacted rather than by company size or alphabet. The grouping shows which names belong to active work and which are historical. A list built from memory will miss the quiet contacts that still matter.
For each active contact, record the role, the company, and the person inside the team who owns the relationship. A name without an owner is a relationship that will drift when the assistant changes a greeting or a cc line. The owner should be a person who can confirm the contact's current authority. Write the date the detail was last confirmed.
Mark the contacts who are sources of information rather than decision makers. A scheduler, an assistant, or a receptionist may be essential to reach the right person but should not be asked to approve a change. The distinction prevents the assistant from escalating to someone who cannot decide. It also prevents an accidental bypass of the real owner.
Separate decision makers from information sources
Record the decisions each contact is allowed to make in plain terms. One contact may approve a schedule, another may approve a budget change, and a third may only confirm that a document arrived. The assistant needs this list because the same word, approval, can mean different things to different people. A short example beside each entry makes the boundary usable.
Name the contact who should receive a courtesy copy but not a question. Copying a client on every message feels transparent but can turn an ordinary clarification into a visible delay. The map should say when a copy is expected and when it creates noise. A note such as copy only after the decision is recorded is easy to follow.
Write down any contact who must not be emailed directly, with the reason and the approved route. A senior client may expect all messages through an account lead, and a legal contact may require a formal channel. The assistant should be able to recognize the name and stop. A prohibition without a route leaves the assistant with no next step.
Record the preferred channel and timing
Record the channel each contact uses for ordinary work, such as email, a client portal, or a scheduled call. The channel is part of the relationship because a message sent to the wrong place may never be read. The map should also say which channel is authoritative when two are active. A short note about the last confirmed preference keeps the entry current.
Add the response window each contact expects and the time zone they work in. A client who replies within an hour may expect the same, while another may check email twice a day. The assistant should not treat a slow reply as disinterest or a fast one as an emergency. The window should be agreed with the relationship owner rather than inferred.
Note the dates when a contact is usually unavailable, such as a monthly close or a seasonal closure. A message sent during that period may sit unanswered and look like a problem. The map can name a backup contact or a hold date. The assistant should know whether to wait or route the question elsewhere.
Name the topics each contact may raise
List the recurring topics that arrive from each contact, using the words the client actually uses. One contact may write about invoices, another about scheduling, and a third about service changes. The topic list helps the assistant choose the right owner before reading the whole message. It also reveals topics that no current owner covers.
For each topic, record the first question the assistant should ask when the message is incomplete. A billing note without an invoice number and a scheduling note without a date both need a quick clarification. The question should be specific enough to answer in one line. A generic request for more detail usually produces another round of email.
Flag the topics that must never be answered from the inbox, such as commercial exceptions, legal positions, and personnel matters. The assistant may acknowledge the message and route it, but should not offer a view. A clear flag protects the client and the assistant at the same time. The flag should name the person who does answer.
Set the escalation route for unknown senders
Write a rule for a message from an address that is not on the map. The assistant should not guess the relationship from the domain or the signature. A short holding reply may be appropriate, but only if the team has approved the wording. The message should then go to the inbox owner with the sender details attached.
Record how the assistant should verify a new contact before adding them to the map. Verification may require a call to a known number, a check against a signed agreement, or a confirmation from the relationship owner. The map should not grow from every inbound request. A contact added without verification can become a route for a false request.
Name the person who approves a change to the map and how quickly the change takes effect. An approval that lives only in a chat message will be forgotten by the next assistant. A dated entry at the bottom of the map is enough. The map should show its current version and the last review date.
Review the map after the first week
At the end of the first week, compare the map with the messages the assistant actually handled. Mark the contacts that were missing, the owners who were wrong, and the topics that had no route. Treat the differences as the agenda for the first revision. A map that is never compared with real traffic is only a guess.
Ask the assistant which contact was hardest to route and why. The answer may reveal a title that sounds like a decision maker but is not, or a channel that nobody monitors. Use the answer to rewrite one entry rather than the whole document. A specific fix is easier to test than a general instruction.
Keep the map beside the shared inbox and link it from the role-scope card. A document stored in a separate folder will be opened once and then forgotten. The assistant should be able to reach it from the place where the work arrives. The next review should start from the messages that caused a question.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Small Business Administration - Hire and manage employees guidance on setting expectations and managing a new working relationship.
Related reading
Build a shared inbox label scheme a virtual assistant can maintain
A small label scheme tied to the work queue, with clear rename rules, an owner, and a monthly audit so the inbox stays usable after the first week.
Create a voicemail-to-task routine for a virtual assistant
A voicemail routine that turns a message into a task with a caller, a request, a deadline, and a callback rule instead of a forwarded audio file.
Set a calendar booking rule for a virtual assistant who manages interviews
A booking rule that covers interview buffers, panel constraints, reschedule limits, and candidate data before a virtual assistant owns the calendar.
