CRM KitsTowing & roadside operators
Every call logged. Every vehicle accounted for.
A tow operator does not work a board of tickets waiting for a bay. The work arrives by phone, in order, at any hour. Hook is a full dark console where the shift reads down the screen as a log and the selected call sheet stays open beside it.
The shift, in the order it came in.
A dense chronological table grouped by the recorded call date, newest day first, with monospace times and plate references so the time column reads straight down. A call still recorded as active is yellow, a cleared or cancelled call is gray, and the one red marker means a recorded priority flag. The sheet beside it holds the caller and account, the pickup and drop, the vehicle and plate, the truck and driver, the recorded requested, arrived and cleared times with the gap between the first two, the impound record and the recorded charges.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Two-column call log: a dense chronological table beside a 380px call sheet, each scrolling inside one shared height
- Yellow for an active call, the selected row and a primary action, and red for exactly one thing, a recorded priority flag
- Impound lot tile grid ordered by days held, counted from the recorded lot-in date to the console date you choose
- Accounts, trucks and releases derived from the loaded calls, each labelled as derived on screen
- Insights over recorded statuses, call types, the clear rate, arrival gap spread and reference totals by currency
- Installation-wide neutral black theme, so native CRM pages render as dark surfaces in the same frame, with full CRM tools
four pipelines
- Roadside calls · 8 stages
- Impound and release · 7 stages
- Account customers · 7 stages
- Heavy duty and transport · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Call assignment task
- Arrival check task
- Cleared call note
- Impound intake checklist note
- Notice reminder task
- Release paperwork task
- Account month-end review task
- Heavy duty scheduling task
- Driver debrief note
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore fourteen fictional calls across four fictional account customers, six of them recording a vehicle still on the lot with holds from the same night out to almost two weeks. Example edits stay in the current page’s memory and reset on navigation or reload; sample calls 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, 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 call helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, keeps stable charge IDs, preserves unknown fields inside the impound record, and checks the current record state before saving. Stage changes use the host’s own pipeline mutation, so they obey your existing roles. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A call is one dispatch request, stored as a native contact-linked opportunity with a namespaced call record name, call type, caller and account labels, pickup and drop locations, vehicle year, make, model and plate reference, truck and driver labels, the recorded call date and the recorded requested, arrived and cleared times, the recorded call status, a priority flag, an optional rate reference, an impound record and recorded charge rows. The rate reference and the charge rows stay separate from native opportunity value. Other custom fields are preserved, and charge rows are archived rather than dropped from a save.
Every cross-field rule is checked in the browser and again on the server: a requested time needs a call date, an arrival needs a requested time it cannot precede, a cleared time needs an arrival it cannot precede, a cleared call needs a cleared time, an on-scene, in-tow or cleared call needs a truck label, a transport or impound call needs a drop location, and nothing is on the lot without a recorded lot-in date. Days held is a difference between two dates and the arrival gap is a difference between two typed times, so neither is a measured response time, a service level or a charge. There is no GPS and no truck tracking, no dispatch routing and no motor club, insurer or app integration, no invoicing, payments or storage-fee accrual, no lien processing, statutory notice, title work or auction handling, no driver or caller messaging, and no calendar booking. The impound lot, accounts and trucks views are all derived from the calls that are loaded, and each says so on screen. Empty values are reported in words, so a call with no truck says "No truck recorded" rather than showing a dash.
Four optional pipeline templates and nine inactive workflow drafts. Fourteen fictional in-memory calls, six of them recording a vehicle on the lot, across four account customers.
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 Towing & Roadside 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?
Hook keeps its towing navigation across the original console views and 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 automotive & fleet kits
Browse all 220 kits
