A repeat tenant call may describe the same unresolved maintenance issue or a genuinely new problem. Deduplication should reduce clutter without suppressing new information or closing work that has not been resolved.
Match the property and unit first, then review candidate open issues using the manager's approved policy. A shared phone number or broad category such as “plumbing” is not enough to decide two reports are identical.
Separate duplicate delivery from repeat contact
The same event delivered twice is a technical retry. A tenant calling again is a new interaction that may need a linked update. Keep those cases distinct so the system can prevent duplicate creation while still recording the tenant's changed report or follow-up request.
Use event identity for repeated deliveries and a business request identity for the open issue. Scope both by the correct management account and property. One tenant can legitimately have several active issues.
Work through a fictional repeated repair report
A tenant reports a kitchen problem Monday and calls again Wednesday. The ticket is still open, and they provide new information. The agent links the call, adds the report under the approved workflow, and records the requested follow-up.
If the tenant also reports a separate bedroom issue, capture an independent intent. Do not fold unrelated work into the kitchen ticket merely because the same person called.
| Repeat report | Required behavior |
|---|---|
| Same property and open issue | Linked update |
| New facts about old issue | Preserve changed report and routing review |
| Unrelated issue | Separate tracked intent |
| Existing ticket uncertain | Staff reconciliation |
| Create response timed out | Check outcome before retry |
Keep the tenant's follow-up visible
Linking a call should not make it disappear. Staff need the date of the latest contact, new facts, current owner, and next action. If the report matches approved escalation rules, apply them rather than assuming the old priority remains correct.
Aggressive merging keeps queues short but can hide legitimate work. Loose creation preserves every contact while overwhelming staff with duplicates. Review uncertain matches and maintain explicit rules for when issues belong together.
Test concurrent calls, repeated events, and a closed ticket the tenant disputes. Review duplicate job prevention for technical action-state handling.
Questions about duplicate tickets
Should the caller receive the existing ticket number?
Only through the manager's approved verification and disclosure process, with an accurate explanation of its current status.
Can an old closed ticket be reopened automatically?
Use the explicit management workflow. A follow-up review, reopening, and new request have different meanings.
What if matching remains unclear?
Capture a reconciliation request and preserve the tenant's report. Do not discard it or create another consequential action blindly.