The Overlap: How to Date Several People at Once Without Being a Jerk About It

Our guides walk the whole arc — the profile, the first messages, the meetup, the second date, the DTR, and both kinds of ending — and every one of them quietly assumes you are doing all of it with exactly one person. But the actual default state of app dating sits in the gap none of them covers: you matched with several people, you are talking to several people, and nobody has had any conversation about exclusivity because it is far too early for one. That period has a bad reputation it does not entirely deserve. The overlap is not the dishonest part of dating. The dishonest version of it is — and the difference between the two is not how many people you are talking to. It is whether you are running the overlap on purpose.

First, the Argument We Already Made Against This

We are on record here. Our piece on slow dating argues that full attention on someone promising beats divided attention across a roster you can't keep straight — and this guide agrees with every word of it. The reconciliation is that slow dating is an argument about attention, not a rule about exclusivity. A small, deliberate overlap — each conversation getting real attention, each person treated as a person rather than an option — is compatible with everything that piece says. The roster you can't keep straight is not. And we have already written down exactly how the unmanaged version fails: our ghosting piece names the cognitive load of managing several connections at once as a direct mechanism of it — overload builds quietly until one thread simply stops, without anyone ever deciding to stop it. That sentence is this article's reason to exist. Everything below is the how of not becoming it.

Nobody Decided This, Which Is the Problem

Here is the strange thing about the overlap: almost nobody chooses it. It accumulates. And it is worth knowing that the product will not run it for you, because knowing that is what makes it your job. On Intently, intake is slow by design — the free tier is capped at five likes a day, a rule you will not find printed anywhere in the app: no screen shows the number, nothing counts down what you have left, and running out just looks like an ordinary error (the day flips at midnight UTC, incidentally, not at your midnight). So an overlap builds gradually, like a bookshelf — one deliberate-feeling choice at a time, until one day there are six conversations and no plan.

And once it exists, the app's bookkeeping stops well short of managing it. Your Matches list is ordered by when you matched, newest first, and carries no signal at all about which conversation moved last. Messages is the one activity-ordered screen — whoever spoke most recently rises to the top, with not-yet-started threads slotted in by their match date — but that screen is built from your 50 newest matches, so a conversation attached to an older match than that isn't on it at all, however alive it is. There is no archive, no pin, no notes; the unread mark on a thread is a dot, not a number. If several conversations are being kept straight, it is because you are keeping them straight. Which is exactly why the overlap has to be run deliberately: the drifting version has no safety net underneath it.

The Disclosure Rule

Honesty in the overlap is cheaper than people think, because what it requires is narrow: never claim, or accept, an exclusivity you are not practicing. You do not owe anyone a roster, a running tally, or a feed of your week. You owe them an accurate picture of the state — that this is early, non-exclusive dating — delivered before they have reason to believe otherwise.

On Intently there are exactly two places to put that picture where people will see it before they invest. The intent badge you chose at onboarding rides on your card and your profile everywhere they appear — and one of the seven zones, Lifestyle, exists precisely for people whose openness is the point (it is the ENM and poly zone; if that is you, the structured signal already exists, use it). For everyone else, the bio: five hundred characters of free text, the one surface on the product where you can say anything at all. One sentence does the work.

What Each Connection Is Owed

Disclosure buys you the right to run the overlap. Attention is what keeps it honest week to week — and attention is where the width of it gets decided, not by a number but by your own behavior. The signs the overlap is too wide for you are behavioral and unmistakable: replies you keep deferring because answering feels like admin, details you have to scroll up to re-check before you dare respond, the same anecdote pasted into two threads because writing it twice felt like work. (That invisible workload is real and we have written about it — managing expectations across several connections is labour whether or not you call it that.) When those signs show up, the honest move is not to get better at logistics. It is to narrow.

Three working rules keep the individual threads clean. Each conversation is with them, not with the pipeline — if a message could be pasted into another thread without editing, it isn't really addressed to anyone. Plans, once made, are real — the overlap never functions as a standby list, and cancelling a made plan because a more exciting thread lit up is the single fastest way to become the villain of someone's week. And when you misfire — eventually you will send a message aimed at the wrong person — know your actual options: an edit is possible for fifteen minutes and wears a permanent (edited) marker; a delete has no time limit and removes the message for both of you. Use them for the embarrassment. Don't use them to un-ring a disclosure: if the stray message revealed that you're seeing other people, deleting the evidence and hoping is the drifting move. The deliberate one is the sentence from the card above, sent about ninety seconds later than it should have been.

Close Threads as You Go

The overlap is a comparison state, and comparisons resolve. The failure mode our ghosting piece describes is what happens when they resolve silently — a thread loses, and instead of being ended it is just… left. So the discipline that separates a deliberate overlap from a drifting one is pruning: when a thread has resolved to a no in your head, close it that week, not eventually. The scripts are already written — the kind no scales them to how far things went, and is clear that a match that never really became a conversation isn't owed a farewell message at all. What this guide adds is the mechanics: after the no — or instead of one, for those never-started threads — the chat header's unmatch control removes the conversation for both of you, quietly; the other person isn't notified. That quietness is why the order matters. Unmatch is a clean second step and a lousy substitute for a first one: for a thread with real conversation in it, the kind no comes first and the unmatch is just tidying up afterward.

Where the Overlap Ends

Run honestly, the overlap expires on its own: one thread starts winning, and you notice you are comparing everyone else to it. Recognizing that moment — and raising it — is a different article's whole job: our DTR guide covers the signs it's time, how to bring it up without the awkwardness, and what to do when you're not on the same page. We won't re-teach any of it here. The only rule that belongs on this side of that line: if the conversation lands on exclusive, the overlap ends that day. Not wound down, not quietly maintained as insurance while the new thing proves itself. The same afternoon — kind nos out, threads closed. Keeping a warm bench after promising exclusivity isn't overlap anymore; it's the thing this whole guide exists to be instead of.

The Bottom Line

Dating several people at once is not the jerk move. The jerk moves are all downstream of doing it accidentally: the implied exclusivity nobody stated, the thread that starves because nobody decided anything, the plan that evaporates for a better offer, the no that never gets said. Run it on purpose instead — disclosure up front in the two places the product gives you, real attention to each thread or a narrower set of threads, misfires owned instead of deleted, losing threads closed with a kind no while they can still hear it kindly, and the whole thing retired the day one conversation earns exclusivity. On an app named Intently, this is the version of the early game we can actually endorse: not fewer people necessarily — fewer accidents.