Invite-only · desktop CRM for agencies on Passes and Fanfix
A sale lands. The database says who closed it.
Kult matches a sale to the outbound message that made it and writes the chatter’s credit itself. Nobody types a number into a report.
The Overview page with demo data. Names and amounts are invented.
Credit is computed, not claimed.
Three things happen when a sale is written to the database. None of them is a human opinion.
A sale lands.
A fan pays for a paid DM, a tip or an unlock. The row arrives with the platform’s transaction id and, when there is one, the id of the message it answered.
- Paid DMMia Laurent · @dan_k+$45.0014s
- SubscriptionAva Rose · @wolfie+$14.9928s
- TipLena Park · @mr.ocean+$50.0042s
The database looks for the message.
An insert trigger finds the outbound message with that id and credits whoever sent it. A tip without an id goes to the chatter who last wrote to that fan within 24 hours. Otherwise, nobody.
The credit lands on the report.
The chatter’s line moves. A client cannot set the chatter or the attribution on a sale; the trigger overwrites whatever it sends.
Automation that stops one click short.
Welcome, follow-up and win-back run on a timer in the database and come out as Assist tasks with a script ready to copy. A chatter pastes it and presses send. There is no code path in Kult that sends as a creator.
Fan card beside the inbox
Lifetime spend, tags, notes, last purchase. Written by your team, kept in your workspace.
Scripts to the clipboard
One click copies the script; the chatter pastes and sends in the platform’s own window.
Assist counts down in the open
Welcome, follow-up and win-back tasks with a due time, who took one, when it was done.
Numbers that end the argument.
Who was clocked in, which creators they had, what landed while they were on. Hours and sales on the same line, per chatter, per creator, per day.
Four rules, in plain words.
Kult sits next to your creators’ Passes and Fanfix accounts all shift. These are the promises that make that acceptable.
- 01embedded login · per-creator profile
No creator passwords.
The creator signs in on the platform’s own login page, embedded with the platform’s own captcha. Kult never reads the form and cannot replay the login elsewhere.
- 02tasks, not sends
No bot sends.
Assist tasks are copy and paste. A chatter sends from the platform’s window. There is no auto-send code path to switch on.
- 03metadata only
No message bodies stored.
A message is kept as ids, direction, time and price. What a fan wrote never leaves the platform.
- 04RLS · triggers
Locked rows, computed numbers.
Row-level security on every table, by workspace and role. Attribution and reply times are written by database triggers, never trusted from a client.
One shift, in 24 seconds.
A sale lands, the database matches it to the message, the Assist queue counts down, the report fills in.
No sound. Demo data.
A few agencies at a time.
Invite-only while we onboard the first teams on Passes and Fanfix. Tell us about yours and we’ll reply by email.