Outsourced customer support is commonly priced around dedicated capacity, productive hours, handled work or a defined managed-service scope. The right model depends on demand stability, complexity and how much operational responsibility the provider owns.

The main cost drivers

Channel and complexity

Email, live chat, messaging and voice place different demands on staffing, response time and training. Simple first-line questions differ from technical troubleshooting, regulated conversations or retention work.

Coverage window

Business-hours coverage is different from evenings, weekends or 24/7 shifts. Wider coverage requires enough people for handovers, breaks, leave and reliable continuity.

Volume and variability

A predictable daily workload is easier to plan than sudden peaks. Share historical ticket volume, contact reasons and seasonal patterns where available.

Training and knowledge

A straightforward workflow may launch quickly. A large product catalogue, frequent policy changes or multiple languages requires more preparation and ongoing knowledge management.

Tools, reporting and service levels

Helpdesk licences, telephony, quality reviews, analytics, security controls and demanding response targets can all affect the operating design.

Common pricing structures

  • Dedicated team: capacity is reserved for the client and managed against an agreed scope.
  • Hourly or productive-time model: useful for controlled pilots or variable workloads when time is recorded clearly.
  • Per-contact model: can work for standardised, measurable work but requires careful rules for complexity and rework.
  • Managed service: combines people, workflow ownership, reporting and service standards under a defined fee.
Lowest price is not the same as lowest cost. Compare the full service: training, management, quality, access controls, escalation, reporting and continuity.

What to prepare for an accurate estimate

  • Channels and hours required
  • Monthly volume and peak patterns
  • Top customer contact reasons
  • Languages and time zones
  • Existing helpdesk, CRM and communication tools
  • Expected response and escalation standards
  • Training materials and approval process
  • Pilot length and review criteria

How to compare proposals

Ask each provider to state assumptions, what is included, what changes the price and which responsibilities remain with the client. A proposal should explain the team structure, launch work, quality process, reporting, security expectations and the route for scaling up or down.

Kobitel’s approach

Kobitel does not publish a single price for every operation because the service scope matters. We begin with a free support audit, then define a focused pilot around the channel, workload, coverage and controls you actually need. See our delivery model or request a scoped estimate.