What to Text When Your Co-Parent Won't Confirm the Exchange

What does an unconfirmed exchange actually cost you?

You send the ordinary courtesies of co-parenting admin — Friday, 5:00, the usual place — and get silence. So you wait. You check your phone at lunch. You check it again at dinner. By Thursday you are not really waiting for information; you already know what the agreement says. You are waiting for permission to stop being anxious, and the person who can give it to you is enjoying not giving it.

That is the mechanism. The unanswered question is a small power position: as long as nothing is confirmed, you stay slightly on edge and your co-parent stays completely free — free to show up, free not to, free to announce a different plan on Friday afternoon as if it had always been the plan. Silence costs them nothing and bills you by the hour.

The fix is not to ask better, or louder, or one more time. The fix is to take the power out of the silence by stating a default: your message confirms the agreement's terms and announces what you will take silence to mean. Now the burden of the thread flips.

What does the bait look like?

Sometimes the bait is pure silence. Sometimes, when you follow up, it is a brush-off like this one:

Read that message for what it is: an attempt to make your ordinary confirmation request sound unreasonable, so that you stop making it — and so that the exchange stays unconfirmed, on their terms. The answer is not to defend the request. The answer is to make the request unnecessary.

What should you send?

The script is built in three moves. First, it confirms the agreement's own terms — the day, the time, the place — so the message is a statement of what is already settled, not a request for something new. Second, it names the default out loud: silence counts as confirmation. Third, it closes the loop with what you will do — be there at 5:00 — which means the plan no longer depends on a reply arriving. Notice what is absent: no question mark that matters. You are not asking permission to follow your own agreement. You are putting the plan on the record, once, and letting the record stand.

What should you never send?

Never send this: three follow-up nudges across two days, or a sarcastic "fine, forget it."

The nudges feel diligent. They are actually the problem. Each follow-up teaches that your confirmations are negotiable and your attention is permanently on tap — why would anyone answer the first message when the second and third are guaranteed to arrive? And the sarcastic sign-off is worse than silence: sarcasm in writing is a gift to anyone reading the thread cold later, because it is the one line in the exchange that makes you look like the difficult one. The unanswered question only has leverage while you keep asking it. One message, complete and final, is what confidence looks like on paper.

What if they escalate?

Go where you said you would go, at the time you said. That is the whole escalation plan, and it matters: the default only means something if you act on it exactly as announced.

If they no-show, log the time, send one line — "I was at the parking lot from 5:00 to 5:20; no exchange took place" — and let that be the end of it. Facts, sent once, are remarkably hard to argue with. A no-show that repeats becomes a pattern in your log, and patterns are what mediators and attorneys can actually work with. What you do not do is chase, plead, or retaliate at the next exchange by being vague yourself. Your side of the record is the asset. Keep it boring.

Why does one short message work?

Every message you send has three audiences: your co-parent, you six months from now, and any professional — a mediator, a coordinator, a judge — who may one day read the thread cold. The confirming-with-a-default message serves all three. Your co-parent gets a closed question that requires no cooperation to work. Future you gets a thread where the plan was stated clearly, in writing, before it happened. And a professional reading cold sees exactly one parent confirming agreements in writing and showing up — and one parent who could not be troubled to reply. You cannot control which parent your co-parent appears to be in that record. This script controls which one you appear to be. (It pairs with the habit in the Five-Sentence Rule: one topic, a handful of sentences, then stop.)

What if your situation is slightly different?

The branches below adapt the same script's shape — same default, your details.

Your details differ. Different day, different place, a rotating schedule — the shape holds. Confirm the agreement's terms for this exchange, name silence as confirmation, state where you will be. Nothing else in the message needs to change.

The silence is about a one-off decision, not the standing exchange. Give the default a date. The same shape, with a deadline attached: if you don't hear by Thursday, you'll plan on the original arrangement. A default with a date turns an open-ended wait into a plan that proceeds either way.

They confirm — then don't show. That is no longer a confirmation problem; it is the escalation above. Show up as announced, log the time, send the one factual line, and repeat the identical routine next time. Repetition is what turns individual no-shows into a documented pattern instead of a series of arguments.

If late arrivals are the bigger problem at your exchanges, the companion case is worked in What to Say When Your Co-Parent Is Always Late for Pickup — and when the reply that finally arrives is a whole new plan, see the last-minute swap demand.

The principle

A confirmation you have to chase is a negotiation. A default you state once, in writing, is a plan — and plans do not need anyone's permission to proceed.

This scenario — and the other 54 — is worked in full in the book, Co-Parenting or Parallel Parenting with a Toxic Ex.