GoSeedly Dental Practice Kit
A general office books households, not individuals. Clearday puts a family recall desk beside an unscheduled treatment column, so one call books everyone who is due and no presented plan goes quiet, inside the CRM your practice already runs.
YOUR CLEARDAY FRONT DESK
01 — DESK
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 / DeskHouseholds on the left, two thirds of the desk, with the households that have the most members due first. Each member is one row with a recall dial of months since their last hygiene visit against their own recorded interval. The unscheduled treatment column sits beside it, one card per plan still waiting on a decision.
02 / PatientsThe ledger: patient label, household, age band label, the recall dial and its state in words, open plans, the recorded last visit month and the derived desk state. Search by label, household or note, or filter to one desk state.
03 / FamiliesEvery household block with all of its members, sorted so the households with the most members due within the window come first. Two or more due is marked "book together" in words. Booking is recorded on each patient record; the kit holds no time and reserves nothing.
04 / Hygiene recallEvery recorded hygiene recall, past due at the top, with the dial, the months since the visit against the recorded interval, the contact attempts and the last contact date. Hygiene recall is a category label the desk uses to sort a call list.
05 / Unscheduled treatmentEvery plan by the plan label your office types, its recorded reference amount, the days since it was presented and its decision state: accepted not scheduled, thinking it over, needs a financing talk or declined. A plan past your recorded follow-up window says so in words. Totals by decision state are sums of recorded numbers, not a forecast.
06 / ReactivationPatients with no recorded visit inside the reactivation window your practice sets, longest away first, with the last contact date and the recall state. Both the follow-up window and the reactivation window are recorded per account with a revision guard.
07 / InsightsEvery derived desk state with the patients behind it, plus recalls due within the window, households worth one call, open plans past follow-up and reactivation candidates. Each panel states the number of loaded records it counted.
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 eighteen fictional patients in eight households. Eleven are due or past due for hygiene, five of them past due, and three households have two or more members due. Nine unscheduled plans cover all four decision states, three past the recorded follow-up window, and four patients qualify for reactivation. Sample edits stay in page 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.
PLEASE READ
THE KIT, UNPACKED
One native contact-linked opportunity is one patient relationship, grouped into a household by a label your office types. The namespaced record holds the patient label, an age band label, the household label, the preferred contact window, the last hygiene visit month, the recall interval in months, the recall state, contact attempts, the last contact date, the last visit month, a non-clinical staff note, unscheduled plans as child rows with stable IDs, and an editable front desk checklist. Other custom fields are preserved, including every field written by version 0.1.0 of this kit.
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 practice 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 Clearday helpers are required for connected record creation, edits, the recorded desk windows and resource setup. They preserve native account permissions, unrelated custom fields and row history, run the clinical guard before anything is written, and check revisions before saving. Deploy them from your authoritative backend source. Pipelines and workflow drafts are optional. Upgrading from version 0.1.0 keeps every identifier you already have installed: the installer restores the earlier release and writes this one in a single step, and a 0.1.0 patient record is read and shown with the new defaults while every field it already held is preserved untouched and named on the record rather than displayed.
Clearday is a front-desk and treatment-coordinator workspace. It is not a dental record, an EHR or a practice management system, and it makes no HIPAA claim. It never stores procedure names or codes, tooth numbers or surfaces, diagnoses, clinical findings, images, medications, medical or dental history, insurance member or policy numbers, remaining benefits, government identifiers or dates of birth; an age band label is the most it records about age. The shared model refuses text that looks like any of those in every field and in the plan label, on the server as well as in the browser, and names the rule it matched; the plan labels, amounts, dates, scheduling notes and phone extensions a front desk really types are accepted. Treat that as help against accidental entry, not a guarantee. A plan amount is a reference number your office typed: nothing is quoted, billed, financed or collected, and a total is a sum of those numbers rather than revenue or a forecast. Recording a recall or a booking does not contact anyone, reserve a chair, hold a time or create a calendar event. The follow-up and reactivation windows are office preferences the practice records for itself, not clinical intervals.
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
No, and it does not claim to be. It is not a HIPAA compliance product, an EHR or a practice management system, and installing it does not make a practice compliant. It is a front-desk and relationship workspace for recalls, reminders, follow-up and intake progress. Keep clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information in your clinical system. The kit runs on your own Seedly CRM; DevLaunch does not host, receive or process your patient data, and your practice remains responsible for its own privacy, security and regulatory obligations.
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.
Clearday keeps its pine masthead and front desk tabs across the seven kit 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.
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.