Onboarding

Set a refund request log for a virtual assistant

A refund log that ties each request to the original transaction, the written policy, the evidence, the approval limit, and the confirmation the customer receives.

By OnboardingEmployees editorial team | | 7 min read

Set a refund request log for a virtual assistant
On this page
  1. Capture the request and the original transaction
  2. Check the written policy and the approval limit
  3. Record the evidence before a decision
  4. Route the decision and log the outcome
  5. Follow the payment back to the customer
  6. Review the log for repeat causes
  7. Key takeaways
  8. Related reading

A refund request log is not a folder of complaint emails. For a virtual assistant, the log is the working record that ties a request to the original transaction, the written policy, and the decision. A refund handled from memory is hard to defend and easy to repeat. The log makes each outcome traceable to evidence.

Capture the request and the original transaction

Record the customer, the date of the request, and the channel it arrived through. A request that arrives by phone should be written down while the details are fresh. The assistant should keep the customer's own words rather than a summary. A later reviewer needs to know what was actually asked.

Find the original transaction and copy its reference into the log. Include the date, the amount, the items, and the payment method. The assistant should not accept a screenshot as a substitute for the record in the system. A reference that cannot be matched leaves the request unresolved.

Check whether the request names a specific item, a full order, or a duplicate charge. Each type follows a different path and needs different evidence. The assistant should record the requested outcome in the customer's terms. A vague request should be clarified before a decision is made.

Note any deadline that applies to the request or the response. A customer may have a limited window, and the team may have its own response standard. The assistant should record both dates. A late response can turn a simple request into a complaint.

Check the written policy and the approval limit

Open the current written policy and quote the section that applies. A policy that lives only in a training session cannot be checked by a reviewer. The assistant should record the version and the date of the policy used. A decision without the policy reference is an opinion.

Identify the amount limit that the assistant may approve without a second person. The limit should be written in the log template rather than remembered. The assistant should route anything above it to the named owner. A limit that is not recorded will be tested by the next unusual request.

Check whether the request falls inside a warranty, a service commitment, or a statutory right. These routes may override the usual policy and require a different approval. The assistant should record the basis for the route. A policy that conflicts with a legal right should be escalated, not applied.

Look for a pattern of repeated refunds from the same customer or the same product. A pattern may indicate a defect, a misleading description, or a misuse of the policy. The assistant should record the observation without accusing anyone. The reviewer can decide whether the pattern matters.

Record the evidence before a decision

Collect the order record, the delivery confirmation, and any correspondence about the issue. The assistant should attach the files or the links to the log entry. A decision made before the evidence is gathered will usually be revisited. The log should show what the reviewer actually saw.

Record the condition of the item or the state of the service when that matters. A returned item may be unopened, used, or damaged, and each state follows a different rule. The assistant should use the terms in the policy rather than an impression. A photo can support the description when the policy allows it.

Note any communication with the customer about the timeline or the possible outcome. The assistant should avoid promising a result before the decision is made. A statement that a refund is approved is a commitment. The log should reflect what was actually said.

Mark the evidence that is still missing and who is responsible for it. A request should not sit in a queue without an owner. The assistant should set a follow-up date for each missing item. An open item without a date is likely to be forgotten.

Route the decision and log the outcome

Send the request to the approver with a short summary and the evidence attached. The summary should state the policy section, the amount, and the requested outcome. The assistant should name the decision needed rather than asking for a general review. A clear question produces a faster answer.

Record the decision, the date, and the person who made it. If the decision differs from the request, record the reason in plain language. The assistant should not rewrite the customer's request to match the outcome. A clear record protects both the customer and the team.

Tell the customer the outcome and the next step in writing. Include the expected timeline and the contact for a question. The assistant should avoid internal codes and unexplained policy language. A clear message reduces the chance of a second request.

Update the log when the decision changes after a review. A first answer that is overturned should keep both versions. The assistant should record who approved the change and why. A log that shows only the final answer hides the path that produced it.

Follow the payment back to the customer

Record the refund method and the date it was issued. The method should match the original payment unless the policy or the customer agrees otherwise. The assistant should keep the confirmation reference. A refund that cannot be traced is not complete.

Check the expected arrival time for the method that was used. A card refund and a bank transfer follow different timelines. The assistant should record the expected date and set a follow-up. A customer who is told a realistic date is less likely to ask again.

Confirm that the refund reached the customer before the log is closed. The confirmation can be a system record or a customer reply. The assistant should note the source of the confirmation. A closed log without a confirmation is only a hope.

Handle a failed or returned refund as a new task with its own owner. A closed transaction can fail after the fact. The assistant should reopen the entry rather than create a duplicate. A duplicate entry makes the totals wrong.

Review the log for repeat causes

Review the log every month for the reasons behind the requests. Group the entries by product, channel, and policy section. The assistant should look for a cause that appears more than once. A repeat cause is cheaper to fix than a repeat refund.

Compare the decisions for similar requests and note any inconsistency. Two customers with the same evidence should not receive different answers without a reason. The assistant should record the comparison and the question for the owner. An unexplained difference undermines trust in the policy.

Check that every entry has a policy reference, an approval, and a confirmation. A missing field is a sign that the process was skipped. The assistant should list the gaps for the owner. A monthly check catches drift before it becomes a habit.

Propose one change to the request form or the product description that would prevent the most common request. The change may be a clearer size guide or a faster delivery notice. The assistant should record the proposal and the owner. The log becomes a source of improvement rather than a record of failure.

Key takeaways

Tie every request to the original transaction and record the customer's own words. Include the date, the amount, the items, and the payment method. A screenshot is not a substitute for the record in the system. A request without a reference cannot be resolved with confidence.

Quote the current policy and record its version and date. Write the assistant's approval limit into the template and route anything above it. Check whether a warranty or a legal right changes the route. A policy that conflicts with a legal right should be escalated, not applied.

Collect the evidence before a decision and mark what is still missing with an owner and a date. Record the decision, the reason, and the person who made it. Tell the customer the outcome and the next step in writing. A log that shows only the final answer hides the path that produced it.

Follow the payment to the customer and confirm it before closing the entry. Review the log monthly for repeat causes and inconsistent decisions. Propose one change that would prevent the most common request. A repeat cause is cheaper to fix than a repeat refund.

Continue building the workflow

Related support: onboarding operations support, contact us. The Internal Revenue Service - Recordkeeping for small businesses explains how businesses should keep records that support reported income and expenses.