Ova-view
Four parts wey dey move, and all of dem ordinary
People, with record of wetin you allowed to send dem. Graph wey decide wetin happen when. Documents wey render into wetin di graph want send. And engine wey carry contacts through di graph without losing anybody, double-sending, or breaking when you edit am half past four on Friday.
Step six feed step two. Message wey dem open sef na trigger; link wey dem click na trigger; di absence of either one for ninety days na segment wey person fit enter. Dat loop na di whole product, and everything below na detail of how one of di six parts build.
Wetin dey follow no be feature list wey dem arrange to look impressive. Na di shape of di system, in di order wey person actually meet am.
Di contact plane and di account plane no dey meet at all
A customer na you — you sign in with castomo account, and ClickSomo never see your password, because identity belong to separate service and dem verify am offline.
A contact na person wey you market to. Contact never sign in, never hold credential, and never become account. Dem keep di two planes separate forever, because you be di data controller for your own contacts and we be di processor — and na dat arrangement make di whole thing lawful no be just convenient.
E get practical edge sef. Payment no create contact. Booking no create contact. No quiet back door dey wey sibling service fit use add person to your list without basis to write to dem.
- 1Three identifier-demTenant, project and user, as uuid-dem. No password, no profile, no card.
- 2Quota-dem as number-demKontakt-dem, send-dem, AI generation-dem. No amount, no currency, no invoice — billing word-dem no cross dis line.
- 3Your kontakt-demNa your own. E scope to one tenant and one project together, so one forgotten project no go see anything, no be another person row-dem.
Two plane-dem, wey dem separate forever
Everything wey dey happen here dey happen inside person pocket.
Di engine
One run na one row, and one wait na time wey dey on top am
One run per contact per funnel version. One worker go lease di run-dem wey due, e go run di node-dem until e reach one wait or one terminal, and e go write di next wake-up time. Na so di whole loop be, and di plainness na di point.
One node na pure function
Of di run, di contact and di node — and im effect-dem commit inside di same transaction as di run own advance. If dem kill one worker between "send" and "advance", e no go leave anything half-done, na dat one make retry safe instead of second e-mail.
Wait-dem no be queued row-dem
One wait go set wake_at on top di run. Dem no write anything downstream before time, so nothing downstream dey to spoil when you edit di funnel — na di failure mode of every tool wey pre-materialise sequence at entry.
Idempotency na one index
No be check wey dem follow with insert: di window between di two na exactly enough space to double-send. One unique index over run, node, contact and window na wetin really stop am, and e still stop am under load too.
Di part-dem, in order
Eight page-dem, and after dat you don read di product
No hidden depth dey under dis one. Each page na di real mechanism, no be summary of am.
Contacts & consent
Identity na di e-mail address. Dem store di name whole. Consent na one ledger wey get lawful basis, and absence no be permission.
Learn moreFunnels & triggers
Fourteen trigger-dem, sixteen action-dem, seven flow node-dem, and di seven awkward case-dem wey dem test di engine against.
Learn moreChannel dem
E-mail, SMS, push and printed letter-dem. Bring your own sending, and one delivery vocabulary no matter which provider carry am.
Learn moreCreative
One document, six render target-dem, merge variable-dem wey dem check at publish, and one warning before Gmail clip your message.
Learn moreTracking & reports
One separate tracking host, signed redirect-dem, one-click unsubscribe, and bot traffic wey dem label instead of to count am quietly.
Learn moreAI & agents
One sentence go in, one funnel go out — dem validate am di same way as human own. One MCP server wey im best tool na dry run.
Learn moreDi API
API first, no private endpoint-dem, OpenAPI dey /docs, idempotency key-dem everywhere, signed webhook-dem dey go out.
How e take compare
Where dis one dey beside Mailchimp, Brevo, ActiveCampaign, Klaviyo and e-clicks.pro — dem state am as fact-dem about ClickSomo.
Learn moreHow much e cost
Start free, scale by kontakt-dem and channel-dem, and you no go pay anything for sending because you bring your own.
Learn moreWetin dis one no be
E no be CRM. E hold one mailing list and wetin dat list do, no be your pipeline, your deal-dem or your invoice-dem. If you need dose one-dem, keep di system wey you get and dey send am event-dem.
E no be agent wey go decide by imsef wetin e go send. AI go draft one funnel or one copy at one point wey you ask am; di graph wey e produce, di same checker wey dey gate human own go validate am after, and nothing go reach real person without one human publishing am. Na deliberate limit be dat, and na why one run dey reproducible.
E no be mail server, and e no go ever be. Deliverability reputation belong to your provider or your own mailbox — na also why another person bad campaign no fit damage your own here.
Di honest part: to bring your own sending na real trade. You go configure one mailbox or one provider, add three DNS record-dem and check say dem verify, and you go own di consequence if you send something wey people report. In exchange, you no go pay anything for delivery, your reputation no go pool with stranger-dem, and to switch provider no go change anything upstream of am.