## TL;DR
"Engineering is looking at it" is honest exactly once; after that it becomes a holding pattern customers can smell. Say what you actually know, what the next step is, and when you will update them next. Specificity is the difference between transparency and a brush-off.

## The query

```text
how to tell a customer "engineering is looking at it" honestly
```

## Use this when

- A ticket is sitting with engineering
- The customer keeps asking for status
- Agents default to vague reassurance
- Customers complain updates say nothing

## Not for

- Writing the engineering escalation itself
- Outage or incident communication
- Promising fix timelines
- Chasing engineering internally

## Steps

### 1. Say only what you actually know

Check the escalation before you reply. If engineering reproduced it yesterday, say that. If nobody has touched it in three days, dont claim otherwise. Customers can tell when you are guessing, and one caught guess costs more trust than a slow fix.

Expected output: every status update is verifiable against the escalation thread.

### 2. Name the next step, not just the current state

"They reproduced it and are testing a fix" beats "they are looking at it." If you dont know the next step, find out before replying, or say honestly that you are checking and will report back by a specific time.

Expected output: the customer knows what happens next, not just what is happening.

### 3. Give a real next-update time and keep it

"I will update you by Thursday" is a promise you control. Then update by Thursday even if the update is "no change yet." The cadence is the trust; the content is secondary.

Expected output: the customer never has to ask twice.

### 4. Translate engineering status into customer language

"Fix merged, rolling out with Thursday's release" means "you will see this fixed Thursday." Skip the jargon, keep the timeline. The customer cares about when their problem ends, not about your deploy pipeline.

Expected output: status updates a non-technical customer can act on.

### 5. When there is no news, say so and say why

"No change since Tuesday: it is queued behind two higher-severity fixes. I am checking again Friday." Honest bad news beats vague reassurance every time, because it respects the customer's intelligence.

Expected output: even empty updates carry information and a next check-in.

## Ready-to-use update

```text
Quick update, [Name]: engineering reproduced the export issue on
Tuesday and is testing a fix now. I dont have a ship date yet, but
I will check in again by Thursday either way, even if the news is
"still testing."
```

## Variant phrasings

### what to tell customers while waiting on engineering

Steps 1 through 3. What you know, what is next, when you will update.

### honest status updates for escalated tickets

Step 5. The no-news update is the one agents skip and customers need most.

### how to avoid "we are looking into it" in support

Steps 2 and 4. Name the next step and translate the jargon.

## Why it happens

Agents reach for vague reassurance because they genuinely dont know more, and admitting that feels like failing. But customers dont need certainty; they need evidence that someone is paying attention. A specific, modest update outperforms a confident, empty one because it proves attention.

## Edge cases

- Engineering told you not to share details: share the timeline without the internals. "Testing a fix" is fine; the branch name is not needed.
- The customer demands a date you dont have: give the check-in date, not a fix date. Never invent a timeline to end a conversation.
- The ticket was deprioritized: tell the customer plainly, with the reason. "Queued behind two outage fixes" is honest and understandable.
- The customer is escalating to your manager: brief your manager with the same specifics so the story stays consistent.
- Multiple customers asking about one bug: post one status update on the master ticket and point everyone there. Consistency beats personalization here.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_UWk1P-qk18OktHPfefEOyA