A VP of CX at a mid-market healthcare network is staring at next year's operating plan. Patient-access volume is up 40 percent year over year. Two of her three current vendors are missing SLA. The procurement deck on her desk has logos from the usual enterprise BPOs, all selling cost-per-seat math that does not reconcile with what her CFO will sign off on. She does not need another vendor pitch. She needs to know which service shape matches the work she actually has.

That is the question this page answers. Invictus runs four distinct service shapes, each with a defined scope. The right starting point is the shape that fits the work in front of you. The other three compose around it as the relationship grows.

The four service shapes

1. Nearshore contact-center operations

Full-service inbound and outbound contact center across voice and digital channels (chat, email, SMS, voicemail). Operations run from Belmopan, Belize, with US-business-hour overlap across both coasts and 24/7 coverage available where the work requires it.

Typical work in this shape:

• Customer service across voice and digital

• Technical support, tier-1 and tier-2

• Sales overflow and retention

• Claims intake and first notice of loss

• Patient access, appointment confirmation, and after-hours triage routing

• Account servicing and dispute resolution

Vertical practice leads sit alongside the operating teams in each industry served. A supervisor handling a real-time call on a healthcare account has direct access to the healthcare practice lead. Industries with named operating bench today include healthcare, financial services, insurance, logistics, retail and consumer brands, telecommunications, and consumer technology.

Agent coverage is native-English bilingual, with 150+ language real-time bidirectional translation available through the iKunnect platform's multilingual layer. That means a single call can move across English, regional Spanish (Cuban, Venezuelan, Mexican, Castilian), Portuguese, Mandarin, and beyond without a translation queue interrupting the customer.

2. Back-office services

The operational long tail that lives behind the front-line contact center. Lower visibility than voice work, often higher per-transaction value, because errors here compound into customer-facing problems downstream.

Typical scope:

• Document processing and invoice handling

• Claims documentation and adjudication support

• Account reconciliation

• Exception management and escalation queues

• Application intake and verification workflows

• Data entry against regulated documentation standards

Pricing here is typically per-transaction or per-document with documented accuracy bars (for example, 90 percent or higher accuracy on invoice processing at a defined throughput). The same QA discipline that runs the contact-center side runs the back-office side: 100 percent of work reviewed, weekly supervisor cadence, audit logging on every transaction where the controls require it.

This shape lands well for operations where the contact center is already handled (in-house or with another partner) and the back-office volume is the next bottleneck. It also runs as a complement to the contact-center shape, where the same case that started as a customer call ends as a back-office workflow without a vendor handoff in the middle.

3. Enterprise GBS (Global Business Services)

Bundled BPO operations plus iKunnect platform for enterprises that want a single operating partner across the entire customer-facing function. This shape replaces the multi-vendor model (one vendor for contact center, one for back-office, one for the technology stack) with one operating relationship.

A typical engagement at this scale:

• 1,000+ FTE-equivalent across contact center and back-office combined

• Multiple industry programs running concurrently under one governance structure

• iKunnect platform as the system of record across every contact and every workflow

• Quarterly business reviews on the record with named executive ownership

• US law and US-headquartered governance, with the operating presence in Belmopan

Enterprise GBS engagements get a dedicated practice leadership team. The vertical leads, supervisor layer, QA team, and analytics function all wire into one operating picture, with the customer's full history pre-loaded at the start of every contact regardless of which channel or which workflow it arrived through.

This shape fits where the buyer is consolidating away from a multi-vendor stack, or where the operation has grown to the point that vendor seams are creating customer-experience problems. The arithmetic that wins the conversation here is revenue protected and CX score gained per dollar of customer-operations spend, against a baseline of what the multi-vendor stack costs end to end.

4. Pilot programs

60- to 90-day scoped engagements for buyers who want to test the operating model on a defined slice of volume before committing to a multi-year program. Same operating discipline as a full program, scoped tighter.

Common pilot shapes:

• Single-vertical. Healthcare appointment lines only, or financial services loan intake only.

• Single-channel. Voice only, or chat-and-email only, leaving the rest of the channel mix with the incumbent.

• Single-language. Spanish-language overflow only, with regional dialect coverage where the customer base requires it.

• Single-geography. A specific US region or a specific time-window (overnight coverage, weekend coverage).

• Outcome-specific. A defined volume of transactions at a defined quality bar over the pilot window.

Pilots run with explicit success criteria documented at the start, the same QA cadence as full programs, and a documented decision point at day 60 or day 90 on whether to scale into a multi-year engagement. The pilot shape carries the operating-cost weight of a real program because it has to prove out the operating model honestly, not generate a sales-friendly demo.

How to choose the right service shape

The right shape comes out of five questions about the operation, not five questions about the vendor.

1. What scope of customer-facing work needs an operating partner today, and what scope will need one in the next 24 months? A contact-center-only ask today can land in the contact-center shape; if back-office is on the 18-month roadmap, enterprise GBS is the better starting frame.

2. Is the work voice-dominant, digital-dominant, or omnichannel from day one? The four shapes all support omnichannel, but the operating bench, supervisor ratios, and QA cadence calibrate differently depending on channel mix.

3. Are existing vendor relationships staying in place, or is consolidation on a single operating partner the goal? Consolidation maps to enterprise GBS. Coexistence with incumbents maps to the contact-center or back-office shape with a clearly scoped boundary.

4. What is the tolerance for a pilot before committing to a multi-year program? Buyers under quarterly board pressure on customer-experience metrics often need the pilot shape first. Buyers replacing a failed vendor often need the contact-center shape on a compressed implementation, with the pilot decision already made by circumstance.

5. What is the multilingual coverage requirement, at what dialect granularity? Markets with regional Spanish coverage requirements (US Southwest, US Southeast, US Northeast) calibrate the agent staffing model differently than markets needing primarily English-Spanish bilingual.

The shared delivery model

All four service shapes run on the same operating discipline. This is the part that does not change across shapes.

• Two-week agent onboarding before any agent takes a live customer contact. Curriculum covers product, systems, vertical regulations, and quality standards.

• In-house QA, not contracted out. 100 percent of contacts QA reviewed across every shape.

• Weekly supervisor cadence with documented one-on-ones, coaching plans, and call reviews.

• Quarterly business reviews with the customer's executive team, on the record, against the documented success criteria from the start of the engagement.

• iKunnect platform as the system of record across every shape. Unified view of every customer across every channel and every workflow.

Implementation is 30-day typical for full programs. Pilots run on a compressed cadence within the 60- to 90-day pilot window. Emergency takeovers run faster where the operating situation requires it.

Where Invictus fits in the BPO landscape

Pure-play contact-center vendors handle one of these four shapes. Buyers consolidating to a single operating partner end up shopping a second vendor for back-office and a third for the platform layer. The seams between vendors become the customer-experience problem.

Big-brand enterprise BPOs run all four shapes at enterprise scale. At that scale, account-level executive attention is harder to get, and the operating discipline often gets handed to a regional delivery center two or three layers removed from the named account team.

Invictus runs all four shapes at mid-market scope. The same operating bench, the same QA team, the same platform, and the same executive layer cover all four. A buyer starting with one shape gets the same operating discipline that would scale them across all four if the relationship grows that way.

Where to start the conversation

Start with the shape that fits the current work. Pilot if the operating model needs to be proven on a slice of volume. Contact center if voice and digital coverage is the bottleneck. Back-office if document and exception volume is the bottleneck. Enterprise GBS if the multi-vendor stack is itself the problem.

The other three shapes are available when the relationship is ready for them. The operating bench and the platform stay constant across all four.