At a software vendor, support is not just one department among others. It is the most frequent point of contact with customers, and often the only place where people really know how the product is used.

Well organized, it becomes a competitive advantage. Poorly connected to the rest of the company, it is reduced to a cost center putting out fires. Here is why support holds a central position at a software vendor, and how to make the most of it.

The team behind our flexible, automatable CRM tells you everything.

A department at the crossroads of the company

The quality of after-sales service weighs heavily on customer engagement. Some companies have made it their trademark, to the point that their name first evokes the quality of their service. At a software vendor, the stakes are even higher, because customers use the product every day and deal with support far more often than with their sales rep.

No support organization can be transposed as is from one vendor to another. But they all share one difficulty: support is connected to almost every other department.

What support exchanges with other departments

Billing

Is the customer up to date with payments? What level of service does their contract entitle them to? Should an out-of-contract intervention be billed? Support needs these answers when handling the request, not three days later.

Marketing and product management

Support holds information no one else has:

• the products and versions that concentrate the most difficulties;
• the versions actually used by customers, often very different from what people think;
• the foreseeable effect of retiring a version on support workload and on the customers concerned.

Development

Through the escalation mechanism, support reports bugs and enhancement requests. It thus directly influences the product roadmap, provided its reports are structured and qualified.

Sales reps

Before a renewal or upsell meeting, a sales rep must know the support status for that customer: open incidents, recent irritants, pending requests. Arriving without knowing means discovering the problem in front of the customer.

Professional services

Some requests sent to support actually fall under consulting or training. Directing them to the services teams provides better service to the customer and opens a legitimate additional sale.

Organizing escalation to development

Escalation is the most sensitive point. Without rules, two drifts appear: everything goes up to development, which is overwhelmed, or nothing does, and bugs pile up. A few principles are enough to frame it.

• Defined support levels: what the first line handles, what requires expertise, what goes to development.
• Written escalation criteria: reproducible bug, impact on several customers, no possible workaround.
• A complete bug report: version, reproduction conditions, customers affected, severity.
• A link between the bug and customer tickets, to notify everyone when the fix is delivered.
• Feedback to support on the decision taken: fix, workaround, postponement.

This last point is often forgotten. A support team that does not know what happened to its reports stops qualifying them carefully, and development receives less and less useful information. The basic support process is detailed in our article on customer support.

Why a single tool

These exchanges require information to flow. When support, billing, sales and bug tracking live in separate tools, they must be connected, and these connections are fragile.

Managing these processes in the same CRM has three advantages:

• each team works on the same customer view, including contract, invoices, tickets and opportunities;
• processes are natively connected, with no integration to maintain between disparate tools;
• the overall cost decreases, with a single tool to administer and evolve.

These processes are often joined by the management of licenses, contracts and installed equipment. A configurable CRM makes it possible to model them without custom development. To go further on day-to-day efficiency, read our article on customer support productivity.

Your questions about support at a software vendor

How many support levels should you plan for?

Two or three are enough in most cases. Beyond that, each transfer lengthens the delay without improving the answer.

Should support bill for certain interventions?

Depending on the contract, yes. The rule must be known to the customer before the request, never discovered on the invoice.

How can you prevent development from being overwhelmed?

Through written escalation criteria. A bug that cannot be reproduced stays with support until it can be.

Should sales reps have access to tickets?

Read-only, yes. An informed sales rep avoids proposing an upgrade to a dissatisfied customer.

Which indicators should you track first?

First response time and volume per version. The latter guides product decisions as much as support decisions.