Managing Linked Tickets for Outages and Emergencies in Visp.net Service Desk

Introduction

During outages, emergencies, scheduled maintenance, or widespread service disruptions, support teams may receive multiple tickets from customers reporting the same underlying issue. The Linked Tickets feature in Visp.net Service Desk helps organize those related tickets by connecting them to a primary incident ticket.

For outage management, the most effective approach is to use a parent-child ticket structure:

The parent ticket represents the main outage, emergency, or root cause.
The child tickets represent individual customer reports related to that larger issue.

This structure allows your team to track the outage from a central ticket, identify affected customers, reduce duplicate work, and support more accurate post-outage communication.

Prerequisites

Before managing linked tickets for an outage or emergency, make sure you have:

Access to Visp.net Service Desk.
Permission to view, edit, and link tickets.
A designated ticket for the main outage or emergency.
The ticket IDs or identifying details for customer tickets affected by the outage.
A clear internal process for:
- Declaring an outage.
- Creating a parent outage ticket.
- Linking related customer tickets.
- Resolving or closing outage-related tickets.
- Communicating with affected customers.

1. Understand How Linked Tickets Support Outage Management

Linked Tickets allow you to establish relationships between tickets. During an outage, this helps your team manage multiple related customer reports as part of one larger event.

Why linked tickets are important during outages

Centralized incident tracking
- The parent ticket becomes the main record for the outage or emergency.
Clear customer impact visibility
- Child tickets show which subscribers reported issues related to the outage.
Reduced duplicate work
- Teams can avoid troubleshooting each customer ticket as if it were unrelated.
Improved communication
- Support staff can identify affected customers for updates or follow-up.
Better operational awareness
- Technicians and managers can see the scope of the incident from the parent ticket.
Cleaner reporting
- Related tickets can be reviewed together for post-incident analysis.

2. Identify When to Use Parent and Child Tickets

Use a parent-child structure when one main issue affects multiple customers, services, or locations.

Use a parent ticket for

The outage root cause.
The primary network or infrastructure issue.
The main emergency event.
A planned maintenance activity.
A major service disruption.

Use child tickets for

Individual customer reports.
Subscriber-specific troubleshooting notes.
Follow-up work for affected customers.
Customer-specific equipment issues related to the outage.
Service restoration confirmation.

3. Create or Identify the Parent Outage Ticket

The parent ticket should represent the main outage or emergency.

Examples of parent outage tickets

Region-wide Internet Outage – North Sector
Main Fiber Line Cut – XYZ Area
Core Server #3 Offline – Affecting VoIP Services
Planned Network Upgrade – Downtown Area – July 15, 2025
Power Surge – Damaged Access Point at Main Tower

Recommended information to include in the parent ticket

Outage title or summary
- Use a clear name that identifies the affected service or area.
Affected area
- Include neighborhood, region, tower, access point, node, or service zone.
Reported start time
- Document when the issue began or was first reported.
Known symptoms
- Examples: no internet, intermittent connectivity, no dial tone, degraded speeds.
Suspected or confirmed cause
- Include details such as fiber cut, equipment failure, power issue, or maintenance.
Assigned team or technician
- Assign ownership for restoration work.
Current status
- Use an appropriate status such as Open, Pending, In Progress, or your organization’s equivalent.
Customer communication notes
- Include any messaging already sent or planned.

4. Determine Which Customer Tickets Should Be Linked

Before linking tickets, confirm that each customer ticket is related to the outage.

Review each customer ticket for

Subscriber location.
Reported symptoms.
Time the issue began.
Affected service type.
Equipment or infrastructure involved.
Notes from support or field technicians.

Link the ticket when

The symptoms match the outage.
The customer is in the affected area.
The issue started during the known outage window.
The affected service matches the parent outage ticket.
Support or network operations confirms the relationship.

Avoid linking unrelated tickets, even if they appear similar. Incorrect links can cause confusion, inaccurate reporting, and improper customer communication.

5. Link a Customer Ticket as a Child of the Parent Outage Ticket

To connect an individual customer ticket to the main outage ticket, link it as a child ticket.

Steps to link a child ticket

Open the customer ticket
- Open the individual subscriber ticket affected by the outage.
Scroll to the Linked Tickets section
- Locate the Linked Tickets section in the ticket view.
Select the relationship type
- Open the relationship dropdown.
- Select is child of.
Search for the parent ticket
- In the Search Ticket ID or… field, enter the parent outage ticket ID or relevant keywords.
Select the correct parent ticket
- Choose the parent outage ticket from the search results.
- Confirm the ticket ID and summary before linking.
Click Link Ticket
- Select Link Ticket to create the relationship.
Verify the link
- Confirm that the customer ticket now shows it is a child of the parent outage ticket.

Repeat this process for each customer ticket related to the same outage.

6. View All Child Tickets from the Parent Outage Ticket

After customer tickets are linked, the parent ticket provides a centralized view of affected subscribers.

Steps to review linked child tickets

Open the parent outage ticket.
Scroll to the Linked Tickets section.
Review the list of tickets linked as child tickets.
Click any linked ticket ID to open the customer-specific ticket.

Use this view to identify

Customers affected by the outage.
Duplicate or overlapping reports.
Subscriber-specific notes.
Customers requiring follow-up.
Tickets that may need to remain open after the outage is resolved.

7. Use Linked Tickets During the Outage Response

Linked tickets help support, dispatch, and technical teams coordinate work while the outage is active.

For support teams

Check whether a customer’s issue is part of a known outage.
Link new customer reports to the parent ticket.
Avoid creating unnecessary duplicate troubleshooting tasks.
Provide consistent updates based on the parent ticket status.

For technicians

Review the parent ticket for the root cause and restoration plan.
Use child tickets to identify affected customers or locations.
Document work performed at the outage level when appropriate.
Add customer-specific notes to child tickets when needed.

For managers and dispatchers

Monitor the scope of the outage.
Track the volume of customer reports.
Assign resources more effectively.
Prioritize restoration based on impact.

8. Use Common Outage Linking Scenarios

Linked tickets are useful across many outage and emergency situations.

Internet outage

Parent ticket
- Region-wide Internet Outage – North Sector
Child tickets
- Individual customer tickets reporting:
  - No internet connection.
  - Intermittent connectivity.
  - Slow speeds related to the outage.

Scheduled maintenance

Parent ticket
- Planned Network Upgrade – Downtown Area – July 15, 2025
Child tickets
- Customer tickets created for:
  - Expected service interruption.
  - Post-maintenance service issues.
  - Follow-up verification.

Server downtime

Parent ticket
- Core Server #3 Offline – Affecting VoIP Services
Child tickets
- Customer tickets reporting:
  - No dial tone.
  - Unable to make calls.
  - VoIP registration failure.

Mass service disruption

Parent ticket
- Power Surge – Damaged Access Point at Main Tower
Child tickets
- Customer tickets reporting:
  - Service loss.
  - Damaged customer premises equipment.
  - Connectivity failure after the event.

9. Communicate with Customers After the Outage Is Resolved

One of the most valuable uses of linked tickets is identifying customers who may need follow-up after an outage.

Use linked child tickets for targeted outreach

After the parent outage ticket is marked Resolved or Closed, use the child ticket list to identify affected customers.

Customer outreach may include:

Service restoration confirmation.
Apology for the disruption.
Instructions to reboot equipment.
Request to report ongoing issues.
Follow-up appointment scheduling.
Credit or billing review, if applicable.

Use automated or manual communication

Depending on your Visp.net configuration, communication may be handled through:

Ticket update notifications.
Email messages.
Text messages, if enabled.
Messenger workflows, if configured.
Manual follow-up by support staff.

If automated notifications are enabled, confirm that the message content is appropriate before sending customer-facing updates.

10. Confirm Whether Child Tickets Should Be Resolved or Remain Open

Resolving the parent outage ticket does not always mean every child ticket should be closed immediately. Some customers may still require individual follow-up.

Close or resolve child tickets when

Service has been restored.
The customer does not require further assistance.
The ticket was only related to the outage notification or report.
No subscriber-specific issue remains.

Keep child tickets open when

The customer still reports service problems.
Equipment replacement is needed.
A technician visit is required.
The issue may be related but not fully resolved.
Customer confirmation is required before closure.

Review child tickets carefully before closing them in bulk or marking them resolved.

11. Use Merge Relationships for Duplicate Tickets

In addition to parent-child relationships, Visp.net may provide merge-related ticket links.

Merged to

Use merged to when the current ticket has been combined into another ticket.

The current ticket is no longer the primary working record.
The linked ticket should be treated as the main ticket.

Merged into by

Use merged into by when another ticket has been combined into the current ticket.

The current ticket remains the primary record.
Another ticket has been merged into it.

When to use merge relationships

Use merge relationships for:

Duplicate reports of the same isolated issue.
Multiple tickets created by mistake.
Redundant tickets for the same subscriber and same problem.
Consolidating overlapping service requests.

For outages, use parent-child relationships for customer impact tracking. Use merge relationships for duplicate ticket cleanup.

12. Follow Best Practices for Outage Ticket Linking

To keep outage records accurate and useful, follow these best practices.

Create the parent ticket early

Create or designate the parent ticket as soon as a widespread issue is identified.
Use a clear title that staff can easily recognize.

Use consistent naming

Include the affected service, location, and issue type in the parent ticket summary.
Example: Outage – Fiber Cut – West Service Zone

Link only confirmed or likely related tickets

Avoid linking tickets based only on general symptoms.
Confirm service area, timing, and outage impact.

Document the reason for linking

Add a note when the relationship may not be obvious.
Example: Linked to parent outage ticket due to matching service area and outage start time.

Keep customer-specific details on child tickets

Use the parent ticket for outage-wide updates.
Use child tickets for subscriber-specific notes, equipment issues, or follow-up tasks.

Review linked tickets before closure

Confirm whether each child ticket can be resolved.
Do not close tickets that still require customer-specific work.

Use the parent ticket for the official outage timeline

Document key timestamps such as:
- First report.
- Outage confirmation.
- Technician dispatch.
- Root cause identified.
- Service restored.
- Customer notifications sent.
- Final resolution.

Coordinate communications

Ensure support, dispatch, and technical teams use the same outage status.
Avoid sending conflicting updates to customers.

Conclusion

Linked tickets in Visp.net Service Desk provide a structured way to manage outages, emergencies, and widespread service disruptions. By using a parent ticket for the main outage and linking affected customer tickets as child tickets, your team can centralize incident tracking, improve technician coordination, reduce duplicate work, and communicate more effectively with affected subscribers.

For best results, create the parent outage ticket early, link only relevant customer tickets, maintain clear status updates, and review all child tickets before closing them. This approach improves operational efficiency, strengthens outage documentation, and supports a better customer experience after service is restored.