01
Client writes in any messenger
Telegram, WhatsApp, Facebook, Viber or Email — Jarvis replies in the same channel automatically, without human involvement.
AI SALES BOT
Jarvis: AI assistant that qualifies leads instead of your manager
Full conversation with clients in Telegram, WhatsApp, Viber and Email — without human involvement. Qualified lead in Planfix at any hour.
- Omnichannel: Telegram, WhatsApp, Facebook, Viber, Email
- SPIN methodology: uncovers pain points, proposes solutions
- Auto-creates contact and task in Planfix
- Knowledge base — Google Sheet you update yourself
Free consultation
How it works
02
Structured SPIN conversation
Bot learns about their situation, uncovers pain points, proposes solutions — following sales methodology, not just templated FAQ.
03
Qualification and handoff
Qualified lead appears in Planfix: contact card, task with full chat transcript, qualification status.
04
Manager gets a warm lead
No cold "tell me about your services". Manager joins when the client is already ready to talk.
Jarvis vs a regular bot
| Criterion | Regular bot | Jarvis |
|---|---|---|
| Communication | Buttons and menus | Full conversation |
| Pain discovery | None | SPIN methodology |
| Dialogue memory | None | Full context |
| Knowledge base | Hardcoded | Google Sheet (you update) |
| Channels | Usually 1 | Telegram, WhatsApp, Viber, Email |
| CRM record | Manual | Auto in Planfix |
| New channel | Rewrite code | Connected in 1 day |
Knowledge base — no technical skills needed
Jarvis knowledge base is a Google Sheet. You fill it in yourself: services, pricing, cases, FAQ, objection handling. Change a row → bot already knows the new answer.
Services & pricing
Service list with descriptions. Bot never quotes prices without permission — you control the boundaries.
Cases & reviews
Real work examples. Bot picks the most relevant case for each client query.
FAQ & objections
"Too expensive", "I'll think", "competitors are cheaper" — ready answers for every scenario.
Rules & limits
What the bot can and cannot say. Edge cases always go to a human manager.
Who needs Jarvis
Company of 5–50 people that:
- Receives 20+ new inquiries per week
- Wastes manager time on primary "tell me about your services" conversations
- Wants leads not to be lost on weekends and at night
- Uses Planfix or is ready to implement it
Especially relevant: real estate, IT outsourcing, consulting, service companies, training centres.
What it gives in practice
Jarvis does not try to replace the manager — it takes over the first hour after an enquiry, while the lead is still warm and the person is busy.
An answer at any hour
An enquiry at 23:40 does not wait for morning: the bot greets, asks qualifying questions and records the answers in the CRM. In the morning the manager gets context, not a "hello".
Qualification before the call
Niche, task, volume, timeline and budget range collected before the first conversation, so the call starts with substance.
Filtering out bad fits
Enquiries you cannot serve get a polite answer and do not eat manager time. Cheaper than discovering it twenty minutes into a call.
The same quality every day
The bot does not get tired by Friday evening and asks the same questions in the same order, which makes the funnel comparable between periods.
What the bot does not do
Better to know the limits before launch.
It does not sell for you
Its job is to bring the lead to a human conversation in usable shape, not to close the deal.
It does not promise prices or deadlines
Commercial terms come from a person. The bot states only what you explicitly allow.
It does not pretend to be human
The client knows who they are talking to. Pretending buys a short win and long mistrust.
It does not handle complex cases
A non-standard request is handed to a person immediately, not after five rounds of clarification.
Implementation options
Starter
fromon request
1–2 weeks
- 1 channel (Telegram or WhatsApp)
- Basic knowledge base in Google Sheets
- Planfix integration
- 14 days support
Omnichannel
fromon request
2–4 weeks
- All channels (Telegram, WhatsApp, Viber, Email)
- Extended knowledge base + objections
- SPIN qualification scripts
- Full Planfix integration
- 30 days support
Frequently asked questions
Will the client realise they are talking to a bot?
Yes, deliberately. The bot introduces itself as an assistant and hands complex cases to a person. Pretending to be a live manager buys a short-term effect and long-term mistrust once it is discovered.
What if the bot does not understand a request?
It passes the conversation to a person with full context and a "needs help" flag. One extra handover beats five rounds of clarification with an irritated client.
Can it be taught our specifics?
Yes, and that is the bulk of the work: a knowledge base from your materials, examples of good answers and forbidden phrasings. Without it you get a polite conversationalist who knows nothing about your product.
How long until launch?
A working bot in the first channel usually takes a few weeks. The longest part is not development but collecting and cleaning answers to real client questions — and that is what determines quality.
Is Planfix required for Jarvis?
For the omnichannel variant (Telegram + WhatsApp + Email in one) — yes. For a simple Telegram bot — no, n8n + Supabase is enough. But without Planfix there is no CRM where leads go automatically.
Is it safe to pass client data to AI?
We use self-hosted infrastructure. Data is processed on the client's servers or our dedicated servers in Hetzner (EU). Only anonymised dialogue context is passed to Claude and Gemini.
Can the bot replace a sales manager?
No. The bot handles primary communication and qualification. Deals, negotiations, complex questions — always a human. The bot frees the manager from routine, not replaces them.
What if the bot gives a wrong answer?
The knowledge base is configured per client. There are clear rules: what the bot can and cannot say. Prices without confirmation — forbidden. Edge cases — bot redirects to manager.
How long does implementation take?
Pilot (1 channel): 1–2 weeks. Full omnichannel: 2–4 weeks depending on number of channels and knowledge base volume.
How to update the knowledge base?
You change a row in Google Sheets — the bot already knows the new answer. No technical skills, no developer needed.