20 Things People Miss About Support, Service Contracts, and What Happens After Move-In

The conversation about support almost never happens before the installation agreement is signed. The integrator presents the system design, the equipment list, and the project timeline. They describe the capabilities, the scenes, the interfaces, the automation possibilities. The owner is focused on what the system will do and how much it will cost. Support comes up briefly, usually near the end: “We also offer service contracts.” A one-page summary is provided. The owner signs the installation agreement and assumes the support will be sorted out at move-in. By the time move-in arrives, the integrator is managing the next project, and the owner is on their own with a system they understand in outline but not in depth.

The twenty items below are what people miss in that process - not because they are hidden, but because nobody flagged them clearly at the right moment. Read them now, before you sign anything. If you are already in a service contract, read them to understand what you have and what you may need to add. Each item has a straightforward resolution. None of them are complicated once you know they exist.

1. People miss that the install warranty is not the same as a service contract.

A manufacturer’s warranty covers hardware defects - a Crestron processor that fails due to a manufacturing fault, a network switch with a defective port, a projector lamp that fails prematurely. The installation warranty covers workmanship - a connection that was not properly terminated, a configuration error that causes an intermittent fault. Neither warranty covers ongoing support, routine maintenance, software updates, or response to operational issues that are not defects. The warranty is a one-time backstop. The service contract is the ongoing operating model. On a $600,000 integrated system, most homeowners assume the warranty covers everything for the first year and the service contract covers everything thereafter. In reality, the warranty covers a narrow category of failure causes, and the service contract covers a defined scope of ongoing services - and the two often overlap less than owners expect. Read both documents at the same time and map what is covered by each.

2. They forget that software updates are not automatic.

Crestron control processors, network switches, wireless access points, NVR software, and virtually every other component of a smart home system receives periodic software and firmware updates. Those updates do not apply themselves. They require a technician to log in, review the update release notes, test for compatibility with the existing configuration, and apply the update during a low-usage window. Without a structured firmware management program, a system that is two years old may be running software that is eight to twelve versions behind current - accumulating security vulnerabilities and compatibility gaps with every passing quarter. Most service contracts include firmware management as a defined service. Most homeowners do not realize it is a separate line item until they ask why their Crestron system behaves differently after a manufacturer update that was applied without their knowledge by the auto-update function. Confirm with your integrator that firmware updates are managed, scheduled, and tested - not pushed automatically or ignored entirely.

3. People miss that response time and availability are different promises.

A support contract that promises “24/7/365 availability” may not promise a 15-minute response time. Availability means someone can be reached at any hour. Response time is how long it takes that person to actually begin working on the issue after being reached. These are different commitments, and both need to be explicit in the contract. An integrator who answers the phone at 2am but cannot begin remote access to your system for four hours - because the technician who answers the phone is not the technician with system access credentials - has delivered on availability and failed on response time. Ask specifically: who answers after-hours calls, do they have remote access to my system, and what is the defined response time commitment from call to active troubleshooting? Those three questions reveal the actual support architecture behind the availability promise.

4. People miss that remote monitoring requires active enrollment, not just installation.

Remote monitoring is not a feature that activates automatically when the system is installed. It requires the integrator to enroll your system in their monitoring platform, configure alert thresholds for each device category, and verify that the monitoring platform has network access to all covered equipment. On systems that were installed without a service contract, remote monitoring may never have been configured - meaning the integrator has no visibility into the health of your system until you call to report a problem. When you sign a service contract, confirm in writing that your system has been enrolled in the monitoring platform and ask for a report showing which devices are currently monitored and what alert conditions are configured. If the integrator cannot produce that report within 24 hours of your request, monitoring either is not configured or is not working correctly.

5. They forget that ISP outages are not covered.

When the internet goes down, many smart home functions go with it - not because the smart home system failed, but because it depends on cloud services, remote access, and internet-connected devices that require connectivity to function. A service contract does not cover ISP outages and cannot compel an internet service provider to restore service. What a good contract does cover is the network infrastructure response: confirming that the gateway, router, and modem are functioning correctly and that the failure is at the ISP level rather than within the home network. That confirmation is valuable - it tells you whether to call your integrator or your ISP. The distinction matters at 7am when nothing is working and you have a video call in 90 minutes. Ask your integrator to document the escalation path for ISP-suspected outages so you know exactly who to call and in what order.

6. People miss that the integrator's support team may be one person.

A small AV integration firm may have a support “team” that consists of one person - the owner, or a lead technician, who handles support calls between installation projects. When that person is on a job site, on vacation, or unavailable for any reason, there is effectively no support. This is the most common support failure mode in the luxury residential integration market, and it is invisible until the moment you need support and cannot get it. Ask your integrator directly: how many people are on your support team, what are their names, and who covers when the primary support person is unavailable? A team of one is not a support team - it is a best-effort arrangement that will fail at the worst possible time. A real support operation has minimum two dedicated support staff, a documented escalation path, and a named backup for every function.

7. People miss that discounts on future work are negotiated at contract time, not requested later.

The discount on future project work - new rooms, new equipment, system upgrades - is a benefit that should be negotiated into the service contract at signing, not requested as a favor when a new project comes up. Integrators who offer service contracts typically have a defined discount schedule for contract holders, but that discount is often not automatically applied unless the client asks for it explicitly. At contract signing, ask: what is the discount on future project labor, what is the discount on new equipment purchases, does the discount apply to subcontractor costs as well as integrator costs, and is the discount documented in the contract or subject to change? A discount that is described verbally at signing but not written into the contract is a courtesy, not a commitment. Get it in writing before you need it.

8. They forget that after-hours calls may cost extra.

Many service contracts include daytime support at no additional charge per incident and bill after-hours calls at a premium - typically 1.5 to 2 times the standard hourly rate for remote calls and 2 to 2.5 times for on-site visits between 6pm and 8am or on weekends and holidays. On a contract that appears to offer 24/7/365 coverage, after-hours pricing can produce a $600 to $1,200 bill for a two-hour Sunday evening visit that was expected to be covered. Read the after-hours rate schedule before signing. Premium-tier contracts typically waive after-hours premiums for Severity 1 emergencies and cap them for Severity 2 issues. If after-hours premium rates are a concern, negotiate a cap or a waiver for defined emergency categories at contract execution.

9. People miss that the service contract may not transfer with the house.

If you sell your home, the service contract that was structured around your relationship with the integrator may not automatically transfer to the new owner. Some contracts are property-specific and fully transferable. Others are owner-specific and terminate at sale. Understanding the transfer terms matters both for your own planning and for the property’s value - a luxury residence with a documented, active service contract and a maintained technology system is worth more than one without. If your contract is not transferable, negotiate transferability at signing or at renewal. A transferable service contract becomes a selling point: the new owner inherits an active support relationship, current firmware, a service history log, and a known-good system. That is worth money. And ask the integrator what their relationship with the new owner looks like - will they conduct a handoff walkthrough, update contact information, and provide the service history? Those details should be documented.

10. They forget that annual audits are proactive, not reactive.

An annual systems audit is a scheduled, comprehensive review of every supported system - not a response to a reported problem, but a proactive health check conducted on a defined schedule. A proper audit covers: firmware versions across all devices against current release levels, network utilization and capacity headroom, battery status on all wireless devices, camera coverage and image quality, backup and redundancy verification for NVR and network switching, and a structured owner interview to capture any operational concerns. The audit produces a written report with prioritized recommendations - not a verbal summary, a written document the owner can review and act on. Most service contracts include one audit per year. Some premium contracts include two. Confirm that the audit is a documented deliverable with a written report, not a 30-minute site visit that generates a phone call. The audit report is also the record you use to evaluate whether the support you received in the prior year matched what you paid for.

11. People miss that firmware updates can break things.

Firmware updates improve security, add features, and fix bugs. They can also introduce new bugs, change system behavior in ways that affect automation logic, and occasionally break integrations with other systems. A professional support operation reviews every firmware release before applying it to client systems - checking the release notes, confirming compatibility with the existing configuration, and testing on a non-critical device before deploying broadly. An integrator who applies firmware updates automatically and at scale - pushing the update to all client systems simultaneously without review - is treating a risk management function as a maintenance task. Ask your integrator: what is your firmware update process, who reviews release notes before deployment, how do you test for compatibility, and what is your rollback procedure if an update causes a problem? Those questions reveal whether firmware management is a discipline or a checkbox.

12. People miss that ‘priority scheduling’ needs a definition.

Priority scheduling for service contract holders means the client’s service requests are scheduled ahead of non-contract clients and ahead of the general project queue. It does not mean same-day service for every request - it means the client gets the next available slot, not a slot three weeks out because the project pipeline is full. The definition of “priority” should be specific: how many days maximum to the next available appointment for a Severity 2 issue, what is the guarantee for Severity 1, and how is priority defined when multiple contract holders make requests simultaneously? Without a specific definition, priority scheduling is a sentiment, not a commitment. In a market like NJ/CT/NY metro where qualified integrators have full project pipelines, the difference between priority and standard scheduling can be three to six weeks on a non-emergency request. That gap matters when you are planning a system upgrade or a new installation that has a deadline.

13. They forget that multi-property bundling requires proactive setup for each location.

A multi-property service contract is not active at all locations automatically. Each property must be individually enrolled in the monitoring platform, with site-specific documentation, contact information for local caretakers, and confirmed network access for the support team. On a multi-property bundle, the administrative setup for each location can take four to eight hours of integrator time and should be completed before the contract becomes effective at that location. Properties where remote access has not been configured are not protected by the monitoring component of the contract. Confirm, for each covered property, that remote access has been verified and the monitoring enrollment is active. Ask for a per-property monitoring confirmation report. For vacation properties that are seasonally occupied, confirm the process for re-activating monitoring at the start of each season and deactivating it at close.

14. People miss that MTTR is the metric that actually matters.

Mean Time to Resolution (MTTR) is the average time from when a support ticket is opened to when the issue is confirmed resolved. It is the single most meaningful measure of support effectiveness - more meaningful than response time alone, because a fast response that leads to a slow resolution still leaves the owner with a broken system for a long time. Ask your integrator for their MTTR data before signing the service contract. A professional support operation tracks this metric by severity tier and can report it. Target MTTR for a Severity 1 residential issue should be under four hours. Severity 2 should be under 24 hours. Severity 3 should be under five business days. If the integrator cannot provide MTTR data, they are not measuring their own performance - which means they have no mechanism for improvement and no accountability for outcomes. That is not acceptable at the price point of luxury residential support.

15. They forget that the service contract starts at signing, not at move-in.

A service contract that begins at the contract signing date - rather than at move-in or system commissioning - means the monitoring and support coverage is active before the owner occupies the property. That matters because systems often experience their first issues during the final construction and commissioning phase, when the building is being tested under real loads for the first time. Coverage that begins at move-in leaves the owner unprotected during the period of highest system activity and highest risk of configuration-related issues. Negotiate a contract start date that aligns with commissioning, not move-in. The integrator’s support team should be engaged and monitoring from the moment the system is live - not from the moment the owner first sleeps in the house.

16. People miss that high annual spend thresholds require proactive tracking.

If your service agreement includes bundled support hours at qualifying annual spend levels, those hours do not activate automatically - they require the integrator to track your cumulative annual spend, confirm when you have reached the qualifying threshold, and adjust your support billing accordingly. Without a proactive tracking mechanism, you may reach the threshold, receive bundled support hours, and continue to be billed for support at the standard rate because no one updated the account. At contract signing, ask: how is annual spend tracked, who is responsible for notifying me when a threshold is reached, how quickly does the billing adjustment take effect, and what happens to support charges incurred between the threshold date and the billing adjustment date? Those questions protect your financial interest in a benefit that requires active administration to realize.

17. They forget that documentation is a service deliverable, not an afterthought.

The as-built documentation package - conduit schedules, rack elevations, network device inventory, system passwords, firmware versions, and warranty registrations - is a deliverable that should be included in the installation contract and confirmed complete before final payment is released. On systems installed without this discipline, the first service contractor who arrives after move-in spends the first two hours of every visit reverse-engineering the installation before they can begin addressing the actual issue. That reverse-engineering time is billable, and it compounds on every visit. A complete documentation package eliminates it entirely. If you are already in a home without complete documentation, commissioning your integrator to produce it is worth the investment - typically $1,500 to $4,000 depending on system complexity - because the documentation savings on future service calls begin immediately.

18. People miss that NVR drives are wear items with a finite life.

Network video recorders (NVRs) store security camera footage on hard drives that are specifically rated for continuous write cycles. Even rated surveillance drives have a finite lifespan - typically three to five years under continuous recording load. When the drive fails, the recording history is lost and the cameras are no longer recording. On an unmonitored system, NVR drive failure is discovered when the owner or caretaker notices that the camera feed shows old footage or no footage - which may be days or weeks after the drive failed. Proactive monitoring flags drive health indicators - SMART data showing increasing error rates or decreasing spare sectors - before the drive fails. A well-structured service contract includes NVR drive health monitoring and a replacement recommendation when a drive reaches 70 percent of its rated lifespan. Confirm that your contract includes this coverage specifically, not just “camera system monitoring.”

19. They forget that user error is the most common support call trigger.

The most frequent source of support calls on a luxury residential smart home system is not hardware failure or software bugs - it is user error. Occupants who are new to the system change settings that should not be changed, put systems into modes they do not understand, or create conflicts between manual overrides and automation logic. A well-designed support program includes user training - not just at commissioning, but on an ongoing basis as occupants change or as new features are added. Ask your integrator: is user training included in the service contract, how many hours per year, and does that training extend to new occupants or family members who were not present at the original commissioning walkthrough? An integrator who treats user training as a one-time event at move-in will generate more support calls than one who treats it as an ongoing relationship. Those calls cost money and create owner frustration that is entirely preventable.

20. People miss that the service contract renewal is a negotiation, not an automatic renewal.

A service contract that auto-renews at the prior year’s rate - or at a rate the integrator sets unilaterally - is a contract that the owner has effectively given up the right to renegotiate. Auto-renewal clauses with short cancellation windows - 30 days or less - mean the owner must remember to evaluate and potentially cancel the contract within a narrow window to preserve any negotiating use. Read the auto-renewal and cancellation terms of any service contract before signing the initial agreement. The renewal is the right moment to evaluate the integrator’s performance, negotiate the next year’s rate, add or remove covered systems, and adjust the SLA commitments based on how the prior year played out. A 60-day cancellation window gives you enough time to evaluate and, if necessary, seek competitive quotes. A 30-day window is barely enough time to evaluate. A 15-day window is a trap. Know the terms before you sign.

What These Twenty Items Have in Common

Read through the list and the pattern is clear. These are not esoteric technical issues. They are information gaps - things the homeowner was never told, or was told in a context where the implication was not obvious. The warranty versus service contract distinction. The auto-renewal window. The after-hours rate schedule. The firmware update risk. The fact that remote monitoring requires active enrollment. Every one of these items is addressable at contract signing if the right questions are asked. The challenge is that the right questions require knowing which questions to ask - and most homeowners sign installation and service contracts without that knowledge. That is what this list is for.

The resolution in every case is the same: get it in writing, in the contract, before you sign. Not in a sales presentation, not in a verbal conversation, not in a follow-up email. In the contract document. Every commitment the integrator makes - response time, firmware management, discount on future work, bundled hours at qualifying spend levels, documentation deliverables - should be a contractual obligation with a defined remedy if it is not met. That is the standard for a professional service relationship at the price point of luxury residential smart home integration.

What a Well-Structured Care Plan Looks Like

A well-structured Care Plan eliminates most of the gaps on this list by design. It defines the covered scope with a device-level list. It specifies the SLA by severity tier in a table. It defines the firmware management cadence and the testing protocol. It includes the annual audit as a documented deliverable. It specifies the discount on future work in a percentage, not a promise. It defines the spend thresholds at which support hours are bundled. It confirms that monitoring enrollment is active for each covered location. And it defines the documentation deliverables that must be received before the contract is considered fully onboarded. None of those elements are complicated to include. They require discipline and a commitment to specificity that distinguishes a professional service organization from one that is winging it. Ask your integrator to walk through their standard contract and address each item on this list. The answers will tell you what kind of organization you are working with.

Bottom Line: The twenty items above are not cautionary tales. They are a checklist. Use it before you sign. If you are already in a contract, use it to evaluate what you have and identify what you need to add. Restrepo Innovations provides Care Plans that address every item on this list, with written SLAs, documented monitoring enrollment, and defined deliverables at every phase. Call 201.405.2022 or visit our offices at 599 Franklin Ave, Franklin Lakes, NJ 07417 to review a Care Plan for your property.