Prospecting
Discover and enrich eligible contacts.
One shared work queueSALESOS PLATFORM
Keep your team and connect the work around every conversation: approved products, prospect research, human calling, AI coaching and performance reporting.
20 annotated chapters · 3 min 20 sec
Walkthrough of implemented screens using example data. Telephone use requires activation. Use fullscreen or pause at any step.
Keep products, callers, prospect research and management conversations together in a company workspace. Follow the readiness checklist to prepare your operation.
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.
The human desk has microphone, reservation and call controls. Check the input device and request eligible work. Telephone use requires an authorised company connection and activation.
The human-call permission workflow starts with an unrecorded connection. After telephone activation, follow the approved notice and permission steps before requesting recording.
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 written response to the owner-defined exercise. Company AI provides feedback. Practice completion remains separate from live call 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.
Check readiness, reported blockers and owner decisions. Keep approved products, caller schedules and company connections current.
AN AI MANAGER FOR YOUR TEAM
Discuss call evidence, explain blockers and practise a focused skill. Review subsequent comparable calls for improvement. Your team can challenge assessments; you retain employment and operational decisions.
Choose how much to delegateExplore the configured workflow (live calling is disabled). Follow the prospect through your team. You approve the rules, choose who calls and decide who answers when they call back. SalesOS keeps the context connected.
Approve products, audiences, budgets and automation permissions.
Discover and enrich eligible contacts.
One shared work queueAssign human callers with approved product guidance.
Your outbound choiceA cold prospect or a warm lead.
Company-scoped contact recordSave who should handle the campaign’s return calls.
Independent incoming choiceDiscuss human-call evidence with each caller, capture blockers, assign written practice and review later calls.
This diagram shows campaign configuration. Live telephone use is currently disabled and requires approved activation. AI conversations and written feedback require the company’s OpenAI connection.
EXPLORE THE PLATFORM
Connected capabilities, with clear activation requirements.
Company AI required for website drafts
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. Assign caller readiness to the relevant approved product version.
Authorised Apollo account required
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 supported approved buyer filters, estimated enrichment budgets and in-flight limits. Unsupported filters are rejected; actual provider credits still need reconciliation.
Configurable queue buffer
Choose an approved product, currency and allowance using normal form fields. Adjust queue size, search batches and call retry settings.
Authorised workers refill a configured queue buffer. Caller eligibility and restrictions control access to the prepared work.
Reservations prevent two callers taking the same contact at once. Deduplication and account ownership help coordinate work across products.
Twilio connection and activation required
Request microphone access, select an input device, mute, use the keypad and hang up. Telephone use requires an activated company connection.
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.
Permitted human-call evidence required
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.
Company OpenAI connection required
Each caller membership has a persistent thread, visible to authorised company management. Company AI uses recent context to answer questions and discuss feedback.
Check queue and connection status, schedules and reported blockers. Product and data concerns can be referred to the owner for review.
Use working schedules, briefings and quiet hours. Avoid interruptions during calls and combine repetitive alerts into useful follow-through.
Written exercises and evidence-based review
Plans record a behaviour, baseline, owner-defined target and practice task, evidence and review threshold. Callers can acknowledge or discuss an assigned plan.
Submit a written response to the assigned exercise for AI feedback. 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”.
Configuration available · live calls require activation
Save the outbound caller type and incoming handler separately for each campaign.
Create a draft profile with its product version, opening, objective, model and voice. Verify model access and approve the profile.
Configure the company number, operating permissions and call-duration and concurrency limits. Live telephone use requires activation.
Recorded outcomes and explicit targets
Track prospects through the sales pipeline with recorded stage changes, reasons and confirmed outcomes. AI suggestions remain distinguishable from facts.
Set behaviour-rate targets for a campaign and ramp stage. Reports retain periods, denominators and sample sizes; model observations still need quality review.
Review activity, conversations, qualification and outcomes alongside operational blockers. Empty queues prompt investigation rather than invented leads.
Company-scoped memberships
Create an email-bound private invitation link and share it with your caller. Roles control navigation and access.
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.
Schedules and action grants apply
Review recent evidence, plans, caller responses and blockers alongside the requested decision. Record a resolution or a request for further review.
Save an owner or manager decision into the caller thread. The exception records who resolved it. Employment decisions stay with people.
Durable jobs schedule work and track proposals, execution and provider results. Retries and reconciliation are provider-specific; ambiguous results may need operator investigation.
OAuth application setup and host consent required · live verification pending
Each person receiving appointments connects their own Google or Microsoft calendar and sets working hours, meeting length, booking notice and gaps.
Select eligible hosts when creating a campaign. Callers choose a host and an available time; booking attribution stays with the caller.
Recheck availability before booking, reschedule or cancel appointments, and reconcile provider changes. A confirmed invitation is kept separate from attendance.
Verified identity and authorised access
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.
Verify your email and use an authenticator for protected company operations. Manage access through company memberships.
Yes—the host-calendar workflow supports Google Calendar and Microsoft 365 / Outlook calendars, including Outlook.com accounts. Each meeting host connects one provider and one calendar, and campaign owners select eligible hosts. Provider application setup and host consent are required; live account verification is still pending. Support covers calendars and meeting invitations.
With company OpenAI connected, callers can ask questions, discuss recent evidence and report blockers. Target-based plans provide written practice and review later comparable calls. Scheduled coaching follows your working hours and action grants.
Reports show recorded outcomes and applicable behaviour observations against campaign and ramp-stage targets, with periods, denominators and sample sizes. Review AI observations against the evidence.
Yes. Each campaign stores an independent outbound selection and incoming handler. Product-bound AI profiles have their own approval and model-access checks. Live telephone use requires separate activation and is currently disabled.
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. Live calling is currently disabled and requires successful configuration, approved testing and activation.
Start with your company workspace, team, products and connected accounts. Telephone use requires activation.