Situations › Two chatters claim the same tip

A $400 tip lands at 3:12am. Two people worked for it.

One of them sent the message the fan was replying to, twenty-five minutes before the money arrived. The other was covering the account when it landed. Both are telling the truth, and both want the commission.

“Who earned it” has no answer. Somebody would have to decide which message caused a stranger to spend four hundred dollars, and whoever decides that is the person both chatters will argue with every month from now on. “Who was covering the account at 3:12am” has exactly one answer, and it was written down before the money arrived.

Book a demoRead the attribution rule

The contested sale
$400

A single tip, on one creator, with two people named in the claim and one rota that already answers it.

Between the send and the money
25 min

Long enough for a shift to change hands, which is the only reason this is a dispute at all.

People who decide it after the fact
0

A rule invented after the money lands is not a rule. It is a decision about a person, and everyone can tell.

The night, on one line.

Two shifts, one handover, and the two moments that the argument is about. The shift boundary at three in the morning was on the rota a week earlier.

21:0000:0003:0006:0009:00
02:47Dev sends the message the fan replies to
Dev RamanCara Lindqvist
03:12the $400 tip lands

Neither chatter is inventing anything. Dev really did send the message at 02:47 and it really was the last thing the fan read before paying. Cara really was the person covering the account when the payment cleared. The rule does not resolve the disagreement about who deserves it — it removes the need to have one.

What the record already held, before anybody asked.

None of this was assembled for the dispute. Every line below was written as the night happened, which is the only reason it is worth anything the following morning.

02:41
The fan opens the conversationA returning spender on this creator, in the tier that has bought at this price before. Nothing has been sent yet tonight.
What was recordedfan tier, last purchase, shift = Dev
02:47
Dev sends a messageRecorded under Dev’s own login, not the creator account. That a message went out and when it went out are both on the record; what it said is not.
What was recordedsent by Dev, 02:47, message count +1
03:00
The shift changes handsCara clocks in and the handover is acknowledged on the record. Dev clocks out. The boundary was on the published rota a week before either of them worked it.
What was recordedclock-out Dev, clock-in Cara, handover ack
03:12
$400 arrivesThe payment appears in the transaction feed and, the following day, on the creator’s own Statements page at the same figure. Credit goes to the shift covering the account at 03:12.
What was recordedtip $400, credited to Cara, grade: statement
09:20
Both of them claim itThe conversation takes four minutes, because the rota, the clock-ins and the timestamp are all on one screen and none of them are in dispute. What is in dispute is the rule, and the rule is published.
What was recordedno change — the period is not editable

Three ways to answer it. Two of them make the next one worse.

Every agency picks one of these, usually without noticing, and usually after the first big tip rather than before it.

Credit whoever sent the last message
Somebody now has to decide which of the night’s messages caused the payment, and the honest answer is that nobody knows. It also teaches the team to send one more thing at the end of a shift, which costs you the fan long before it costs you the argument.
rejected
Credit the shift covering the account when the money landed
One answer, available before anyone asks, from a rota published in advance. It is not a claim about who deserved it. It is a claim about who was responsible for the account at 03:12, which is a fact rather than an opinion.
the rule
Credit nobody, when the send was automated
If the message that produced the sale went out on its own, the revenue is credited to Automation as its own row rather than to whoever happened to be on shift. That keeps payroll honest, and it produces a number most tools do not separate out: how much of the month the team actually earned.
its own row

There is a fourth outcome, and it is the one that matters most for trust. If a sale cannot be placed on any shift at all, it is reported as unattributed — its own figure, printed on the same page — rather than quietly distributed across the team to make the totals look complete. It is the number that makes the table look worst, and it is the one that tells you the rota is not being kept.

What the rule costs Dev

The part of this worth saying out loud, because a chatter reading the page will work it out anyway.

Dev lost twenty-eight dollars of commission on a message they actually sent. That is not a bug in the rule, it is the rule, and it is the reason the rule is worth having: it applies the same way when it runs in Dev’s favour, which over a month it does roughly as often. Two weeks later a fan paid at 21:40 for a conversation somebody else had spent the afternoon building, and that one went to Dev.

The thing that makes it tolerable is that nobody can move the boundary afterwards. A rule you can appeal is a rule somebody can lobby, and the person who lobbies best is rarely the person who worked hardest. What is left for a manager to do is the part that actually needs judgement: if somebody is consistently timing sends to land inside their own shift, that pattern is visible in the record, and it is a conversation about behaviour rather than about arithmetic.

What the attribution rule will not do.

Three refusals, on purpose
  • It will not be changed after the money lands. Not for a good argument, not for a senior person, and not for a tip large enough to make it tempting.
  • It does not read messages to decide anything. The record holds that messages happened and how many, never what was said, so no figure on the page depends on somebody interpreting a conversation.
  • It cannot tell you who was more persuasive. It can only tell you who was responsible for the account at the moment the payment cleared.
And the limits of the record itself
  • If the rota is not kept, the rule has nothing to attach to. An unscheduled hour produces unattributed revenue, which is visible but not useful.
  • It does not stop the argument being had. It shortens it to four minutes and moves it from “what do you remember” to “do you accept the rule”, which is a question a person can answer once rather than monthly.

The same rule, in other places.

The Shift ConsoleThe attribution rule in full, traced from a fan’s payment to a line on a payslip.Open
A chatter says their check is wrongThe same tip, a month later, as one line in a statement two people read together.Read
MethodologyThe rule as published, alongside the three things attribution refuses to do.Read
Four seatsWhy no seat but the owner can reach the attribution settings.Open

Publish the rule before the next big tip.

A 20 minute walkthrough, then 14 days on your real roster. Pick the sale you argued about last month and see which shift the record puts it on.

Book a demoAll eight situations

FanOptik

Analytics and chatting for OnlyFans agencies and independent creators. Measured across the whole roster, with every figure graded by where it came from.

© 2026 FanOptik. All rights reserved. · Built for agencies that would rather measure the roster than estimate it.