Outsourced Philippines guide
Write a Service Credit Rule for Missed Outsourcing SLAs
Turn a service dispute into a calculation with measurable levels, documented exclusions, a capped formula, and a short claim path.
A missed service level often ends in an argument about intent. The client remembers a late response, the provider points to an ambiguous clause, and both sides spend time reconstructing what was promised. A written service credit rule turns that argument into a calculation. The rule should be simple enough to apply in a week and specific enough to be fair when the facts are disputed.
On this page
Define the service level in measurable terms
Write each service level as a number, a clock, and a population. For example, ninety percent of priority tickets receive a first response within four business hours. State when the clock starts, when it stops, and which tickets are excluded. A service level that says timely response cannot be measured or credited, and it gives both sides room to argue about what timely meant.
Separate response time from resolution time, because they measure different things. A team can acknowledge quickly while a fix waits on a vendor. If the client cares about resolution, define what counts as resolved and who confirms it. Put both measures in the schedule so the credit rule points at the right one, and label the dashboard with the same definition the contract uses.
Name the exclusions before the first miss
List the conditions that pause or exclude the clock, such as a client-side approval, a missing access grant, or a documented vendor outage. The list should be short and tied to evidence the team can produce. Write it into the schedule before the first missed target so both sides know the rule. An exclusion added after a miss looks like an excuse, even when it is legitimate.
Require a timestamp and a source for each exclusion. A note that says the client was slow is not evidence, while a ticket showing the approval request and the reply time is. The provider should log the pause when it happens, not reconstruct it at the end of the month. Good records make the exclusions credible and keep the monthly review focused on the few cases that need a decision.
Set a formula and a cap
Use a formula the client can calculate without a spreadsheet expert. One common approach is a percentage of the monthly fee for each missed service level, with a cap on the total credit. Keep the number of tiers small so the rule does not become a second negotiation. State whether credits apply to the next invoice or the current one, and show the line item on the invoice so the client can see it.
A cap protects both sides from a single bad month turning into an unsustainable loss. It also prevents the credit from becoming larger than the value of the service. Write what happens when the same service level misses in consecutive months. A pattern may deserve a review rather than a larger credit, because the credit treats the symptom while the review can fix the cause.
Make the claim path short and visible
Tell the client where to send a claim and what to include. A short form with the date, the ticket, the expected time, and the actual time is enough. Acknowledge the claim within two business days and give a decision date. The process should not require the client to prove the miss from scratch, and it should not depend on a single account manager who may be on leave.
Keep a shared log of claims, decisions, and credits applied. The log lets both sides see whether the rule is working and whether the same issue keeps recurring. Review it in the monthly service meeting rather than waiting for a renewal. Transparency here prevents small disputes from becoming trust problems, and it gives the provider a chance to explain a legitimate exclusion early.
Apply the rule the same way every time
Train the account team to apply the rule without improvising. If a miss is unclear, escalate it to the named owner rather than making a goodwill call in the moment. Record the reasoning beside the decision so a later reviewer can follow it. Consistency matters more than generosity in a single case, because a different answer for two similar clients undermines the rule.
Sample a few claims each quarter and check the evidence, the calculation, and the timing. Look for claims that were never filed despite a visible miss, because those gaps can signal a reporting problem. Correct the dashboard or the notice rather than blaming the client. The rule only builds trust when both sides can see the same numbers and the same path to a correction.
Review the rule when the service changes
A new channel, a new client segment, or a change in tooling can make an old service level meaningless. Put a review date on the schedule and revisit the thresholds with real data. Ask whether the measure still reflects what the client values. Update the credit formula at the same time so the two documents do not drift, and tell the client what changed before the next billing cycle.
Keep prior versions and the reason for each change. That history helps a new account manager explain why the current rule looks the way it does. It also prevents a client from being held to a target that was retired. A service credit rule is a living part of the contract, not a one-time clause, and it should be reviewed with the same care as the pricing schedule.
Sources and next steps
Continue with operations support, then confirm scope, authority, and review ownership before expanding the role.