AI features & integrations

Wedding Computer includes AI features designed to cut down on admin time. All of them are opt-in, and none act without your involvement unless you’ve explicitly configured them to do so.

AI email drafting

On any contact or email thread, click Draft reply to have the AI write a suggested response. The draft is informed by the couple’s details, their wedding date and location, your notes on this contact, their pipeline stage, and recent email history.

You see the draft before anything is sent. Edit it, discard it, or send it as-is — it never sends automatically unless you’ve also enabled auto-reply (below).

AI enquiry auto-reply (Pro)

When you set availability sharing to AI auto-reply under Settings → Availability, incoming enquiries receive an automatic reply. The AI checks your availability for the requested date and follows any custom instructions you’ve written.

To write your AI instructions: Settings → Enquiry form → AI instructions. Use this to set your tone, provide context about your packages, specify what to say (or not say) about pricing, or give any other guidance. The AI follows these instructions for every auto-reply it sends.

You can test the output before enabling it by clicking Draft reply on an existing enquiry — this shows what the AI would have sent, without triggering the auto-send.

AI run sheet generator

From a wedding workspace, use AI → Generate run sheet to have the AI draft a day-of timeline based on the wedding’s details: date, ceremony type, getting-ready times, ceremony start, portrait timing, and reception start. The result is a starting point — edit and add to it like any other run sheet.

AI import extraction

When importing contacts via Settings → Import, you can paste raw text (an email, a screenshot description, a note) or a URL and the AI will extract contact details from it. Review the extracted fields before the contact is created.

The MCP server — connect AI assistants (Pro)

The MCP server at POST /mcp exposes 25 tools that let MCP-compatible AI clients read and write your Wedding Computer data. Supported clients include Claude Desktop, Cursor, Sourcegraph Cody, and any other tool that implements the Model Context Protocol.

Setting up the MCP connection

Go to Settings → Device sync and copy your sync token
Add a new MCP server in your AI client’s settings:
- URL: https://wedding.computer/mcp
- Authentication: Bearer your-sync-token

Claude Desktop (~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "wedding-computer": {
      "url": "https://wedding.computer/mcp",
      "headers": {
        "Authorization": "Bearer your-sync-token-here"
      }
    }
  }
}

What the AI can do via MCP

With the connection active, you can ask an AI assistant things like:

“What weddings do I have coming up in November?”
“Show me the run sheet for Sarah and James’s wedding”
“Add a timeline item: portraits at 4pm at the rose garden”
“What’s the weather forecast for the Parker wedding?”
“Check my private notes for the Chen wedding”
“What vendors are on the Martinez wedding?”
“Generate a run sheet for the Williams wedding”
“Draft a reply to my latest enquiry from Emma”
“Add sunrise and sunset markers to the Thompson wedding timeline”

The MCP server enforces the same permission model as the web app. The AI can only access data within your account, and only for weddings where you’re a member. If a wedding has a managing vendor, timeline change requests from the AI go through the same approval flow as changes made in the app — they don’t bypass it.

The lead intake API & Zapier (Pro)

The lead intake API lets external services push leads directly into your CRM. Common uses:

Zapier: Facebook Lead Ads → Wedding Computer, or any form tool → Wedding Computer
Custom webhook: your website’s native form → Wedding Computer
Booking platform: any external system that supports outbound webhooks

Get your enquiry intake key from Settings → Enquiry form → API & webhooks, then use it as a Bearer token:

POST https://wedding.computer/api/v1/enquiries
Authorization: Bearer your-enquiry-intake-key
Content-Type: application/json

{
  "first_name": "Emma",
  "last_name": "Wilson",
  "email": "emma@example.com",
  "partner_first_name": "Liam",
  "wedding_date": "2026-04-12",
  "source": "facebook_lead_ads"
}

GET /api/v1/form returns your current enquiry form schema, which Zapier or an AI agent can use to discover the correct field names automatically. Rate limits are 120 requests per minute and 2,000 per day.

Privacy & data handling

What data AI can access

AI features only have access to data relevant to the specific task being performed. The email drafter sees the contact record and recent thread. The run sheet generator sees the wedding’s timing details. An MCP tool call returns exactly what you requested (e.g. a specific wedding’s run sheet, or a contact record) — not a dump of your entire account.

There is no background processing where AI reads your data without you initiating a specific action.

Training

Wedding Computer does not use your data to train its own AI models. Your data is used only to generate a response to your specific request and is not retained by the AI provider for training purposes. The AI providers used — Anthropic (Claude) and Cloudflare Workers AI — have data processing terms that prohibit using API request data for model training by default.

Opting out

Every AI feature requires a deliberate action on your part to activate:

Email drafting: you click “Draft reply” each time
Auto-reply: you explicitly enable it in Settings
Run sheet generator: you click “Generate run sheet”
MCP server: you configure it in your AI client’s settings

If you don’t set any of these up, no AI processing happens on your account.

Where your data is stored and processed

All your data lives on Cloudflare’s infrastructure:

Database: Cloudflare D1 (globally distributed SQLite)
Files: Cloudflare R2 (object storage)
Sessions and cache: Cloudflare KV
Application layer: Cloudflare Workers (runs at the edge, close to you geographically)

Transactional emails are sent via Resend (US-based). Card payments are processed by Stripe (US-based). AI inference uses Anthropic’s API or Cloudflare Workers AI, both US-based with global edge presence.

Privacy tracking

Wedding Computer does not use Google Analytics, Meta Pixel, advertising trackers, or any cross-site behavioural tracking. There are no third-party analytics scripts loaded on any page. Usage analytics that do exist (enquiry counts, conversion rates, etc.) are computed from Wedding Computer’s own data and are not shared with advertising networks.

Legal responsibility

AI features are drafting tools. AI-generated emails, run sheets, and replies are suggestions for you to review and take responsibility for before sending or relying on them. Wedding Computer does not provide legal, financial, or professional advice, and AI-generated content should be reviewed by the relevant professional before use.

For contracts: Wedding Computer stores and delivers whatever wording you provide. The wording is yours — Wedding Computer provides no templates and no legal review. Have any contract reviewed by a lawyer in your jurisdiction.

For celebrant documents (NOIMs and related paperwork): Wedding Computer’s NOIM generator populates fields from the couple details you’ve entered. You must verify all details are correct before a document is signed or lodged. Wedding Computer is a software tool, not a licensed celebrant services provider, and cannot be held responsible for errors in document content.