My Cousin Copied My Baby Name and Called Me Dramatic

She shared a meaningful baby name with a cousin she considered one of her closest friends. Months later, that cousin announced the very same name for her own daughter, then accused her of being dramatic for feeling hurt. Now the family is taking sides, and she’s wondering whether she’s upset about a name nobody can own or the trust she thought existed between them.

01. First of All…

Sweetheart, I need someone to explain how you went from sharing a meaningful family name during a private conversation to discovering that your cousin had apparently placed the entire combination on her daughter’s birth certificate. Because you didn’t casually mention that you liked a name you saw on a television show. You shared something connected to your late grandmother, explained why it mattered to you, and trusted that conversation to someone you considered practically a sister. Then you found out about her decision through a social media announcement, just like everyone else. I can understand why that felt startling, even if the name itself was never exclusively yours to use.

Now, before we start issuing legal notices on behalf of the alphabet, let’s establish something important: nobody owns a baby name simply because they thought of it first. Families can have children with the same names, cousins can share names, and meaningful names are often passed through generations. Your cousin has the right to name her daughter Eliana Rose, just as you have the right to use that name for a future child. But having the right to make a decision doesn’t automatically mean the decision was considerate of the people involved. Sometimes the question isn’t whether someone was allowed to do something. It’s whether they handled it with the care a close relationship deserved.

And I think that’s where your hurt is coming from. Your cousin didn’t accidentally choose a similar name without knowing your plans. According to your letter, she remembered the conversation and knew the personal meaning behind the exact combination. She may genuinely have grown attached to it, and there’s nothing inherently wrong with that. But she also knew you had a connection to the name, and she chose not to mention her decision until after the baby was born. That silence, followed by calling you dramatic when you expressed disappointment, seems to have damaged your trust more than the name itself.

02. Let’s Unpack This

Let’s begin with the emotional significance of the name, because that’s what makes this situation different from two relatives independently choosing something popular. Eliana Rose wasn’t simply a combination you thought sounded pretty. You connected it to your grandmother, someone who played an important role in your childhood and whose memory you wanted to honor. When people choose names associated with loved ones, those names can represent grief, gratitude, family history, and hopes for the future. Your cousin may have appreciated the beauty of the combination without fully understanding how deeply attached you were to it. But because you shared the story with her, it’s reasonable to wish she’d treated that connection with greater sensitivity.

There’s also an important distinction between a name being meaningful to you and a name belonging to you. Your grandmother was part of your wider family history, and your cousin may have her own memories or affection for her. It’s possible that the name became meaningful to your cousin for reasons beyond simply hearing you mention it. We don’t know whether she had already considered Eliana, whether she associated Rose with the same grandmother, or whether the combination grew on her over time. Those possibilities don’t erase your disappointment, but they remind us that family names can carry overlapping meanings. One person’s emotional connection doesn’t automatically cancel another person’s right to honor the same family member.

What complicates the situation is that your cousin apparently didn’t tell you she was considering the exact name. She kept the choice private until the birth, which many parents do for perfectly understandable reasons. Some people want to avoid unsolicited opinions, arguments, or pressure before introducing their child. But given your earlier conversation, it’s also understandable that you would have appreciated a heads-up. She didn’t need your permission to use the name, but a thoughtful conversation might have prevented the surprise from feeling like a betrayal. Something as simple as acknowledging that she remembered your plans and explaining why she’d chosen the same name could have shown respect for your feelings, even if the outcome remained unchanged.

Then there’s her argument that you’re not pregnant and therefore can’t reserve the name. Technically, she’s correct that you can’t claim exclusive rights to a name for a hypothetical future child. But that argument doesn’t fully address what you told her. You weren’t demanding that she legally change her daughter’s name or insisting that nobody else could ever use it. You were explaining that you felt hurt because she knew the significance of the name and didn’t discuss her decision with you. Responding by pointing out that you aren’t pregnant may be factually relevant, but it doesn’t demonstrate much empathy for why the situation upset you.

I also want to consider your cousin’s circumstances without using them to excuse everything. She recently gave birth, and the postpartum period can involve exhaustion, physical recovery, emotional changes, and the overwhelming responsibility of caring for a newborn. Your relatives may be worried about adding stress during an already demanding time. That concern is reasonable, and it’s worth approaching conversations with sensitivity. But being postpartum doesn’t mean someone is incapable of acknowledging another person’s feelings, nor does it mean every disagreement must be permanently avoided. Timing and tone matter, but so does the ability to have respectful conversations within a family.

Now let’s talk about the relatives who have decided this disagreement requires an official family opinion. Your aunt thinks you should feel honored, your mother believes your cousin should have spoken to you, and other relatives want you to apologize. Everyone seems to have developed a position, even though the original issue was between two people who used to be extremely close. Family disagreements often become more difficult when relatives start interpreting the conflict as a choice between supporting one person or the other. You don’t need a committee to determine whether your feelings are legitimate, and your cousin doesn’t need the family to defend her naming decision. The more people involved, the harder it may become for the two of you to have a calm, honest conversation.

Finally, I want you to consider what you’re actually grieving in this situation. It may be partly the idea of having a daughter with a name you’d imagined for years. But I suspect you’re also grieving the easy trust you had with your cousin. You shared something personal, assumed she understood its importance, and then discovered that she made a decision involving that very thing without discussing it with you. Her dismissive response may have made you feel that your feelings mattered less than avoiding an uncomfortable conversation. That’s a relationship issue, not simply a disagreement over letters arranged in a particular order. And relationship issues deserve more thoughtful attention than being told to stop acting dramatic.

03. Here’s What I’d Tell You

First, I’d encourage you to separate the name itself from the way your cousin handled the situation. You can’t change the fact that her daughter is named Eliana Rose, and I don’t think asking her to reconsider the name would be productive or fair to the child. Her daughter is now a real person with a name her parents chose, and she shouldn’t become the center of an ongoing family argument. But you can still acknowledge that the surprise and your cousin’s response hurt you. Accepting that the name is hers to use doesn’t require pretending the situation was handled thoughtfully.

Next, give the situation a little time before attempting another serious conversation. Your cousin is adjusting to life with a newborn, and you’re still processing the surprise and disappointment. Trying to resolve everything immediately may lead to more defensiveness, especially with relatives offering unsolicited opinions. You don’t need to disappear from her life or make a dramatic announcement about ending the relationship. You can simply allow some breathing room while you decide what you want to communicate. Sometimes a conversation becomes more productive once both people have had time to separate their immediate emotions from the larger relationship.

When you’re ready, I’d suggest explaining your feelings without framing the situation as theft. You might say, “I know you had the right to choose whatever name you loved for your daughter, and I’m not asking you to change it. But when I shared Eliana Rose with you, I explained how much it meant to me because of Grandma. Finding out you chose the exact name without ever mentioning it surprised and hurt me. What bothered me even more was being called dramatic when I tried to explain how I felt.” That keeps the focus on consideration, honesty, and the relationship rather than suggesting you had ownership over the name.

I’d also encourage you to listen to her explanation if she’s willing to offer one without turning the conversation into another argument. Perhaps she genuinely fell in love with the name and avoided telling you because she anticipated conflict. Maybe she believed that since you weren’t expecting a child, the choice wouldn’t affect you in a meaningful way. Neither explanation automatically makes the decision considerate, but understanding her thinking may help you decide whether this was a thoughtless mistake or part of a broader pattern of disregarding your feelings. The goal isn’t to prove that one of you is the villain. It’s to understand whether the trust between you can be repaired.

Then consider setting a boundary with the relatives who keep inserting themselves into the disagreement. You might say, “I love my cousin and her daughter, and I’m not asking anyone to take sides. I was hurt by how the situation happened, and I’d prefer to work through that privately with her.” You don’t need to defend your feelings to every aunt, uncle, or cousin who has an opinion about the name. You also don’t need to apologize simply because other people are uncomfortable with the tension. If you said something unnecessarily harsh during the disagreement, you can take responsibility for your words. But having feelings about what happened isn’t something that requires an apology.

Now, about whether you should still use Eliana Rose if you have a daughter someday: absolutely consider it if the name continues to feel meaningful to you. Your cousin using it doesn’t erase your connection to your grandmother, and there’s no rule that says cousins can’t share a name. Families have repeated names for generations, sometimes intentionally honoring the same relatives. You may eventually decide that sharing the name feels beautiful, awkward, or simply not what you want anymore. Any of those reactions would be understandable. But don’t abandon something meaningful solely because you’re afraid of how your cousin or other relatives might respond. Your future decisions should reflect your own wishes and circumstances.

Finally, think about what repairing the relationship would actually require. Do you need your cousin to acknowledge that she knew the name mattered to you? Would an apology for calling you dramatic help you move forward? Are you comfortable accepting that she made a decision you wouldn’t have made, provided she treats your feelings with more respect in the future? Those are questions worth considering because reconciliation doesn’t always require complete agreement about what happened. Sometimes it means recognizing that two people experienced the same situation differently and choosing to handle future disagreements with more care.

04. Love, Tessa

Sweetheart, I don’t think you’re wrong for feeling disappointed by what happened. You shared a name connected to someone you loved deeply, and your cousin chose that exact combination while knowing its significance to you. She was entitled to make that choice, but it would have been considerate to acknowledge your connection to the name before you discovered the decision through a social media announcement. More importantly, calling you dramatic when you expressed your feelings made an already uncomfortable situation harder to resolve. You can accept that her daughter has the name without pretending the way things unfolded didn’t hurt.

What I hope you’ll remember is that your grandmother’s memory belongs to more than one moment, one name, or one future possibility. The love you have for her isn’t diminished because your cousin named her daughter Eliana Rose. If you eventually have a daughter and still want to use that name, you can make that decision when the time comes. And if you choose something different, it won’t mean your cousin took away your opportunity to honor your grandmother. There are countless ways to carry someone’s memory forward, and none of them become less meaningful simply because another family member chose a similar tribute.

And one final observation before I return to my imaginary family group chat. I fully support beautiful baby names, sentimental family traditions, and honoring the people who helped shape our lives. But if your cousin tells you she’s dreamed of naming her daughter Eliana Rose because of Grandma, perhaps don’t quietly adopt the exact combination and then act shocked when she has feelings about it. Because, baby, nobody owns the alphabet, but consideration is still free. You can choose whatever name you want without pretending that knowing someone else’s emotional connection is completely irrelevant. And if the family insists on holding a meeting about it, somebody please remind them that the baby has already been named and does not need a committee reviewing the paperwork.

Love, Tessa ♡

LETTER STATUS: ANSWERED. FAMILY BABY NAME COMMITTEE: DISBANDED.

Now it’s your turn, Group Chat. Can someone really copy a baby name, or is every name fair game until it’s on a birth certificate? Would you be upset if a close relative used the exact name you’d shared for your future child, especially if it had sentimental meaning? And would you still use the name afterward? Bring your opinions, your family naming traditions, and your best advice. We’re discussing baby names, family boundaries, and emotional attachments—not accepting applications for exclusive ownership of the alphabet.

Editor’s note: This Dear Tessa letter is a fictional scenario created for entertainment and discussion. It does not represent an actual reader submission.