Lorenzo

Lorenzo is the AI who works every wedding. He reads the whole wedding before he answers: the moments, the vendor pipeline, the budget and what has been paid, the roster and who has replied, the run sheet. Ask him things, hand him jobs, or let his notes find you on the overview.

The chat#

The phone gives a wedding its own Chat tab. On the web, the wedding shell has no separate chat button; the trip surface that owns the wedding's underlying trip is where the shared Lorenzo chat lives. The wedding's documents, activity and other wedding tools remain on the wedding page. See The couple for the couple's trip view.

The chat is shared by everyone on the wedding: you, your team, and the couple once they are invited in. It is the wedding's conversation, with Lorenzo in it, not a private line. What that means in practice:

Writing to each other is fine. Lorenzo stays out of human-to-human threads unless he is tagged.
@ mentions people on the wedding, and @lorenzo (or @ai) calls him into a group thread. One-to-one, he always answers.
Each person picks how present he is for them: respond to everything, only when mentioned, or off, from the chat's own menu. The owner sets the wedding's mode the first time a multi-person chat starts.

The composer takes attachments (files, photos, camera), which join the wedding's documents. A pinned header keeps the wedding's vitals in view: days to the ceremony, what is sitting with the couple, what needs you.

Long threads stay coherent: Lorenzo keeps a running summary of the older conversation and consults it as he answers. He writes in the wedding's own language, the planner's at the time the wedding was begun, so everyone on it reads one language.

He speaks weddings#

On a wedding Lorenzo talks about the couple, moments, vendors and guests, not travelers, bookings and days. The travel tips are off entirely: nobody needs packing advice counting down to a ceremony. What he does leave on the overview are his notes, the extractions from a forwarded contract or invoice waiting for your yes, and his reading of where the wedding stands.

Ask him plainly and he does it:

"Add the caterer to the reception."
"Where are we?" for the pipeline, the budget against what has been paid, what is due, what the couple has not answered, and the headcounts, in one answer.
"Catch me up", "what's new this week", "did they sign yet" for the last few days on a wedding, a deal or the whole business, newest first, straight from the activity thread.
"Mark the florist booked."
"Add a budget line for the string quartet, 900, due the first of May."
"Add a budget line for the caterer: three payments, 30/40/30, the last a week before."
"Record the photographer's deposit."
"Record the caterer's second instalment."
"What's owed this month?" for the same numbers as the due view, without opening it.
"Add a run-sheet line: flowers arrive at the church, 14:00, 30 minutes."
"We're twenty minutes behind on the ceremony, from the processional." He moves that line and everything after it inside that moment, tells you how many moved, and reminds you that any vendor already sent their sheet now has the wrong times.
"Who has not replied?" for the households still silent, the answers per moment with the children counted in, and the rooms asked for.
"Lay out the countdown."
"Here is the guest list" with a paste, reconciled against the roster before anything is created, rooms and per-moment answers included.
"Fill the rooms at the Quinta." He seats the households who asked, largest first, and names the ones no room was big enough for.
"The block goes back on the first of May," which sets the release date and starts the two reminders that come with it.
"Put the Moreiras at table four." He seats the household together, and if that table breaks a keep-apart rule he says so rather than refusing.
"Keep Ana's uncle and Luís's father apart," which writes the rule from then on.
"Seat everyone for the reception," the same pass as the button.
"How does the room look?" for the tables, who is still standing and which rules the seating breaks. A read, so anyone who can see the wedding can ask.
"Lay out the floor for the reception," which places the unplaced tables on the floor the way the button does.

Five of those need the wedding unlocked: the countdown, the guest-list paste, filling the rooms, the release date and the table plan. He says so rather than failing. Everything else works on a free wedding inside its ceilings; see Plans and billing.

He does not mail a vendor their sheet. That stays a press on the run sheet, so nobody's day is rewritten by a sentence. See The run sheet.

He can also search places (a restaurant for the welcome dinner, a hotel for a second block) and return cards with ratings, hours and map links, convert a currency mid-thread, create tasks on the countdown, and propose the options for a decision you put to the couple.

Example: the morning of#

The florist rings Inês at the venue: the flowers are running late.
She types "we're twenty minutes behind on the ceremony, from the florals drop."
Lorenzo shifts that line and the eleven after it, says so, and reminds her that Duarte Foto already has their sheet. She presses Send their sheet again from the pipeline.

Lorenzo and your clients#

He reads the client layer too, from the same chat. These asks need the professional surfaces on your plan; when one is missing, he names the upgrade rather than half-doing the thing.

"Who is this client?" A name or an email, and he reads the whole relationship: their contact row, every wedding they worked or were married on, the deals open and past, when you last heard from them.
Move a deal along. Name the deal and the stage; he moves it and logs why on the deal's thread, in your words.
"Chase the contract on the Ferreira deal." He adds a follow-up to that deal, due on the day you name, and works out who should hold it.
"What do I owe people this week?" Every follow-up waiting, optionally just yours or just the overdue ones.
"Finish the follow-up on the Ferreira deal." He marks it done.
"Run the enquiry follow-up on the Ferreira deal." He applies one of your workflows by name, and its steps land on the deal.
Draft the proposal. Point him at a couple or a deal and the price, in your own words, and he writes the document with its pages, its optional lines and its validity date. He can write the two other shapes too: a quote is a price with no pages, a brochure is pages with no price and nothing for the couple to accept. It lands as a draft on the proposals page. The send is your press.
Draft the agreement. He merges your template and shows you the filled-in body. The send is your press.
Draft the deposit. He writes a payment request against a deal and leaves it unsent. Nobody is charged.
Draft the invoice. Point him at a client, a deal or a budget milestone and he writes a draft on the invoices page, priced at what is still owed today. It has no number until you press Issue.
"Send Ana the dietary form." That one goes straight away, no draft.
Draft a reply to a lead. Point him at a deal and he answers what the couple actually wrote, in their language, with one clear next step. It is always a draft: he tells you where to send it from, and never mails it himself.
"Who should I get back to today?" Your open deals, ordered by how likely each is to book, with the one thing to do next on each. Ask about one deal and he says the same for it alone.
Turn a call into a note. Paste what you wrote down or a transcript and he saves a call-summary note with its decisions and action items, and offers to make those items into follow-ups.

Every open deal also carries a priority — hot, warm or cool — worked out from your own booked history: how the date, budget and guest count compare to what you usually take, how well that source has converted for you, and how recently the couple wrote back. Open the deal to see the reasons in words, or sort the board by priority to work top down. The deal's own page also names the next step it thinks matters most — a reply overdue, a proposal opened twice with no answer, an agreement waiting on a signed proposal — with the button that does it.

The surfaces themselves are in Clients, deals and getting paid.

Housekeeping#

The chat's ⋯ menu holds the rest: Export transcript renders the session as Markdown (a download on the web, the share sheet on the phone); the owner can clear the whole conversation for everyone, and anyone can clear their own messages.

Free accounts have a daily allowance of five Lorenzo replies; the planner subscription lifts it, along with the places search and the rest of his toolbox. See Plans and billing.