When someone doesn’t respond, you’re left wondering: Are they busy? Is their internet down? Did they forget about the meeting? <\/p>\n\n\n\n
Without clear availability expectations, you’re dealing with the same constant anxiety about whether work is actually getting done. <\/p>\n\n\n\n
Resentment builds on both sides because VAs feel always “on call” while employers feel ignored.<\/p>\n\n\n\n
The solution isn’t more surveillance. It’s clear. When everyone knows the rules, following them becomes effortless. Here\u2019s how<\/p>\n\n\n\n
This is the non-negotiable window when your VA needs to be online and responsive. Three to four hours of overlap is the sweet spot for most US-Philippine working relationships. <\/p>\n\n\n\n
It’s enough time for real-time collaboration without forcing anyone to work through their entire night. Use these hours for meetings, urgent questions, and collaborative work. <\/p>\n\n\n\n
Everything else can happen asynchronously around this core window.<\/p>\n\n\n\n
Not every message needs an immediate response, but every channel should have a defined expectation.<\/p>\n\n\n\n
Urgent channels like Slack or WhatsApp might require responses within 15 to 30 minutes during core hours. After-hours messages shouldn’t expect any response until the next business day unless you’ve explicitly arranged on-call coverage.<\/p>\n\n\n\n
Your call-out protocol is the step-by-step process for what happens when someone can’t work their scheduled hours.<\/p>\n\n\n\n
Planned absences like vacations or medical appointments should be communicated three to five days in advance. This gives you time to redistribute work and reschedule meetings.<\/p>\n\n\n\n
Same-day call-outs for illness should be reported as soon as possible. First thing in the morning is ideal, but if someone wakes up seriously ill, give them until mid-morning.<\/p>\n\n\n\n
Mid-shift emergencies can’t be predicted. The expectation is simple: communicate as soon as safely possible, even if it’s just “family emergency, will update later.”<\/p>\n\n\n\n
Designate one primary channel for absence notifications. For most teams, this is either direct message on Slack or a text message to a specific number. It should be something you check consistently.<\/p>\n\n\n\n
Establish a backup channel for when the primary one fails. If Slack is down or someone’s phone is broken, they should know to email you or message on WhatsApp.<\/p>\n\n\n\n
A good call-out message covers three things:<\/p>\n\n\n\n
The fact that they’re unavailable and how long they expect to be out. “I’m sick today and won’t be able to work” or “Family emergency, need to take tomorrow off.”<\/p>\n\n\n\n
Any urgent tasks that need coverage. If they were supposed to send an important email or attend a client meeting, flag it immediately.<\/p>\n\n\n\n
Expected return time. Even a rough estimate helps. “I’ll be back tomorrow” or “I’m not sure yet, will update you by end of day.”<\/p>\n\n\n\n
Your VAs don’t owe you detailed medical information or personal crisis details.<\/p>\n\n\n\n
Set a basic expectation: notify as early as possible, even if it’s just “too sick to work today.” If it extends beyond one day, check in once every 24 hours with a simple update.<\/p>\n\n\n\n
In the Philippines, medical certificates are standard for absences lasting three or more consecutive days. This protects both parties if questions arise later.<\/p>\n\n\n\n
Immediate notification when possible, but understand that someone dealing with a hospitalized family member might not message you for several hours. When they do reach out, keep your response simple: “Take the time you need, let me know when you’re able to come back.”<\/p>\n\n\n\n
In the Philippines, these are frustratingly common. Typhoons knock out power for days. Internet service providers have random outages. Entire neighborhoods lose connectivity without warning.<\/p>\n\n\n\n
Your VA should notify you as soon as their connection drops if they’re in the middle of their shift. If the outage happens before work hours, they should message you using mobile data.<\/p>\n\n\n\n
Establish a backup plan for recurring outages. Can they work from a caf\u00e9 with Wi-Fi? Do they have mobile hotspot capability? These solutions cost money, so discuss upfront whether you’ll reimburse these expenses.<\/p>\n\n\n\n
Specify how far in advance requests should be submitted. Two weeks is standard for single days, longer for extended absences.<\/p>\n\n\n\n
Define your approval process. Will you respond within 24 hours? Does time off get auto-approved after a certain number of days without response?<\/p>\n\n\n\n
Clarify whether time off is paid or unpaid, and if there are any blackout periods. If you have critical business periods like month-end closing, communicate these dates clearly.<\/p>\n\n\n\n
Purpose-built time tracking tools create automatic records of when people actually worked. These systems should show scheduled hours versus actual hours, making patterns visible.<\/p>\n\n\n\n
Time tracking also protects your VAs. When you can clearly see they worked their full hours despite starting late one day, there’s no room for unfounded concerns.<\/p>\n\n\n\n
Create a dedicated channel for availability updates. A simple Slack channel or shared calendar where people post when they’ll be late, leaving early, or taking time off.<\/p>\n\n\n\n
Set status indicators consistently. “Available” means available for conversation. “Busy” means working on focused tasks but still checking messages. “Away” means genuinely not at the computer.<\/p>\n\n\n\n
Every availability policy and call-out procedure should live in a central location. Include examples of good call-out messages. Add FAQs for common scenarios: “What if I’m sick but can work reduced hours?” “What happens if I miss the call-out deadline?”<\/p>\n\n\n\n
Update this documentation whenever you discover gaps.<\/p>\n\n\n\n
The first time someone doesn’t follow your call-out procedure, assume good faith. Have a direct conversation: “I noticed you were offline this morning without notification. For future reference, I need a message on Slack by the time your shift starts. Can you walk me through what happened?”<\/p>\n\n\n\n
These conversations often reveal gaps in your communication.<\/p>\n\n\n\n
Repeated no-shows signal a different problem. Document each instance clearly. When did the absence occur? What communication did you receive? What was the impact?<\/p>\n\n\n\n
After the second or third occurrence, be direct: “This is the third time in two weeks you’ve been unavailable without notice. I need reliable communication about your availability. If this continues, we’ll need to discuss whether this arrangement is working.”<\/p>\n\n\n\n
When someone’s dealing with genuinely catastrophic circumstances like serious accidents or natural disasters, your immediate response should be: “Take whatever time you need, I’ll handle the work side.” You can sort out details later.<\/p>\n\n\n\n
These situations are rare. If they’re happening constantly, trust your instincts about what’s actually going on.<\/p>\n\n\n\n
Your written policies only work if supported by the right expectations.<\/p>\n\n\n\n
If you don’t have a formal call-out procedure yet, start small.<\/p>\n\n\n\n
This week, write down your core expectations about availability and call-out notification. Keep it to one page. Share it with your VA and ask for their input.<\/p>\n\n\n\n
This month, implement those expectations and see where confusion occurs. When someone asks “what should I do if…” that’s a gap in your documentation. Fill it immediately.<\/p>\n\n\n\n
Next quarter, review how well your system is working. Make adjustments based on real experience.<\/p>\n\n\n\n
The perfect system doesn’t exist. Your goal is creating something clear enough to follow, flexible enough to handle real life, and documented well enough that nobody has to guess what’s expected.<\/p>\n","protected":false},"excerpt":{"rendered":"
Managing remote Filipino VAs requires crystal-clear availability protocols. From core overlap hours to emergency notifications, this guide covers everything you need to build accountability without micromanagement.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[32,36,9],"class_list":["post-166","post","type-post","status-publish","format-standard","hentry","category-for-employers","tag-management","tag-time-management","tag-virtual-assistants"],"_links":{"self":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/166","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/comments?post=166"}],"version-history":[{"count":2,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/166\/revisions"}],"predecessor-version":[{"id":275,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/166\/revisions\/275"}],"wp:attachment":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media?parent=166"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/categories?post=166"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/tags?post=166"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}