---
title: LolaCore for Forms
canonical_url: https://lolacore.com/lolacore-for-forms/
last_updated: 2026-06-27T22:15:03+00:00
plugin_version: 1.2.2
---

# LolaCore for Forms · Free Add-on · Requires LolaCore

## Build forms by conversation.

Describe the form you need and Lola builds it field by field in chat: a workshop registration with track selection and seat counts, a project intake with budget ranges and timelines, a vendor application with the consent checkbox already required. She also learns what normal looks like for each form, so when signups drop she tells you whether the form broke or the traffic did. No drag-and-drop builder required.

[Get it free →](https://lolacore.com/install-lolacore-for-forms)

[See what Lola can do →](#forms-demo)

· 24 capabilities (15 with WPForms Lite) · Works with WPForms Lite & Pro · Built on the public WPForms PHP API

## The Problem

### You think in whole sentences. Building the form means clicking them out one field at a time.

When you need a form, the sentence is already in your head: "workshop signup with track selection and how many seats," "project intake with budget range and timeline," "why did registrations die after we moved the events page." WPForms can do all of that. What building it asks of you first is the visual builder: drag fields, set dropdown choices one option at a time, open notification tabs, hunt for embed settings, save, copy a shortcode, paste it on the right page and hope you remembered which one.

One real intake form is twenty minutes of clicking. Three forms for a launch is most of a day. And when submissions stall, you are back in All Forms, then Entries, then filters, reconstructing by hand whether it was traffic, a broken embed, or a notification that never fired.

LolaCore for Forms removes that translation step. Same forms, same data. You stopped clicking and started talking. You say the sentence to Lola, she builds the form in chat, checks placement and notifications, reads submission trends against what she remembers as normal, and on WPForms Pro she triages the inbox without you opening five admin screens.

## Demo

### What changes when Lola handles your forms

**Building a real intake form, not a three-field contact box**

**User:** We're opening registration for our spring workshops. I need a signup form: name, email, dropdown for track (Intro, Advanced, Kids lab), number field for how many seats they're booking, radio for experience level (first-timer or returning), a paragraph for dietary or access needs, and a required photo consent checkbox. Send confirmations to the registrant. Notify events@ourstudio.com with subject 'New workshop signup.' Confirmation message: 'You're registered. We'll email details 48 hours before your session.'

**Lola:** Got it. I'll create 'Spring workshop registration' with seven fields: Name, Email, Track (Intro / Advanced / Kids lab), Number of seats, Experience level (first-timer / returning), Dietary or access needs (optional paragraph), and Photo consent (required checkbox). Notifications to events@ourstudio.com, subject 'New workshop signup.' Confirmation goes to the submitter with your 48-hour message. One thing before I save: should Number of seats show a hint that you cap bookings at 5 per submission?

**User:** Yes, add that hint.

**Lola:** Updated. Placeholder on Number of seats: 'Max 5 per booking.' Confirmation message now carries that line too. Preview ready. Save?

**User:** Save it.

**Lola:** Done. Form ID 42 is live. Embed with `[wpforms id="42"]` or the WPForms block. I'll remember this form as your workshop registration pipeline. /events/spring-workshops/ doesn't have a form yet. Want the embed pasted there next?

✓ 7 fields · dropdown + number + radio + settings · purpose stored in memory

You described an operational form in one breath. Lola mapped it to the right field types, refined a detail through placeholder and confirmation copy, set routing in the same pass, and saved without you opening the builder once.

**Catching a signup collapse before the event sells out**

**User:** Workshop registration usually has 30 to 40 signups by Thursday. We're at 6. Something's wrong.

**Lola:** Checking form 42 'Spring workshop registration.' This week: 6 submissions, down 84% from your baseline of 38. I ran an anomaly scan and found three things. The form is still embedded on /events/spring-2025/, which you unpublished after the rebrand. The live page /events/spring-workshops/ has no form on it. The notification email is still events@oldstudio.com. I also cross-checked Statistics: /events/spring-workshops/ pulled 520 views this week, so the traffic is there and the form isn't. Want me to update the notification address and tell you exactly where to re-embed on the live page?

✓ Baseline compared · placement break found · traffic cross-check

You gave a business deadline, not a technical ticket. Lola compared against what she remembers as normal for this form, traced placement and notifications, and pulled page views from Statistics in one answer.

**Triage without the inbox maze (WPForms Pro)**

**User:** Anything in workshop registration I need to act on before Friday?

**Lola:** Form 42 has 23 unread entries since Monday. Breakdown: 14 Intro, 7 Advanced, 2 Kids lab. Five mention dietary needs in the access field (two gluten-free, one wheelchair seating). Three Advanced bookings request 4 or 5 seats each, worth a manual capacity check. One entry landed in spam with a valid-looking email and complete track selection, probably a false positive. I masked emails in this summary. Want the full detail on the large Advanced bookings, or should I mark the obvious spam false positive for review?

✓ 23 unread triaged by track · PII masked by default

You didn't open All Forms, pick the form, switch to Entries, then build filters. Lola read the inbox the way an events coordinator would: who's coming, what needs logistics, what looks off.

## Cross-domain

### A quiet form is rarely just a form problem.

When submissions drop or spike, the cause often lives somewhere else. The page lost traffic. The embed moved during a redesign. A search change sent visitors to a different URL. Lola has affinity declared with Statistics, content, and SEO, so when a form finding overlaps another domain she follows it across.

**User:** Workshop registration is flat, but the events landing page looks busy. Are people bouncing before they sign up?

**Lola:** Form 42 on /events/spring-workshops/ has 6 submissions this week. The page had 520 views, so rough conversion is about 1.2%, down from your usual 7 to 9% for this form. Placement is correct now. Notification routing is fine. I compared with Statistics: bounce rate on that page jumped from 38% to 71% after you replaced the hero last Tuesday. Organic traffic to the same URL is steady. The drop lines up with the hero change, not search visibility. The form works. People are leaving the page before they submit. Want me to confirm which page holds the embed so you can move the form block higher on that template?

✓ Conversion proxy · timeline correlated · form ruled out

The signup count was the alarm. The real finding was page behavior above the form. Lola connected form performance, traffic, and timing because she reads both sides in one conversation.

## Companion, not a replacement

### Lola works inside WPForms. She doesn't replace it.

WPForms still stores entries, runs anti-spam, processes payments, and sends emails. Lola reads and writes through the same API, so a form she builds is identical to one built in the visual panel. She is not a second form plugin and she is not an SMTP fix. When delivery or checkout breaks, she surfaces it and points you to the right layer.

A few things still start in the WPForms builder for now, conditional logic being the one most people ask about. Lola is upfront at each handoff: what she did in chat, what WPForms still owns, and the shortest route between them. The full picture is in the FAQ and the roadmap below.

## Capabilities

### 24 capabilities across 6 areas. 15 with WPForms Lite.

The nine entry and payment capabilities need WPForms Pro with entry storage and/or payments active. They register automatically when Lola detects them. Everything else works on WPForms Lite.

**Overview**
Forms dashboard with field counts and submission totals. Plugin status: Lite or Pro, LiteConnect, entry storage, payments, and the field types available to you.

**Conversational form builder**
Create a form shell with optional initial fields. Add, update, or remove allowlisted fields without the visual builder. Update notification, confirmation, and anti-spam settings with a dry-run preview. Get embed details: shortcode, block name, and edit URL.

**Form health and placement**
Human-readable form summary. Health audit covering notifications, confirmation, anti-spam, and placement. Notification routing: who receives each rule. Form placement: where a form is embedded across the site.

**Submission trends**
Week-over-week submission trends per form. Anomaly detection for drops, spikes, spam surges, traffic without submissions, and dominant forms. Form-to-form comparison with optional conversion proxy when LolaCore for Statistics is active.

**Entry inbox (WPForms Pro)**
Inbox summary with unread, starred, spam, and trash counts. Recent entries with field labels and PII masked by default. Entry detail, unread triage, spam breakdown. Mark read and delete with dry-run preview.

**Payments (Pro, when active)**
Payment summary by form and date range. Failed and pending payment rows pulled out for review.

## Free vs Pro

### What you need on the WPForms side

| WPForms Lite | WPForms Pro |
| --- | --- |
| Conversational form builder | Yes | Yes |
| Form health, placement, and notification routing | Yes | Yes |
| Submission trends and anomaly detection | Yes | Yes |
| Row-level entry inbox reads | No | Yes |
| Mark read and delete entries | No | Yes |
| Payment summaries | No | Yes (when payments active) |
| LolaCore for Forms add-on | Free | Free |

The add-on itself is always free. What changes is the edition of WPForms you already run and whether entry storage and payments are active on your site. The nine gated capabilities appear automatically when Lola detects them. Everything else behaves the same on Lite.

On Lite, submission counts come from form meta and weekly trends. Lola reports those honestly. She does not invent row-level inbox data that WPForms Lite does not store locally.

## Memory

### Lola remembers what each form is for

Every form you build with Lola leaves a trace. Not the raw entries, the purpose: "workshop registration pipeline," "project intake," "vendor application." Submission baselines too, so what counts as normal for each form is recorded, and a drop or spike means something instead of being a bare number.

That baseline is what turns "registration is usually at 40 by Thursday, we're at 6" into a useful question. Without it, 6 submissions is just 6. With it, that's 84% below your usual for this form, and the event is in ten days.

The memory lives inside your WordPress install. It decays over time so old context fades, and it updates as you keep working. The longer the add-on stays active, the sharper her sense of each form becomes.

## Safety

### No write happens without your approval

Creating a form, adding a field, updating a notification recipient, deleting an entry: every write action passes through a confirmation step. Lola shows you exactly what will change before it changes, including dry-run previews for settings updates.

Read actions, including inbox summaries and health audits, run directly. Entry reads mask email, phone, and IP by default. You get the unmasked values only when you explicitly request them.

Deleting an entry removes it for good, so Lola names the exact entry and waits for your go-ahead on each one before anything is removed.

## What we're building next

### Conditional logic from chat comes first.

Everything below is planned work on the conversational builder, in priority order. No fixed dates. Items ship when they're ready and land in the add-on changelog.

**1. Conversational conditional logic (next)**
Describe show/hide rules in plain language. Example: *If Service is Consultation, show Preferred date; if Emergency, show On-call phone.* Preview the rule, confirm, saved, in the same flow you already use to create fields. This is first because it's the screen WPForms users reach right after basic field setup.

**2. Richer builder coverage**
- Multi-page forms and page-break flow from chat.
- Layout and repeater fields without opening the drag-and-drop panel.
- Payment field setup from chat when gateways are already connected in WPForms.

**3. Explored for later**
- Deeper bridges for WPForms add-ons (Surveys, Webhooks, User Registration).
- LiteConnect entry reads, if a stable public API becomes available.
- Multisite support.

When you ask for something on this list before it ships, Lola names it as planned work and gives you the fastest workaround today, rather than "I can't do that" with no path forward.

## Requirements

### What you need

| | |
| --- | ---