Give callers prepared work.
Approved product guidance, suitable prospects and a coordinated queue help callers start with a clear next action. They can spend their attention on the prospect instead of assembling lists and switching between tools.
Prepare prospects, choose a human or AI outbound caller, and decide independently who answers return calls. Connect human coaching, AI call handling and owner oversight around the same approved products and company records.
Your company. Your people. Your approved rules.
20 annotated chapters · 3 min 20 sec
Silent walkthrough using example data. Use fullscreen for a closer look, or pause at any step.
Explore the shared workflow. Prospecting, approved product rules and outcomes stay together, while each campaign decides who starts and who answers.
Open Overview and follow the company readiness checklist. Each company has its own products, callers and connected accounts.
Open Account security. Set up an authenticator and complete verification before configuring protected company settings.
In Integrations, connect your company’s OpenAI key. Review the usage consent before saving. Your company pays its own provider account.
Connect your company’s Apollo account and confirm its permissions. Prospect search and phone enrichment are separate operations.
Open Products and start a website draft. Review the extracted source passages, edit the details and resolve unknowns before submitting for approval.
Choose an approved product version, name the campaign and set its currency and spending allowance. Expand the queue and retry options if needed.
Open Human & AI calling. Select Human or AI for outbound calls, then independently choose Human, AI or a message for return calls. Save the campaign options.
Choose an approved product, model and voice. Write the disclosed opening and objective. Verify model access, then approve the profile. Live calling still needs activation.
Open Research, choose the campaign and set a result limit. Run research against the approved audience using your connected Apollo account.
Inspect the returned facts and possible buying hypotheses. Select suitable prospects and import them. Request telephone enrichment separately when needed.
Open Calling workspace. Check your headset and microphone, then get the next eligible prospect. Missing setup or an empty queue is shown explicitly.
Start an authorised human call when the desk is ready. Follow the approved notice and permission workflow before recording. Respect refusal or withdrawal.
Open a call review and inspect the transcript. For permitted recordings, evidence links seek to the matching audio. This example fixture has no recording.
Open AI manager to ask questions, explain blockers or challenge feedback. Connected company AI is required for live replies. This is an example conversation.
Open Performance to review a plan’s behaviour, target and practice task. Acknowledge the plan and discuss any unclear expectations with your manager.
Open Practice and submit a response to the assigned exercise. Practice helps preparation; it does not increase live call performance metrics.
Open Reports and choose a reporting period. Read outcomes with their denominators and sample sizes. Later comparable calls determine improvement.
Return to Overview to check readiness and operational blockers. Prepare your team, review owner decisions and keep approved campaigns and provider accounts current.
Our target is a median below 300 ms for straightforward responses. Read bridge and recipient measurements separately. No measured telephone result is claimed in this example.
Your prospects, approved product knowledge and outcomes stay in one system. Each campaign chooses its outbound caller and incoming-call handler independently. Explore a combination below.
Prospecting · Approved imports · Warm leads
Company rules, contact restrictions and ownershipPrepared guidance. A person leads the conversation.
Your campaign decides the route and unavailable fallback.
Optional AI → human handoff · Availability checked · Context kept with the interaction
Permitted evidence → Discuss gaps → Practise or review AI settings → Check later results → Owner decisions
Human coaching and AI review stay distinct. Outcomes retain who handled each call.Campaign configuration is available. AI live calling and handoff require provider activation and approved telephone verification. Response target: median below 300 ms for straightforward turns; not yet verified on live calls. Aircall synchronisation and custom voices are not enabled in this release.
SalesOS is built to take on the routine management work around a human telesales team: preparing work, reviewing evidence, having the coaching conversation and checking what changes afterwards. The value is in connecting those responsibilities into one continuing process.
Approved product guidance, suitable prospects and a coordinated queue help callers start with a clear next action. They can spend their attention on the prospect instead of assembling lists and switching between tools.
The AI manager uses permitted evidence to discuss strengths and gaps directly with the caller. It asks about blockers, assigns focused practice and makes the next session’s priority clear.
Later comparable calls show whether the behaviour improves. The owner receives the evidence and decision needed when an issue exceeds the AI manager’s authority.
Use the whole workflow as your checklist. Individual products can overlap these categories; this is a comparison of responsibilities, not a claim that every alternative lacks them.
| Starting point | The question to ask | SalesOS approach |
|---|---|---|
| CRM and pipeline | Who turns recorded activity into the caller’s next action? | Connect the record to prepared work, manager conversations and follow-up. |
| Prospecting and dialling | Who prepares eligible work and helps the person making the call? | Bring approved research, contact reservations, product guidance and human browser calling into the same workflow. |
| Call review and analytics | Who discusses the findings and checks that behaviour changes? | Link permitted evidence to a two-way discussion, focused practice and review of later calls. |
| Day-to-day team management | Who keeps coaching moving when the owner is busy? | Run authorised management work in the background and bring the owner exceptions that require a decision. |
Identify callers meeting your targets, callers improving and callers whose results need attention. Assess them against the relevant product, campaign and ramp stage, with the reporting period, sample size and evidence visible.
Use approved product knowledge, readiness checks and focused practice to establish the right behaviours. Review progress against the caller’s ramp stage.
Recognise demonstrated strengths and isolate a specific gap, such as qualification or agreeing a next step. Discuss it and review the next comparable conversations.
Distinguish a coaching need from poor data, an empty queue, phone failures or an unsuitable offer. Review unresolved performance concerns with the evidence and prior interventions attached.
One workflow connects preparation, selling and improvement. The owner sets the rules and campaign routes; human and AI callers handle their assigned work; authorised background processes keep the operation moving.
Start with your website or enter your knowledge. Review claims, prices, limitations, buyer criteria and playbooks before approving a version.
Discover and review suitable contacts, request phone enrichment separately and maintain a work queue within your approved campaign rules.
Select a human or AI outbound caller per campaign. Choose incoming handling separately, with optional handoff. AI processing and recording have distinct permission controls.
Permitted recordings become transcripts and structured analysis. Follow evidence back to the audio; keep uncertain findings and confirmed outcomes distinct.
The AI manager talks directly with the caller, hears their blockers and agrees a focused behaviour to practise. The caller can ask questions or dispute an assessment.
Review later comparable conversations against the plan. Send the owner a decision packet when an issue needs human authority.
A shared operating workspace for your products, callers and owners. Explore the capabilities below; provider-dependent features require the relevant connected accounts and activation checks.
Turn a public product page into an editable draft. Supported JavaScript pages can be read in a browser; source passages and missing information stay visible.
Approve claims, limitations, pricing guidance, qualification and playbooks. Earlier calls retain the product version that applied at the time.
Give each product its own audience and campaign. Allocate caller readiness without mixing one product’s promises with another’s.
Run company-authorised research, inspect the returned facts and review prospects before importing them into SalesOS. Possible buying interest stays a hypothesis.
Search first, enrich separately. Missing numbers, partial results, pending completion and provider errors have explicit states.
Use approved buyer criteria, exclusions, budgets and provider limits. Unsupported criteria are surfaced rather than silently widening the search.
Choose an approved product, currency and allowance using normal form fields. Adjust queue size, search batches and call retry settings.
Background workers prepare more eligible work under your approved rules. Callback commitments, caller readiness and account restrictions inform the workflow.
Reservations prevent two callers taking the same contact at once. Deduplication and account ownership help coordinate work across products.
Check microphone and headset readiness, select devices, mute, use the keypad and hang up without leaving the calling workspace.
SalesOS checks the caller, product, destination, contact restrictions and calling window before connecting through the company’s Twilio account.
Handle requested callbacks, incoming routing and offline fallback. Save call records and wrap-up outcomes even when later processing needs attention.
Connect without recording by default. Follow the approved notice and permission steps, with confirmed recording controls and refusal or withdrawal handling.
Review permitted audio with timestamped transcript segments and evidence links. Search the transcript and seek to the relevant moment.
Inspect qualification, observations, uncertainties and possible claim risks. Callers can challenge assessments; reviewed transcript corrections retain their history.
Each caller membership has its own manager thread. Ask for guidance, explain a blocker or respond to proactive feedback with the context preserved.
Consider queue availability, data quality, phone failures, schedules, calendar capacity, product relevance and what the caller reports.
Use working schedules, briefings and quiet hours. Avoid interruptions during calls and combine repetitive alerts into useful follow-through.
Capture the behaviour, baseline, target, supporting evidence, practice task and review date or call count. Keep concurrent priorities limited.
Work through targeted exercises in the practice workspace and discuss the result with the AI manager. Practice completion does not raise live performance scores.
Use subsequent comparable calls to evaluate progress. Plans record their review and result, instead of ending at “training completed”.
Prepare and approve product-accurate follow-up, track the action’s status and respect unsubscribe and contact restrictions.
Check availability, recheck before booking and handle rescheduling, cancellation, conflicts and disconnected calendar access.
Keep future bookings, attendance, reschedules and host no-shows separate. An invitation is not counted as an attended meeting.
Track prospects through the sales pipeline with recorded stage changes, reasons and confirmed outcomes. AI suggestions remain distinguishable from facts.
Set targets by product, campaign and ramp stage. Reports retain the reporting period, denominator, sample size and maturity of the data.
Review activity, conversations, qualification and outcomes alongside operational blockers. Empty queues prompt investigation rather than invented leads.
Bring your own human callers and invite them into the company. Owners and callers get navigation and access suited to their responsibilities.
A person can belong to several companies with separate roles, assigned work and conversation histories. New company workspaces begin empty.
Manage access, revoke memberships and prepare callers for each product. This is company software, with no public caller marketplace or payroll.
See the evidence, previous interventions, caller response, blocker status and the decision needed. Resolve an exception or request another review.
Relay decisions with attribution through the manager conversation. Employment, discipline, hiring and pay decisions stay with people.
Durable background jobs schedule work, retry failures and reconcile provider actions. A proposed action is never presented as completed delivery.
Verified accounts, multi-factor security and company membership checks protect workspaces. Callers see their assigned work and private reviews; support content access requires an audited grant.
Recording access is authorised. Retention, deletion, export and offboarding workflows keep their progress and retry status visible.
Manage software access, entitlements, invoices, plan changes, cancellation and recovery. Committed call finalisation and essential safety controls remain available when limits are reached.
You should not have to personally turn every weak call into a coaching session. Within your approved authority, the AI manager works directly with each caller: explaining the evidence, hearing their response, agreeing a focus and following up on later conversations. This work continues with your browser closed.
Delegate routine coaching and follow-through while retaining control of strategy, targets and exceptions. Hiring, formal discipline, dismissal and pay decisions remain yours. When a decision reaches you, the evidence, prior interventions, caller response and unresolved blockers come with it.
Choose how much to delegateLink the observed gap to permitted call evidence and the relevant target.
Capture the caller’s explanation and examine operational blockers.
Agree a limited priority with a baseline, target and focused exercise.
Review later comparable calls and record the plan’s result.
Give the owner a clear decision packet and relay their answer with attribution.
A prepared queue, product guidance, browser phone, callbacks and call reviews. A private manager conversation and focused practice make the next action clear.
Approve programmes, prepare the team, monitor pipeline and meaningful results, and resolve the exceptions that need your judgement.
Keep company records and memberships separate while supporting multiple products and callers. People working across companies switch into the right role and context.
Connect accounts inside your company workspace. Each integration shows its connection state; missing credentials and provider failures remain visible.
Prospect search, research and separate contact enrichment.
Your company connects an authorised account and pays its Apollo subscription and credits.
Human browser calls, incoming callbacks and permitted recording.
Your company connects and pays for its telephony account and approved caller numbers.
Product drafting, permitted transcription, analysis and AI management.
Each company connects its own OpenAI key in SalesOS and approves usage on its own account.
Availability, meeting coordination and permitted follow-up.
Connect the relevant calendar and sending accounts. SalesOS tracks integration status and delivery failures.
Create your company, invite your team privately and build approved programmes. Software subscriptions cover platform access; your connected Apollo, Twilio and OpenAI accounts remain company-paid.
SalesOS is onboarding companies. Commercial plans and prices are awaiting approval. Live calling, recording, calendar and payment features require the relevant account setup and activation checks.
Already have an account? Sign in to your company
That is the purpose of its AI manager: prepare work, discuss permitted call evidence directly with callers, capture blockers, assign focused practice and review later performance. Proactive actions require the appropriate automation mode and grants; Observe mode only recommends. Owners retain strategy, approvals, exceptions and employment decisions. Connected accounts and activation checks are required for provider-dependent work.
It compares recorded outcomes and observed behaviours with your configured targets for the relevant product, campaign and ramp stage. Results retain their sample size and reporting period. The manager investigates operational blockers before attributing a gap to the caller, and uses later comparable calls to review progress. It does not infer motivation or personality from a voice, and insufficient evidence is not a reliable performance verdict.
You bring your human team. Each campaign independently selects a human or AI outbound caller and human, AI or message handling for incoming calls. Optional AI-to-human handoff is configured separately. AI live operation requires approved profiles, company-owned provider accounts, applicable operating approval and live verification. It is not automatically enabled by saving a campaign.
Yes. Each company can have multiple products, campaigns and callers. Approved knowledge, buyer criteria, caller readiness and campaign targets stay specific to the relevant programme.
Yes. SalesOS can draft product details from a public website, including supported pages that need browser rendering. You review source passages, edit the draft and resolve unknowns before approving it. Linked pages are not automatically a complete website crawl.
The permission workflow governs recording. SalesOS does not secretly transcribe or score unrecorded audio. Manual call outcomes remain available, and analysis must represent missing evidence as unknown or not applicable.
Authorised background work runs independently of an open dashboard. What the manager may do depends on your automation mode, action grants, working schedules and connected providers. Exceptions needing an owner decision remain available for review.
Yes. The manager thread is two-way. Callers can explain circumstances, raise blockers, ask questions and challenge assessments. Improvement plans are reviewed against later comparable calls, not just whether a practice exercise was completed.
Your company pays Apollo, Twilio and OpenAI directly through its own connected accounts. SalesOS software access is separate. A campaign’s spending allowance is a control, not an additional SalesOS charge for those vendor costs.
Create a workspace first, then connect accounts, approve product rules, invite and prepare callers, and complete the relevant operating and live-provider checks. Calling, recording, calendar and payment availability depend on successful configuration and activation.
Commercial software plans and prices are awaiting approval and will be published when available. The workspace includes subscription and usage management; no illustrative price is presented here as an approved offer.