You told her you'd call this week. That was six weeks ago. You remember the moment clearly — the parking lot, her father's diagnosis, the way she looked at you when you said you'd check in — and you also remember, with a small drop in your stomach, that you never did. Somewhere between a funeral and a budget meeting and a sermon that wasn't writing itself, her name slipped off the list you were keeping in your head, because a list in your head is the only place it ever was.
This happens to every pastor who has ever tried to carry two hundred people's names in memory alone. The failure is common enough that it deserves two separate answers: what do you do about this person, right now, and what do you do so the next name doesn't vanish the same way.
The apology that actually repairs something
A good apology here is short, specific, and undefended. It names the thing you failed to do, without a paragraph of context about how busy the fall has been. “I told you I'd call and I didn't, and I'm sorry — that wasn't okay” lands better than any explanation, because the explanation sounds like an excuse even when it isn't one. People forgive being forgotten. They forgive it more slowly when the apology tries to justify it.
Resist the urge to soften it with “I've just been so slammed.” It is true, and it is also, from where she's standing, beside the point. The point is that she waited for a call that measured, to her, how much she mattered, and it didn't come. Say the plain thing and let it sit for a second before you move on.
Then do the thing you were supposed to do
An apology without the follow-through behind it is just a nicer way of forgetting her twice. If you owed her a phone call, make it that same day, not “soon.” If you owed her a visit, put a date on the calendar before you hang up, out loud, so it exists somewhere other than your intentions. The apology buys you a second chance; it doesn't discharge the original debt.
This is also the moment to ask a direct question you might be avoiding: is there anything time-sensitive you missed while this sat? A hospital stay, a job loss, a decision she needed input on. Ask plainly. If something did slip that mattered, better to know now and respond late than to find out later that you never asked.
Why this particular kind of failure stings more
A missed birthday card is a small thing. A missed follow-up after someone told you something vulnerable is a different category, because the promise to check in was itself part of the care. When you said “I'll call you,” you weren't scheduling an errand — you were telling her that what she shared mattered enough to come back to. Forgetting doesn't just delay a task. It quietly retracts that message, even though you never meant it to.
Naming that gap out loud, rather than hoping she didn't notice, is usually what she needs to hear. Most people can absorb “I dropped this” far more easily than they can absorb silence that leaves them wondering whether they mattered less than they thought.
One missed follow-up is a mistake; a pattern is a system problem
If this is the first time it has happened, an honest apology and a real follow-through are enough. If you can think of three other names this year that got the same treatment, the problem isn't your memory or your character — it's that you're running a follow-up process that lives entirely in your head, and heads lose things under load. That's worth admitting to yourself before you promise anyone else it won't happen again.
A weekly admin rhythm that includes a fixed time to look at who's waiting on you is a more honest promise than good intentions, because it doesn't depend on remembering to remember.
Building a follow-up board that ages, so nothing sits quietly
The specific failure that happened here — a promise made and then lost — has a specific fix: every promise gets a name attached to it, a date, and a place it lives outside your memory. This is the whole idea behind the guest-to-member path done well — a next step isn't “I'll get to her,” it's an owned task with a due date, sitting somewhere visible enough that it ages instead of disappearing.
SundayBridge's follow-up board works this way on purpose: when you tell someone you'll check in, that promise becomes an item with your name and a date on it, and the board visibly ages whatever nobody has picked up, instead of trusting that you'll remember. It doesn't make the call for you, and it doesn't know what to say when you do — it just makes sure the promise doesn't quietly stop existing the way it did this time.
What to do differently with the next person you promise
Before you leave the conversation where you make the promise, write it down somewhere that isn't your memory — on paper, in a notes app, on a board that ages tasks nobody has picked up. The specific tool matters less than the discipline of never trusting a commitment to your own recall, especially in a season with a funeral, a budget cycle, and a sermon all competing for the same Tuesday afternoon.
It also helps to build in a regular look-back, not just a forward list. A directory your whole team trusts means the follow-up doesn't live only with you either — a part-time secretary or a co-elder can see the same aging list and notice what you've missed before six weeks pass, rather than finding out from the person herself.
Rebuilding trust takes longer than the apology
One good conversation doesn't erase six weeks of silence in her mind, and it shouldn't have to. What actually rebuilds the trust is what happens the next time you tell her you'll check in — whether the call comes when you said it would. Consistency over the following months is the real repair; the apology just opens the door for it. Expect to have to prove, quietly and more than once, that this was the exception and not the pattern.
That's uncomfortable to sit with, but it's also fair. She gave you information that mattered to her and got silence back. The debt gets paid down one kept promise at a time, not settled in a single phone call, however honest it is.