Setting call centre targets is not a matter of choosing an impressive answer-time percentage and asking an outsourced team to deliver it. Australian businesses need targets that connect customer demand, staffing, service quality, commercial priorities and compliance. This guide helps you decide which measures belong in an operating brief, which should remain diagnostic, and how to turn them into an achievable plan for inbound enquiries, outbound campaigns or overflow support.
The practical decision is whether a target is useful, controllable and affordable to measure. A small business answering appointment calls may need dependable coverage and accurate booking more than a low average queue time. A sales team may care about qualified conversations and compliant follow-up. A business facing seasonal demand may need a temporary overflow target rather than a permanent staffing commitment.
1. Define the job before defining the number
When it applies: Use this principle whenever a business is moving from informal telephone support to an internal or outsourced contact centre arrangement. It is especially important when several teams use the same phone number for sales, customer service, bookings and general enquiries.
Why it works: A target only makes sense when it describes the customer job being performed. “Answer 90% of calls quickly” is incomplete if callers need identity checks, order information, appointment availability or escalation to a specialist. Start with the business outcome, then identify the service behaviour that supports it.
Turn the operating brief into customer journeys
Separate the work into contact types rather than treating every call as interchangeable. A useful first map might include:
- Inbound service: answering questions, updating records and resolving routine requests.
- Inbound sales: responding to product enquiries, qualifying opportunities and arranging follow-up.
- Appointment setting: identifying a suitable need, checking availability and confirming the booking.
- Outbound calling: contacting opted-in or otherwise lawfully contactable prospects, customers or members.
- Overflow support: taking calls when internal staff are unavailable, busy or handling a peak period.
- Escalations: recording the issue accurately and transferring or referring it to the responsible team.
For each journey, specify the caller’s likely reason for contact, the information the agent must collect, the action that completes the interaction and the circumstances that require escalation. This produces a more useful target than a single centre-wide average.
Failure mode: A business sets one target for all calls. Agents then rush complex cases to protect an average handle-time measure, while simple calls receive more effort than necessary. The resulting dashboard may look efficient even though customers repeat themselves or unresolved work accumulates.
Implementation example: A trades business receives calls for new quotes, existing-job updates and urgent rescheduling. Its brief could define three separate outcomes: capture enough information for every new quote, resolve routine job updates during the first interaction where possible, and route urgent rescheduling to the correct coordinator. The target is not merely “answer calls”; it is to make the next operational step reliable.
A sound target describes what the customer and the business should have at the end of the contact—not just what the agent did during the contact.
2. Establish a baseline before selecting a service level
When it applies: Use this approach when historical call data exists, when an existing internal team is being supplemented, or when an outsourced provider will inherit an established phone channel. If no reliable history exists, use a clearly labelled starting policy and review it after real demand is observed.
Why it works: Demand is rarely even across the day. A daily average can conceal a short, damaging peak at opening time, after a campaign email or immediately after a service interruption. Baseline analysis shows whether the main problem is volume, coverage, routing, training, callback discipline or the mix of call types.
Build a minimum useful baseline
Collect enough information to distinguish demand from performance. At minimum, examine:
- offered contacts by half-hour or another operationally useful interval;
- answered, abandoned, missed and returned calls;
- wait time distribution, not only the average;
- reason for contact and the proportion requiring escalation;
- repeat contacts for the same issue;
- outbound attempts, conversations, outcomes and follow-up actions;
- known seasonal, promotional or operational events.
Do not present an illustrative threshold as an industry fact. For example, a business might adopt a starting policy of reviewing calls in 30-minute intervals and revising it after four weeks of representative data. That is a planning choice, not a universal benchmark. The correct interval and review period depend on volume, variation and the cost of missed calls.
Failure mode: The business uses only average speed of answer. A centre can hit the average while a smaller group of callers waits much longer, particularly during a concentrated peak. The manager then invests in the wrong fix, such as asking agents to speak faster instead of adding coverage at the relevant time.
Use a target-selection matrix
The following framework turns a list of possible measures into a prioritised operating brief. Score each measure against the customer consequence, business consequence, controllability and measurement effort. The scores are a decision aid, not a promise of performance.
| Target area | Use it when | Primary question | Priority signal | Example action |
|---|---|---|---|---|
| Coverage and answerability | Missed calls or abandonment threaten revenue or access | Can customers reach a person or receive a dependable callback? | High customer and commercial consequence | Align roster coverage with peak intervals |
| Response speed | Waiting causes abandonment or poor first impressions | How long does a caller wait before a useful response? | Important, but only after coverage is realistic | Set a queue or callback objective by call type |
| Resolution | Repeat contacts and hand-offs consume time | Was the customer’s need completed or clearly progressed? | High consequence for service-heavy calls | Authorise agents to complete defined routine actions |
| Accuracy and quality | Incorrect advice, bookings or records create downstream work | Was the contact handled correctly and documented? | High consequence even at low volume | Review a representative sample against a checklist |
| Outbound outcome | A campaign has a defined audience and next action | Did the conversation produce the intended qualified outcome? | Prioritise quality over raw dials | Separate attempts, conversations, leads and appointments |
| Compliance and consent | Calls involve marketing, personal information or recordings | Can the business demonstrate lawful, controlled handling? | Non-negotiable control | Include suppression, consent and escalation checks |
Implementation example: A software company with limited historic data could begin by tracking offered calls, answered calls, abandoned calls, reason codes and completed outcomes by interval. It may make coverage and accurate categorisation its first priorities, postponing ambitious speed targets until the demand pattern is clear.
3. Set inbound coverage targets around availability and peaks
When it applies: This principle applies to customer service lines, reception, appointment enquiries, order support and overflow arrangements. It matters most when callers are likely to hang up, call a competitor or create extra work through repeated attempts.
Why it works: Inbound performance is a chain. Opening hours, roster coverage, routing, queue messaging, callback handling and escalation capacity all influence whether a caller gets a useful response. A fast answer is not a success if the agent cannot complete the next step or the callback is never returned.
Specify coverage in operational terms
A practical inbound brief should state:
- the hours and days when live answering is required;
- which call types are in scope and which are excluded;
- what happens when the queue reaches a defined condition;
- whether a callback is offered, recorded and owned through completion;
- what constitutes an urgent call and how it is escalated;
- how public holidays, campaign peaks and unexpected surges are handled;
- which information must be captured before a call is considered complete.
Use more than one service measure. For example, pair an answerability measure with an abandonment review, a callback completion measure and an accuracy check. A speed target without a completion control encourages superficial handling; a completion target without a coverage plan leaves customers unable to start the process.
Failure mode: The provider is measured on answered calls but not on abandoned calls or callback ownership. Agents may prioritise calls that are easy to close, while callers who leave a message remain invisible in the performance report.
Implementation example: An allied-health practice might define the target journey as: answer booking enquiries during agreed hours, capture patient details securely, book only within the approved availability, and escalate clinical questions rather than improvising an answer. During a seasonal demand spike, the business can add overflow coverage and a callback workflow without pretending that normal staffing can absorb unlimited demand.
Make queue data actionable
Review inbound results by interval and call reason. When a target is missed, classify the cause before changing it:
- Demand problem: more calls arrived than forecast.
- Coverage problem: the right people were not available at the right time.
- Process problem: routing or information requirements created avoidable delay.
- Capability problem: agents needed better knowledge or authority.
- Technology problem: the phone or callback path did not behave as expected.
This distinction prevents a common mistake: lowering the target to make the report look healthier when the real requirement is better scheduling or a simpler call journey.
4. Balance speed with resolution, quality and customer effort
When it applies: Use this principle for service desks, technical support, complaints, account questions and any interaction where an incomplete answer creates another contact.
Why it works: Speed is visible, but it is not the same as usefulness. A call centre can reduce handling time by transferring difficult cases, ending calls before the customer is ready or asking the customer to repeat information later. A balanced scorecard recognises both immediate responsiveness and the quality of the completed outcome.
Choose a small set of linked measures
For each call type, connect a speed measure to an outcome measure and a quality safeguard. Possible combinations include:
- response time plus first-contact resolution review;
- average handling time plus transfer and repeat-contact rates;
- callback completion plus accuracy of the recorded reason;
- booking completion plus booking-error checks;
- complaint response time plus escalation-quality review.
Average handling time can be useful for capacity planning, but it should rarely be a standalone agent target. The appropriate duration varies with the work. A short billing query and a sensitive complaint should not be forced into the same conversational mould.
Failure mode: Leaders reward low handling time without checking the customer’s next experience. Agents shorten calls, transfer more work and avoid documenting nuance. Supervisors then see a lower average while internal teams inherit unresolved cases.
Implementation example: For a membership organisation, the primary service target might be accurate resolution of routine account enquiries. A secondary measure could monitor transfers, while a quality reviewer checks whether the agent verified the member, selected the right reason code and explained the next step. The target is therefore fast enough to be practical, but not so narrow that accuracy becomes optional.
Use sampling rather than pretending every interaction is identical
A quality programme can review a defined sample of calls or records against a checklist. The checklist might assess:
- correct identification and information capture;
- appropriate use of the approved script or knowledge material;
- accuracy of the answer or booking;
- clear explanation of the next step;
- appropriate escalation;
- professional and respectful communication.
Set a rule for what happens when a critical error appears. A single serious privacy or safety issue should not be averaged away by many satisfactory calls. Escalate it, correct the process and record the remediation separately from ordinary quality scoring.
5. Design outbound targets around outcomes and Australian calling rules
When it applies: This applies to telemarketing, appointment setting, lead qualification, renewals, customer reactivation and research-related calling. It applies whether the calls are made by an internal sales team or an outsourced contact centre.
Why it works: Raw dial volume is easy to count but often a weak proxy for commercial value. A campaign should distinguish attempts, answered conversations, qualified opportunities, appointments, sales-ready referrals and requested follow-up. The correct target depends on the campaign’s purpose and audience.
Build an outcome ladder
Define the stages before the campaign begins:
- the approved audience and contact records;
- attempts made and the result of each attempt;
- live conversations with the intended contact;
- qualified conversations meeting the agreed criteria;
- appointments or other defined next actions;
- accepted hand-offs and subsequent business ownership;
- suppression, opt-out and do-not-call outcomes.
Do not use a high number of attempts to disguise weak list quality, poor timing or an unclear offer. Conversely, do not judge a campaign solely by immediate sales when the agreed job is qualified appointment setting. The target must follow the commercial hand-off.
Failure mode: A campaign rewards agents for booked appointments without checking suitability or consent. The calendar fills with poor-fit prospects, sales staff lose confidence in the leads and customers may feel misled.
Implementation example: A business-to-business training provider could define a qualified appointment as a conversation with an authorised or relevant contact who confirms a genuine training need and agrees to a scheduled discussion. “Interested” alone would not meet the target. The campaign report should show the number of attempts, conversations, qualified appointments, cancellations and opt-outs separately.
Make compliance a launch gate, not a footnote
For Australian campaigns in 2026, review the applicable telemarketing requirements before calling. The Australian Communications and Media Authority’s telemarketing guidance covers calling practices and obligations, while the Australian Government’s Do Not Call Register explains the register and its role in limiting unsolicited telemarketing calls. These are regulatory and operational controls, not performance measures to trade away for more dials.
Include documented rules for:
- which lists may be used and when they were checked or authorised;
- how opt-outs are captured and suppressed from future activity;
- what agents say when a person asks who is calling and why;
- how abandoned, wrong-number and vulnerable-person situations are handled;
- which campaign outcomes require immediate escalation;
- who owns complaints and evidence of the campaign process.
Also define the source of truth for campaign outcomes. If appointments are entered into one system and cancellations into another, a “conversion” target may be overstated. Reconcile the hand-off, not just the call report.
6. Protect personal information and make reporting trustworthy
When it applies: This principle applies whenever agents access customer records, take payment-related information, record calls, capture health or identity details, or pass information between a business and an outsourced support team.
Why it works: A target is only useful when the data behind it is defined, consistent and handled appropriately. Privacy and reporting design should be agreed before live calls begin, because retrofitting controls after an incident or disputed result is more difficult.
The Office of the Australian Information Commissioner’s APP 6 guidance addresses the use and disclosure of personal information. For a 2026 outsourcing arrangement, document the permitted purpose, access boundaries, retention approach, escalation route and responsibilities of each party rather than assuming that a service report is automatically harmless.
Define each metric so two teams calculate it the same way
For every reported target, record:
- Definition: what event starts and ends the measure?
- Population: which queues, campaigns, channels or call types are included?
- Exclusions: which calls are removed and why?
- Owner: who can change the process when performance moves?
- Cadence: when is it reviewed and when is it formally reported?
- Action: what happens when the target is missed or exceeded?
For example, “callback completed” should specify whether a voicemail counts, whether an unsuccessful attempt is included, and how quickly the callback must occur under the agreed policy. Without those definitions, two parties can report different results while both believe their calculation is correct.
Failure mode: The report contains many attractive measures but no definitions. One team reports calls answered by a person; another includes automated interactions. A target dispute follows, and managers spend time reconciling spreadsheets instead of improving the customer journey.
Implementation example: A retailer outsourcing overflow calls can agree that a completed overflow contact means the caller was answered, the reason was coded, the requested action was recorded and any follow-up owner was assigned. The weekly report can then separate completed contacts, unresolved contacts, transfers and callbacks rather than combining them into one “handled” number.
Connect marketing data without overstating causation
Where telephone outcomes are linked to digital campaigns, define the hand-off and attribution window carefully. Google’s official Google Ads conversion-tracking guidance explains that conversion tracking is used to understand actions after an interaction with an ad. That does not by itself prove that every later sale was caused by the ad or by the call centre. Treat attribution as a measurement choice with assumptions, not as an unquestionable fact.
Use a simple reconciliation such as campaign source, call reason, qualified outcome and eventual disposition. Keep “contacted”, “qualified”, “appointment”, “sale” and “revenue received” as separate stages unless the business has a defensible reason to combine them.
7. Turn the targets into a review and improvement routine
When it applies: Use this principle when targets are agreed by multiple stakeholders or when demand, scripts, products and campaign lists change regularly. It prevents the operating brief from becoming a static document that no longer matches the work.
Why it works: Performance changes for reasons that are not always agent performance. A new promotion can change call mix; a product change can increase handle time; a broken booking process can create repeat contacts. A review routine separates a target miss caused by demand or process from one caused by execution.
Run three levels of review
- Operational review: inspect coverage, queues, missed calls, urgent cases and same-day exceptions.
- Performance review: examine trends by call type, interval, campaign, outcome and quality category.
- Business review: decide whether the target still reflects revenue, customer experience, risk and capacity priorities.
Keep the action log specific. “Improve service” is not an action. “Add a peak-period callback rule for existing-customer enquiries, train the team on the new reason code, and review repeat contacts at the next meeting” is testable and owned.
Failure mode: Managers reset a missed target every month without investigating the cause. The number becomes a negotiation rather than a control, and recurring process defects remain hidden.
Implementation example: If appointment-setting quality declines after a new offer launches, compare the campaign script, qualification criteria, cancellation rate and sales acceptance rate. The correct response might be to clarify qualification or update the script, not simply demand more calls per hour.
Implementation plan: put a workable target set into service
Use the following sequence when preparing an internal or outsourced contact centre arrangement. It is deliberately ordered so that measurement follows the work rather than replacing it.
- Describe the customer journeys. List inbound enquiries, outbound campaigns, appointments, service requests, overflow calls and escalations. State the completed outcome for each.
- Gather the available baseline. Export call volumes, intervals, abandonment, outcomes, repeat contacts and campaign results. Mark gaps instead of filling them with invented assumptions.
- Choose the critical few targets. Select coverage, response, outcome, quality and compliance measures according to consequence and controllability. Keep diagnostic measures separate from commitments.
- Write the calculation rules. Define starts, stops, inclusions, exclusions, data owners, review cadence and action thresholds for every reported measure.
- Check the control environment. For Australian 2026 outbound activity, confirm list permissions, suppression, caller information, opt-out handling and escalation responsibilities using the relevant regulatory guidance.
- Run a controlled starting period. Label the first policy as illustrative where data is limited. Review real demand and call mix before making a long-term promise about coverage or speed.
- Review causes, not just scores. When a target is missed, classify demand, coverage, process, capability and technology causes. Assign one owner and one corrective action.
- Reconfirm the brief at a scheduled business review. Keep targets stable long enough to learn from them, but change them when the customer journey, campaign, opening hours or business priority materially changes.
Impératif Call Centre Partners provides outsourced inbound, outbound and overflow telephone support for Australian businesses, including customer service, enquiry handling and related contact centre work against client-defined requirements. Impératif Call Centre Partners can point you to the verified services available for organisations that need practical call handling support.
Authored with NotFair SEO
