Bring the enquiry and source into view.
Website forms, ads, marketplace, CSV and any webhook feed a customer record the team is able to own.
About
Built to run a real sales desk. Now open source.
Outbound OS started as the system behind a pharmaceutical export business answering buyers from marketplace, WhatsApp and email across markets. The work behind that sales desk became a shared inbox, lead records and follow-up workflows, released under AGPL-3.0.
- Based in
- India
- Built for
- Teams handling customer conversations
- Open source since
- 2026
- License
- AGPL-3.0
Built in the open
The work is visible.
Read the source, follow releases and see how issues are handled. Setup and hosting are optional services from the people working on the project.
See the releasesThe product
One operating record across the channels already in use.
Outbound OS does not ask a business to abandon the identities its customers already know. It connects those accounts to consistent CRM work.
Connect qualification, conversation and next action.
Scoring, assignment and pipeline status help the team decide and act without losing context between tools.
Run the approved sequence, then stop at the answer.
Campaigns and follow-up respect connected accounts and configured limits. A customer reply returns the work to a live conversation.
Let approved AI clients work through MCP.
The MCP server exposes explicit lead, message, campaign, analytics and system tools instead of requiring a copied export.
Who it is for
Businesses where customer conversation is operating work.
Built for teams whose sales day happens across WhatsApp, email and other customer channels. The common need is practical: see the conversation, know who owns it and keep the next action clear.
A shared inbox is not enough without ownership.
The customer thread needs a status, a responsible person and a visible next action.
Automation should stop at the customer’s answer.
Follow-up is useful while a lead is quiet. Continuing a sequence over a live reply is a product failure.
AI access should expose real tools and real consequences.
MCP makes the CRM available to approved clients, while sending and destructive actions remain explicit.
Direction should not be confused with availability.
The roadmap separates what ships today from what is being built and what is only a plan.
The thesis
Make the routine work consistent. Keep judgement accountable.
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