ChattingOFM EN / FR
Handling Objections

Handling

Objections in chatting, and how they are answered

Nine sentences come back every night, in every language, on both platforms. They are not obstacles to get around. Each one is a piece of information about where the conversation actually is, and the answer that works is usually the one that treats it that way.

Published 2026-09-14 Updated 2026-09-14 3 sources

Two screens of open conversations in a dark room
Two screens of open conversations in a dark room

A chatter working a full shift will meet the same nine objections dozens of times. The repetition is the useful part: an objection that appears in a thousand threads is not a quirk of one reader, it is a structural feature of the situation, which means it has a structural answer. What follows is the list, what each one is actually saying, and the shape of the response. Not the words. The shape.

1. "That is too expensive"

Almost never about money. It is about the ratio between what is being asked and what the reader currently believes they are getting, and the second half of that ratio is the half you control. A reader who can picture the thing precisely rarely says this sentence; a reader who cannot always does.

The response that works goes backwards, not forwards: back to the thing, not on to the price. The response that does not work is any version of lowering the number, for the reasons in pricing psychology. Holding the price and changing the object is the move that keeps the rest of the relationship priceable.

2. "Is this really you"

The most consequential objection in the trade, because it is the one where the industry's actual structure is at stake. It is asked because the practice is public: Vice described chatters working the inboxes of three or four creators at a time,1 and the BBC reported on a worker paid less than $2 per hour to do it.2 Readers have read those articles too.

This site takes one position and will not move off it: whatever answer an operation gives to this question, it should be an answer the operation could stand behind if it were published. That is a statement about the operation, not about a message. The practical version is that the question is best made rare rather than answered well, and it becomes rare when the thread has continuity, memory and specificity, which is to say when it does not read like it was written by three different people who had not met.

The reliable answer to "is this really you" is a conversation that never made the question occur.

3. "I already paid for the subscription"

A true statement, and a reasonable one. It is what happens when the subscription was sold as access to everything and the thread then behaves as though it was access to a door. The objection is almost always the delayed cost of a promise made upstream, in a bio or a promo post, by someone who was not going to be the one answering for it.

Nothing in the thread fixes a promise made outside the thread. What the chapter can do is make the distinction concrete and early rather than at the moment of a price, so that the first paid message is not the moment the reader discovers the model.

4. "Send it for free and I will buy next time"

This is a test, and it is read as one by everybody involved. The reader is not primarily trying to obtain a file; they are establishing whether the stated terms are the real terms. Both possible answers are informative to them, which is why the one you give matters more than the item at stake.

Refusing without friction, and staying warm, resolves it in one message. Conceding resolves it too, in a different direction: it establishes that prices here are provisional, and the same reader will test again, usually at a higher value.

5. "I will buy later / tomorrow / when I get paid"

Sometimes literally true, particularly around pay cycles, and treating it as an excuse is a real error with real cost. The mistake is not believing it; the mistake is having no mechanism to come back, so that a genuine "later" becomes a dead thread by default.

This objection is the strongest practical argument for the follow up discipline described in timing and time zones. It is answered by a note and a return, not by pressure in the moment.

6. "I just want to talk"

Frequently sincere, and frequently profitable over a horizon longer than one shift. The thread is not refusing to spend; it is refusing to spend now. Whether the operation can serve that reader is a question about how the work is measured, not about the reader: a chatter on a per shift sales target cannot afford them, and an account that can afford them tends to find they buy eventually and buy larger.

The heaviest spenders described by Rest of World, the ones worth upward of $1,300 and more than 20% of platform revenue,3 are built, not found. Several of them began as this objection.

7. "Can I have a discount"

Distinct from objection 1: this reader is not saying the price is wrong, they are asking whether the price is a price. Treat it as a question about the system rather than about the number, and the answer is straightforward, because it is a description of how things work here rather than a defence of one figure.

A discount granted here does not produce a satisfied customer. It produces a customer who knows to ask again, and who now reads the previous price as an attempt.

8. Silence

The most common objection and the one least often counted as one. Silence after a tease and silence after a price mean different things. After a tease, the object was not wanted enough, and the correct move is to build it, not to price it. After a price, the wanting existed and something about the number or the moment broke it, and the correct move is to change the moment, not to repeat the number.

Resending the same paid message to a silent thread is the single most common unforced error in the job. It converts rarely and it tells the reader the offer has no scarcity.

9. "I am going to cancel"

Said out loud, this is rarely a decision. A reader who has decided to cancel simply cancels; a reader who announces it is describing a disappointment and giving you one chance to respond to it. The content of the disappointment is almost always in the previous two days of the thread, and almost never about price.

The response that works addresses the disappointment and does not mention the renewal. Mentioning the renewal converts a relationship complaint into a billing conversation, and billing conversations end in cancellations.

The thing the nine have in common

Every one of them is cheaper to prevent in an earlier chapter than to answer in the chapter where it appears. Objections one, three and seven are pricing structure. Objection two is continuity. Objections four and eight are teasing. Objections five and six are the clock. Objection nine is the cooldown that got cut when the shift target was tight.

Which is the uncomfortable conclusion of this page: objection handling is mostly a symptom. A team that is spending its shift answering objections is a team whose sequence broke two chapters earlier, usually for reasons that have more to do with load and hours than with skill. That load is the subject of the day of a chatter.

Sources

  1. Vice. Eloise Hendy, Think You're Messaging an OnlyFans Star? You're Talking to These Guys. https://www.vice.com/en/article/onlyfans-management-agency-chatters/ published 2023-10-24, read 2026-09-14
  2. BBC News. Chris Vallance, “Icky and heartbreaking”: The $2 per hour worker behind the OnlyFans boom. https://www.bbc.co.uk/news/articles/cq571g9gd4lo published 2026-03-11, read 2026-09-14
  3. Rest of World. Michael Beltran, A hidden network handles chats for OnlyFans stars. AI could soon take over. https://restofworld.org/2025/onlyfans-ai-dm-bots/ published 2025-08-20, read 2026-09-14