Qualify inbound before a rep touches it
Incoming enquiries are answered immediately, asked your qualifying questions, and scored against your criteria — so the pipeline a rep opens contains leads worth their time.
Turn WhatsApp into a qualified sales pipeline — inbound leads handled, qualified and followed up without a rep watching the inbox.
This system is planned. Productization has not started, so there is no release, no images and no documentation to download yet.
Most businesses that sell on WhatsApp are running the channel out of a phone. Conversations live on one person's device, nothing reaches the CRM, and follow-up happens when somebody remembers. This system puts a real sales desk behind the number: every inbound message is captured, qualified against your criteria, and either progressed by an AI agent or handed to a human with the full thread attached.
Incoming enquiries are answered immediately, asked your qualifying questions, and scored against your criteria — so the pipeline a rep opens contains leads worth their time.
Follow-up sequences run on schedule against the CRM record rather than someone's memory, and stop the moment a human replies.
Business knowledge is indexed and retrieved at answer time, so pricing, availability and policy answers come from your documents rather than the model's guess.
When a conversation needs a person, it moves to them with the whole thread, the qualification result and the CRM record already attached.
Inbound WhatsApp messages hit the system's webhook endpoint and are written to the conversation store before anything else happens.
An AI sales agent responds using your business knowledge, asks your qualifying questions, and updates the CRM record as the conversation develops.
The lead moves through your pipeline stages automatically, with follow-ups scheduled against the record.
Escalation rules or an explicit request route the conversation to a person, who picks it up with full context.
How the system is put together, top to bottom.
The twelve release gates that turn a repository into a business system. This is the live state of this system, not a description of the process.
Properties of how the system is packaged and run. Botlane makes no certification or audit claims.
No public releases yet. This system has not reached a tagged release, so there is nothing to download or verify. Releases appear here with their version, date and checksums once published.
The catalogue remains the source of truth while verified email delivery is being prepared.
Yes. Self-hosting is a first-class path — you get the release package, images, configuration templates and documentation, and you run it on your own infrastructure. BotLane Deploy and BotLane Managed are options, not requirements.
No. It is a BotLane Distribution built on DeskcommCRM, pinned at v1.12.0. BotLane packages, tests, hardens, documents and supports it. The upstream project belongs to its own authors and keeps its own licence.
You can. What BotLane adds is everything between a repository and a system a business can depend on: a pinned tested release, installation tooling, configuration validation, secrets handling, health checks, backup and restore, an upgrade and rollback path, and documentation. Those are the twelve release gates listed on this page.
On your infrastructure. The system stores conversations and CRM records in its own database on a persistent volume you control.
BotLane Custom covers modifications, additional integrations and custom workflows on top of the packaged system.
Botlane can host, monitor, update, and maintain eligible AI systems under an engagement-specific operating agreement.
We configure and install the system directly inside your company's AWS, GCP, or Azure account, then hand over the keys.
Complete source packages and Docker containers for teams that want 100% control over deployment and data.
Weekly client reports assembled from your own systems, approved in Slack, and delivered as PDF without anyone writing them.
Answer every inbound customer conversation, book the appointment, and escalate to a human only when it actually matters.
Give internal IT a service desk that triages, drafts and resolves — with approval gates on anything that touches production.