Insid di castomo famili
Where customer stop to be eight customers
If you already dey use dash-b, castomo, clickSomo or FABLS, you don meet the modern integration wahala: everything dey connect to everything, and the same human being go come dey exist eight times, spell small small different, for eight places wey each one believe say na im own be the correct one.
The normal fix na synchronisation job, wey be machine wey im whole work na to make two lies agree. E dey work until somebody edit one side while e dey run — then you get third lie plus support ticket.
iKonekt no just dey integrated with the family. E dey inside am. Same sign-in, same account, same platform under — so the customer record no need any reconciling across products, because na only one of am dey.
castomAPI under am
The platform layer wey every product for the family dey run on top: one account, one wallet, one set of services for auth, billing, payments and bookings. Na im make the connectors short instead of heroic.
clickSomo, both ways
Messaging automation go stay where e dey good — inside clickSomo. Wetin dey travel na the conversation and the outcome, so a sequence go know when human take over, and a seller fit see wetin a sequence don talk before.
FABLS, dey feed the top
Blogging and socials dey bring readers; readers dey bring enquiries; enquiries land here with the article wey bring dem recorded as the source. The loop close without spreadsheet for middle.
castomUI forms
Sites and landing pages wey castomUI generate carry forms wey land here directly — no be by e-mail, no be by webhook wey you go maintain. The page and the inbox na the same family build dem.
dash-b, dey watch
Dashboards wey dey read from the same account, so the number for wall and the number for CRM no fit disagree — property wey rare pass wetin you go expect.
castomo, the house
The account wey you already get. If you don sign in to anything for the family, you don sign in to dis one — no second registration and no second password to lose.
Wetin "both ways" really mean
Two-way na word wey people dey overuse, so make I give you the specific version. A connector for dis family no be nightly export. When clickSomo send a sequence and the customer reply, the reply dey on the iKonekt thread, and clickSomo know say make e stop to send — because human dey talk now. When a seller close a job here, the products wey e concern dem go hear am, once, in order, and dem fit act on am.
The functionality no dey move. clickSomo go continue to be the messaging product and iKonekt go continue to be the conversation. Wetin cross the line na the small set of facts wey each side really need, delivered well well make neither side need to guess.
One observation from building am: the hard part of integration almost never be the sending. Na to agree wetin a thing be — whether a "contact" for one product na "lead" for another and "customer" for a third. To be one family mean say that argument happen once, internally, and e no come turn your own problem.
One account, and one way to comot
To share one account across products go raise the fair question of wetin go happen when somebody want make dem delete im data. For dis family, erasure request no be mailbox rule — e fan out to the products wey hold anything, and each one go answer for imself. That one hard pass to build form, and na im make e worth to mention am here instead of inside policy wey nobody dey read.
If you already dey inside the family, you already get account here.
Same sign-in, same customer, no migration weekend and no synchronisation job wey dey quietly invent third version of the truth.
“So we go need to sync am with everything else.”
Nothing to sync dey.
One account across the family, one customer record under am. A synchronisation job na machine wey im whole work na to make two lies agree; dis one get one truth instead.
Si di platfom →