Lead records and pipeline
Create and update leads, assign ownership, set sales status, add context and keep the record visible through the working pipeline.
Capabilities
The working surface, grouped by responsibility.
Outbound OS covers the path from a new enquiry to an owned conversation, controlled follow-up and a pipeline a manager or an approved AI client can inspect.
On this page
Browse by operating responsibility.
CRM & intake
Start with one customer record, however the enquiry arrived.
The source stays attributable. The working status, owner, activity and conversation stay with the lead.
Connected intake
Website forms, Facebook Lead Ads, marketplace, TradeIndia, JustDial, Zapier and any other webhook, plus the conversations arriving on WhatsApp or email. Duplicates merge into the existing lead.
Instant first contact
A lead from a live source gets your approved WhatsApp template and an email within seconds, on every channel you have connected.
CSV import and export
Map a structured lead file into the workspace and export lead data when a team needs to move or review it elsewhere.
Activity timeline
Keep messages, notes, tasks and record changes in chronological context instead of reconstructing the customer history from several apps.
WhatsApp Business conversations
Send and receive through Meta’s WhatsApp Cloud API, with sent, delivered and read receipts. Template and provider rules remain in force.
Photos, PDFs and voice notes
Files leads send on WhatsApp are saved on your server and open in the inbox; send price lists and catalogues back the same way.
Telegram and iMessage
Message leads from your own Telegram account, or on iMessage through a Mac running BlueBubbles, in the same inbox.
Customer-owned email
Send through SMTP and receive through IMAP using the business’s own mailboxes, including replies within an existing thread.
Shared working context
Keep channel history, lead status, assignment and follow-up state available to the people responsible for the customer.
Inbox & messaging
Work the conversation without losing the CRM state.
The inbox is not a second record. It is the customer history attached to the same lead the pipeline uses.
Qualification & ownership
Make priority and responsibility explicit.
Queue order helps a team decide what to inspect first. It does not turn a lead score into buyer intent.
HOT, WARM and COLD tiers
Recency and engagement help order the queue using a deliberately small, readable vocabulary.
Lead assignment
Give a record one responsible team member or move it when ownership changes.
Tags and working filters
Segment leads by source, country, status, engagement and the tags the team uses to organise its own work.
Lead pools
Control which records a team member can see without copying the underlying customer record.
Draft and targeted campaigns
Create campaigns against a defined lead filter, preview the matching audience and keep the campaign in draft until it is ready.
WhatsApp, email or both
Use supported connected channels and the sender account chosen for the campaign rather than an Outbound OS-owned identity.
Reply-aware follow-up
A buyer reply removes the lead from the active sequence so a scheduled chase does not land on top of a live response.
Pause and resume controls
Stop a running campaign or the automated sending queue while preserving the work already completed.
Campaigns & follow-up
Consistency with a real stop condition.
The system can execute an approved plan. The team decides who should be contacted and what the message is allowed to promise.
Orders & customers
After the reply: the order, the invoice, the shipment.
A won lead becomes a customer without leaving the record the conversation lives on.
Customers and products
Convert a lead into a customer and keep a product catalogue to build orders from.
Orders, invoices and shipments
Record order items, raise invoices and track shipments against each order.
Order updates on WhatsApp
Send confirmed, shipped and delivered updates with your approved templates.
Revenue and margin
Revenue, supplier costs and profit in your home currency.
MCP & developer access
Operate the CRM from approved external tools.
The MCP server is an available product surface, not a planned integration.
Read the MCP guideLead and timeline tools
Search and inspect leads, read activity, update status, assign ownership and perform explicit record actions.
Message and campaign tools
Read channel history, import lists, create draft campaigns and—when approved in the client—send or change campaign state.
Analytics and system tools
Pull current funnel or campaign data, inspect sender health and control the automated sending queue.
Webhooks and Google Sheets
Signed events to any endpoint you control, and a live row in Google Sheets for each new lead and reply.
Reporting
Activity with the record behind it.
Pipeline and funnel
Review progression, source, tier and current working state, then inspect the conversations behind the summary.
Campaign and email performance
Compare sent and reply activity held by the product without presenting a message as the verified cause of revenue.
Administration & access
Control who can work what.
Roles
Admin, manager, agent and viewer roles separate setup, oversight, customer work and read-only visibility.
Connected-account health
Inspect sending readiness, limits and product notifications when a channel or scheduled action needs attention.
Protected credentials
Stored connection credentials are encrypted at rest with AES-256-GCM, with keys generated per install. See Security for details.
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.
git clone https://github.com/thatsarpit/outbound-os.gitcd outbound-oscp .env.example .envdocker compose up -dOpen http://localhost:3001 and sign in