Skip to content
View packages

GoSeedly Counseling Practice Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

02

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

03

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. The included original backend helpers are required for connected record creation, edits, the workspace store and resource setup. They preserve native account permissions, unrelated custom fields and row history, run the boundary guard on the server, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers Client relationships, Enquiry responses, Recurring openings, Referral sources. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

Explore 61 fictional records: 4 enquiries of which 2 are past the recorded response days, 11 people on the waitlist with the longest at 14 weeks, 2 with an opening offered, 41 active clients, 2 paused and 1 closed. Five fictional clinicians, two of them over their own recorded weekly target and one with no recurring opening recorded, six recurring openings of which four fit at least one waiting person, five quiet clients and six referral sources. Sample edits stay in memory and reset on navigation or reload. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

MORE OF THE WORKING DAY

From the first inquiry
to the final handoff.

Editable native forms and document templates give your team a practical starting point.

01 / INTAKE & FOLLOW-UP

Three ready-to-edit forms.

  • Counseling enquiry: name, email, phone, then the kind of appointment, the days, the time windows, a preferred clinician, the best way to reach you and whether a voicemail may be left, all as fixed choices
  • Availability update: name, email or phone, the days and time windows that now work, and whether to pause a place on the waitlist
  • Practice feedback: two star ratings and five single-choice questions about scheduling and communication, with no comment box

Choose forms individually in Setup & resources, then customize and publish them in the native form builder.

02 / WORKING DOCUMENTS

Three reusable templates.

  • Waitlist call sheet
  • Opening offer letter
  • Administrative check-in call sheet

Open each template in Documents and complete it for the actual job or visit.

03 / THE NEXT STEP

Checklists alongside the work.

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

A front-desk workspace, not a medical record.

  • This kit is not a HIPAA compliance product and does not make a practice HIPAA compliant. It is not an EHR, EMR or practice management system.
  • It is built for relationship work: recalls, reminders due, follow-up, intake progress and front-desk tasks. Clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information belong in your clinical system, not here.
  • You install the kit on your own Seedly CRM. DevLaunch does not host, receive or process your patient data. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations, including any agreements with its hosting and software providers.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-counseling-practice/config.ts to set practice name, descriptor and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

What the workspace records

One contact-linked opportunity is one client or enquirer relationship. It holds the client label of a first name and last initial, the age band label, the service line as the practice’s own label, the stage with the date it was reached, the date the enquiry arrived and the date it was first answered, the contact attempts and last contact, the preferred and assigned clinician, the recurring slot day and time, the cadence label, the session length in minutes, whether a next appointment is recorded and its date, the referral source label, a fee arrangement label with no amount required, availability rows of a day and a time window, and an editable checklist. The clinicians with their own recorded weekly targets, their recurring openings, the referral sources, the recorded response days and the recorded quiet days live in one account store behind a single revision guard.

Weekly client hours are the sum of recorded session lengths over a clinician’s active clients, counted once a week for a weekly client, as one half for a fortnightly client and as one quarter for a monthly client, held in quarter-minutes so the three cadences total exactly. An opening’s fits are a plain availability comparison: the waitlist stage, the same day and the same time window, sorted oldest wait first and capped at three. Nothing is weighted, scored or decided for you, there is no clinical or suitability judgement, and offering an opening is still a conversation somebody has. This is the most careful kit in the collection and it records less than any other: no presenting concern, reason for seeking counseling, symptom, diagnosis, risk or safety information, session note, treatment goal, progress, medication, substance use, relationship or family detail, trauma history, school or employer detail beyond a referral source’s name, insurance or authorization number, government identifier or date of birth, and it holds no monetary field at all. A server-enforced guard refuses free text that looks like any of those in every field and every non-name label, which is help against accidental entry rather than a guarantee. There is no scheduling engine or calendar sync, no insurance, superbills or billing, no automated reminder or message of any kind, no client portal, no payments, no telehealth, and no crisis or emergency service: the enquiry form says so and carries a crisis line. None of the three public forms has a message box. A submission lands as a native Seedly form record, so it never passes through the kit’s guard, and an open box on a counseling form would be the one place a reason for seeking support could be typed and stored: every question other than a name, an email address and a phone number is a choice from a fixed list or a star rating, no form has a textarea and no form has a file field, and each form says “This form has no message box on purpose.” The kit gives no clinical or mental health advice.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.