Your support workspace,
inside Seedly.

1. Get the source

After verified payment, sign in with your checkout email and open Support Desk in Downloads. Active All Access members use the same library. Download the source archive and integrity manifest, compare the SHA-256 and extract the archive.

Read README.md, QUICKSTART.md and docs/AGENT_INSTALL.md. The bundle includes the original module source, installer, tests, recovery tools and setup documentation.

2. Install in your host

Back up your Seedly checkout. From the extracted module directory, preview the installer and then apply it to your designated test host:

node bin/install.mjs --seedly /absolute/path/to/seedly
node bin/install.mjs --seedly /absolute/path/to/seedly --apply
node bin/doctor.mjs --seedly /absolute/path/to/seedly

Generate the complete installed Convex API. Follow QUICKSTART.md to run the supplied host tests, backend/web type checks, native extension guards and production build. Deploy through your own host’s release process, backend before web.

3. Set ownership and access

Give staff the appropriate account-wide Support Desk actions and Contacts read access, and include Support Desk in restricted plans that should use it. Settings changes require native account-wide Settings update permission.

Open Support Desk Settings to choose elapsed response targets, an eligible default owner and owner alerts. Native notification preferences remain in control of the configured channels.

4. Connect a Seedly form

1. Create or edit a native form with a required email field mapped to the contact email, a required subject text field, and a separate required request text/textarea field.
2. Open Support Desk → Forms. Choose the form, map the subject and request fields, choose priority and opt-in portal sharing.
3. Choose Connect form and enable workflow. The module creates and publishes a native form-specific workflow with re-entry for subsequent requests.
4. Publish the form separately in Seedly Forms, then use its normal URL or embed. Submit a test request and inspect the ticket and native workflow execution.

Connecting needs account-wide Forms read and Workflows read/create/update access, Support Desk create permission and the corresponding plan features. The active native location must match.

The action reads the original submission so long requests are preserved. Subject limit: 180 characters; request limit: 12,000, subject to stricter native form validation. The native form success response records submission acceptance; ticket creation then runs asynchronously through Workflows.

5. Enable portal conversations

Enable Support in Settings and explicitly share a ticket, or choose sharing when connecting a form. Clients use their existing native portal link to see shared tickets and reply. Private notes remain staff-only. Public form submissions do not mint or send portal links.

Client Portal is optional. For its combined policy/navigation connection, use Client Delivery 0.6.0-alpha.2 or later; existing owners can get the update in their download library.

Manage and customize

The Forms dialog links to the native workflow editor. Use it to pause/resume intake, change mapping or routing, and inspect execution results. Unchanged setup retries reuse the existing connection; they do not create another workflow.

Customer ticket messages use the portal. Email/SMS ticket intake and delivery, attachments and business-hours calendars are outside this version. Hosting, provider usage, installation services and contracted support are separate.

For source removal or interrupted installation, use the documented uninstall/recovery tools. Source removal does not delete stored tickets; retain or explicitly retire data before removing its schema.