We agree where the routine stops before it starts.
Opryq provides remote administrative support for small businesses, from Austin, Texas. You approve the task and the wording. The assistant handles the agreed routine and returns decisions that sit outside it. This is human office help, not autonomous software.
Scope and fees in USD are agreed separately before work begins. The cost depends on volume and frequency, access requirements, approval rules and the review needed. An inquiry does not book capacity or authorise work.
Access / a deliberate boundary
A task permission is not permission to run the business.
The useful starting question is not “Which password do you need?” It is “Which action is the assistant allowed to take?” That answer determines the access request, and it keeps a routine job from quietly expanding into responsibility you did not intend to delegate.
Use a task-specific invitation or delegated access where your system supports it. Keep account ownership with your business. Passwords and recovery codes do not belong in the public inquiry form or support chat.
Read the working sequence
Make the next action clear to both sides.
- 01
Define a task that has an end.
Describe the work in terms of an action and a completion check. “Manage the inbox” leaves too much open. “Review messages in the agreed folder and draft replies from the approved sheet” says where the work starts without granting authority to settle every question in the account.
Identify the person who can approve the instruction and answer exceptions. A small business may have several people requesting help, but contradictory instructions need a named decision route. The assistant should not have to choose whose commercial preference wins.
- Before agreement
- Confirm the task boundary, expected frequency, channels and who owns approvals. Discuss fees in USD and the practical arrangements before any work starts.
- 02
Approve the instruction and limit access.
Bring the wording you already use, even if it needs a clearer stop rule. An instruction should say what can be done without further approval and what must remain untouched. A reply template that answers a routine question must not become permission to promise a refund, alter a fee or accept a new obligation.
Then match access to those actions. If a task only needs a defined folder or calendar, broad account permissions are not the starting point. Where a tool cannot support the proposed limits, discuss a different route or a narrower task rather than quietly accepting more access.
- Approval evidence
- Keep a current instruction with an identifiable approval and version. Agree the place where updates are recorded so an old message does not become the accidental source of authority.
- 03
Review the initial task before repeating it.
The first task is a check of the instruction, not evidence that every future case is covered. Compare the result with the agreed completion check. Look for missing context: an invitation without the correct time zone, a record changed without a source, or a drafted response that is accurate but not approved for sending.
Agree how the initial review happens and which actions wait for it. There is no fixed review period promised on this site. A task can stay in draft or paused status while a missing decision is resolved, rather than being marked complete to keep the queue looking tidy.
- Release to routine
- Record any correction to the instructions, confirm that it applies to the next occurrence and keep the approval boundary visible.
- 04
Log the exception where it can be answered.
An exception is a specific question, not an admission that the routine failed. State what prevented the next action and what decision is needed. Keep it separate from completed work. “Awaiting approval to send the revised wording” is useful; “follow up later” leaves the same uncertainty for the next person.
If a repeated exception reveals a gap in the instruction, ask for an approved update. Do not treat yesterday’s one-off permission as a permanent expansion of scope. That is how a harmless administrative shortcut turns into an unintended commercial promise.
- While waiting
- The affected action stays paused. Other agreed work can be considered separately; a silence or unread message is not approval to continue the blocked item.
- 05
Hand back the record and remove access.
At a change of scope or the end of the arrangement, agree which work is complete and which questions remain open. Transfer the working instructions and the status record through the agreed channel. Do not leave a new owner to infer status from a collection of drafts.
Review delegated permissions, recurring notifications and any scheduled actions that might continue after handoff. Your business retains ownership of its accounts. The closure plan should identify who revokes access and which material is returned or removed, subject to agreed requirements and applicable law.
- At offboarding
- Use the handoff to reconcile outstanding work, not to declare an unconditional clean slate. Any disputed task is reviewed against the instruction that applied to it.
Instruction / specimen
Write down the permission, not just the desired result.
This specimen shows the structure of an instruction. It is not a completed client agreement or an example of work already delivered. The words in the final instruction need to fit your actual task.
Routine instruction record
Proposed format / no client data
- Trigger
- Specify what puts an item into the queue. Receiving a request does not, by itself, authorise every action mentioned in it.
- Permitted action
- Describe the approved operation and the source of truth. Say whether the assistant may send, draft only, change a field or prepare a change for review.
- Stop condition
- Name the mismatch that requires your decision. A missing source, conflicting instruction or request outside the approved wording should have a clear destination.
- Completion evidence
- Define what is recorded when the task is finished. A status should distinguish action taken from action proposed; a draft is not a sent reply.
- Change authority
- Identify who approves a revised instruction and how the current version is recognised. New permissions are explicit rather than inferred from informal conversation.
A useful instruction can be short. It cannot be silent about the part of the task that carries a business decision. Your assistant needs enough context to recognise that boundary, without collecting unrelated customer records to make the task sound more detailed.
Handoff / keep status honest
Completed work and open questions belong in different places.
A single “done” list hides the decisions that still need a business owner. The handoff separates recorded actions from items awaiting approval, so you can read it without opening every underlying message.
Agree the reporting frequency with the scope. A daily checklist does not mean a promise of continuous monitoring, and a report does not replace an urgent channel that your business needs to operate independently.
Completed
What was done, under which instruction, and where the completion evidence can be found.
Awaiting decision
What is paused, why it is paused, and which approval allows the next action.
Practical fit
You keep the decisions. We take on the repeat work.
Virtual office assistance makes sense when a routine can be described and the business can answer the exceptions. It is less useful when every item requires a new policy decision. In that case, begin by defining a smaller task rather than outsourcing an undefined role.
If instructions are still rough
You can still inquire. Describe one recurring action and the current difficulty in ordinary language. We can discuss what would need to be clarified before it is suitable for remote support. Sending a question does not commit you to a service.
If you need an independent decision-maker
This is not an executive substitute or regulated advisory service. Emergency dispatch and around-the-clock answering are outside the offer. A business that cannot supply an approval route needs a different arrangement.
Questions about errors go to [email protected] for review against the agreed instruction. Include a general description of the issue first, not a full export of private records. The service and website terms explain the boundary on guarantees and separately agreed arrangements.
Start with the work
Bring one routine that needs an owner.
Tell us the action you repeat and the point where you need to remain involved. You do not need to send account credentials or private client details to begin.
Discuss a taskChoose the scope before counting the hours.
The weekly workload planner records your own frequency and timing estimates. Use it after deciding what an occurrence means. It calculates entered minutes only; setup and unentered review time still need discussion.
For the boundaries of a particular task, read calls and email, appointment scheduling, CRM cleanup, document organisation or daily administration. Each page owns the rules specific to that work rather than treating every administrative request as interchangeable.
General descriptions are enough for an initial conversation. Read the privacy notice before submitting information, and use the data request route for questions about information already provided.