AI Conversion

Turns visitors and AI agents into leads: forms an agent can fill through WebMCP, submissions that are never dropped, and AI-drafted follow-up for a person to approve.

Part of
An open framework for AI on WordPress
Status
A written design on open standards. Not for sale or download.
Works with
WordPress, WebMCP, CRM APIs, WP REST API, Action Scheduler, OpenAI, Anthropic and Gemini APIs
AI Conversion · how it works
  1. 01FormIn the site's design
  2. 02MCPAgentThrough WebMCP
  3. 03CheckSpam and abuse
  4. 04DeliverUntil the CRM confirms
  5. 05AIFollow upEmail drafted
  6. 06ApproveA person sends

How a form submission becomes a lead and a follow-up. A diagram of the design, not a screenshot.

The short version

  1. No dropped leads

    Every submission waits in a queue until the CRM confirms it.

  2. Forms agents can fill

    Every form is offered through WebMCP, so AI agents fill it in properly.

  3. Follow-up, drafted

    The hub drafts the follow-up email from the site's own content, for a person to approve.

  • WebMCP
  • Confirmed by the CRM
  • A person presses Send

The problem

Forms are where a website earns its keep, and where it leaks. A hand-off to the CRM can fail without anyone noticing, AI agents now arrive on behalf of buyers with no structured way to fill anything in, and the follow-up email is written from scratch, if it is written at all.

The pattern

AI Conversion renders the CRM's forms in the site's own design, checks every submission for spam and abuse, and holds each one in a queue until the CRM confirms it, retrying if it has to. A failed hand-off becomes an alert, not a lost lead.

Every form is also offered to AI agents through WebMCP, so an agent acting for a visitor can find it and fill it in properly instead of guessing at the page. The person still reviews it and presses Send.

After a submission, the hub drafts a follow-up email from the site's own content, matched to what the visitor asked for. A person approves it before anything is sent.

What it replaces

Before

Forms that ignore the design, hand-offs that fail without anyone noticing, no way in for agents, and follow-up written from scratch.

After

Native forms, a delivery queue with alerts, WebMCP for agents, and follow-up drafted for a person to approve.

Under the hood

  1. Form. The CRM's form renders natively, in the site's own design.
  2. Agent.MCP An AI agent acting for a visitor finds the form and fills it in through WebMCP.
  3. Check. Every submission is sanitised, spam-checked and rate-limited, whoever filled it in.
  4. Deliver. Each submission waits in a queue until the CRM confirms it, with retries and an alert if it keeps failing.
  5. Follow up.AI The hub drafts a follow-up email from the site's own content.
  6. Approve. A person approves the email before anything is sent.

Guardrails

  • No submission is dropped: each one waits until the CRM confirms it.
  • Personal data is kept only as long as delivery needs it.
  • Agents go through the same checks as people, and a person presses Send.
  • Emails are drafts until a person approves them.

Works with

  • WordPress
  • WebMCP
  • CRM APIs
  • WP REST API
  • Action Scheduler
  • OpenAI
  • Anthropic and Gemini APIs

What it does

  • Native forms

    The CRM's forms rendered in the site's own design.

  • Delivery queue

    Submissions held and retried until the CRM confirms them.

  • WebMCP

    Every form offered as a tool AI agents can use.

  • AI email follow-up

    Follow-up emails drafted from the site's content, approved by a person.

  • Privacy by design

    Form data kept only for delivery; analytics without personal data.

Why it matters

More of the people and agents who reach a form become leads, and every lead gets a timely follow-up.

What it changes

  1. A failed hand-off becomes an alert instead of a lost lead.

  2. AI agents can fill the forms properly, instead of guessing.

  3. Follow-up starts the same day, in the site's own words.

4 questions about AI Conversion, answered

What is AI Conversion?

The conversion part of my open framework for AI on WordPress: forms that people and AI agents can fill, submissions that are never dropped, and follow-up emails drafted by AI for a person to approve.

How do AI agents fill the forms?

Through WebMCP. Each form is offered to the browser as a tool with clear fields, so an agent acting for a visitor completes it properly instead of guessing at the page.

What happens if the CRM is down?

The submission waits in a queue and is retried until the CRM confirms it, and the team gets an alert if it keeps failing. Nothing is dropped.

Does AI send emails on its own?

No. The hub drafts follow-up emails from the site's own content, and a person approves them before anything is sent.