GoSeedly Process Server Kit
A service board for process serving offices: every job from the papers arriving to the affidavit going back, each attempt logged with its date, time and outcome, serve-by dates in plain words and affidavit status by job. Knockbook keeps jobs, attempts, due dates and affidavits in one connected workspace, and keeps the respondent to a name and the address your client supplied.
YOUR KNOCKBOOK WORKSPACE
01 — BOARD
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / BoardJobs past the client's serve-by date, planned attempts nobody logged and affidavits past the client's return date lead. Then every job sits in its lane, new, attempting, delivery recorded, affidavit returned or closed, with one tally mark per logged attempt.
02 / AttemptsThe last 14 days of attempts by day, then the full log newest first with time, window, outcome as recorded, server and recorded miles in their own column.
03 / Due datesPast the serve-by date, due today, due in the next 7 days and later, each with attempts logged, the planned next attempt and the court date as your client gave it.
04 / AffidavitsJobs with a recorded delivery or closed unserved, by affidavit status from not started to returned to client, with the client's return-by date. Knockbook records the status; your office prepares the affidavit on the court's own form.
05 / ClientsOpen jobs, jobs received in the last 30 days, attempts logged and recorded charges per client, each in its own column, then every job by client.
06 / ServersOpen jobs assigned, attempts, recorded deliveries and recorded miles in the last 7 days per server, each in its own column, then open jobs by server.
07 / InsightsJobs by lane, attempts by outcome, days from received to recorded delivery, recorded miles by window and recorded charges by kind. Attempts, days, miles and dollars are never added together.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore 12 fictional service jobs: two new, four attempting, three with a delivery recorded, two with the affidavit returned and one closed unserved, with 21 logged attempts and 22 recorded charges. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
One contact-linked service job holds the client and their reference, the case or docket number and court as labels, the papers, the service level, the server, the respondent's name and the address the client supplied, the received, serve-by, court and planned attempt dates, every attempt with its outcome and recorded miles, the affidavit status, recorded charges and an editable checklist.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Edit business name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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 service job creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, logins, card numbers, Social Security numbers and respondent identifiers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Knockbook records what your office and servers wrote down. It gives no legal advice and makes no valid-service, court-acceptance or statutory-compliance claim; an attempt outcome is a label. It does not draft, sign, notarize or file affidavits, calculate legal deadlines, locate people, verify identities, track GPS, dispatch servers, bill or send messages. Dates of birth, ages, license and ID numbers, vehicle plates and physical descriptions of the respondent, gate, lobby and call box codes, passwords and logins, payment card numbers and Social Security numbers are refused in recorded text and in the native form drafts.
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.
DEVLAUNCH ALL ACCESS
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
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.
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.
Knockbook keeps its petrol top bar and highlighter tabs 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.
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.
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.
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.
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.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.