Virtual Assistant Provider guide
Run a sales proposal follow-up queue without inventing urgency
A practical sales proposal follow-up queue routine for a Philippines-based virtual assistant, with evidence, checks, handoff rules, and a manager-owned decision boundary.
Key takeaways
- a queue with the last customer signal, approved next message, due date, salesperson, consent or no-contact state, and unresolved question
- Read the latest thread before drafting.
- The assistant keeps records current and prepares approved follow-ups. They do not negotiate, discount, manufacture scarcity, or claim a result the team cannot support.
- The daily closeout lists replies needing judgment, messages sent, records corrected, no-contact updates, and tomorrow’s due items.
Start with the real problem
Proposal follow-up needs persistence, but it also needs restraint. A stale deal, an active legal review, and a prospect who declined are three different states. For Virtual Assistant Provider, the useful routine is the one that leaves the next person with a reliable record—not a vague “done” message.
Define a finish line
Treat the completed sales proposal follow-up queue as a queue with the last customer signal, approved next message, due date, salesperson, consent or no-contact state, and unresolved question. Write that definition beside the recurring task so the assistant and reviewer are checking the same outcome.
Run the work in a visible sequence
Begin from the approved source, record the current state, prepare the permitted action, run the checks, and preserve the result. When information conflicts or a required approval is absent, stop in a visible waiting state.
- Read the latest thread before drafting.
- Stop sequences after an opt-out or clear decline.
- Route pricing and scope changes to the salesperson.
Keep judgment with its owner
The assistant keeps records current and prepares approved follow-ups. They do not negotiate, discount, manufacture scarcity, or claim a result the team cannot support.
Review the first five examples
Demonstrate one example, then review the next four against the source. Record corrections by cause: missing input, unclear instruction, access gap, execution error, or late owner decision. If messages go out on time but prospects reply with confusion, inspect stage definitions and source notes before increasing cadence.
Protect accounts and source material
Use a named account, multi-factor authentication, and only the permissions the lane requires. Keep sensitive details in approved systems and link to them when possible. NIST’s framework is useful for assigning governance and response ownership; CISA’s guidance supports stronger sign-in controls.
Close the day with a usable handoff
The daily closeout lists replies needing judgment, messages sent, records corrected, no-contact updates, and tomorrow’s due items. The handoff should tell the next reader what changed, what remains safe to do, and which decision cannot be delegated.
Further reading
daily planning guide, handoff guide, NIST Cybersecurity Framework 2.0
Provider questions to copy
"Can you show how this role is screened, trained, checked each week, and replaced if fit is poor?"
"Can we start with a small task list before we expand the role?"
FAQ
Who should own the sales proposal follow-up queue?
A virtual assistant can own repeatable preparation and checks. A named manager owns exceptions, approvals, and business judgment. The assistant keeps records current and prepares approved follow-ups. They do not negotiate, discount, manufacture scarcity, or claim a result the team cannot support.
What evidence should remain?
Keep the source, action, check result, timestamp, exception, and reviewer decision. Store sensitive material only in its approved system.
When can review move from every item to a sample?
Only after the lane is stable across normal and exception cases. Return to full review after a serious miss, instruction change, or permission change.
Sources and notes
These sources are included as planning references. They do not replace legal, tax, security, or HR advice.
- NIST Cybersecurity Framework 2.0: Use named ownership, protection, detection, response, and recovery outcomes when a routine touches business systems.
- CISA More than a Password: Protect work accounts with multi-factor authentication and an explicit recovery owner.
- Google Search Central: Creating helpful, reliable, people-first content: Make each operating record useful to the person who must review or act on it.