KillerConversions – Contact Form Builder

Yes. Build and publish forms, save submissions in WordPress, export CSV and configure ordinary notifications without a KillerConversions account or licence. Optional website registration, marketing emails and third-party connections remain separate choices. Free has no trial expiry or artificial form/submission quota; hosting and documented safety limits apply.

Completed entries are stored in your WordPress database and appear in KillerConversions > Inbox. Search, filter, star, mark read/unread, assign and export them. A committed entry remains saved if email transport later fails. If the queue cannot be stored before commit, the submission is rejected so the visitor can retry. Entries are not encrypted at rest by the plugin; protect database access and backups.

Yes. Export filtered entries in wide or long CSV layouts for use in a spreadsheet. Entry-access permissions also apply to exports. Submitted-entry totals are counts, not conversion rates.

Yes. Show or hide follow-up fields based on previous answers, with server-side validation of relevant required questions. Nested conditions, step branching and advanced conditional actions require Pro. During a partial update from an older Pro, finish updating both editions before using condition-dependent forms.

Free collects quote enquiries, service requirements and project briefs. Pro calculates estimates from configured pricing and can produce a branded PDF. A quote request in Free does not calculate a price. Payments, signatures, AI form generation, A/B testing, multisite and a full CRM are outside scope.

Multi-step applications, supported private uploads and visitor save-and-resume require Pro. Visitors explicitly save an incomplete application and return through a private link with a 1-, 3- or 7-day expiry. Free includes administrator form-design drafts; these are separate from a visitor's incomplete answers.

Yes. Add the KillerConversions block in the WordPress block editor, or place [killerconversions id="123"] in a shortcode block using the published form's actual ID. The form picker requires administrator access; other post editors can use an ID supplied by a form administrator.

Free supports up to three repeated groups, ten rows per group and six text, email, number, date or select questions per row. Groups require JavaScript. Nested groups, uploads, consent, pricing and conditional dependencies inside groups are excluded.

The staff notification address starts empty. Entries still appear in Inbox. Open the form's Connect tab, enter a Staff notification email, then publish. Or leave it blank to use Inbox only. Visitor confirmations and Pro routing have separate settings. Check any paused-delivery notice, submit through the published page and review Delivery. Confirm receipt with the intended recipient: WordPress mail acceptance is not proof of inbox delivery. Configure SMTP or another mail transport separately if your host needs it.

Free includes a honeypot and submission rate limiting. Optional Cloudflare Turnstile adds a browser challenge and server verification. It starts off: open Settings > Spam protection, add your widget's site key and secret, acknowledge the external service, enable it and publish. Test the published form; the editor preview does not load Turnstile. Protected forms require JavaScript. See the external-service disclosure below.

Yes, after explicitly configuring the provider, list or group and a separate optional visitor marketing-consent question. The connection creates or updates the consenting subscriber; it does not send a newsletter campaign or perform double opt-in. Your provider's configured automations may run. An enquiry or staff notification is not newsletter consent. See the service disclosures below.

Free offers optional browser recovery, conflicting-save protection and a ten-design history. Credentials and operational settings stay outside that history. Import/export moves sanitised form configurations, not a full backup: entries, credentials, private destinations and live operational state are excluded by default. Review local destinations after import.

Install Free first and a compatible Pro add-on, then activate the licence for this website before using Pro editing tools. After successful activation, ordinary licence expiry or a licensing-service outage does not remove earned access. Plans differ by their allowance of 1, 3 or 10 websites; each distinct WordPress website needs a licence, with no additional staging allowance. Free does not download or install Pro.

Basic workflows continue with Free alone. Premium-dependent forms and jobs retain their data and pause with an explanation; they do not calculate a different price or silently choose a fallback recipient. Existing scoped staff restrictions remain enforced. Missing or incompatible Pro also preserves saved data and privacy operations. Finish both updates before editing during a mixed-version upgrade.

Yes. Hide or restore sidebar previews and contextual suggestions for your administrator account on this website. Explore Pro stays available. Editor preview links open separately to preserve unsaved work. The pricing example uses fixed sample rates and does not enable Pro calculations. Local preview preferences remain until the documented explicit full uninstall.

Published forms have a standard server submission fallback and relevant server validation still applies. Enhanced multi-step navigation, repeatable groups, visitor save/resume, live estimates and the visual editor require JavaScript. Without it, ordinary fields remain readable together. Turnstile-protected forms require JavaScript.

Visit the documentation, WordPress.org support forum or support page. Public support has no guaranteed response time. No subscription or sister-plugin installation is required for local features.

Keep a pre-upgrade database/files backup and test restoration on a separate copy. Reinstalling an old ZIP does not reverse migrations. Do not overwrite newer submissions with an old database. Follow the matched update and recovery guidance.