CRM KitsAppliance repair services
Diagnose once. Fix on the return visit.
Appliance repair is a two-visit trade with a wait in the middle. Reset draws every job as one row on one fourteen-day axis: the day somebody went out, the gap while the part is on its way, and the day somebody is going back. The rows with no day going back are the ones you can see at a glance.
One row, one job.
Every job in the selected pipeline sits on one shared fourteen-day axis, grouped by appliance type, with an emerald rule on today. Each bar carries the diagnostic visit day, the hatched parts wait, and the return visit day, or an open dotted segment when no return is booked.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Two-visit tracker with a fourteen-day axis, appliance-type groups, a today rule and a job sheet
- Repair jobs grouped by native pipeline stage beside the recorded job state
- Parts waiting, longest wait first, with a per-line overdue marking
- Return visits by date and the diagnosed jobs with none booked
- Insights drawn from recorded visits, part lines and quoted references
- A light type-only Reset index rail with permission-filtered All CRM tools
four pipelines
- Residential repairs · 8 stages
- Warranty and manufacturer jobs · 7 stages
- Property manager accounts · 7 stages
- Maintenance plans · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Diagnostic visit preparation
- Diagnosis recorded review
- Part ordered review
- Expected part check
- Overdue part follow-up
- Return visit booking
- Return visit reminder
- Job complete review
- Thirty-day check-in
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore twelve fictional repair jobs across six appliance types, with 11 part lines and 16 recorded visits. Four are waiting on a part, one of those past its recorded expected date, five record a return visit and three record a repair. Example edits stay in the current page’s memory and reset on navigation or reload; sample jobs are never inserted into your CRM.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set company name, descriptor, promise line, and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original appliance repair helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks every cross-field rule, and compares the current record timestamp and revision before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A repair job is a native contact-linked opportunity with a namespaced appliance record (type, brand, model, serial reference, age reference and warranty flag), the recorded fault code and finding, a technician label, a quoted amount, job notes, up to 20 part lines with stable IDs, and at most one diagnostic visit and one return visit. Two jobs on the same machine stay independent; the kit keeps no appliance master record.
Visits and part lines are staff-entered records. A visit date reserves no technician, checks no availability and creates no native Calendar appointment. A part line records an order placed in the supplier’s own system: there is no parts catalog, supplier integration, delivery feed or inventory. A part line is marked overdue only when its recorded expected date has passed and it is not received, which is the only warning state in the kit. The warranty flag is a staff entry; nothing checks coverage or submits a claim. The recorded job state is derived from the visits and part lines on every read, and the helper exposes no stage mutation at all, so it can never disagree with the native pipeline stage.
Four optional pipeline templates and nine inactive workflow drafts. Twelve fictional in-memory repair jobs with 11 part lines and 16 recorded visits.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Appliance Repair Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Reset keeps its index rail across the original repair views and the native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More home services kits
Browse all 220 kits
