Consultation Request for WordPress
Discovery-call request with service, budget, and timeline qualification. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why WordPress developers choose splitforms for consultation request
WordPress contact form plugins (Contact Form 7, WPForms, Fluent Forms) work but add database bloat, update fatigue, and a monthly subscription for features like webhook delivery or advanced spam controls. The consultation request on this page drops into a Custom HTML block — no PHP, no plugin activation, no settings page to configure. Every field POSTs to splitforms as standard form data, so your WordPress admin stays clean. You keep using WordPress for content management and page building while splitforms handles the form pipeline.
Yes — this is the shortest safe path for WordPress.
Use the PHP snippet on this page, keep the consultation request fields visible in your WordPress UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.
Paste the PHP version, then replace YOUR_ACCESS_KEY.
The posted payload contains full name, email, phone, topic, what do you need help with?. Required fields are full name, email, phone, topic and what do you need help with?.
WordPress core has no contact-form feature — every contact form on a WP site is either a plugin (Contact Form 7, WPForms, Gravity Forms, Forminator, Fluent Forms, Ninja Forms) or a custom theme template.
Discovery-call request with service, budget, and timeline qualification.
Built for WordPress developers who hate operating a backend.
Splitforms is the form backend for WordPress sites. One POST endpoint, no SDK, no plugin — drop the consultation request into a page and ship.
Splitforms is the form backend for WordPress sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.
- ✓500 form submissions per month
- ✓2 forms on Free; unlimited forms on Pro
- ✓Spam protection (honeypot + classifier)
- ✓Webhooks: Slack, Discord, WhatsApp, custom
- ✓CSV export of all submissions
- ✓Email notifications (CC and BCC on Pro)
Drop into any WordPress project.
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a WordPress page, and ship. No build-time integration required.
Generate, embed, receive.
Three actions stand between you and your first consultation request submission. None of them require a backend, a database, or a CAPTCHA library.
Generate a free splitforms key
Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.
Paste the consultation request into your WordPress project
Drop the form snippet into a WordPress page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.
Receive submissions
Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
What changes when this consultation request lives in WordPress.
These notes come from the WordPress platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.
WordPress core has no contact-form feature — every contact form on a WP site is either a plugin (Contact Form 7, WPForms, Gravity Forms, Forminator, Fluent Forms, Ninja Forms) or a custom theme template. Plugins add 3-7 database tables, increase TTFB by 50-300ms, and most require a paid SMTP plugin (WP Mail SMTP) on top because shared-host PHP mail() lands in spam. CF7 alone is 1.2MB of JS/CSS loaded on every page. Anti-spam is a separate Akismet subscription ($10/mo for commercial use) or a paid CAPTCHA plugin. Splitforms replaces the plugin: a <form> tag in a Custom HTML block, pointing at our endpoint, with a hidden access_key field. No plugin, no extra DB tables, no SMTP gymnastics.
WordPress runs on shared hosts (Bluehost, Hostinger), managed WP hosts (Kinsta, WP Engine, Pressable), or self-hosted Apache/nginx. The form's POST is cross-origin to splitforms.com, so the host doesn't matter for delivery. Caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache) cache the page that hosts the form — that's fine, the form action URL is static. Don't proxy through WP's admin-ajax.php or wp_remote_post — adds latency and re-introduces the SMTP problem. For Multisite, use one access key per site or a shared key with form-name to disambiguate. Headless WP (Next.js/Astro front) doesn't involve PHP at all — use the matching framework's snippet.
WordPress wpautop() mangles your form HTML in posts
If you paste a <form> directly into a Classic Editor post, WordPress's wpautop filter wraps random <p> tags around your inputs and breaks the markup. Use a Custom HTML block (block editor) or a theme template file instead — wpautop doesn't touch those.
Caching plugins (WP Rocket, W3 Total Cache) cache the form page itself
Page caching is fine — your form posts to splitforms.com directly, not a WordPress endpoint, so the cached HTML still works. But if you ever switch to a WP-side handler (e.g. wp_ajax), exclude /contact/ from the page cache or submissions will hit a stale page.
Theme-injected JavaScript can hijack form submission
Some themes (Astra, OceanWP, GeneratePress 'Premium') auto-attach AJAX handlers to every form on the page. Add data-no-ajax="true" or a custom class your theme excludes — or use a Custom HTML block which most themes leave alone.
Cloudflare Bot Fight Mode blocks splitforms responses
If you proxy your WP site through Cloudflare with Bot Fight Mode on, the redirect from splitforms.com → /thanks may be flagged. Whitelist your domain in splitforms's allowed-domains list AND ensure /thanks is reachable without a Cloudflare challenge.
Pattern A — Custom HTML block (Block Editor / Gutenberg)
Drop a Custom HTML block on any page or post. Survives theme switches and plugin updates. No PHP required, no theme file editing. Reusable Patterns let you save the form once and drop it on every page. Use the same wiring for the consultation request fields on this page.
Pattern B — theme template with key from wp-config constant
For developer-managed themes (Bedrock/Sage/classic), define SPLITFORMS_KEY as a constant in wp-config.php and echo it via esc_attr(). Keeps the key out of the theme repo, lets staging and production read different keys via environment. Use the same wiring for the consultation request fields on this page.
What every field actually does.
Each field below ships in the consultation request template — rename, remove, or add your own. Splitforms accepts any name you POST.
Full name
Greeting + dashboard label so submissions don't all read 'anonymous'.
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
Phone
Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.
Topic
Dropdown — keeps responses normalised so you can filter the dashboard.
What do you need help with?
Free-text context — what the visitor actually wants you to know.
One backend. Every framework.
The same consultation request template works on every framework splitforms supports. Pick yours.
Consultation Request on WordPress — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.
Other ready-to-ship WordPress forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a consultation request on WordPress in 60 seconds.
500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your WordPress project.