---
title: Send a proposal
description: Send a client a personal link from their project, so they can choose a package, pay, sign, and book that same project.
section: Core workflows
order: 4.1
---

# Send a proposal

A proposal is a personal link for a client who has already inquired. They choose a package and any add-ons, confirm, pay if payment is due, and sign if there's a contract. The project you sent it from then becomes booked, so you don't end up with a second project.

## Before you start

You need a published service [booking page](/docs/bookings), since a proposal starts from a page's packages, add-ons, and payment settings.

**Send proposal** appears on a project's **Progress** checklist while the project is **New Lead** or **Follow Up**. The project also needs:

- A client with an email address.
- No contract already published, sent, or signed, and no invoice already published.
- No payment already recorded.

To take payment, [connect Stripe](/docs/invoices) first. Without it, you can still send a proposal that has nothing to pay. **Send proposal** is in the web app. In the mobile app, you can put the [proposal link](#put-the-proposal-link-in-an-email) in an email you write from a project.

## Make and send a proposal

1. Open the project and choose **Send proposal**.
2. Choose a **Booking page**. It starts on the service's [booking page for proposals](#choose-a-page-for-each-service), if it has one. If the project has no service yet, choose a **Service** too.
3. Choose the packages to offer. You can change a price for this client, and mark one **Recommended**. It starts with the page's [recommended package](/docs/bookings#add-and-arrange-blocks), if you offer it. Your client sees a **Recommended** label on it, but nothing is chosen for them unless you offer only one package. [Date only](/docs/services#booking-preferences) packages are marked.
4. Choose what **Your client can** do: **Book** lets them book and pay straight away, and **Request** has them [send you a request](#let-your-client-request-first) to accept first. It starts from the booking page's choice.
5. Choose how the client pays under **Payment**. For a deposit, also choose when to collect the remaining balance. Your client pays the deposit, plus tax, when they book. The rest of the package and any add-ons go on the project's [payment link](/docs/payments). If they book after the balance's due date, it's due the day they book.
6. Set the date:
   - **A date and time:** the client books that time.
   - **A date with no time:** the client books that date, with the time to be agreed.
   - **No date:** the client picks from the page's available times. For a Date only package, they pick from its available dates, with the time to be agreed. Dates that have reached your **Date-only jobs per day** aren't offered. If the page has no [availability](/docs/bookings#availability-and-scheduling), your client asks you for a date instead, so a **Book** proposal becomes a request.

   If you offer a Date only package on a date that has already reached your **Date-only jobs per day**, the panel says so. You can still send it, and your client can book that date.

7. Add a **Personal note** if you like. It starts with the booking page's [personal note](/docs/bookings#proposals), with your client's details filled in.
8. Set **Valid until** if you'd like the proposal to [expire](#valid-until): the last day your client can book it or send a request. It starts from the booking page's **Valid for**, if it has one. Leave it empty to keep it open.
9. For a date with a Date only package, set **Hold the date until** if you'd like to [keep the date](#hold-the-date) for this client. Leave it empty to hold nothing.
10. Choose **Preview** to see what your client will see.
11. Choose **Send proposal** to email it, or **Copy link** to share the link yourself.

Nothing is saved until you send or copy. Sending by email moves a **New Lead** project to **Follow Up**, as any email to the client does. Copying the link doesn't.

A proposal keeps the terms you sent: its packages and prices, each package's [What's included](/docs/services#add-packages) list as it was when you sent it, and the payment. Later changes to the page or its packages don't change them, and discount codes don't apply to it. Proposals don't show a package's delivery time, so nothing is promised that could change after you send it.

Your client signs the [contract set on the package](/docs/services#booking-preferences) they book, as it is when they book, whatever the booking page's own contract setting. If you change a package's contract after sending, your client signs the new one. If that package has no contract, there's nothing to sign, and the project's **Contract required** stays as it was: you can still [send a contract](/docs/contracts) from the project, or turn it off there.

The look and blocks are different: a proposal shows its booking page's [Page tab](/docs/bookings#design-the-page) as it's published now. When you [publish](/docs/bookings#publish-and-share) a change to them, your client sees it the next time they open the proposal. If you unpublish or archive the page, its proposals keep its last published look and blocks. If you delete the page, they show the **Neutral** look with no blocks. The look never changes what your client can book. If the page puts its [title on the opening photo](/docs/bookings#the-opening-photo), the proposal's name and "Prepared for" line go on it too. A [Testimonials block](/docs/bookings#testimonials) shows your testimonials as they are when your client opens the proposal, at random or the ones you chose.

## Valid until

Your client can book a proposal with a **Valid until** date, or send a request for it, until the end of that day in your account's time zone. Their page shows "Valid until" with the date, and so does the **Proposal** card. If you change your account's time zone, it ends at midnight in the new one.

Once the day has passed, the card says **Expired**, and **Activity** notes it. Your client can still open the link, read the proposal, and ask you a question, but can't book it or send a request. Nothing else changes: it stays the project's open proposal, and you're not notified.

From the card:

- **Extend 7 days:** gives your client until a week from today.
- **Choose a date** (**⋮** menu): pick another day, today or later.
- **Close:** your client can no longer book from it.

Your client isn't emailed when you extend it. Their link shows the new date, including a page they already have open once they come back to it, and **Activity** notes "Valid until changed". Before the day has passed, **Change valid until** in the **⋮** menu moves it, earlier or later.

If the proposal is also out of date, or its email wasn't confirmed as delivered, the card offers **Resend** instead, and the resent proposal is valid for 7 days from today. Once the proposal's date has passed, the card offers only **Close**, unless you've changed the project's date to one still to come, which a resend takes.

Valid until only applies while your client hasn't answered:

- **A request your client already sent** isn't affected. They can still change it until you answer it.
- **An accepted request** uses [Book by](#book-by) instead.
- **If your client is paying** when the day passes, they can finish. If the payment doesn't go through, the proposal shows as expired.

When you resend a proposal, it keeps its **Valid until** while that's still to come. **Replace** starts with it too. Copy link still works on an expired proposal, and the card notes that your client needs it extended to book it or send a request. Proposals made by the [proposal link in your emails](#put-the-proposal-link-in-an-email) have no **Valid until**.

## Hold the date

While you hold a proposal's date, it counts toward your **Date-only jobs per day** the way a booking does. When the hold takes the date's last place, clients on your booking pages see it as **Fully booked. You can still send a request.**, and another client's proposal for that date says it's fully booked. Your own client can still book it.

**Hold the date until** shows when the proposal has a date and offers a Date only package, and your **Date-only jobs per day** isn't **No limit**. Choose a day from today up to the proposal's date, and no later than **Valid until** if it has one. The date is held until the end of that day, in your account's time zone, and never past the end of the proposal's date.

If the date is already full, the panel says so, and sending holds it for your client anyway. On a **Request** proposal, that only lasts while the hold does. On a **Book** proposal, your client can book that full date for as long as the proposal is open, as without a hold.

The **Proposal** card shows "Date held until" with the day. The day before the hold ends, you get a notification so you can decide whether to extend it, follow up, or let it go. You're not notified for a hold that ends with the proposal's date itself.

### When it ends

When the day passes, the date isn't held any more. Nothing else changes: your client can still book while the date has room. The card says the date is no longer held, and **Activity** notes "Hold ended". If you held a date that was already full and it's still full when the hold ends, the card says it's fully booked and you get a notification. If your client has already sent a request, the card doesn't say so and you're not notified: **Accept** tells you the date is full.

The hold also ends early when:

- The proposal is booked, replaced, or closed, or the project is marked lost or archived.
- You change the project's date to a different one.

Changing the project's time, location, or client keeps the date held, and so does adding the held date to a project that had none. **Resend** keeps the hold while it's running and the date is the same. **Replace** starts with it too.

### Extend hold

From the card:

- **Extend hold:** holds the date again until a week from today, or the proposal's date or **Valid until** if that's sooner.
- **Choose a hold date** (**⋮** menu): pick another day.
- **Change hold date** (**⋮** menu): move it while the date is still held, earlier or later.

If the date has filled since, you're asked first, and holding it lets your client book it anyway while it's held. **Extend hold** isn't available while your client is paying, after the proposal's date, once **Valid until** has passed, or once you've changed the project's date to a different one, until you change it back. Moving **Valid until** earlier than the hold moves the hold too, and **Activity** notes the hold changed. Extending **Valid until** doesn't extend the hold.

### When your client sends a request

The hold stays on the date you offered, even if your client suggests another one. The card shows the held date apart from the date they asked for. When you accept, **Hold the date until Book by** moves the hold to the date you agree. It's on when the date is being held. Without it, the hold ends.

## Let your client request first

With **Request**, your client chooses a package and add-ons, confirms the date or suggests another, and sends it to you. Nothing is paid, signed, or booked. You look it over, change anything you need to, and accept it. Then they confirm, pay, and sign, as with a proposal they book.

To make it the default for a booking page, edit the page and, under **When a client chooses a package**, choose **Request**. This also sets the page's own link and website embed to take [requests](/docs/bookings#requests-from-a-booking-page) instead of bookings. You can still switch any proposal to **Book** or **Request** when you send it.

A **Request** proposal doesn't need Stripe to send, since nothing is paid until you accept. Neither does a **Book** proposal with no date whose booking page has no availability, since your client sends a request for the date they'd like. If what you accept takes payment, Stripe needs to be connected then.

A proposal set to **Book** also asks your client to request, rather than book, when:

- They choose a Date only package on a date that's reached your **Date-only jobs per day**. Packages with a time can still be booked.
- It has no date, and its booking page has no availability, or can no longer be booked from.

### Review a request

You get a notification when your client sends a request, and again each time they change it. The project moves to **Requests to Review** under **Inquiries** in **Projects**, and the **Proposal** card shows **Your client sent a request**: the package and add-ons with the total, the date, and whether they suggested another one.

From the card:

- **Accept:** opens Accept, below.
- **Reply:** write back in the project's conversation.
- **Close request** (**⋮** menu): ends the request and keeps the inquiry open. Your client isn't told, and can't change it any more. Automatic follow-ups carry on and can include a new proposal.
- **Mark lost and archive** (**⋮** menu).

A request can't be resent or replaced. If you change the project while it's waiting, your client still sees that it's with you, and accepting is how you move on.

### Accept a request

**Accept** opens with what your client asked for: the package at its price, their add-ons, their date, your payment terms, and **Book by** a week from today. You can change the package and its price, the add-ons, the date and time, the payment terms, and **Book by**, including a package or add-on from the booking page that the proposal didn't offer. Accept shows:

- The reminders your client will get before **Book by**, such as "Reminders 3 days and 1 day before Book by".
- A warning when **Book by** is after the date.
- Whether a time your client picked from your booking page is still free.
- That the date is fully booked for Date only jobs, if it is. Accepting takes it anyway.
- **Hold the date until Book by**, for a Date only package when you have a **Date-only jobs per day**. It's on when the date is being held. The agreed date is then held until **Book by**, or the end of the date if that comes first.

Choose **Accept and email client**. The project takes the agreed date, package, and price straight away, and your client gets an email saying you accepted their request. Their link shows what changed from what they asked for, with what you agreed already chosen, then payment and signing as for a proposal they book. If they changed their request while you were looking at it, Accept asks you to check it and accept again.

### Book by

Your client can book until the end of the **Book by** day, in your account's time zone. The **Proposal** card shows the date, and you get a notification the day before if they haven't booked yet. If you change your account's time zone, **Book by** ends at midnight in the new one.

Nothing closes when **Book by** passes. The card says **Book by has passed**, and your client can still book while the date has room. From the card:

- **Extend Book by:** choose a new date, before or after **Book by** has passed. Your client isn't emailed. Their link shows the new date, and they get reminders for it if your payment reminders are on. Reminders for the old date that haven't gone out are dropped. **Activity** notes the change.
- **Close:** your client can no longer book from it.

**Extend Book by** isn't on the card while the proposal is out of date, since your client can't book it until you resend it, or once the job's date has passed. If **Book by** has passed when you resend, the resent proposal gets a new **Book by** a week from today.

If you held the date until **Book by**, the hold moves with **Extend Book by**, and ends when **Book by** passes or the date itself does. The notification the day before names the date. Once the hold has ended, **Extend Book by** or a resend gives your client a new **Book by** but doesn't hold the date again. To hold it again, turn on **Hold the date until Book by** in [Change accepted terms](#change-what-you-agreed).

If you accepted a date that was already fully booked for Date only jobs, your client can book it anyway until **Book by**. After that, they can only book it once the date has room again. The notification the day before says they're about to lose the date, and you get another if **Book by** passes while it's still full. If the date fills while they're deciding, the card says so. **Extend Book by** lets them book it anyway, or use **Send other dates**.

### Change what you agreed

To change what you agreed before your client books, choose **Change accepted terms** on the card. It opens with what you agreed, and you can change the package and its price, the add-ons, the payment terms, the date and time, **Book by**, and the **Personal note**. If **Book by** has passed, it starts a week from today. Choose **Save and email client**. The project takes the new terms, and your client gets an email saying their booking details were updated.

If you change the project's package after accepting, the card asks you to agree it this way, since a resend keeps what you agreed.

### Reminders before Book by

Your client's reminders follow your [payment reminders](/docs/invoices#payment-reminders): each **Before due** reminder also goes that many days before an accepted request's **Book by**, at noon. With payment reminders off, there are none. Each asks your client to confirm and pay, or to confirm if there's nothing to pay, and links to their proposal. They show as **Book by reminder** in the project's **Automated emails**.

- A reminder that would go on or before the day you accept or extend, or after the job's date, isn't sent.
- A reminder isn't sent while your client is paying, or while the proposal is out of date. One that falls due then is skipped, and **Automated emails** says why. When you resend it, your email takes its place, and the resent proposal gets its own reminders.
- They stop once your client books, or you close the proposal.

### Follow-ups and requests

A request isn't a reply, so your service's [follow-ups](/docs/services#client-emails) don't stop for it. They wait for your answer:

- While your client's request is newer than your last email to them, follow-ups wait. The automatic reply to the inquiry doesn't count as your answer. They start again from your next email, and wait again if your client changes their request.
- After you accept, they wait until **Book by** has passed and count from then. A question from your client during that time still waits for your answer.
- If you close the request, or close an accepted proposal before **Book by**, they count from then.
- Once a follow-up has gone out and your client replies, the rest still stop for good.

## Choose a page for each service

Each service can have a **Booking page for proposals**. **Send proposal** starts on it, and the proposal link in your emails, including the service's [automated emails](#in-automated-emails), makes proposals from it.

1. Go to **Settings → Services & Packages** and edit the service.
2. On the **Details** tab, choose a **Booking page for proposals**. The list shows your published booking pages that offer at least one of the service's packages. If only one does and the service has never had a page chosen, it's already chosen.
3. Select **Save**.

You can also choose them from the booking page: in **General**, under [**Proposals**](/docs/bookings#proposals), choose **Choose services**.

If the page is later unpublished, archived, or deleted, or stops offering the service's packages, the service says so when you edit it, and the proposal link can't make proposals for that service until you fix the page or choose another. To stop using a page, choose **No page**. If the service's automated emails to inquiries have the link, it also [warns you](#warnings-before-an-inquiry-arrives) when a proposal couldn't be made from the page as it is.

## Put the proposal link in an email

Instead of sending a proposal on its own, you can put a link to it in any email you write from a project. Insert **Proposal link** from the **Personalized text** button in the project's email, or from **Merge tags** in the mobile app. You can also add it to a template whose category is a service, in **Settings → Message templates**, and a service's [automated emails](#in-automated-emails) can send that template. General and Mini sessions templates can't have it, since they're also used where there's no project. A template that has it can move to another service, but not to General or Mini sessions.

Your client sees a link reading **View your proposal**, or **View your booking** once the project is booked.

In version 1.0.1 of the mobile app, **Merge tags** doesn't have **Proposal link**. If you send a template that has it, the app only says it couldn't send or schedule the email, and a **Failed** email doesn't say why. Update the app, or use the web app.

### When the email goes out

The link is filled in when the email goes out, about 30 seconds after you choose **Send**, or at the time you scheduled. Then:

- **The project has an open proposal:** the link opens it, as it is. An [expired](#valid-until) one is sent as it is too, and your client sees that it has expired, with **Ask a question**.
- **It doesn't:** LYGHTBOX makes one from the service's booking page for proposals, as **Send proposal** would if you changed nothing: every package of the service on that page, at the page's prices, with the page's recommended package and payment settings, its personal note and **Valid for**, and the project's date, time, and location. The **Proposal** card follows it like one you sent yourself.
- **The project is booked:** the link takes your client to their booking.
- **Your client is paying:** the link shows that their payment is in progress.

**Undo send**, or **Cancel send** for a scheduled email, brings the email back as you wrote it, with the link, and sending it again checks everything again. If the email had already started going out, the proposal it made stays on the project as **Not sent yet**.

### When Send refuses the link

When you choose **Send**, or schedule the email, LYGHTBOX checks what the link would do, and doesn't send or schedule the email if it can't be used. The message says why, so you can fix it, or remove the link to send the email now. For example:

- **The link is typed into a link's address.** Remove that link and insert **Proposal link** instead.
- **The email isn't from a project,** such as a mini session booking's.
- **The project is closed** (archived or Closed Lost), or **has no client** to send it to.
- **The open proposal can't be booked as it is:** it's out of date, so resend it; its date has passed, so send a new one; or it's an accepted request whose date is now fully booked, so extend **Book by** to let your client book it anyway, or send other dates. Do these from the project's **Proposal** card.
- **The open proposal takes payment, and Stripe isn't connected.** [Connect Stripe](/docs/invoices), or send a new one with no payment from the project's **Proposal** card.
- **The project can't have a proposal,** such as when a contract or invoice is already published, or a payment is recorded.
- **There's nothing to make it from:** the project has no service, or its service has no booking page for proposals, or that page can't be used. Choose a service for the project, or [a page for the service](#choose-a-page-for-each-service).
- **The page can't make a proposal as it is,** such as a package with no price, a deposit with no amount, or payment due with Stripe not connected. Fix the page or package, or use **Send proposal** on the project.
- **The project's date has passed,** or **a Date only package's date is already at your Date-only jobs per day.** Change the date, or use **Send proposal**, which lets you take a full date anyway.

The **Proposal** card, services, booking pages, and Stripe are in the web app, so make those fixes there.

### If it can't be used when the email goes out

Things can change between choosing **Send** and the email going out, especially for a scheduled email. LYGHTBOX checks again when the email goes out. If the link can't be used then, the email isn't sent and nothing is made. It shows as **Failed** in the project's thread, with the reason under it, starting "The proposal link couldn't be used". Write the email again, without the link if you need to send it now.

You don't get a notification when this happens, so check the project's thread once a scheduled email is due.

If you change the project's client or reset its proposal link after choosing **Send**, the email isn't sent, so the link never reaches someone it wasn't meant for.

## In automated emails

A service's [automated emails](/docs/services#client-emails) can send a template with **Proposal link**: its reply to inquiries, its follow-ups, and its Client emails. The link is filled in when each email goes out, as in an email you write.

- **A new inquiry:** the reply makes a proposal from the service's [booking page for proposals](#choose-a-page-for-each-service), as **Send proposal** would if you changed nothing, so your client can choose a package moments after inquiring, with no one at the desk. It's the project's open proposal from then on.
- **A follow-up:** it links to the project's open proposal, whether you sent it or the reply made it. If there's none, it makes one, as the reply does.
- **Client emails** go once the project is booked, so their link takes your client to their booking.

The **Proposal** card shows **Sending automatically** while the email is going out, then **Emailed automatically** with the date. Once an automated email with the proposal has gone out, a **New Lead** project moves to **Follow Up**, as when you send one yourself. If LYGHTBOX can't confirm the email was delivered, the card says **Delivery not confirmed** and offers **Resend**. Check with your client before sending it again.

While your account is on hold, an automated email doesn't make a proposal, so an email that would make one is skipped. Emails that link to an open proposal or a booking still go.

### When the link can't be used

When an automated email with the link is due, LYGHTBOX checks what the link would do, as **Send** does for an email you write. If it can't be used, the email isn't sent and nothing is made. The project's **Automated emails** marks it **Not sent** and says why, such as the service having no usable booking page for proposals, the project already having a contract, or a proposal that takes payment while Stripe isn't connected.

A skipped email isn't sent later, even once you fix the cause, so a skipped reply to an inquiry is gone for good. Use **Send proposal** on the project instead. Follow-ups still count from your next email to the client, as usual. You don't get a notification when an email is skipped.

An email after delivery with the link isn't sent once the project is archived, since an archived project's link shows its proposal as closed.

### Warnings before an inquiry arrives

Because a skipped reply can't be sent again, LYGHTBOX warns you about a setup that would skip it:

- **On the service:** when its reply to inquiries or a follow-up uses a template with the link, **Booking page for proposals** on the **Details** tab says if a proposal couldn't be made from the service as it is: it has no page, the page can't be used, a package has no price, the page's deposit is more than a package's price, the page takes payment and Stripe isn't connected, or the page lists more than 20 packages, or more than 50 add-ons across them. Client emails don't need a page, so they don't count. If an email after delivery has the link, **After delivery** on the **Client emails** tab notes that it isn't sent once the project is archived.
- **On the template:** in **Settings → Message templates**, a template with the link that a service's reply or follow-ups use says what happens when it goes out, and names any of those services with no usable booking page for proposals.

These are warnings, so you can still save. They check the service, not each inquiry, so something that depends on the inquiry, such as its date being fully booked, can still skip the email when it's due.

## Follow it on the project

The **Proposal** card on the project shows how far it has got, such as **Emailed**, **Link copied**, **Opened by your client**, **Your client sent a request**, **Request accepted**, **Your client is paying**, or **Expired**. **Opened** means your client did something on the page, not only that the link was loaded. **Activity** in the sidebar keeps the history: sent, opened, expired, **Valid until** changed, the date held, the hold extended, changed or ended, request sent, updated and accepted, **Book by** changed, replaced, closed, link reset, and booked. It also notes when you send a proposal for a date that's already full, when the proposal's date fills or frees up, and when a late payment books a date past your **Date-only jobs per day**.

From the card you can:

- **Copy link:** get the link again.
- **Resend:** send it again after a failed email or a change to the project.
- **Replace** (**⋮** menu): change the terms. The new proposal takes over, at the same link.
- **Reset link** (**⋮** menu): stop earlier copies of the link working, then share the new one. Use this if the link went to the wrong person.
- **Close** (**⋮** menu): your client can no longer book from it. You can send a new one later.

## When the date fills up

If a proposal offers a Date only package on a date that reaches your **Date-only jobs per day** before your client books, the **Proposal** card says the date is fully booked. You also get a notification, unless the date filled because you changed your limit or a package. Your client can't book the Date only packages on that date, and can still book packages that have a time. They can [send you a request](#let-your-client-request-first) for the date instead, and if you accept it, they can book it anyway. For a request you've already accepted, see [Book by](#book-by).

From the card:

- **Send other dates:** writes a message to your client in the project's conversation, listing up to five dates that are currently free on the booking page, for you to check and send. If none are free, it says the date has filled.
- **Replace** (**⋮** menu): send the proposal again to take the job on that date anyway, or to offer another date.

The notice goes away if the date frees up.

## While a proposal is open

- **You change the project's client, date, time, location, service, or package:** your client sees that the proposal is being updated until you choose **Resend**. If the service changed, choose packages for the new service.
- **You publish a contract or invoice, or record a payment:** LYGHTBOX asks you to close the proposal first, since the client could otherwise book on top of it. You can still save a draft invoice.
- **A draft invoice comes up for its scheduled send:** it waits. It goes out if you close the proposal or mark the project booked yourself. It doesn't go out if your client books from the proposal, or if the project is marked lost or archived.
- **You mark the project lost or booked, or archive it:** the proposal closes.
- **Your client is paying:** changes to the project wait until the payment has finished, and the proposal can't be replaced, closed, or reset.

## Use a page only for proposals

Turn off **Public booking link** on a service page if you only want to use it for sending. Publish the change, and new visitors can no longer book from its link or your website. Clients who are already booking can finish.

A page used only for proposals doesn't need [availability](/docs/bookings#availability-and-scheduling). Proposals made from an inquiry start with the date your client gave you, and without availability, your client asks you for a date when the proposal has none or they'd like another. If you add availability, they pick from it instead, since turning off the public link only stops new visitors.

## Related guides

- [What your client sees on a proposal](/docs/proposal-client-page)
- [Cancel or refund a proposal booking](/docs/proposal-cancel-refund)
- [Booking pages](/docs/bookings)
