CRM KitsLocksmiths
Answer the call that is waiting.
An urgency queue over a hardware ledger. Tumbler puts lockouts waiting now beside the rekeys, installs and commercial master-key work that are measured in dates, locks and keys cut.
Three urgency bands, one screen.
Open jobs sit in the lockout now, today and scheduled bands. Every row carries the site, the job type, the technician label, the minutes since the call and a strip of locks serviced, keys cut and hardware still to source.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Queue operating view
- Jobs operating view
- Lockouts operating view
- Rekeys and installs operating view
- Hardware operating view
- Commercial accounts operating view
- Insights operating view
- Three native form drafts and three editable document templates
- An editable visit log per job with preserved row history
four pipelines
- Locksmith service jobs · 7 stages
- Emergency lockouts · 7 stages
- Rekeys and installs · 7 stages
- Commercial master-key accounts · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Lockout dispatch
- Arrival note
- Authorization check
- Hardware sourcing
- Install scheduling
- Rekey completion
- Commercial account review
- Job follow-up
- Review request
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Service request
- Rekey and key count details
- Job feedback
- Job authorization record
- Key and hardware schedule
- Completion summary
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 13 fictional jobs: three lockouts with one past the recorded threshold, six scheduled rekeys and installs, and four commercial account visits. Sample edits stay in memory and reset on navigation or reload.
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 business 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 backend helpers are required for connected job creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and refuse a code-like value on the server as well as in the browser. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked job holds the site record, the urgency band, the call and arrival times, the technician label, the locks serviced, the keys cut, the hardware lines and a visit log. Keyway and stamped labels are descriptors; key bitting, key codes, safe combinations, alarm codes and door codes are never stored.
A recorded wait turns red only when a lockout passes the 45-minute threshold. An arrival cannot be recorded before its call, and a lock recorded as opened needs a verified authorization with a method label. The authorization flag records that staff checked the customer's right to access; it is not an identity verification service. The kit does not dispatch, track location, hold key codes, source or order hardware, take payments or send messages.
Four optional pipeline templates and nine inactive workflow drafts. 13 fictional in-memory examples.
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 Locksmith 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?
Tumbler retains its application frame across the kit views and native CRM tools in the same signed-in account. 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
