How internet service providers can make support processes controllable: self-service, CRM, and ticketing

How to turn an inquiry into a manageable process

A manageable support process can be broken down into five steps.

‍

1. Capture the request

The process begins with a specific observation from the customer. This could be a lost internet connection, unstable Wi-Fi, a problem with router setup, or a known network outage. A general description like "the internet isn't working" is usually not enough for further processing. Self-service can clarify the situation by asking targeted questions about when the problem started, which devices are affected, and under what circumstances it occurs.

‍

2. Verify and narrow down the request

Next, the digital process performs appropriate checks and troubleshooting steps. Depending on the use case, this may include a connection check, a router test, a speed test, or a Wi-Fi measurement. The result can be a direct solution, clear information, or the identification of a potential cause. Even an unresolved request gains structure through this process.

‍

3. Consolidate relevant context

If personal assistance is still required, the relevant information is compiled into a single case. This includes the identified error pattern, key test results, steps already taken, and the reason for the escalation. A case or ticket number ensures that the information remains linked to the same issue and also facilitates communication with the customer.

‍

4. Hand over the case to the existing process

The case is routed to the appropriate team via the defined contact or ticketing process. The CRM and ticketing system add customer context, ownership, priority, and status. This provides the support team with a prepared foundation for their work. Which information is transferred directly or provided via a dashboard depends on the specific system architecture.

‍

5. Document and evaluate the result

After the case is resolved, it should be clear how the issue was handled. Recurring reasons for escalation provide clues on where self-service can be improved. For example, if many cases pile up after the same failed router test, it may be useful to provide additional instructions, a clearer explanation, or an extra automated check. In this way, processing data becomes the basis for process optimization.

‍

‍

Which information is relevant for pre-qualification

Pre-qualification means that a request is systematically captured and categorized before personal handling. The goal is a concise summary that allows the support team to continue working on the case immediately.

‍

The information required depends on the specific process. For a technical support case, the following areas of information may be relevant:

More data does not automatically improve a support case. What matters is its relevance to the next stage of processing. A clear summary of the findings is usually more helpful to staff than an unfiltered collection of raw technical data.

‍

Data protection, purpose limitation, and access permissions must also be considered during the design phase. Teams should only have access to the information they need for their specific tasks.

‍

How CRM and ticketing benefit from existing context

CRM and ticketing systems are often viewed together in day-to-day operations, but they serve different functions.

‍

The CRM provides customer context

The CRM primarily answers the question of who a request belongs to. It is where contract data, connection information, and previous contacts converge. This context helps support staff correctly categorize the case. For a technical diagnosis, CRM data alone is often insufficient. Only by combining it with the current error profile and the results of self-service can you see what has already been checked in a specific case.

‍

The ticketing system manages the workflow

The ticketing system answers the question of how a request is to be processed. It tracks elements such as status, priority, the responsible team, deadlines, and internal notes.

‍

The quality of a ticket depends significantly on its content. A ticket stating "Internet not working" requires further follow-up questions. A pre-qualified request can already show:

• what the problem is
• which components are affected
• which checks have been performed
• what the results are
• which measures have already been taken
• why further processing is necessary

This allows the ticketing system to better fulfill its primary purpose: routing the request to the appropriate workflow.

‍

The ticketing function is a potential hand-off point for issues that cannot be fully resolved via self-service.

‍

The dashboard provides an operational overview

A service dashboard can visualize the processes completed within the app and display relevant technical information. This gives service agents an additional perspective on the process history.

‍

For management, aggregated reports are key: Which processes are used most frequently? Where do customer contacts originate? Which issues occur repeatedly? The Conntac dashboard thus supports both the handling of individual cases and the analysis of self-service usage.

‍

Why integration can be implemented in stages

The term system integration often creates the expectation of a massive IT project. However, the actual effort depends on which information needs to be exchanged between which systems.

‍

Distinguishing by depth of integration helps with planning.

‍

Level 1: Defined contact path

Self-service directs customers to a suitable contact channel after a predetermined exit point. Information is not yet fully transferred to another system.

‍

This option is easy to implement but provides support with limited context.

‍

Level 2: Structured handover

Self-service summarizes inquiries, verification results, and previous steps. Information is transferred, for example, as a structured ticket or to an existing CRM or email application.

‍

The benefit lies in a uniform data structure and clear assignment to the specific case.

‍

Level 3: System-supported assignment and processing

Relevant information is assigned to the appropriate customer accounts and processes via defined interfaces. Status, priority, and responsibility can be managed within the existing support logic.

‍

This requires clearly defined data fields, identifiers, permissions, and error scenarios.

‍

Level 4: Feedback to the digital channel

Additionally, the processing status can be sent back to the app or a customer portal. Customers can then see, for example, that their request has been received or is being processed.

‍

Whether this level of development is necessary depends on the use case. A status display can reduce follow-up inquiries, but it also increases the requirements for synchronization and data maintenance.

‍

A sensible starting point therefore begins with a clearly defined process. A common use case such as router setup, connection issues, or fault reporting is better suited than attempting to connect all service processes and systems at once.

‍

Before technical implementation, five questions should be answered:

1. Which process should be improved?
2. What information does the responsible team need?
3. In which system will the follow-up processing take place?
4. How are customer accounts and cases uniquely identified?
5. What feedback do customers need after the handover?

Only then can you decide what level of integration is required.

‍

How to keep support manageable during high demand

Under normal conditions, missing information can sometimes be compensated for by asking follow-up questions or performing manual research. During network outages, activation days, or large-scale router replacements, this approach quickly reaches its limits.

‍

Structured processes help in several ways during high demand:

• Self-service answers recurring questions and guides users through standardizable checks.
• Known issues can be communicated early on.
• Unresolved requests reach support with a defined minimum level of context.
• Cases can be sorted by error type, urgency, or responsibility.
• Similar cases become easier to identify in the reports.
• Employees spend less time re-collecting basic information.

Controllability is thus achieved through two effects: some requests are resolved digitally, while the remaining cases reach support in a more manageable format.

‍

Learn how internet providers can manage planned and unplanned traffic spikes in our expertise on Peak Management.

‍

How to measure process quality

The number of tickets created does not indicate whether the interaction between self-service, CRM, and ticketing is working. A combination of digital, operational, and qualitative metrics is more meaningful.

Metrics should be evaluated separately by request type and process. A complex Wi-Fi issue can hardly be compared meaningfully with a simple service outage notification.

‍

Interpreting individual values also requires context. A short handling time is not very informative if it leads to many repeat contacts. A low transfer rate can be positive, but it may also indicate early process abandonment.

‍

The First Contact Resolution helps to evaluate resolution at the first point of contact. For economic assessment, contact volume, handling effort, and cost per support case are also relevant.

‍

How MyProvider complements existing system landscapes

MyProvider connects a self-service app for customers with the Conntac dashboard for service and management. Guided processes provide support for tasks such as setup, troubleshooting, Wi-Fi optimization, and outage notifications.

‍

If personal handling is still required, relevant information from the process to date can be provided to support. Requests can be integrated into existing workflows via defined contact and ticketing processes. The dashboard makes digital operations and evaluations visible to the service organization.

‍

What this integration looks like in practice depends on the existing systems, the chosen use case, and the agreed technical implementation. CRM, ticketing systems, or ACS are not simply replaced across the board. The goal is a clear division of tasks, where self-service prepares and complements existing support processes.

‍

Frequently asked questions about self-service, CRM, and ticketing

How can self-service be integrated into an existing CRM?

First, it must be determined which information the CRM requires for the respective use case. This can include customer identification, the nature of the request, verification results, and a case number. The technical implementation depends on the available interfaces and the desired depth of integration.

‍

Does a self-service solution replace the existing ticketing system?

As a rule, the ticketing system continues to manage open cases. Self-service can resolve requests digitally or prepare unresolved cases in a structured manner for the ticketing system.

‍

What role does the case number play?

The case number connects customer information, the digital process, and subsequent handling. It enables clear identification and helps keep information consistent across multiple contact points.

‍

What data should self-service pass on to support?

The most important requirements are the specific request, relevant verification results, steps already taken, and the reason for the handover. Depending on the process, this may also include customer, contract, device, or connection data.

‍

Does the entire system landscape have to be rebuilt for self-service?

The scope depends on the use case. A step-by-step approach is often sensible: a clearly defined process is first established from a business perspective and then connected to the data and systems actually required.

‍

Which processes are suitable for getting started?

Frequent and clearly definable requests are ideal, such as router setup, connection testing, Wi-Fi optimization, or outage information. For these processes, the necessary information, verification steps, and handover points can be defined with relative clarity.

‍

How do support teams benefit from structured pre-qualification?

Employees gain a better foundation for categorizing cases. This reduces the need for basic questions, repetitive checks, and manual research. The actual impact should be measured through processing time, repeat contacts, misrouting, and resolution rates.

‍

Conclusion: Controllable service requires clear system roles

Self-service, CRM, and ticketing form a unified support process when tasks and information flows are clearly defined. Self-service guides customers, performs checks, and structures the request. The CRM provides customer context. The ticketing system organizes responsibility, status, and further processing. The dashboard creates transparency regarding digital operations and their usage.

‍

For internet service providers, the decisive step comes before technical integration: first, the specific use case, the required information, and the subsequent processing path must be established. This determines which systems are involved and which interfaces are actually needed.

‍

A step-by-step approach reduces complexity. At the same time, it creates a solid foundation for integrating further processes in a targeted manner later on.

‍

Embedding self-service into existing support processes

Learn how MyProvider complements existing support systems and better prepares inquiries.

Schedule your personal demo now

‍