Philippines staffing blog ·
Handle a support request made on someone else's behalf
A workflow for requests from assistants, family members, and colleagues that separates helpful context from authority the desk cannot assume.

Direct answer
Operational guidance
Why a request on behalf needs a rule
Assistants, family members, and colleagues often contact support for someone else. The request may be entirely legitimate and still arrive without proof that the requester may act on the account. Without a rule, the desk swings between refusing useful context and granting access on a polite introduction. A written step keeps the agent from deciding the same question differently on every shift. A refusal that arrives without an explanation feels arbitrary to the customer.
The rule should separate three things that are easy to blur. The first is the account holder, the person whose data or service is affected. The second is the requester, the person writing or calling today. The third is the authority that connects them, which may be a delegation, a role, or a signed consent. Naming all three keeps the note usable when the conversation moves to a new owner.
Identify both people before the details
Start by recording who holds the account and who is asking. Ask for the account identifier rather than a name alone, because names collide and nicknames change. Confirm the requester's relationship to the account in their own words. Do not infer authority from an email signature, a shared office, or a familiar caller history. A shared inbox hides which person actually made the request today.
If the account holder is present, a short verification step is usually enough. If the account holder is absent, the desk needs a documented basis for the request or must route it to someone who can approve it. Record which situation applies before discussing the underlying issue. That single field decides whether the agent can continue or must pause. The pause should come with a named owner and a realistic next step.
Record the authority the requester has
Write the authority in plain language rather than a vague label. A note such as the customer asked their assistant to request a copy of the last invoice is stronger than a note that says authorized contact. Add the evidence that supports the statement, such as a callback to the number on file or a signed delegation. If no evidence exists, say so and name the decision owner. A vague authorization note is worse than one more requested document.
Scope the authority to the task rather than the whole relationship. An assistant allowed to request an invoice may not be allowed to change payment details or reset a password. Record the limit beside the approval so the next agent does not extend it by habit. When the request changes shape, treat the new request as a new authority question. Scope notes stop a small favour from turning into a broad permission.
Where the handoff fails
The most common failure is a summary that names only the requester. The next agent sees a helpful assistant and assumes permission that was never checked. Copy the account holder, the requester, the authority basis, and the task limit into the handoff. A short field set prevents the story from drifting as it moves between queues. The receiving agent should not have to rebuild the delegation from old messages.
A second failure is a refusal that explains nothing. If the desk cannot proceed, say which fact is missing and what the customer can provide instead. Record the refusal reason and the safe alternative offered. The customer should leave with a next step even when the answer today is no. Offer a verified route even when the current request cannot proceed.
A worked example
An executive assistant asks for a copy of a recent invoice and a change to the billing email. The agent confirms the account holder, the assistant's role, and the scope of the original delegation. The invoice request fits the recorded authority, so the agent fulfils it and notes the evidence. The email change does not fit, because it affects account security and payment notices. The difference between the invoice and the email change decides the whole case.
The agent explains the limit, offers a verified callback to the account holder, and records both requests separately. The invoice is delivered, while the email change waits for the owner to approve the new destination. Nothing is refused wholesale and nothing is granted by assumption. The next agent can see exactly which part of the request was completed and why. Both outcomes are recorded so the customer sees one clear plan.
What the manager decides
The manager decides which relationships the desk may accept without further approval. A payroll provider, a legal representative, or a family member may each need a different evidence standard. Publish that list beside the intake form so agents do not invent a hierarchy under pressure. Review the list when a new client type or contract appears. The list should name the evidence required, not only the relationship.
The manager also decides how long delegation evidence is kept and who may read it. Consent documents and identity records should not sit in an open queue note. Store the minimum reference needed to justify the action and link to the protected record. A clear retention rule keeps a helpful workflow from becoming a privacy problem. A protected record is easier to defend than a note copied into every queue.
Train with three cases
Use a routine delegation, a request that exceeds the delegation, and a case where the account holder cannot be reached. Ask agents to say which field decides each outcome and what they would write in the handoff. The exercise should take ten minutes and produce one shared sentence for each case. Repetition builds a consistent answer without a long policy debate. The cases should include one where the correct answer was a polite no.
Add the check to the weekly quality sample. Look for requests that were fulfilled without an authority basis and refusals that left no next step. Coach the gap rather than the person, and update the template when the same field is missing twice. The aim is a desk that can say yes quickly when the evidence allows it and no clearly when it does not. A missing next step is a defect even when the refusal itself was correct.
Close and review
Close the request only when the task is complete, refused with a reason, or waiting on a named owner. Record which of those states applies and who owns the next update. If the requester asks for a new task, capture the new authority question instead of stretching the old approval. The record should let a reviewer reconstruct the decision without reading every message. A reviewer should see which request was completed and which one was held.
Review a small sample of behalf requests each month, including at least one that was declined. Ask whether the authority evidence was proportionate and whether the customer received a usable next step. Adjust the form or the guidance when the same ambiguity appears again. A steady rule protects the account holder and lets legitimate helpers move quickly. Proportionality is the test, not the volume of paperwork collected.
Authoritative sources
- NIST SP 800-53 Rev. 5 security and privacy controls
- FTC Safeguards Rule
- ISO 18295-1:2017 customer contact centres