Keep a complaint loop open when there is no resolution update
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
The investigation is still open, the team has no answer, and the promised update is due. Waiting for something more useful to say may feel sensible internally. For the customer, it leaves a different question unanswered: is anyone still taking responsibility for this complaint?
Send an interim update when a promised checkpoint arrives, a previous expectation becomes inaccurate, or a blocker changes what the customer should expect. You do not need a resolution to communicate. You need an accurate account of the current state and a next communication commitment your team can control.
1. Decide whether to send or wait
Do not make new investigation findings the only trigger for contacting a customer. That rule makes silence most likely when a complaint is difficult to resolve. Instead, check the communication obligation as well as the evidence.
- An agreed checkpoint is due or missed: send an update even if the investigation is unchanged.
- An earlier expectation is no longer reliable: correct it before the customer continues relying on it.
- A dependency changes the likely path: explain its practical effect.
- The customer needs to act: request the specific missing information and explain why it matters.
- Nothing is due, nothing has changed, and no action is needed: wait until the agreed checkpoint.
More messages are not automatically better. Repeated acknowledgements can become noise. Where no checkpoint exists, establish one around the next meaningful review opportunity and the customer's communication preference, rather than adopting an arbitrary daily cadence.
2. Build the update from verified facts
Keep a resolution estimate separate from an update commitment. A resolution may depend on evidence or another party; reporting the current state should not. Make that distinction visible whenever the customer could mistake a contact date for a completion date.
Before drafting, assemble five fields:
- Status: what remains unresolved?
- Completed work: what relevant work has actually happened?
- Blocker: what prevents the next decision?
- Uncertainty: what outcome or date remains unknown?
- Checkpoint: when will the customer hear again, including if nothing changes?
If no additional work has been completed, identify the last verified step without presenting it as new. An internal reminder is a follow-up action, not evidence about the complaint. Include it only if it helps explain what will happen next.
Record each checkpoint with a calendar date, time and confirmed time zone. Do not infer the customer's zone from a phone number, address or language. If it is unknown, confirm it before presenting a local-time commitment.
3. Use this filled decision table
Fictional worked example: A customer disputes an additional service charge. The invoice has been compared with the customer's account, but the service-completion record is missing. All details and dates below are hypothetical, not Alactic customer results.
These are three alternative states of the same complaint, not a sequence of messages to send together. In each alternative, the customer has confirmed Europe/London as the communication time zone. The dates shown fall in British Summer Time, BST, UTC+1. The team has checked that it can meet the proposed checkpoints.
| Case | Trigger | Send decision | Next commitment |
|---|---|---|---|
| A: Unchanged investigation | The agreed 9 June 2026, 15:00 BST checkpoint is due; no new evidence has arrived. | Send at the checkpoint. Report the unchanged evidence state. | Update by 11 June 2026, 15:00 BST, even if the record remains unavailable. |
| B: Missed checkpoint | It is 10 June 2026, 09:00 BST. The promised 9 June 2026, 15:00 BST update was not sent. | Send now. Acknowledge the missed communication separately from the investigation. | Update by 10 June 2026, 12:00 BST, after a scheduled evidence check. |
| C: Unreliable retrieval expectation | On 10 June 2026, the records team withdraws its earlier expectation of retrieval by 11 June 2026, which was shared with the customer. | Send now. Explicitly correct the earlier expectation; do not wait for the next routine checkpoint. | Update by 12 June 2026, 14:00 BST. Retrieval and resolution dates remain unconfirmed. |
Case C warrants contact because something material has changed: the customer has an expectation the team can no longer support. An undated dependency alone would not justify an extra message if nothing had changed and no checkpoint were due.
4. Turn the decisions into filled message briefs
The briefs below are reusable artifacts: replace their facts with verified case details, retaining the distinction between evidence, uncertainty and contact commitments. The sample messages are fictional.
Brief A: Meet the checkpoint without implying progress
- Status and completed work: complaint open; invoice comparison completed on 8 June 2026. No additional evidence reviewed.
- Blocker and uncertainty: service-completion record missing; charge cannot yet be assessed; retrieval date unknown.
- Next action: check for the record and review it if available.
- Commitment: 11 June 2026, 15:00 BST, Europe/London, confirmed with the customer.
- Customer action: none.
Your complaint about the additional service charge remains open. We compared the invoice with the details you supplied on 8 June 2026. Since our last message, we have not received or reviewed additional evidence.
We need the service-completion record to assess whether the charge was justified. We do not yet have a confirmed date for receiving it.
We will update you by 11 June 2026 at 15:00 BST (Europe/London), even if the record is still unavailable. You do not need to resend the information you have already provided.
Brief B: Repair a missed communication
- Status and completed work: complaint open; invoice comparison remains the latest completed investigation step.
- Blocker and uncertainty: record missing; outcome and retrieval date unknown.
- Communication failure: promised 9 June 2026, 15:00 BST update missed.
- Next action and commitment: check evidence before an update by 10 June 2026, 12:00 BST, Europe/London, confirmed with the customer.
- Customer action: none.
We promised an update by 9 June 2026 at 15:00 BST and did not send it. I am sorry we missed that commitment.
Your complaint remains open. The invoice comparison is complete, but we are still waiting for the service-completion record. We cannot yet decide whether the disputed charge was justified, and we have no confirmed resolution date.
We will check the evidence status and update you by 10 June 2026 at 12:00 BST (Europe/London), whether or not the record has arrived. You do not need to take any action for that update to happen.
Brief C: Correct an expectation that no longer holds
- Trigger: on 10 June 2026, the records team says its previously shared retrieval expectation is no longer reliable.
- Verified fact: retrieval remains pending, with no replacement date.
- Correction: the earlier expectation of retrieval by 11 June 2026 should no longer be relied on.
- Next action: check retrieval status and assess whether available evidence supports another authorised decision route.
- Commitment: 12 June 2026, 14:00 BST, Europe/London, confirmed with the customer.
- Customer action: none.
We previously told you we expected the service-completion record by 11 June 2026. The records team has now told us that expectation is no longer reliable. Please do not rely on that retrieval date; there is no confirmed replacement date.
Without the record, we cannot yet decide whether the disputed charge was justified. We will check retrieval status and assess whether the evidence already available offers another route to a decision.
We will update you by 12 June 2026 at 14:00 BST (Europe/London). That is a communication commitment, not a promised retrieval or resolution date.
5. Explain only the dependency the customer needs
Describe the missing evidence and the decision it prevents, not the internal queue or departmental dispute behind it. This keeps the explanation useful without shifting responsibility to someone the customer cannot contact.
Check whether any proposed workaround actually has authorisation. For example, a temporary adjustment should appear in the message only if it has been approved for that case, with its scope accurately described. Do not imply that the complaint is settled because an interim arrangement exists.
Remove unnecessary personal or internal information. The customer needs enough context to understand the blocker, not the names of every person involved in retrieving the record.
6. Recover when checkpoints or investigations stall
A repeated missed checkpoint needs an operational correction, not a stronger apology alone. Check whether the team has time to inspect the case before the deadline, whether absence has cover, and whether the next commitment depends on someone who has not agreed to it.
Do not compensate with a more ambitious resolution promise. Choose a replacement communication deadline that can be met using the evidence currently available.
Repeated unchanged updates signal a different problem. Reassess whether the missing evidence is essential, whether another authorised decision route exists, and who can decide that question. Keep a record of the decision rather than letting the complaint wait indefinitely for an unanswered request.
Review cadence with the customer where practical. A changed schedule should be explained, not introduced through silence. Escalation may change who reviews the complaint; it does not, by itself, establish a result or completion date.
7. Run the final sending check
Read the message as a set of factual claims and promises:
- Is completed work distinguished from planned work?
- Does the blocker explain the unresolved decision?
- Have unsupported earlier expectations been explicitly corrected?
- Are unknown dates identified as unknown?
- Does the checkpoint include a calendar date, time and confirmed named zone?
- Can the team meet it without receiving new evidence?
- Is any customer action necessary, specific and not a duplicate request?
- Are any interim arrangements authorised and accurately described?
Also distinguish preparation from communication. A saved draft is not contact, and a sending attempt is not evidence of delivery. If the chosen channel cannot be used, check permitted alternatives and customer preferences rather than recording the checkpoint as completed.
8. Test the loop on open complaints
For a hypothetical pilot, review ten unresolved complaints. Record the latest promised checkpoint, whether contact occurred by it, the current blocker and the next commitment. Mark missing evidence separately from missing communication records so the two failures do not become interchangeable.
After the pilot, count checkpoints met, checkpoints missed and cases without a next commitment. Review a sample of messages for corrected expectations and accurate descriptions of completed work. These are observable communication outcomes, not proof of good complaint decisions.
Start with one overdue complaint: complete the five-field brief, check the date and confirmed zone, and send the warranted update through a permitted channel.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications