Aftercare is repeat business: turning handover into an AMC

The months after handover quietly decide whether a client ever calls you again. Treat that window as a real operation, not an afterthought, and interior aftercare warranty and AMC become the reason a customer comes back for their next home, their office, or a friend's project.

Why aftercare is where repeat business is won

You spent months turning a lead into a deal, a deal into a project, and a project into a signed handover. Then the site clears, the team moves on, and the relationship goes quiet until a hinge sags or a laminate lifts. What happens next is the whole game. A complaint handled cleanly, on the same phone the customer already uses, turns a defect into proof that you stand behind your work. A complaint lost in a WhatsApp thread turns a happy client into a one-time client.

Aftercare is not a cost centre you tolerate. It is the cheapest sales channel you have, because the hard part, earning trust, is already done. The firms that grow steadily in India are rarely the ones chasing the most new leads. They are the ones whose old customers keep coming back and keep referring, and that only happens when service after handover feels as organised as the build itself.

A defect handled well is not a problem. It is the most convincing sales pitch you will ever make to a customer who has already paid you.

From handover to a running service operation

The mistake is treating post-handover service as ad hoc favours. Panzo Aftercare runs it as an actual operation, with every record hanging off the same customer, project and installed-asset register as the rest of your pipeline. That means you finally see the full life of an account: the quote, the build, the handover, and every service touch after it, in one place instead of scattered across chats and spreadsheets.

The moving parts you actually get today are concrete, not aspirational:

• Service tickets with TKT-YYYY-NNNN numbering, an admin-defined stage flow from Raised to Closed, an SLA clock, and an honest close reason on every ticket so your dashboard reflects reality.
• Service tasks, the real steps under a ticket (inspect, repair, replace, follow up), kept separate from your project task list so aftercare never pollutes execution.
• Appointments, one scheduled site visit at a time, run through a proper state machine with required photo evidence on a completed repair.
• Service visit charges and service invoices, numbered SVC bills that age and accrue interest like any other receivable.
• Warranty policies with asset activation and AMC preventive entitlements, so cover is honest and routine visits stay on schedule.
• A public complaint form your customers can use from your website with no login.

The service ticket lifecycle, start to close

A ticket is the life of one complaint. What keeps it honest is that the engineer never declares their own work done. They complete a site visit with photos, the ticket stays In Progress, and a manager reviews the evidence before it is marked Fixed and Closed with a recorded reason.

1. Raise the ticket

   It comes in by phone, by your public complaint form, or from a snag, and opens as Raised with a ticket kind (General Service, Snag, or Warranty Claim) and an SLA target for its category.

2. Assign an engineer

   A manager assigns it from the queue, on web or on the phone. A manager on mobile sees the whole non-closed queue, including tickets that still need assigning.

3. Run the visit

   The engineer taps Start Visit on arrival and the ticket moves to In Progress by itself. They complete with an outcome, a work note, time on site, and photos, which are filed against the ticket and surface in the project's Documents.

4. Review, fix and close

   A manager checks the evidence, marks the ticket Fixed, and closes it with a reason that separates a real fix from a duplicate or a customer who went quiet. Mark Fixed and Close are gated on a permission, not a job title.

Because a single ticket can need several visits, no access first, then parts, then the fix, each trip is its own appointment with its own outcome. An access-blocked visit needs only a clear reason and is never forced into warranty or labour fields, so your records stay truthful about what actually happened.

Making interior aftercare warranty and AMC pay for themselves

This is where service stops being a drain and starts being a reason to return. When a project reaches handover completed, Panzo builds the installed-asset register from the deal BOQ automatically, with brand and serial left blank for your operator to fill rather than guessed, and attempts warranty activation on a best-effort basis so an aftercare hiccup can never block the handover itself.

Warranty status is derived from the activation and expiry dates, so it is always right without a nightly job. When a claim arrives, Panzo surfaces advisory eligibility and flags (expired, payment due, reported late, possible latent defect, third-party tampering) for an authorised person to decide. It never auto-rejects a customer, and it pre-fills the visit's cover from the claim and the linked asset. The AMC side is the preventive half: each customer gets four quarterly windows across year one, each consumed once when a preventive visit is completed, so the routine maintenance that keeps a home looking new stays on the calendar instead of being remembered too late.

Billing the work you should be paid for

Plenty of interior firms lose money after handover simply because chargeable service quietly becomes free service. Panzo keeps that split clean. Your standard rates (inspection, logistics, labour per hour, minimum billable hours) live in Control Panel, while the actuals for a given job, material cost and hours on site, are entered on the visit. When a visit is not covered, Raise Invoice turns that snapshot into an SVC service invoice due on the terms and working-day calendar you already use, with 2% per month late interest, and a database constraint means a double click can never bill a customer twice.

Service receivables then show up in your Finance overview with an "of which service" metric, so aftercare income is visible alongside project billing rather than hidden. A couple of honest caveats: there is no client-facing invoice PDF or automatic email yet, so sending stays manual, and the service invoice carries a single tax percentage with no HSN or SAC codes, so treat it as an internal bill rather than a fully GST-compliant tax invoice for now.

Let customers reach you the way they already do

The last piece is intake. Panzo gives you an embedded public complaint form you can place on your website through an expiring, revocable link, so it never trusts an organisation ID from the browser. A customer enters their registered mobile number and, if they have it, a project code. An unambiguous match raises a normal ticket immediately, and anything uncertain is held as a pending request for your service desk to verify before approving.

The confirmation screen is deliberately uniform: it reveals nothing about whether a number belongs to a customer, returning the same "request received" message and an anonymous reference either way, which keeps it within India's DPDP expectations. It is rate-limited per IP and phone and carries a honeypot spam guard. Pair it with the way most Indian customers actually talk to you, and read our take on WhatsApp for interior businesses so intake and updates land where people already are.

How aftercare fits the rest of the pipeline

Aftercare is not a second CRM. It reuses the same customer, project, installed-asset, Products and Finance foundations as everything before it, which is exactly why the account view is complete. If you want the mental model for how leads, deals and projects flow into this, our three-object pipeline post lays out the spine that handover and aftercare hang off. And if you are still deciding whether all of this belongs in one system, the owner's view of Panzo shows why one rulebook across build and service beats stitching tools together.