Chatbot
Answers first, hands over the moment the question needs a person.
The castomo family's CRM and communication hub
Every conversation,
one place.
A customer can reach you eight different ways, and every one of them expects to be remembered. iKonekt keeps track — so the sticky note on the fridge can finally retire.
Try it here — no account, real map data
Pick a town. Count the businesses around it.
Type a town or paste coordinates anywhere in Poland, Spain or the Netherlands, choose how far to look, and see how many businesses the map records inside that circle: what kind they are, where they cluster, and how many list no website. Chain outlets and public offices are left out, and no business is named — only numbers.
Places to start from
How it works
Catch every channel
Chatbot and live chat, contact and reach-me forms, the call-me widget, e-mail buttons, phone numbers, a QR code on a printed flyer. Each is a source, and each lands in the same inbox with its origin recorded.
Give it a seller
Assignment happens on arrival — by rule, by territory, or by rota. Nothing sits in a shared mailbox waiting for someone to feel responsible for it, because there is no shared mailbox.
Work it to the invoice
Notes, quotes, bookings and payments all hang off the same contact. When the deal closes, the invoice is raised from the record that already holds every detail — no re-typing, no second system.
What iKonekt makes possible
Five things that stop being your problem
iKonekt is not an inbox bolted onto a CRM. It is the CRM, written for a business that gets found in more places than one — and it is built on the same platform as the rest of the castomo family.
Nothing falls through the cracks
A chat that starts at eleven at night, a form filled in on a phone at a bus stop, a call nobody picked up. Each becomes a contact with a timestamp, a source and an owner — automatically, before anyone has looked at a screen.
The rule underneath is deliberate: the system never sends a cold message, and it never leaves one unassigned either.
Anna KowalskaChat · 23:41
- AKAnnaDo you install on the weekend? I found you through the pricing page.
- BOTAssistantSaturdays, yes. I have passed this to Marek, who will confirm the slot in the morning.
- MWMarekGood morning Anna — Saturday 10:00 is free. Shall I hold it?
Source: chatbotOwner: Marek W.Assigned in 0.4 s
One thread per customer,
notes included
Every seller sees the whole history with a customer across every channel they have ever used — chat, form, call, e-mail, in that order or any other. Internal notes sit in the same thread but carry a private flag, so pricing thinking and coaching never leak into a customer-facing reply.
Notes are team-visible by default. That is the choice that makes a handover possible when someone is ill.
Anna Kowalska4 channels
- @E-mailSent the quote — 2 400 zł, valid 14 days.
- MWNote · privateCompared us with two rivals. Do not discount below 2 200.
- ☎Call12 minutes. Accepted the quote, asked for a Saturday fitting.
Private notes stay internalVisible to the team
Several brands, one install,
no shared customers
iKonekt was multi-tenant from its first migration, not retro-fitted. Separation is enforced by the database itself with row-level security on every table — not by a filter in application code that one forgotten query can skip.
A group running several companies runs them all here, and no seller in one ever sees a customer of another.
SeparationEnforced below the app
- 1Row-level securityEvery table carries the tenant, and the policy is checked by the database on every read and write.
- 2Composite keysChildren reference the tenant and the parent together, so a stray id cannot cross a boundary.
- 3Per-tenant limitsClaims, prompts and partner programmes are scoped per tenant, never global.
26 tables, forced RLS942 tests
Bookings, payments and invoices on the same record
Hold the slot, take the payment, raise the invoice — without typing the customer's details a fourth time. The thread that began as a chat message ends as a booked, paid and invoiced job, and every step of it is still on the contact.
For Polish sellers that last step means KSeF, which is a service of its own rather than an export you have to remember to run.
Job #2418Closed
- ✓BookedConfirmed by e-mail, reminder sent the evening before.
- ✓Paid2 400 zł by card, on the seller's own account.
- ✓InvoicedIssued from the contact, ready for KSeF.
One record, start to finish
Part of a family,
not an island
iKonekt shares its account and its platform with the rest of the castomo products. If you already use dash-b, castomo or clickSomo, the sign-in is the same one — and so is the customer record behind it.
The connectors run both ways: clickSomo keeps its automation, FABLS keeps its publishing, and iKonekt keeps the conversation.
Every way in
Eight doors,
one room behind them
Whichever door a customer chooses, what happens next is identical: a contact, with its source recorded, and a seller already on it.
Live chat
The same widget, with a seller behind it, on the same thread.
Contact forms
A submission becomes a lead when it is sent, not when it is read.
Reach-me widget
A single button on any page of any site in the family.
Call-me
The customer asks to be rung; the request lands as a task with an owner.
Threaded onto the contact it belongs to, not into a personal mailbox.
Phone
Logged against the customer, with the note the seller wrote after it.
Offline & QR
A flyer, a poster, a referral — a source code that still tells you what worked.
The pipeline
Six stages,
and the record never restarts
The same contact walks the whole way. Nothing is re-keyed at a boundary, because there are no boundaries between the tools — it is one system.
1LandedSource recorded, contact created.
2AssignedA seller owns it within the second.
3In conversationEvery channel on one thread.
4QuotedNotes and pricing kept internal.
5Booked & paidSlot held, reminder sent, card taken.
6InvoicedRaised from the record; KSeF-ready.
0.4 sfrom arrival to an owner, measured on the live console
26tables with row-level security forced on, not optional
942tests behind the tenancy rules, run on every change
Bring every conversation into one place.
Open the console, connect your first channel, and give every customer who arrives a seller from the very first message.
Built to be trusted
Separation you can point at
Multi-tenancy is a claim every CRM makes. Here it is the database's job: each of the twenty-six tables carries its tenant, every policy is written out one at a time rather than generated, and children reference the tenant and their parent as a pair — so even a query that forgets the boundary cannot cross it.
The estate around it follows the same rule. Each sibling service holds its own named token; nothing speaks with a shared credential, and a request can never run without a scope.
What that means in practice
- A seller sees their tenant's customers and no others — enforced below the application.
- Internal notes carry a private flag and never reach a customer-facing reply.
- Erasure is a request the whole family honours, not a mailbox rule.
- The site you are reading loads scripts only from Castomo's own servers (our analytics and the chat button) and sets no cookies.
Part of something larger
One account across the whole castomo family
iKonekt runs on castomAPI — the same sign-in, the same wallet and the same infrastructure as every other product in the family. Connect once and the rest already knows who you are.
castomo castomAPI dash-b castomUI castomFlow clickSomo FABLS castoMIND
Questions
The ones worth asking first
Do we have to move off our current tools?
No. iKonekt is where the conversation lives; the products around it keep doing what they do. clickSomo keeps the messaging automation, FABLS keeps the publishing, and the connectors run in both directions.
What happens to a contact nobody answers?
It cannot exist. Assignment happens on arrival rather than on a first reply, so an unanswered contact is always somebody's unanswered contact — which is a question you can ask at a Monday meeting.
Can we run several companies from one install?
Yes, and it was designed that way from the first migration. Each tenant's rows are separated by the database itself, so no seller in one company ever sees a customer of another.
Is it available in Polish?
Polish and English, both from day one — including this page, which you can read po polsku.
Does it issue invoices for the Polish KSeF system?
Invoicing is a service of its own in the family, raised from the contact record that already holds the customer's details. The KSeF timetable depends on the company, so this is set up per tenant rather than switched on globally.
Where is the data kept?
On EU infrastructure, alongside the rest of the castomo services. This website itself loads scripts only from Castomo's own servers, sets no cookies and serves its own fonts — enforced by the content security policy on every page, not promised in a paragraph.
“So where do we start?”
With a conversation.
Ours.
iKonekt is being opened to its first teams. Tell us how customers reach you today — every door, including the awkward ones — and we will tell you honestly whether this is ready for you, and get you access if it is.
Ask for access Read the product first