How to use the Support Ticket Merge Candidate Finder.
Duplicate tickets need evidence of the same underlying issue. Similar wording can describe different causes or customer impact.
Make the workflow fit your task.
Compare ticket symptoms, error codes, affected objects and timing before suggesting a relationship. Distinguish the same incident from similar wording or repeat reports. Preserve customer-specific impact and confirm the support system's merge behavior before combining records.
- What you provide
- Small ticket set and issue identifiers.
- What you get
- Potential duplicate issues with reasons and source links.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Two tickets mention failed imports but show different error codes.
Completed example
Keep them separate until the codes and source behavior support a shared issue; record any candidate relationship for review.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can two tickets with failed import in the subject be merged immediately?
No. Different errors or datasets may require separate investigation even when the summary language matches.
Why did a merge hide an unresolved customer issue?
The records may not have shared the same cause or resolution. Keep ownership and outstanding needs visible before merging.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑