← All guides

Customer support · Taskending editorial team

How to handle a reopened customer request

When a customer still has the problem, the completion record should support renewed investigation. Reopening is not a reason to erase the earlier explanation.

· 1 min read

How to apply it

Record the new observation and its time in Taskending. Check whether the previous solution reached the same environment. Move to an appropriate open state if needed and clarify ownership. Create a related issue when the root cause differs.

A concrete example

The date filter may be fixed while the customer still uses an old session. If the same defect persists, investigate which condition the earlier test missed. A different failure for another data range may need separate scope.

What to watch for

Rewriting history hides what was already tried. Do not assume every new response describes the same bug. Interpret SLA consequences within the limits of the basic measurement model.

How to check the outcome

The next owner should understand the earlier solution, new symptom and remaining question from the record. Explain the next verification step to the customer too.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free

Keep reading

01
Customer support

Manage tickets from email, a portal and your API

Bring customer requests into one help desk workflow. Practical guidance on email deduplication, internal notes, customer visibility and linked development work.

02
Customer support

Collect requests through a customer portal

A customer portal lets external users follow requests separately from internal team work. Correct roles and project access are the foundation.

03
Customer support

How to write a useful support request

Missing context creates extra correspondence before investigation can begin. Explain the problem, expected behavior and reproduction conditions clearly.