A customer opens the mobile app, sees a login screen they do not recognise and calls the person who installed the system. The recorder, cameras and network may all be working. The problem is that the installer is the only person who knows how those pieces were configured to work together.

That is why after-sales responsibility often follows the installer relationship. The customer remembers who surveyed the site, chose the layout, connected the recorder, configured remote access and handed over the login. The camera manufacturer may own the hardware warranty, but the installer owns the operational context the customer needs when the system stops making sense.

For an installer, this creates a decision. Treat every post-handover question as invisible goodwill, or define the support boundary, measure the work and give the customer a clear way to buy help after installation. The better option is to make support a documented part of the handover and contract before the first call arrives.

The person who configured the system becomes the support path

A CCTV installation is a chain of dependencies. The camera has an address. The recorder has storage and user settings. The site router decides how traffic leaves the premises. Remote viewing may depend on a manufacturer service, a public address, port rules or a relay path. The mobile application adds another account and another permission layer.

The customer experiences that chain as one service. They do not usually separate a camera fault from a router change, an expired password or a recorder that has lost its connection. They call the person who can identify which part changed and what the original design intended to do.

This is an operational consequence of the installation relationship. When the installer holds the site notes, credentials, topology and commissioning history, the installer is the shortest route to an answer.

The manufacturer still has a role. A warranty process may cover a defective product, a repair or a diagnostic step. For example, Hanwha Vision America publishes a five-year warranty period for specified network products, subject to the conditions on its policy page. That fact describes product coverage. It does not transfer knowledge of the customer’s network or the installer’s configuration to the manufacturer.

That distinction explains why the customer can contact the installer even when the suspected fault is inside a camera. The next question is what kind of work the call actually creates.

The call is usually a system question

Post-installation support becomes expensive when the request is recorded only as “remote viewing is down.” That label hides several different jobs.

Customer reportPossible work behind itUseful handover evidence
“The cameras disappeared from the app.”Check power, recorder status, network reachability, account access and the remote connection path.Recorder model, site diagram, connection method and last known status.
“The password does not work.”Identify which password changed: application account, recorder user, router or a shared credential.Credential ownership, reset procedure and the person authorised to approve changes.
“It worked before the internet changed.”Check the new router, address assignment, firewall rules, remote-access service and any changed broadband path.Original network assumptions and the steps required after a router replacement.
“The app works at home but not on mobile data.”Compare local and remote paths, then check the system’s traversal or relay dependency.Remote-viewing design, supported access method and escalation boundary.
“The picture is delayed or keeps stopping.”Check upstream capacity, relay behaviour, recorder load, client conditions and whether the issue affects one user or the site.Expected viewing conditions and a record of the original acceptance test.

The installer is therefore answering a system question, even when the customer names a single camera. A useful support record preserves the relationship between the components so the installer can test the path instead of guessing from the symptom.

That record also makes the boundary between installation work and later service easier to explain.

Warranty coverage and configuration support are different jobs

A product warranty answers a question such as whether a covered device can be repaired or replaced under stated conditions. Configuration support answers a different question: what must change at this site so the customer can use the system again?

The two jobs can overlap during diagnosis. A failed camera may require a warranty process, while the installer still has to identify the unit, preserve the configuration and restore service after replacement. A working camera may produce a support call because the router was replaced, the customer changed an account setting or the remote path no longer works.

Published warranty material should be read with that boundary in mind. Hanwha’s policy, for example, lists a $49 diagnostic fee charged in advance for its out-of-warranty process. That is a vendor repair-process fee. It is not an installer labour rate, and it does not establish what a site visit, remote diagnosis or configuration change should cost.

The practical implication is simple. A warranty reference can help the installer explain where a hardware assessment belongs. It cannot serve as a price list for the work required to understand the whole installation.

Once those jobs are separated, the installer can measure the support load without arguing about whether the customer’s request is “small.”

Measure the work before deciding whether it is unpaid

Support is unpriced when the contract assigns no price to it. That is a contract outcome. The remedy is a record that shows what the work consumes.

Log each contact by issue type and capture the elapsed handling time. Include the first response, remote investigation, customer explanation, escalation, travel and any return visit. Record whether the issue was caused by the installed design, a customer-controlled change, a third-party network change, a hardware fault or an unclear handover.

A useful support log can contain:

  • site and customer identifier;
  • date, channel and issue description;
  • remote handling time and travel time;
  • parts, subcontractor or vendor escalation involved;
  • resolution and whether the same issue returned;
  • contract category: included, warranty-related, billable or goodwill.

The installer can then calculate the internal cost as support hours multiplied by the installer’s loaded hourly rate. The rate should include the labour cost and the business costs the installer chooses to assign to service work. Use the company’s own records to show how much capacity the installation relationship consumes.

After several handovers, the pattern usually becomes clearer. Some calls belong in better documentation. Some require a maintenance agreement. Some reveal a design choice that creates repeated remote-access work. Some are legitimate warranty escalations. Each category deserves its own treatment.

Measurement turns a vague feeling of support debt into a decision about scope and price.

Put the support boundary in the handover

The handover should tell the customer what was installed, what was tested and what can change the remote-viewing experience. It should also identify who controls each dependency.

Include the site network assumptions, recorder details, camera list, viewing method, account ownership, escalation route and the customer’s responsibility for approved network or credential changes. Do not place sensitive passwords in an ordinary handover document. Give the customer a controlled method for access and recovery instead.

The customer should be able to answer practical questions without calling immediately:

  • Which account opens the application?
  • Who can reset that account?
  • What happens if the router or broadband service changes?
  • Which users are authorised to request a password reset?
  • What does the installer support after handover?
  • Which requests require a paid visit or a service agreement?

Acceptance testing should cover the access paths the customer actually uses. If the customer expects viewing from a phone away from the premises, test that path before handover. If the installation depends on a particular network arrangement, write down the dependency and the consequence of changing it.

This does not eliminate support calls. It changes the call from “nothing works” to a request with a known boundary and a useful starting point.

Choose a service model that matches the dependency

There are three practical ways to handle post-installation work. The installer can include a defined period of support in the installation price, sell support as a separate maintenance service, or handle later requests at a published hourly or visit rate. The right choice follows the system’s dependency on the installer and the customer’s need for response.

Included support is easiest to understand when its duration, channels and exclusions are explicit. A separate maintenance service works when the customer values response, periodic checks or help after network and account changes. Periodic checks are also where reactive support starts to become proactive service; Proactive vs Reactive Surveillance sets out what that word should mean. A billable reactive model is clearer when support demand is occasional and the customer accepts response times that depend on availability.

Each model needs a boundary. A service agreement can cover remote-viewing diagnosis while charging separately for broadband faults, civil work, new cameras, cabling changes and customer-requested redesign. A reactive rate can cover remote investigation while defining when a site visit, vendor escalation or replacement becomes a separate charge.

Do not use a warranty period as a substitute for a service term. The manufacturer’s product coverage and the installer’s ongoing availability answer different customer needs.

For installations that need browser-based or branded remote viewing, the same boundary applies. A platform may change the media path or user experience, but it does not remove the need to define who owns account administration, site networking, support response and customer changes. Putting existing CCTV in a browser also requires decisions about the existing recorder and stream path before anyone promises a finished experience.

Choose one support model, write its limits into the handover and review the support log against that model. When the same issue repeatedly crosses the boundary, improve the design or change the service terms rather than treating the call as an exception.

Reduce the calls that come from preventable ambiguity

Some support work is created by a system that was commissioned successfully but explained poorly. The customer may know that remote viewing works while lacking the information needed after a router reset, phone replacement or password change.

A short customer-facing guide should use the customer’s language. “The cameras are offline” needs a different first step from “the app has forgotten my login.” Give the customer a safe check they can perform, the information to collect and the point at which to contact the installer.

Keep a separate installer record with the technical detail required for diagnosis. It should show the installed topology, access method, configuration decisions and changes made after handover. A support call becomes shorter when the person receiving it can see the original design and compare it with the current state.

For multi-site customers, standardise the handover and escalation format across locations. Multi-site surveillance architecture introduces its own operational dependencies, so the support path should identify the site, local network contact and central monitoring responsibility before an outage occurs.

Reducing avoidable calls is useful even when the installer intends to charge for support. It preserves capacity for faults that require engineering judgment and gives the customer a faster route to resolution.

Bottom Line

Your client calls you because you hold the configuration context and the customer relationship that connect cameras, recorder, network and remote access. Product warranty coverage may help with a defective device, while it does not define who diagnoses the site or pays for configuration work.

Document the dependency, measure every support category and choose a clear service model. The installer can then reduce preventable calls and price the remaining work from actual effort rather than absorbing it by default.

Measured support is also the starting point for recurring revenue. That opportunity gets its own post later in this series.

What's Next

The companion piece, The Handover Call: What CCTV Customers Ring Their Installer About First, follows the technical causes behind the remote-viewing problems that reach the installer after handover. Read it when you want to improve the checklist and diagnose the call more quickly.

FAQs

Why do CCTV customers call the installer instead of the camera manufacturer?

They call the installer because the installer usually holds the site configuration, integration history and handover relationship. The manufacturer may handle a product warranty or repair process, while the installer can identify how the complete system was connected and what changed.

Does a camera warranty cover the installer’s support time?

Usually, a warranty statement describes product eligibility and the manufacturer’s repair or replacement process. It does not automatically set an installer’s labour rate for remote diagnosis, travel, configuration or customer training, so those terms should appear in the installation or service agreement.

How should a CCTV installer measure after-sales support?

Record each contact by issue type, handling time, travel, escalation, resolution and contract category. Multiply support hours by the installer’s own loaded hourly rate, then use the record to decide which work belongs in handover documentation, a maintenance agreement or a billable request.

What should a CCTV handover document include?

It should identify the installed equipment, remote-viewing method, account ownership, network assumptions, approved recovery process and support boundary. It should also explain what happens after a router, broadband service, phone or customer credential changes.

Can a browser-based video platform remove CCTV support calls?

No platform removes the need to define ownership of the site network, accounts, media path and support response. Samvyo is based on SFU architecture and offers embeddable SDKs with OEM and white-label depth, but an installer still needs a clear agreement covering what the customer can change and what support the installer provides.

Should CCTV installers charge for every support call?

They should choose a defined model rather than leave the question unresolved. Support can be included within stated limits, sold through a maintenance agreement or charged by time and visit, with exclusions for network faults, new work and customer-requested changes where appropriate.