On this page11 sections+
- 01Which leads enter the calling queue
- 02The agent runs the complete phone sale
- 03Callbacks stay attached to the lead
- 04Order value is handled inside customer-approved limits
- 05Every accepted lead needs a final, interpretable state
- 06The team is dedicated to the project
- 07What must be ready before calling starts
- 08After the initial sale
- 09Where the service stops
- 10Project inputs for launch
- 11Frequently asked questions
Which leads enter the calling queue
The service begins with a lead generated for the client’s offer through the client’s own or authorized campaign. The client confirms its authority to collect, share and use the customer data for the agreed purpose.
The intake rules define what counts as an accepted lead. They should also define how the operation treats:
- duplicate or test records;
- a missing or invalid telephone number;
- a lead submitted for the wrong market;
- missing fields required to run the call;
- a lead outside the permitted customer lifecycle.
TheCall does not buy traffic or generate leads. It does not call bought, scraped or cold databases.
The agent runs the complete phone sale
Lead qualification is one part of the conversation. It establishes whether the submitted lead is contactable, genuine, interested and able to progress through the client-approved sale. When the customer is ready to continue, the agent can complete the commercial work.
Within the approved project rules, an agent can:
- identify the store or brand and the reason for the call;
- establish what the customer submitted and whether they still want to proceed;
- explain the approved product and offer;
- answer permitted questions and handle objections;
- confirm or change product, quantity and price;
- present approved quantity upgrades or relevant add-ons;
- confirm address and other required order details;
- create the project-defined confirmed order or record why the sale did not proceed.
A confirmed order means the customer has agreed the product, quantity, price, address and other project-required details. It is not the same event as dispatch, physical delivery or payment.
Callbacks stay attached to the lead
Before launch, choose the calling window, retry cadence, callback rules and terminal status for the market and offer.
Order value is handled inside customer-approved limits
An upsell is not permission to change the offer freely. The client defines the available quantities, price points, add-ons, combinations and claims. Agents can present those options during the call and record the customer’s accepted choice.
The downstream result still matters. If delivery outcomes are supplied, the team can review whether a quantity or offer pattern is creating confirmed orders that later do not become delivered and paid orders. TheCall does not guarantee average order value or delivery.
Every accepted lead needs a final, interpretable state
Sample call-state map
| Public example code | Meaning | Possible next action |
|---|---|---|
accepted |
Lead passed the project's technical intake rules | Enter the calling queue |
customer_reached |
The project-defined human-connection threshold was met | Continue the sale or record the decision |
callback_due |
Customer asked to speak at an eligible later time | Return to the queue at the configured time |
confirmed |
Required product, quantity, price, address and other fields were agreed | Hand off the order data |
order_updated |
A permitted quantity, product or add-on change was accepted | Return previous and current values |
closed_no_order |
A qualifying conversation ended without a confirmed order | Attach the project reason |
closed_unreachable |
Attempt logic ended without a qualifying connection | Return the final contactability reason |
excluded |
The record did not remain in the eligible calling cohort | Attach the intake exclusion reason |
The final taxonomy is configured for the project. The call team, client and relevant network or fulfillment partner should use the same status-and-reason definitions.
The team is dedicated to the project
Agents are assigned exclusively to the client project rather than a shared queue. Their preparation covers the product, prices, claims, script, customer questions, status definitions and permitted decisions.
Team leads use project-specific checklists, feedback and correction to keep execution aligned with the agreed offer, script and outcome rules.
What must be ready before calling starts
The project brief is the first filter. Before launch, the working setup needs:
- target market and expected lead pattern;
- product or offer information;
- client-approved prices, quantities, claims and restrictions;
- final script and escalation rules;
- accepted-lead rules;
- status, reason and order-field mapping;
- caller identity and approved store presentation;
- integration or reporting path;
- downstream owners for fulfillment, delivery and customer payment.
TheCall can prepare the script, work from a client draft or develop it jointly. The responsible client approves the final version.
After the initial sale
Optional authorized lifecycle calls may include confirmed-order follow-up, project-specific customer support, or reactivation and reorders for people already inside a lawful existing-customer or previous inbound-lead relationship. These are configured additions, not permission to call a cold database.
Where the service stops
TheCall handles the call and returns the agreed outcome. It does not:
- generate or buy traffic;
- call scraped or purchased lists;
- own product legality or registration;
- invent prices, claims or customer terms;
- warehouse, pack, dispatch or deliver goods;
- collect or process customer payments;
- guarantee contact, conversion, order value, delivery or revenue.
Project inputs for launch
Use the project brief to share the market, offer, lead source, approximate volume and current stage, launch need or operating requirement. The first response can then focus on fit, required inputs and the right project structure.
Frequently asked questions
Is this an inbound or outbound call-center service?
The leads are inbound because customers submitted them through the client’s own or authorized campaign. The calls are outbound: agents contact those customers to run the sales conversation.
What does “lead qualification” mean here?
It means establishing whether a submitted lead is contactable, genuine, interested and able to move through the client-approved sale. It is one stage of the full phone sale, not the whole service.
Can agents call under our store name?
Yes, calls can be presented under the client-approved store or brand identity, subject to the project identity, telephony and applicable legal rules.
Can you work with our CRM?
TheCall has its own CRM, dialer, telephony and analytics stack. Project-defined lead and status events can move through a configured API. Compatibility and any custom work are confirmed during technical discovery; there is no promise to connect to every system.
Do teams operate 24/7?
No. Teams operate seven days a week within calling windows agreed for the campaign.
Can you reactivate old customers?
Potentially, when the people are inside an authorized existing-customer or previous inbound-lead lifecycle and the client is entitled to contact them. TheCall does not call cold databases.
Next step
Tell us about the offer and lead flow.
Share the target market, product, approximate daily lead volume, current setup and what you need the calling team to do. We will review the project and reply by email.