how to tell a customer a fix has no ETA honestly

TL;DR

Say "I dont have a date for you" in the first line, not the third paragraph. Customers can handle no ETA; what they cant handle is feeling managed. Tell them what is known, when you will update them next, and what they can do in the meantime, then actually update them on that schedule.

The query

how to tell a customer a fix has no ETA honestly

Use this when

• Engineering cant commit to a timeline for a confirmed bug
• A customer keeps asking for a date you dont have
• The fix is real but unscheduled, or blocked on a third party
• You are tempted to give a soft date to end the conversation

Not for

• Writing outage status page updates
• Negotiating or explaining SLA terms
• Bugs that DO have a timeline (use that instead)
• Closing a ticket you could resolve with a workaround

Steps

1. Put the truth in the first line

"I dont have a timeline for this fix yet" beats three paragraphs of context that end in a shrug. Leading with it signals you respect their time more than your comfort.

Expected output: the reply opens with the no-ETA statement, plainly.

2. Say what IS known

What is confirmed about the bug, what the team is trying now, and what would unblock a timeline. "No ETA" is not "no information." Customers who understand the shape of the problem stop asking for dates every day.

Expected output: two or three concrete facts about current state.

3. Give a next-update time you control

You cant promise a fix date, but you can promise Tuesday. "I will update you by end of day Tuesday, even if the update is that nothing changed." A cadence you own is more reassuring than a date you cant keep.

Expected output: a specific day and time for the next update, in the ticket.

4. Offer the best available alternative

A workaround, a different workflow, a manual process your team can run for them, or an honest "there isnt one right now." Never invent a workaround to soften the message; a fake workaround is worse than none.

Expected output: the customer has something they can do today, or a clear statement that they dont.

5. Keep every update, including the empty ones

When Tuesday comes and nothing changed, write "no change yet, still with the team, next update Thursday." Skipping the update teaches the customer that silence means forgotten.

Expected output: every promised update sent on time, logged on the ticket.

The reply macro

Hi [Name],

I want to be straight with you: I dont have a timeline for this fix yet,
and I dont want to give you a date I cant stand behind.

Here is what I do know: [2-3 concrete facts about the bug and what the
team is trying]. The thing that would let me give you a real date is
[the blocker, e.g. confirming the root cause].

In the meantime, [workaround or alternative, or "there isnt a workaround
for this one right now, I checked"].

I will update you by [day, time], even if the update is that nothing has
changed yet. If anything moves before then, you will hear from me first.

Sorry this one doesnt have a cleaner answer. [Your name]

Variant phrasings

how to say no ETA without upsetting the customer

You cant fully prevent upset; you can prevent the second upset, which is discovering they were strung along. Steps 1 and 5 are the difference.

customer keeps asking for a fix date

That is a signal your updates stopped, not that they are unreasonable. Restart the cadence in step 3 before you answer the date question again.

honest way to say we dont know when it will be fixed

The macro above. Honesty is the structure: truth first, facts second, cadence third.

Why it happens

Agents hedge on ETAs because saying "I dont know" feels like failing the customer. But a soft date you miss does more damage than no date at all: the customer plans around it, it slips, and now you have broken two promises instead of zero. The discomfort of honesty is front-loaded and finite; the damage of a fake date compounds every time it slips.

Edge cases

• Enterprise customers with contractual SLAs: no ETA on the fix does not cancel your response-time obligations. Keep meeting the SLA while being honest about the fix.
• The customer threatens to churn: acknowledge it directly ("I understand this might change your plans") and loop in the account owner. Dont let churn risk push you into inventing a date.
• Engineering gives you a date "off the record": treat it as no date until it is committed. Passing along hallway estimates is how fake ETAs are born.
• The bug gets fixed sooner than expected: great news, and a reason the cadence mattered. Tell them immediately, dont wait for the next scheduled update.
• No workaround exists and the customer is blocked: say that plainly and escalate internally for priority review. Hiding the severity helps nobody.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_X5O8KbvDaRdbRMl5m9LJqw