Client journey · Stage 5 of 5 · Updated July 2026

The HoneyBook offboarding process, that earns referrals.

How you close out a client shapes whether they refer you, leave a glowing review, or simply disappear. Here’s how to use HoneyBook to end every client relationship on a high note.

Sydney Young, HoneyBook Pro Written by Sydney Young, HoneyBook Pro & Template Partner.

New to HoneyBook?

This guide assumes you've already got a HoneyBook account with the basics in place. Starting from zero? Walk through the full setup guide first — brand, services, your first Smart File and payments — then come back here to layer on this stage's playbook.

Jargon, decoded

Smart FileHoneyBook's drag-and-drop document builder — can combine a proposal, contract, invoice and questionnaire into one branded link.
ProjectEvery lead or client gets their own Project — the home for their files, messages and payments.
PipelineThe board view of all your Projects, sorted into stages like New Inquiry → Booked → Completed.
AutomationA rule you build once — "when X happens, do Y" — so HoneyBook acts without you lifting a finger.
Trigger & ActionEvery automation starts with a Trigger (the event) and at least one Action (what happens next, like sending an email).
Smart FieldA placeholder like a client's first name that HoneyBook fills in automatically — type { in any text block to insert one.

The five steps

From final delivery to next referral.

01

Send the final delivery clearly

Whether it’s a gallery link, final files, or a wrap-up summary, send it in one clean file with clear next steps, not buried in a casual text message.

Why it matters: A polished final delivery is often the last impression a client has of your professionalism, make it count.

02

Send a genuine thank-you

A short, personal thank-you note a few days after delivery, referencing something specific about their event, lands far better than a generic "thanks for booking!" template.

Why it matters: Clients remember how you made them feel at the end as much as the beginning. This is where loyalty is won.

03

Automate the review request, with good timing

Set a workflow to send a review request once you know the client has seen and loved the final result, not the moment the event ends, when they’re usually still exhausted.

Why it matters: Timing matters: a review asked for too early gets ignored or lukewarm; asked for at the right moment, it gets written enthusiastically.

04

Make the ask for referrals explicit

Don’t assume happy clients will refer you on their own, ask directly, and make it easy with a shareable link or a simple "know someone getting married next year?" line.

Why it matters: Referrals are the highest-trust, lowest-cost bookings you’ll ever get, but most vendors never actually ask for them.

05

Archive the file, don’t delete it

Keep the completed project in HoneyBook rather than deleting it, contracts, invoices and questionnaires stay searchable if you ever need them for a repeat client, a reference, or a dispute.

Why it matters: You never know when a past client returns for a second event, or when you need to reference an old agreement.

That completes the full client journey. Revisit the inquiry stage to see how the next lead starts the cycle again.

Beyond the five steps

Where this stage actually goes wrong.

Mistake: Asking for a review the moment the event ends.

Instead: Wait until they've actually seen and loved the final result, timing matters more than speed here.

Mistake: Deleting completed client projects.

Instead: Archive instead. They stay searchable for repeat clients, references or a past agreement.

Mistake: A generic thank-you with no personal detail.

Instead: Reference something specific about their event, it's the difference between feeling templated and feeling genuine.

Mistake: Assuming happy clients will refer you on their own.

Instead: Make the ask direct and easy, most vendors never actually ask, and that's exactly why it works when you do.

When the playbook needs to flex

A few situations that don't fit the template.

An unhappy client or unresolved issue: Resolve it privately first. Never automate a review or referral ask around friction that hasn't been addressed.

A repeat client books again: Reuse their old Project as reference instead of starting their file from zero.

A delayed final deliverable: If an album or edit takes months, split the sequence, send the thank-you now and hold the review ask until the deliverable actually lands.

Steal the framework

The exact close-out prompts I use.

The same offboarding framework from my private client setup, built here for wedding and event pros — ready to copy straight into HoneyBook.

Quick primer on the automation language below: a Trigger is the event that starts things off, an Action is what happens (like sending an email), and you can chain more than one Action together (like sending an email, then moving the pipeline stage). That's the whole of HoneyBook's Automations 2.0.

Thank-you & delivery

A clean close to the client experience.

Review & referral

Timed asks that actually get answered.

The soft upsell

A natural next step, not a hard pitch.

The thank-you email

Done for you

Sent a few days after the final delivery lands.

Subject: Thank you, truly 💛
Hi {client.firstName}, Now that [the wedding/event] has wrapped, I just wanted to say — thank you. Being part of your day was such a joy, and I'm so grateful you trusted me with it. I hope you're floating on cloud nine right now. More to come soon! {company.emailSignature}
Smart fields:
Client first nameCompany nameEmail signature
Build it in Automations 2.0
Trigger

Project date3–5 days after

Action

Send emailthis template

Pro tip: Send this 3–5 days after delivery, not the same day. Let them actually experience the result before you ask how they feel about it.

The final delivery email

Done for you

Gallery, album, recap film — whatever the deliverable is.

Subject: Your [gallery/files] are here! 🎁
Hi {client.firstName}, The day is finally here — your final [gallery/files] are ready! 👉 [link] A few notes: - This link will stay active for [X months] — I'd recommend downloading and backing up a copy - Feel free to share, print, and post anywhere you'd like Thank you again for having me be part of this. I hope you love these as much as I loved capturing them. {company.emailSignature}
Smart fields:
Client first nameProject/event dateCompany name

Pro tip: State clearly how long the download link stays live. Nothing generates a panicked email faster than a dead link with no warning.

The review request

Done for you

Timed after they've actually seen and loved the result.

Subject: One tiny favor? 🙏
Hi {client.firstName}, I hope you've had a chance to look through everything! If you loved your experience, would you mind leaving a quick review? It genuinely helps small businesses like mine so much. 👉 [Leave a review here] Prefer to just tell me directly? Feel free to hit reply — I'd love to hear your thoughts either way. Thank you again for everything! {company.emailSignature}
Build it in Automations 2.0
Trigger

Project date2–3 weeks after

Action

Send emailthis template

Later than the thank-you, once they've actually seen the gallery or final result — that's what makes the ask land.

Pro tip: Ask once, then let it go. A single well-timed ask outperforms three naggy follow-ups — and repeated nudges can undo the goodwill you just earned.

The referral ask

Done for you

Don't assume happy clients will think to refer you — ask.

Subject: Know anyone getting married next year? 👰
Hi {client.firstName}, I had such a wonderful time working with you, and it made me think — if you know anyone else planning a wedding or event, I'd be so grateful for the introduction! As a thank-you, [referral offer, e.g. "you'll both get $50 off"] when they book and mention your name. Either way, thank you again for such a special day. {company.emailSignature}

Pro tip: Give a concrete reason to think of you right now — "know anyone getting married next spring?" beats a generic "refer your friends!" every time.

The soft upsell

Done for you

Anniversary sessions, second events, retainer relationships.

Subject: What's next for you two? 💫
Hi {client.firstName}, I've loved every bit of working with you, and wanted to share a few ways we could work together again down the line: - [Anniversary session] - [Referral partnership] - [Next event / retainer relationship] No pressure at all — just wanted you to know the door's always open! {company.emailSignature}
Close it out
Trigger

Project date1–3 months after

Action

Send emailthis template

Action

Move pipeline stageto Completed / Past Client

Keep the project in a Completed pipeline stage rather than deleting it — contracts, invoices and questionnaires stay searchable for repeat clients or references.

  • Final delivery, sent in one clean file with clear next steps
  • A genuine thank-you, a few days after delivery
  • A review or testimonial request, timed after they've seen the result
  • A referral ask, made explicit — don't assume they'll think of it
  • Move the project to Completed instead of deleting it

Pro tip: Only send the upsell to your best-fit clients. A soft pitch to a lukewarm one just feels like a sales email — save it for the people who'd genuinely thank you for it.

Ready to turn clients into referrals?

Start a free 7-day trial and lock in 30% off your first year through my HoneyBook Pro link.

Get 30% off HoneyBook →

Questions

The offboarding stage, answered.

When should I ask for a review?

Once the client has actually seen and loved the final result, not the moment the event ends. Asking too early often gets a lukewarm or delayed response.

How do I ask for referrals without feeling pushy?

Make it a natural, specific ask, "know anyone getting married next year?", paired with a simple way to share your info, rather than a generic "please refer me" line.

Should I delete completed client files in HoneyBook?

No. Archive them instead of deleting. They stay searchable for repeat clients, references, or if you ever need to revisit the original agreement.

What belongs in a final delivery message?

A clear link or file with the final deliverable, a short thank-you, and any clear next steps, kept in one clean file rather than a casual text or scattered emails.

Do I need to delete a client's project once it's complete?

No. Move the project to a Completed pipeline stage instead of deleting it, so contracts, invoices and questionnaires stay searchable for repeat clients or references.

The newsletter

Systems & shortcuts, straight to your inbox.

Join the list for my favourite tools, guides and freedom-building tips. No fluff, unsubscribe anytime.