Outbound OS
Live demo Get setup help

The platform

One customer record. Every conversation and next action.

Outbound OS connects the places customers contact you with the CRM work that follows: qualification, ownership, replies, campaigns, pipeline and reporting.

Intake

Everything lands in one queue.

Each channel keeps its own account and its own provider rules. What changes is that your team stops working four inboxes.

  • WhatsAppCloud API
  • EmailYour mailboxes
  • marketplacePush API
  • Web formsWebhooks & CSV
One working queue
  • Deduplicated against existing buyers
  • Scored and ordered
  • Assigned to an owner

End to end

The conversation becomes accountable work.

Automation advances repeatable steps. A person remains responsible for qualification, commercial promises and when a customer relationship should move or close.

  1. CaptureSystem

    Bring in the enquiry where it already arrives.

    WhatsApp, email, marketplace, CSV and supported webhooks feed the working lead record. The original channel remains the customer’s account and keeps its own provider rules.

  2. UnifyShared record

    Keep channel history with the same customer.

    The team works the customer record with message history, source, status and activity in view instead of reconciling a shared phone, an inbox and a spreadsheet.

  3. QualifyShared

    Use scoring to order attention, then assign an owner.

    Recency and engagement help surface the next record to inspect. The score does not verify intent or fit; a person qualifies the enquiry and owns the next action.

  4. ReplyHuman approval

    Reply from the whole thread.

    Free text inside WhatsApp’s 24-hour window, approved templates outside it, email from your own mailbox. Price, scope, timing and terms come from the person who owns the deal.

  5. Follow upSystem

    Run the approved sequence until the customer answers.

    Campaigns work through connected sender accounts inside configured business hours and limits. A reply removes the lead from the sequence so the live thread takes priority.

  6. TrackShared record

    Review the status with the conversation behind it.

    Pipeline, activity and reporting stay tied to the lead. Managers can inspect why a deal is stalled without asking someone to reconstruct the customer history first.

The approval line

Repeatable work for the system. Judgement for the team.

Handled by Outbound OS

Operating consistency

  • Capturing records from connected sources.
  • Ordering the queue and retaining channel history.
  • Sending first contact the moment a lead arrives.
  • Running approved campaigns inside configured limits.
  • Stopping a sequence when the customer replies.

Owned by the business

Commercial responsibility

  • Deciding whether the enquiry is worth pursuing.
  • Approving price, scope, terms and timing.
  • Choosing who may use each sender account.
  • Following consent and channel policy.
  • Deciding when a deal should move or close.
Outbound OS inbox with a lead's WhatsApp and email conversation, status and owner

One record, different responsibilities

The rep works the next action. The manager sees the gap.

For the person handling the customer

See the assigned queue, the complete thread, current status and the follow-up that needs attention.

For the manager

Review work across the team, open the conversation behind a status and step into a stalled record with the same context the owner sees.

AI clients

The platform is available through MCP as well as the dashboard.

An approved MCP-capable client can work with the same leads, messages, campaigns, analytics and system controls.

Explore MCP access

Ask against current CRM data

Inspect lead status and activity without copying the workspace into a separate prompt.

Prepare work in draft

Import a list or create a draft campaign for a person to review before it starts.

Control real actions carefully

Some tools can send, start campaigns or delete records. Credentials and client approval settings are part of the operating design.

Channels and access

The account still makes the rules.

WhatsApp stays on the official business route

Meta template, consent and messaging rules continue to apply through the customer’s WhatsApp Business setup.

Email stays in customer-owned mailboxes

Connected SMTP and IMAP accounts preserve the business identity customers already know.

Roles and lead pools limit visibility

Admin, manager, agent and viewer roles separate responsibility, while lead pools segment which records team members can see.

Ready to make it your own?

One Docker command starts the app, creates the database and your first admin. The setup wizard does the rest.

Read the install guideView on GitHub
Terminal
git clone https://github.com/thatsarpit/outbound-os.gitcd outbound-oscp .env.example .envdocker compose up -d

Open http://localhost:3001 and sign in