This page is designed for a direct, fair conversation: what is visible in the systems, where the customer-service numbers are behind the peer range, what work is already on par, and what needs to be visible every day.
Data boundary: Hubstaff and tool-use data were freshly fetched. Front and Quo collection stopped around Aug 17 at 1:01 PM HST, so email, customer-call, and follow-up counts do not include the remainder of Aug 17 or Aug 18. A missing measurement is shown as a dash—not silently counted as zero.
Headline position
Tracked time
45.0 h
6 tracked days
Customer calls
12
peer range: 16–47
Credited sales
0*
peer range: 11–23
First-touch pairs
4
peer range: 19–129
Activity
22.7%
peer range: 53.3–72.3%
The central question for today: Maria logged 45.0 hours, 19 recruiting calls, 12 customer calls, and 99.1% core-work classification. The conversation needs to reconcile the remaining time with specific customer-service tasks, queues, tools, or approved offline work.
Maria compared with the anonymized peer range
This preserves privacy by showing the range across the other three VAs rather than naming or exposing any individual coworker’s scorecard.
Metric
Maria
Peer range
What it means
Schedule adherence
80.4%
60.2–98.0%
Not the lowest, but includes 1 missed day and 1 short day that need context.
Hubstaff activity
22.7%
53.3–72.3%
30.6 points below the lowest peer; review as a visibility signal, not a standalone productivity verdict.
Core work
99.1%
98.6–99.4%
On par. It shows approved work domains were open, not that enough outcomes were completed.
B2C customer calls
12 3 in · 9 out
16–47 2–14 in · 14–33 out
Both incoming and outbound customer contact are below the peer range.
Candidate calls
19 5 in · 14 out
0–4
Real work, but a separate lane; it does not replace customer calls.
Sales bookings
0*
11–23
Lowest visible credited result; two unknown creator-ID rows need attribution review.
Sales volume
$0*
$3,399–$5,289
Same preliminary-ledger caveat as sales bookings.
Sent support emails
8
25–54
Sent-message events; draft-only work is not visible in this feed.
First-touch pairs
4
19–129
Below the lowest peer; this is a Front conversation-response measure.
Customer notes
0
0–11
At the low end; every customer call should leave a useful next-step record.
Reopen rate
—
3.2–37.7%
Not judged for Maria: she has only 8 resolutions, below the 10-resolution minimum.
Peer ranges are descriptive, not automatic quotas. The first week of improved measurement should establish a fair steady-state target based on assigned queue volume and scheduled days.
Call and sales detail
B2C incoming
3
customer line
B2C outbound
9
about 1.3 per scheduled day
Candidate incoming
5
recruiting lane
Candidate outbound
14
recruiting lane
Phone talk
61.0 min
19.6 customer · 41.4 recruiting
Customer calls are the customer lane.
Maria’s 12 B2C calls are 3 incoming and 9 outgoing. Candidate calls are tracked separately so outbound recruiting work cannot be used to explain away a customer-support gap.
Sales needs a traceable next step.
Every sales call should end in a booking reference, a follow-up date, or a documented reason the customer did not book. The current ledger shows 0 credited bookings* and $0*.
Why the visible numbers are behind
1
Customer-contact volume is low.Maria has 12 B2C calls versus a peer range of 16–47, including 9 outbound calls versus 14–33. The 19 recruiting calls are real work, but they are a distinct assignment lane.
2
Support follow-through is not visible at the same level.There are 8 sent-email events and 4 qualifying first-touch pairs, compared with peer ranges of 25–54 and 19–129.
3
Customer documentation is missing.There are 0 customer-channel notes for 12 B2C calls. If work happened in another tool or offline, that location and the outcome need to be identified.
4
Activity is materially below the peer pattern.22.7% is 30.6 percentage points below the lowest peer. Calls, meetings, and offline work can be underrepresented, so the practical fix is to reconcile those activities—not to chase keyboard movement.
5
The recorded hours need a task-level explanation.Core work is 99.1%, but core classification only says where computer time was spent. It does not prove customer calls, follow-ups, completed sales, or documented outcomes.
Recommended daily standards
These are minimum starting standards for every scheduled workday, subject to adjustment only when assigned queue volume or manager direction requires it.
1
Answer the B2C queue
When assigned, answer at least 90% of offered customer calls, or return the missed call the same business day. Track offered, answered, missed, and returned—not just answered totals.
2
Make customer calls
Complete at least 5 full customer phone calls every scheduled workday when eligible cases exist. Candidate calls, recruiting calls, voicemails, and no-answers do not count toward this customer target.
3
Work BookingKoala Leads
Use the BookingKoala Leads module for every customer follow-up. Update the lead status, result, next step, and next follow-up date before moving on.
4
Reconcile the day
Before signing off, account for hours by lane: customer support, sales follow-up, recruiting, documentation, meetings, and approved offline work.
Suggested 8-hour segmentation: 3 hours B2C inbound/support coverage · 2 hours recruiting/candidates · 2 hours outbound customer and sales follow-up · 1 hour documentation, inbox cleanup, and daily reconciliation. Adjust when a live queue or manager assignment requires it, but keep the lanes visible.
Required customer follow-up workflow
Every customer interaction needs one short operational record and one detailed record when the issue affects service delivery. The systems have different jobs.
1. BookingKoala Leads = follow-up control
Every lead or customer follow-up belongs in the Leads module in BookingKoala. Update the status, what happened, the next action, who owns it, and the next follow-up date. A customer is not “followed up” until the lead record shows the next step.
2. Quo = brief call summary
After each customer phone call, add a short Quo comment: reason for the call, result, and next step. Keep it brief so the call history is easy to scan; Quo is not the place for the full operational story.
3. Slack = detailed customer record
Put the detailed message in the correct channel: #customer-residential or #customer-business. Include the customer issue, what was promised, who needs to act, and the deadline.
4. Escalate service-impacting issues
Rescheduling, complaints, cancellations, missed service, refunds, special requests, and other service-impacting issues require the detailed Slack post. Do not leave the full explanation only in a Quo comment or only in a private note.
Simple rule: BookingKoala Leads tells the team what follow-up is due; Quo briefly records the call; Slack carries the detailed customer-service context. Complete all three when the interaction requires all three.
Metric definitions
First-touch pairA customer sends an inbound message in Front, and the first recorded teammate action afterward is identified—reply, comment, tag, status change, or another Front action. It is not every follow-up or every email. Maria has 4 qualifying pairs.
First-touch medianThe middle response time, in minutes, from the customer’s inbound message to the first teammate action. Maria shows — because only 4 qualifying pairs were found; the minimum sample is 5.
Reopen rateThe percentage of conversations a VA marked resolved that received another inbound customer message within 48 hours. Maria shows — because 8 resolutions are below the 10-resolution minimum.
Sent support emailsFront out_reply plus outbound events. These are sent-message events, not draft counts. Maria has 8. Draft-only work is not visible in this feed.
Customer noteA documentation entry recording the customer issue, action taken, next step, owner, and due date when relevant. Maria has 0 in the measured window.
Schedule adherenceTracked Hubstaff time divided by scheduled hours on scheduled days. Maria is 80.4%, with 1 missed and 1 short day. The reason still needs manager clarification.
Hubstaff activityKeyboard and mouse activity during tracked time. It is a visibility signal, not a complete productivity verdict; phone calls, meetings, and offline work can register less activity.
Core workThe share of classified computer time mapped to approved work or recruiting domains/apps. Maria is 99.1%, on par with the peer range of 98.6–99.4%. It describes computer location, not completed outcomes.
Sales creditedUnique charged bookings attributed to the VA in the preliminary ledger. Two rows use an unknown creator ID, so the 0 credited result is marked with an asterisk pending attribution review.
End-of-day check-in
Use this to make the next review evidence-based. Include a count and a short outcome, not only “worked on.”
Date:
Scheduled hours / Hubstaff hours:
B2C calls offered / answered / missed / returned:
B2C outbound customer calls / outcomes (minimum 5 completed):
Candidate calls in / out:
BookingKoala Leads updated / next follow-up dates:
Quo brief comments completed:
Detailed Slack posts in #customer-residential or #customer-business:
Support emails replied / sent / drafts still open:
First-touch conversations completed:
Customer notes added:
Sales bookings / booking references / follow-up dates:
Other approved work and where it is recorded:
Uncaptured or blocked work needing manager help:
Fairness and next review
What is already on par: core-work classification (99.1%), no measured non-work time, and meaningful recruiting activity (19 calls). The focus is not to erase recruiting work; it is to separate it clearly from customer-service expectations.
Next review: after one full week of complete offered-call, answered/missed, customer follow-up, email, note, sales-reference, and time-by-lane records. At that point, targets can be calibrated to actual assignment volume and quality—not just raw totals.
*Sales are preliminary because two ledger rows have an unknown creator ID. Quo text-message counts are not reliable enough to report. Data window and source freshness are shown at the top of this page.