Features for
forms your team
can operate.
WandForm is built around the full FormOps loop: draft, review, publish, accept submissions, deliver follow-up, recover failures, and audit what happened.
Draft forms with operating context
Create team-owned drafts, start from intake playbooks, and keep mutable setup work separate from the live public route.
- Team-owned draft forms with editable fields and settings
- Core field support for text, email, number, textarea, checkbox, select, and date
- Playbook-backed draft creation for lead, demo, quote, client service, application, registration, and event intake
- Validation profile recommendations from draft shape and playbook fit
- Expected-revision updates that protect editors from overwriting newer draft work
- Public reference repair for forms that need stable organization/form slugs
Publish like a controlled release
Snapshot immutable versions, preview risky changes, and activate routes through publishing paths that keep the team aware of what changed.
- Immutable version creation from the current draft
- Active public route pointer tied to the published revision
- Migration previews against the currently published version
- Redacted submission simulation before risky schema changes
- Approved migration runbooks required before force-publishing breaking changes
- Governed release requests with approval, scheduling, notifications, and telemetry
Accept submissions against the right revision
Public forms resolve through stable organization and form slugs, then store submission evidence against the active published revision.
- Anonymous published-form lookup through organization slug and form public slug
- Submission acceptance without exposing internal team, form, or route identifiers
- Revision-pinned submission records for later review and audit
- Required, type, email, numeric, string, date, option, and pattern validation
- Structured validation error summaries for client and operator surfaces
- Source, tenant, route pointer, and submitted-field context captured in metadata
See and recover failed follow-up
WandForm treats post-submit delivery as product state: operators can inspect confirmation health, retry failures, acknowledge debt, and review retry runs.
- Confirmation-email delivery state stored with submissions
- Per-form confirmation telemetry for requested, sent, failed, skipped, retrying, and unknown states
- Manual retry for failed confirmation delivery after configuration or address fixes
- Bulk retry for currently failed confirmations on a form
- Due retry workflows and scheduled background sweeps for retryable failures
- Durable retry-run history with processed, sent, failed, and skipped counts
Audit the workflow instead of guessing
Teams can inspect audit timelines, policy changes, release notifications, rollout playbooks, and operational insights without reconstructing what happened from logs.
- Audit event timelines for form and workflow activity
- Governance insights for publish, rollback, submission, risk, and SLO trends
- Team and workspace policy workflows with approval, scheduling, rollback, and notification paths
- Release notification dispatch and telemetry for configured email and webhook targets, with Slack limited to supported runtime paths
Keep ownership and limits explicit
Tenant-authenticated surfaces derive access from Better Auth team context, while plan entitlements come from the shared WandForm pricing catalog.
- Better Auth organization and team context for tenant-scoped app access
- Team access checks for authenticated form, submission, publishing, and settings surfaces
- Shared plan catalog for free, plus, pro, and enterprise entitlements
- Submission allowance, seat limit, webhook automation, branding, support, and guarded API/enterprise identity flags
- Plan usage telemetry for billing-window submissions and seat pressure
- Organization and team release-notification defaults for governed workflows
Start with the fields
production intake needs
WandForm keeps the public claim surface precise: current field support covers the core inputs that can be validated and stored against published revisions.
Clear about what is not claimed yet
WandForm should earn trust by separating shipped operating capability from future expansion.
Ready to operate forms with more control?
Build production forms with a clearer publishing path, cleaner submissions, delivery recovery, and audit evidence your team can inspect.