AI features & integrations

Wedding Computer uses AI for requested productivity features and for two limited automatic safety/planning tasks. Productivity tools require a deliberate action or setting. AI writing, AI text import, MCP, and automated workflows require Pro plus the AI subscription; built-in classification and weather behaviour are described separately below. Spam classification for inbound email and form submissions, and the vendor’s long-range expected-weather note, run automatically when their underlying feature is used.

AI email drafting

Skip staring at a blank reply. Open a CRM contact and click Draft email to have the AI write a suggested response, already informed by that contact’s history — so you’re editing a relevant starting point instead of composing from nothing.

The contact-draft action uses the contact’s details, dates, notes, stage, and availability context. The inbox composer also supports prompt templates, with relevant business, contact, booking, and conversation context from the linked message. Check which record or thread you started from before relying on the draft.

You see the draft before anything is sent. Edit it, discard it, or send it as-is — this draft never sends automatically. Enquiry auto-reply (below) is a separate feature with its own setting.

AI enquiry auto-reply

With Pro plus the AI subscription, an enabled availability-based auto-reply can answer a person’s first enquiry. Later enquiries from the same person produce a draft for review. Delivery depends on processing and email checks; it is not guaranteed instantly.

Set AI auto-reply under Settings → Availability sharing. The app uses your recorded availability and form instructions. Review the form’s confirmation actions to understand which messages will be sent.

Open Forms → Enquiry → When someone submits this form to edit the full AI reply prompt, supported placeholders and additional guidance. Restore default prompt if needed, then save the actions. Check form-confirmation and availability auto-reply settings separately. A contact’s Draft reply creates a reviewed draft; it is not an exact preview of the automatic form reply.

The email template guide explains the 15 editable starter prompts, inline Write from a prompt, preserved customisations and business signatures.

AI import extraction

This requires Pro plus the AI subscription. File-based CSV/TSV/JSON import is part of Pro without that add-on.

Moving contacts over from another CRM, or you’ve got a lead’s details sitting in a pasted email, a text message, or a note? You shouldn’t have to retype every name, date and phone number into the contact form by hand — paste the raw text and let the AI pull the fields out for you.

When importing contacts via Setup → Import, you can paste up to 15,000 characters of raw text from an email, message, document, or note. The AI extracts contact details for you to review before the contact is created. The importer does not fetch a URL or web page; copy the relevant text and paste it into the box.

Automatic spam classification

Not everything that reaches your @wedding.computer inbox or your public enquiry form is a real couple. Automatic classification keeps obvious junk — bot submissions, scrapers, spam — from cluttering your notifications and your CRM pipeline, so the leads you actually need to triage don’t get lost in noise.

Inbound messages to a vendor’s @wedding.computer address and public form submissions are automatically classified by Cloudflare Workers AI. Email classification sends the sender, subject, and up to 1,500 characters of body text. Form classification sends the submitter’s email/name, form title, notes, and other text answers.

The classifier is tag-and-notify protection, not a deletion gate. Every email or form submission is stored first. A high-confidence spam form result can suppress its notification, but the record and any linked contact remain available; classifier failures fail open. This classifier is built in and currently has no account-level off switch.

Expected-weather notes and wallpaper taglines

So a wedding’s weather card isn’t empty in the months before a real forecast exists, and so a phone-wallpaper export comes with a caption without you having to write one, two small AI extras run automatically alongside those features.

Before a wedding enters the live seven-day forecast window, opening its vendor workspace automatically generates an AI expected-weather note when one is not already cached. The prompt uses the place and month, plus a public climate reference where available; it does not include the couple’s names. Notes are cached by place and month.

Exporting a phone wallpaper makes a best-effort Cloudflare Workers AI request for a short tagline. That prompt includes the couple names, date, optional location, and ceremony type. The result is cached for up to 60 days; the export still works without a tagline if generation fails.

The MCP server — connect AI assistants

With Pro plus the AI subscription, a compatible MCP client can read and update permitted Wedding Computer data. Use it to review a run sheet, prepare a vendor briefing, or record information. The client should show you proposed writes so you can check their details before approving them.

The MCP server at https://wedding.computer/mcp exposes tools for contacts, permitted weddings, timelines, checklists, guests, seating, notes, weather, and calendar information. The setup page lists the current tools and requirements.

Voice-first: Siri & Apple Intelligence

Voice access depends on an AI client that supports both your chosen voice interface and Wedding Computer’s remote MCP connection. Wedding Computer does not directly configure Siri or Apple Intelligence for you. Follow the client-specific connection guide and check its current capabilities before relying on a hands-free workflow.

Set up the MCP connection

Open wedding.computer/mcp for the current, client-specific setup guide.

For a client that supports remote MCP and OAuth, add https://wedding.computer/mcp as a custom connector and complete the Wedding Computer authorization screen in your browser. This is the preferred setup because you do not have to copy a long-lived credential into a configuration file.

If your client cannot complete OAuth yet, the guide also shows the manual Bearer-token fallback. Generate that integration token under Settings → Calendar & contacts → Advanced integrations, copy it during its one-time reveal, and keep it secret. It grants agent access to your vendor account; it is not the separate limited-scope enquiry API key, which can read your public-form schema and submit leads but cannot read your CRM.

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?”
“Give me a briefing before my meeting with the Chen wedding’s florist”
“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, formatted for an Instagram caption?”
“Add sunrise and sunset markers to the Thompson wedding timeline”
“What’s still open on my to-do list for the Nguyen wedding?”
“Give me the seating brief for the Parker reception — who’s still unseated, and any keep-away conflicts?”
“I just got off a call with a couple who booked for June 14th — add them as a new wedding”

For an existing confirmed booking, supply the actual participant details and date, then review the proposed import before approving it. Importing a booking records history; it does not collect a booking fee or sign a service agreement. See Importing contacts.

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.

Briefings and recording wedding updates

Ask for a wedding briefing to collect the information your account may access: timeline, notes, files, forms, financial summary and other supported sections. The summary is bounded; request the relevant full list for detail. An unavailable or failed section does not mean there are no records.

Resolve the wedding before writing. If several weddings match a name, choose the correct one. Note capture defaults to private; explicitly choose an allowed shared scope when appropriate. Review changes to details or timeline rows, preserve fields you did not ask to change, and ask the assistant to read back the saved result. Management and private-resource permissions still apply.

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 Forms → Enquiry → Enquiry API, 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"
}

GET /api/v1/form, authenticated with the same key, returns your current enquiry form schema. Rate limits are 120 requests per minute and 2,000 per UTC day for each vendor. API-created contacts are labelled with the API source; the endpoint does not currently accept a custom source label.

Privacy & data handling

What data AI can access

AI features receive context for the requested operation. A contact draft can include contact details, date, location, status, notes, and availability. A contextual inbox draft can also include relevant conversation history. Automatic follow-ups use their own restricted context and exclude private CRM notes; see Enquiry follow-ups. MCP applies the authenticated account and wedding permissions to each tool.

AI processing happens when you request a draft or MCP action, submit text to the AI importer, enable enquiry auto-reply, export a wallpaper tagline, receive inbound email or form submissions that are spam-classified, or open a vendor wedding that needs a long-range expected-weather note. Wedding Computer does not run a general background scan of your CRM or wedding account.

Training

Wedding Computer does not train its own AI model on your account data. When you use an AI feature, the required prompt and context are sent to the configured inference provider to produce that result. See the privacy policy for the current processors and legal terms rather than relying on assumptions about a consumer AI account.

Controls and opting out

The productivity integrations require a deliberate action on your part:

Email drafting: you click “Draft reply” each time
Auto-reply: you explicitly enable it in Settings
AI import: you paste text into the AI import path
MCP server: you configure it in your AI client’s settings
Wallpaper tagline: you request the wallpaper export

Spam classification is automatic when inbound email or a public form submission arrives and cannot currently be disabled separately. The expected-weather note loads automatically for a dated, located wedding on the vendor view before the live-forecast window; omitting the date/location prevents it, but also removes weather functionality. There is no other account-wide background AI scan.

Where your data is stored and processed

Wedding Computer’s primary application storage runs on Cloudflare’s infrastructure:

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

Some operations necessarily send the relevant data to another processor: transactional email uses Resend, card payments use Stripe, and AI inference uses Anthropic or Cloudflare Workers AI. The privacy policy is the source of truth for the current processor list and data-handling terms.

Privacy tracking

Business analytics are calculated from Wedding Computer records. Separately configured advertising integrations can share conversion data: the current Married by Josh integration uses campaign click identifiers and hashed email or phone identifiers for enquiry and booking matching. It is scoped to that business and its configured website, not a general setting enabled for every vendor. Hashing is not anonymisation. The referring business’s website may run its own advertising scripts; consult its privacy notice and Wedding Computer’s privacy policy.

Legal responsibility

AI features are drafting tools. Review requested drafts before sending or relying on them. Enabled automatic replies and follow-ups send without a per-message review, so configure their instructions carefully and use fixed wording where exact copy matters. 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.