Market and coverage
Country, language requirements, operating windows and local team availability.
TheCall prepares a project proposal around the market, workflow, volume, staffing and integration scope instead of publishing a misleading universal per-call price.
Two projects with the same lead volume can require different attempt logic, training, support categories, systems and staffing. A simple seat or call price can hide the work that determines service quality.
We use the brief to define the team and commercial model. Any minimums, setup work, ongoing charges or usage assumptions should be made explicit in the proposal before commitment.
These inputs determine the operating workload and setup effort.
Country, language requirements, operating windows and local team availability.
Script branches, attempt policy, statuses, upsell, escalation and support scope.
Expected leads or contacts, peak timing, seasonality and growth range.
Integration, reporting, QA, data access and client-side ownership.
A pilot should test a commercial assumption and an operating assumption at the same time.
Choose market, offer, service, volume and systems.
Document deliverables, responsibilities, pricing basis and readiness needs.
Train, test and launch against agreed operating measures.
Use the evidence to adapt, scale or stop before wider commitment.
Ranges are acceptable at the first conversation, but assumptions will be written down.
This page deliberately avoids publishing a number before the staffing, workflow and data requirements are known.
The appropriate commercial basis depends on the service and risk allocation. The proposal should state the model, assumptions and exclusions clearly.
A focused pilot can be discussed. Feasibility depends on setup effort, country, team availability, volume and the minimum scope needed to produce reliable learning.
Give us the six inputs above and the commercial problem you want the pilot to answer.
Plan the project