Contact
Tell us what you’re trying to fix.
You do not need to know which system you want. Describing the problem gets a better answer than naming a product, and sometimes that answer is that you can do this yourself.
Before you write
Two pages answer most first questions without needing us: how releases are gated and what self-hosting involves. If your question is answered there, you will get a faster answer by reading than by waiting for us.
Routes
What kind of enquiry is this?
Each one lists what to include. Sending those three things first turns a two-week exchange into one reply.
A specific system
You have found something in the catalogue and want to know whether it fits, when it will be released, or how to get early access.
Include
- Which system
- What you would use it for
- Whether you intend to self-host or want Botlane to deploy it
Deployment or managed operation
You know roughly what you want and would rather not install and run it yourself.
Include
- Which system, and which environments
- Where it would run — your cloud account, your hardware
- Whether you want it operated afterwards or handed over
Custom or bespoke work
Nothing in the catalogue fits, or something in it fits but not quite.
Include
- What the software needs to do that it currently does not
- Whether this extends a Botlane system or starts from nothing
- Any deadline that is real rather than aspirational
A problem, not a product
You know what is broken and would rather describe that than pick from a list. This is usually the most useful place to start.
Include
- What happens today, and what it costs you
- Which tools the process currently runs through
- Roughly how many people are involved
Security disclosure
You have found a vulnerability in a Botlane release or on this site.
Include
- Which system and version
- Steps to reproduce
- Any disclosure timeline you intend to follow
Get in touch
Email is the way in.
There is no contact form on this page yet, and a form that quietly loses enquiries would be worse than none. Email reaches us directly.
Direct
sales@botlane.ioSecurity disclosures reach the same address — use the subject line “Security disclosure” and it will be treated accordingly.
What to put in the email
Anything from the list above is enough to get a useful reply. If you would rather write freely, these are the things we will otherwise have to ask for:
- What happens today, and what it costs you
- Which tools the process currently runs through
- Whether you want to self-host or have Botlane run it
- Any deadline that is real rather than aspirational
After you send
What happens next.
No response-time promise appears here, because Botlane has no support rota to back one yet. What we can describe is the shape of the reply.
- 01
A person reads it
Enquiries are not routed into a nurture sequence. Someone who can answer the technical question reads what you sent.
- 02
We say what applies
Which systems are relevant, what is configuration and what would be custom work — including when the honest answer is that you do not need us.
- 03
Scope before quote
If there is work to do, it gets specified in writing before it gets priced. A quote against a conversation is a guess.