Two Visit Plans
Tepia models cooling and heating tune ups per plan and per system, so a home with three units gets three checklists, not one shared visit.
Read: Service Agreement and Maintenance Plan SoftwareTepia builds custom HVAC maintenance membership apps that sell and renew service plans, schedule spring and fall tune ups against real technician capacity, and apply member benefits automatically at the job. Builds typically pair React Native or Swift and Kotlin with Stripe autopay and a ServiceTitan or QuickBooks connection.
A membership program only works when every member gets both visits on time, renews without a phone call and feels the benefit the moment a technician arrives.
Tepia models cooling and heating tune ups per plan and per system, so a home with three units gets three checklists, not one shared visit.
Read: Service Agreement and Maintenance Plan SoftwareTepia spreads tune ups across shoulder months by zip code and crew count, so July breakdown calls still find open slots on the board.
Read: Field Service Customer Portal DevelopmentCard on file renewals run through Stripe with expiring card alerts, so a lapsed card triggers a text instead of a silently cancelled member.
Read: Custom HVAC Business App DevelopmentMember discounts, priority status and waived trip charges appear on the technician screen before the repair estimate is built.
Industry figures Tepia plans around when scoping HVAC membership software.
The U.S. Energy Information Administration reports about 88 percent of US households use air conditioning equipment.
ENERGY STAR says as much as half of the energy used in a typical US home goes to heating and cooling systems.
Tepia clients report about 90 percent customer retention, the same number a maintenance membership program is judged by.
A maintenance membership looks simple on a flyer: two tune ups a year, priority service and a repair discount. Behind it sits a contract for each home, often covering more than one system, billed monthly or annually, with visits that come due in two different seasons. Tepia starts by writing down every plan you sell, every benefit attached to it and every rule your office applies from memory today.
The edge cases are where member trust is won or lost. A homeowner with a heat pump upstairs and a gas furnace in the basement needs two different checklists. A member who sells the house may want the plan transferred to the buyer. A visit the customer postponed in April still counts against the agreement in June, and technicians need to see that it is outstanding. Filter sizes, refrigerant type and the install year of each condenser belong on the system record so the technician arrives with the right parts.
Renewal rules matter too. California’s automatic renewal law requires clear disclosure of renewal terms and an easy way to cancel online, and several other states have similar statutes. Tepia builds consent capture, renewal reminders and cancellation flows into the membership app so the program holds up when a member or a regulator asks how they were enrolled.
Tepia scopes features from the plans you actually sell and the people who touch them. Most residential HVAC contractors land on a core like this:
| Feature | Who uses it | Why it matters |
|---|---|---|
| Plan catalog with tiers and per system add ons | Owners and sales managers | Lets a two system home and a condo carry different plans without manual math |
| Seasonal visit generator | Dispatchers | Creates every spring and fall tune up due for the season in one pass |
| Enrollment at the job | Technicians | Sells the plan on site with signature and tokenized card capture |
| Renewal and failed payment handling | Accounting | Retries declined cards and texts the member before the plan lapses |
| Benefit rules inside the estimate | Technicians and CSRs | Applies member discounts and priority status without anyone remembering them |
| System records with model, serial and filter size | Technicians | Puts the right filters and parts on the truck before the visit |
| Member app for booking and visit history | Homeowners | Lets members pick a tune up window and see every past visit and finding |
The enrollment step deserves care. The best moment to offer a membership is at the kitchen table after a repair, with the member discount already applied to that day’s ticket. Tepia builds the flow so the technician can show the difference on the current job, capture a signature, enroll the card and book the first tune up before the truck leaves the driveway.
Memberships create a predictable wave of work twice a year, and that wave collides with the first heat spike or cold snap. Tepia builds the scheduling logic around that tension. Cooling tune ups are released in early spring, heating tune ups in early fall, and each is offered in windows grouped by zip code so one technician can finish five or six visits in a neighborhood instead of crossing town.
Members choose a window from a text link or the app, and the system holds back a share of each day for breakdown calls once outdoor temperatures pass a threshold you set. When a member misses their window, the visit moves to a follow up list rather than disappearing, and the office can see how many visits are still owed going into summer.
Tune up findings feed the rest of the business. A weak capacitor, a dirty evaporator coil or a cracked heat exchanger recorded during a visit becomes a repair recommendation with photos, sent to the homeowner the same day. Tepia reports how many of those recommendations turn into approved work by technician, which is often the clearest view of what the membership program actually produces.
A membership app has to agree with your billing and dispatch systems on every member, every visit and every payment. Tepia connects these on most HVAC projects:
Tepia documents the sync rules for each connection during Discovery, including which system owns the member record and what happens when a card fails in one system but not the other.
Tepia runs its six phase process with the membership program at the center, and a US based project manager owns the plan from the first workshop.
Discovery typically runs 1 to 3 months, development and QA 2 to 6 months, and launch about a month. See how the process works.
If you sell one or two plans from a single location and your field service platform already handles agreements, renewals and seasonal visit lists, keep it. Tepia will say so in Discovery. Custom work makes sense when the program has outgrown the module:
A hybrid usually wins: keep the platform as the system of record and add the member experience on top. Compare approaches on our service agreement and maintenance plan software and HVAC business app pages, look through our work, or talk to Tepia about your plans.
A paragraph or two with information on your product/service or describes a problem your product/service is designed to solve.
CEO
Senior Project Manager
VP & Operations Manager