> ## Documentation Index
> Fetch the complete documentation index at: https://docs.florists.digital/llms.txt
> Use this file to discover all available pages before exploring further.

# Converting Enquiries to Events

> Turn a form submission into a full event with pre-filled details.

<Warning>
  Make sure you have proper consent before exporting or sharing customer data. Follow your shop's data protection policy.
</Warning>

**Converting an enquiry turns a customer's form submission into a real event in your dashboard.** Instead of starting from scratch, Digital Florists carries over the date, venue, budget, and other details the customer gave you, so you can get straight to planning.

<Info>
  **Requires the Events (Manage) permission.** Managers and Admins have this by default; your administrator can adjust who has it in [Settings > Team](/settings/team).
</Info>

## What conversion does

When you convert a submission, Digital Florists creates a new event and pre-fills as much as it can from what the customer entered. This saves you from retyping details you already have.

The original submission is marked as **Converted** and linked to the new event, so you have a clear trail from first enquiry to confirmed booking.

## What gets pre-filled

When you click **Create Event** from a submission, the event form opens with the customer's details applied:

* The customer's **name, event date, event type, budget, venue, guest count, referral source, and notes** are pre-filled from the form answers, based on your conversion field mapping.
* An **Enquiry guide** sidebar appears alongside the event form, showing the customer's original responses. This is helpful during a consultation so you can reference exactly what they asked for.
* You can tap **Use summary in notes** to append the enquiry's notes summary into the event notes.

<Warning>
  Review the pre-filled information before saving. Customers sometimes enter approximate dates or misspell venue names, so it's worth a quick check.
</Warning>

## How field mapping works

Open your form's settings and use the **Conversion** tab to map form fields to event fields. This tells Digital Florists which answers correspond to which event details:

* **Event date** — the customer's preferred date goes into the event date.
* **Event type** — their selection (wedding, corporate, and so on) is matched to one of your event types.
* **Budget** — their budget range fills in the event budget.
* **Guest count** — number of guests pre-fills the venue's attendee count.
* **Venue** — venue information pre-fills the venue name.
* **Notes** — their description or vision populates the event notes.
* **Referral source** — how they heard about you fills the marketing source.

The more fields you map, the less you fill in manually.

<Tip>
  Set up your conversion field mapping in form settings before you start receiving enquiries. It only takes a moment and makes every future conversion faster.
</Tip>

## The conversion process

<Steps>
  <Step title="Open the submission">
    Go to the form's submissions list and open the enquiry you want to convert. You'll see the customer's responses and their contact details.
  </Step>

  <Step title="Click Create Event">
    Click **Create Event**. This starts the conversion and opens the event creation form with the submission's details applied.
  </Step>

  <Step title="Review the pre-filled details">
    Check that the date, event type, budget, and other mapped fields look right. If a field maps to a select option that doesn't exist in your dashboard (an unrecognised event type, for example), you'll be prompted to pick a matching one.
  </Step>

  <Step title="Use the Enquiry guide sidebar">
    The **Enquiry guide** sidebar on the right shows the mapped highlights from the submission alongside a notes summary that includes any unmapped answers. Use it as your reference while you work through the form.
  </Step>

  <Step title="Fill in the remaining details">
    Complete anything that wasn't pre-filled, such as venue addresses, colour notes, or contact labels. Click **Use summary in notes** to drop the notes summary straight into the event notes if it's useful.
  </Step>

  <Step title="Create the event">
    Click **Create event**. The event is created in **Draft** status, and the submission is marked as **Converted** with a link to the new event.
  </Step>
</Steps>

## The Enquiry guide sidebar

While you're creating the event, the sidebar keeps the customer's enquiry visible alongside the form. It shows:

* The form title and when the enquiry was submitted.
* The customer's contact name and email.
* The mapped highlights: event date, event type, budget, guest count, venue, and referral source.
* A notes summary that bundles any unmapped form answers and the customer's vision or description.
* A **View submission** link if you need to see the full original responses on a separate screen.

This way you can build out the event without flicking back to the submission.

## What gets linked

After conversion, the submission and event are connected in both directions:

* The submission shows a **Converted** status badge with a **View Event** link.
* The event lists the submission under its form submissions, so you can open the original enquiry from the event.

This lets you trace where a booking started, from first enquiry through to the finished event.

<Info>
  If the customer's email address matches an existing customer in your dashboard, that customer is linked to the event automatically. If there's no match, pick or create a customer from the event creation screen before saving.
</Info>

## Common questions

<AccordionGroup>
  <Accordion title="Do I have to set up field mapping before converting?">
    No. You can convert a submission without any field mapping — you'll just need to fill in the event details manually. Field mapping saves you time by pre-filling what it can.
  </Accordion>

  <Accordion title="Can I convert the same submission more than once?">
    No. Once a submission is converted, the **Create Event** button is replaced with **View Event**. If the customer needs a second event, start a new event from the events dashboard.
  </Accordion>

  <Accordion title="What happens to the original submission after conversion?">
    It stays in the submissions list with a **Converted** status. Nothing is deleted, and you can still view the customer's original responses at any time by opening the submission.
  </Accordion>

  <Accordion title="What if the customer entered incorrect information?">
    You can edit any pre-filled field before creating the event. The Enquiry guide sidebar shows what the customer submitted for reference, but every field on the event form is editable.
  </Accordion>
</AccordionGroup>

## What's next?

<Columns cols={2}>
  <Card title="Managing Submissions" icon="inbox" href="/events/managing-submissions">
    Review, organise, and follow up on your enquiry submissions.
  </Card>

  <Card title="Creating an Event" icon="circle-plus" href="/events/creating-an-event">
    Learn about all the details you can add when creating an event.
  </Card>

  <Card title="Form Settings" icon="gear" href="/events/form-settings">
    Configure field mapping, notifications, and styling for your forms.
  </Card>

  <Card title="Event Lifecycle" icon="arrows-spin" href="/events/event-lifecycle">
    Understand the stages an event moves through from draft to completion.
  </Card>
</Columns>