Rep Requests — How Teamflect Measures Rep Additions, Removals and Modifications

Rep Requests — How Teamflect Measures Rep Additions, Removals & Modifications

What gets measured, where the data comes from, and how these goals connect

Outcome: You understand how your daily rep work drives Teamflect goals (no manual updates required)

What this lesson is really about

Rep additions, removals, and modifications are high-volume tasks — but the standard cannot drop when the workload rises. In 3 hours, your work must be done accurately, captured correctly, and closed cleanly so the client experience and audit trail stay strong.

Speed standard: Rep requests must be completed within 3 hours

Case discipline: Each rep request creates an auto closed case

Client feedback: Closed work triggers surveys/ratings

Lesson audio Press play to listen.

Important: The team does not manually update these Teamflect goals. They are linked to backend spreadsheets fed by your activity in the systems. That means your measurement depends on how cleanly you work, not what you type in Teamflect.

Plain language: Teamflect is your scoreboard. Zoho is the match. If the Zoho recordkeeping is correct, the scoreboard updates itself.

The 3 connected goals this lesson links together

Goal A: Maintain a 100% Case Closure Rate (Closed / Total) using Zoho case status tracking
Goal B: Achieve an average Client Satisfaction Score of at least 70% (survey-based)
Goal C: Maintain a positive Client Happiness Rating (Zoho Desk post-resolution feedback)

Why this matters: A single wrong rep linked to the wrong FSP is not a “small mistake”. It creates reputational risk, client trust issues, and rework that damages service ratings.

The measurement map: how one rep request flows into all three goals

This is the “cause and effect” chain you must understand.

1) You complete the rep request in Zoho

Rep Addition / Removal / Modification is processed and marked complete on our side (within 3 hours).

›

2) A case is created & closed

Each rep request creates a closed case automatically. This supports Case Closure Rate.

›

3) Client feedback & ratings are triggered

Closed work triggers a client survey/feedback. This drives Client Satisfaction and (when Desk is used) Happiness Rating.

Key connection: Rep work quality impacts three measurements at the same time:

Accuracy + closure discipline → Case Closure Rate
Client survey outcome → Client Satisfaction Score
Desk ticket experience (e.g., “Rep added elsewhere”) → Client Happiness Rating

1) Where the Teamflect numbers come from (no manual updates)

›

These goals are linked to backend spreadsheets fed by system activity. The practical meaning is: your Zoho recordkeeping is the source of truth. If your statuses, closures, ownership fields, notes, and completion actions are correct, the measurement updates automatically.

What you do: Work correctly in Zoho + close out cleanly.
What you don’t do: Manually “push progress” in Teamflect for these goals.

Reminder: When a case is auto-created, you still must go to Cases and edit the case by selecting who logged the case. This is important for correct attribution and reporting.

2) Goal A — 100% Case Closure Rate (Closed / Total)

›

This goal measures whether the team consistently closes work, instead of leaving cases open and unresolved. In rep work, this is supported by the system creating a closed case per rep request — but it still depends on correct linking, correct fields, and correct “logged by” attribution.

What improves Case Closure Rate

Completing the rep request in Zoho within the 3-hour standard
Ensuring the auto case is correctly attributed (edit case → select who logged the case)
Ensuring no “stray” open cases are left behind for the same rep request

Common risk: If you rush or feel overwhelmed, you may complete the request but miss a critical admin step (e.g., wrong FSP, wrong rep, wrong reference). That triggers rework and damages downstream ratings.

3) Goal B — Client Satisfaction Score (≥70%, survey-based)

›

When the rep request is completed and the case is closed, the client receives a survey to rate the service. That survey score feeds the Client Satisfaction goal. This is why “completion” is not just about finishing the admin — it’s about finishing with quality and clarity.

Your influence: Even when you do everything correctly, clients may be slow to respond. But when they do respond, the score reflects your accuracy, speed, and how clear the completion communication felt.

What typically improves client survey ratings

Correct rep linked to the correct FSP (no “fix it please” follow-ups)
Fast turnaround within 3 hours (clients feel taken care of)
No missing evidence or steps that delay completion (e.g., DOFA upload, supervision checks, etc.)
Clear completion email and no confusion about what was done

Reality check: A client may not complain to us directly — but they will score the survey lower if they had to chase, correct us, or redo information because of an avoidable mistake.

4) Goal C — Client Happiness Rating (Zoho Desk ratings)

›

This goal is driven by Zoho Desk feedback on resolved tickets. It becomes relevant when a rep request requires a Desk ticket — for example, “Rep Added Elsewhere” where we pause the process, request client instruction, and track the matter on Desk.

Key link: If a Desk ticket is created, the client’s “support experience” (timeliness, clarity, professionalism) can influence the Happiness Rating. That means rep work can impact this goal whenever the workflow touches Desk.

What clients experience in Desk matters:

Do they understand what is happening and why?
Did we keep them updated while the ticket was on hold?
Were our notes and instructions clear and consistent?

5) The “overwhelm rule”: what to do when volume is high

›

We handle many rep requests. The workload can be intense — but rep work is one area where we cannot afford “volume mistakes”. There have been instances where reps were added to the wrong FSP. That is exactly what this measurement system is trying to prevent.

If you feel overwhelmed:

Pause and check before you submit or mark complete
Ask the team leader for help early — don’t wait until it becomes a mistake
Use a quick checklist: Rep identity, FSP identity, request type, required evidence, final confirmation

Mindset: Speed matters (3 hours), but accuracy protects the client and the business. We aim for both.

6) What not to do (to protect the measurement)

›

Do not:

Try to “fix” the Teamflect goals manually — they pull from backend spreadsheets
Leave out the “who logged the case” step (incorrect attribution affects reporting)
Close a workflow without confirming the correct rep + correct FSP + correct request type
Assume “the system will catch it” — the system only reflects what we captured

Do: Treat each rep request as a high-trust task — small admin errors create big compliance and client risks.

Screenshots (how the goals look in Teamflect)

These are for understanding the measurement, not for manual updating.

Teamflect goal — 100% Case Closure Rate (Closed / Total) — **Screenshot 1:** Case Closure Rate goal — driven by clean Zoho case status tracking and closure discipline.

Teamflect goal — Client Satisfaction Score of at least 70% — **Screenshot 2:** Client Satisfaction Score (survey-based) — influenced by accuracy, speed, and clarity at completion.

Teamflect goal — Positive Client Happiness Rating (Zoho Desk) — **Screenshot 3:** Client Happiness Rating — driven by Desk ticket experience on resolved support issues (e.g., “Rep added elsewhere”).

Remember: These are linked to backend spreadsheets from Zoho and will auto-update. Your job is not to update Teamflect — your job is to produce clean, correct, auditable work in the systems.

Play & Learn (quick measurement check)

Choose the best answer based on how rep work affects Teamflect.

Scenario

You completed a rep addition within 3 hours. The system created a closed case. The client later rates the service low. Which goal is most directly impacted?

Correct. The client’s survey rating feeds the Client Satisfaction Score goal. Case Closure is supported by the closed case, but the rating affects the satisfaction metric.

Not quite. Survey scores drive Client Satisfaction. Happiness Rating is Desk-ticket feedback. Teamflect updates automatically from backend sheets.

Scenario

You opened a Zoho Desk ticket for “Rep added elsewhere”, kept the client updated, and resolved the ticket professionally. Which goal can this improve?

Correct. Desk ticket feedback drives Client Happiness Rating. Strong communication and clear resolution help this metric.

Not correct. Desk tickets can influence Client Happiness Rating through post-resolution feedback. Cases and surveys influence other goals.

Previous Topic

Back to Lesson