Di product
Five part, and no join-join between dem
Most CRM na database wey get form for im front, and di conversation dey happen somewhere else entirely — inside mailbox, phone, or chat widget wey get im own small inbox wey nobody don open since March. iKonekt start from di conversation and work outward.
One inbox, evri chanel
Chat, form, di reach-me widget, call-me, e-mail, phone and QR code wey dey paper flyer. Eight door, one room, and every arrival get label of di door wey e pass through.
Assignment as e land
Owner inside di first second, by rule, territory or rota. Di shared mailbox — dat famous retirement home for promising leads — no dey exist here.
One thread, note dem inside
Every channel wey customer don ever use, inside one history, with internal note for di same place and private flag wey really hold.
Pipeline wey reach invoice
Land, assign, dey talk, quote, book and pay, invoice. Same record all di way, so nobody go type address for di fourth time again.
Separation wey di database enforce
Multi-tenant from migration one. Plenty brand, one install, and boundary wey hold even against query wey person write five minute to five on Friday.
And di part wey you no dey see
Underneath all di five na castomAPI — di same account, di same wallet and di same infrastructure as every other product for di family. Na why di connector dem short.
How di five fit
Each one dey exist because di one before am create problem
Dis no be feature list wey committee with whiteboard assemble. If you read am in order, each part na di answer to di mess wey di part before am for make.
Catch everything for one place, and within one week you go get big pile. Volume without ownership na just louder version of losing tins, so assignment must happen as e land — no be when person feel like to reply.
Give everything owner, and di owner go immediately ask di only reasonable question: wetin dem don already tell dis person? Na im make one thread per customer, across every channel, including di awkward part. Seller wey must guess go guess with confidence and wrong, and dat one worse pass make e no guess at all.
Put di whole history inside one thread, and di thread go begin wan finish something. Conversation wey end with "great, send me di details" come disappear, dat one no be conversation, na hobby. So di record continue into quote, booking, payment and invoice without ever being copy into another system.
Carry record reach dat far, and e now hold name, number, price and payment details — and na exactly dat time "we filter by company for di application layer" stop to be acceptable sentence. So separation move down into di database, where forgotten WHERE clause no fit undo am.
Di honest version: each of dose problem dem discover for di order wey dem write am up there, by people wey think say dem don finish di previous step. Di tidy story na retrospective. Di code no be so.
Wetin e no be
Three tins wey iKonekt deliberately no go do
Product page wey only list strength na product page wey nobody believe. Dis na choice dem, and na permanent choice dem be.
E no go ever send cold message
iKonekt dey answer, follow up and remind. E no dey start conversation with people wey no ever ask for one. Dat rule older pass dis product and e no dey configurable, and dat one don cost us at least one interesting meeting.
E no dey score your customers
No be some kain mysterious number between 0 and 100 wey go tell seller who deserve attention. The thread na the evidence. If lead worth to chase, person fit see why within like nine seconds.
E no dey replace your other tools
clickSomo keep the messaging automation, FABLS keep the publishing, your accountant keep the accounting. iKonekt hold the conversation and the customer record. Every other thing go stay where e dey work already.
Start with the inbox. The rest go follow from am.
Connect one channel, watch where e land, then add the next one when you don tire to dey impressed.