The welcome email sequence for new clients

The welcome sequence most guides send is three messages of warmth and one attachment. It is pleasant and it is forgettable, because nothing in it could only have been written for this client on this date. What makes a first message land is not tone. It is a fact the reader could not have looked up without effort and did not expect you to. First light on their morning. What the moon will be doing. How hot it is going to feel by ten. All three are published, free, and specific to the day and the place they booked, which means a sequence built on them reads as written rather than sent. Everything else in the sequence is scaffolding the client reads once and never returns to. The wider set of client-facing channels sits under the getting-booked hub.

Why do most welcome sequences fail?

They are about the guide rather than about the trip.

Open any of them and the content is a biography, a mission statement and a list of species, none of which the client asked for.

What a first-time client actually holds in their head is a short list of anxieties they are slightly embarrassed to raise.

Whether they will be the least capable person on the boat. Whether they will be sick. What happens if the weather turns. Whether they are supposed to tip and how much.

A sequence that answers those four, in order, in plain language, does more for the relationship than any amount of warmth.

The reason nobody writes it that way is that the questions never get asked out loud, so they never make it onto the list of things to cover.

Ask any guide who has run trips for a decade and they will list them instantly, which tells you the knowledge exists and simply never reaches the page.

The channel decision underneath all this is worked through in the text and email comparison.

Hilo Ocean Adventures, HI

What makes a message feel written for one person?

A looked-up fact about their day.

There is a specific quality a message has when it contains something true about the reader's exact date and place, and it survives translation into any voice.

Telling somebody that on their Saturday first light begins at twenty-three minutes past six and the sun clears the horizon twenty-five minutes later is not a flourish, it is information.

It also does a practical job, since the most common first-timer question is what time they actually need to be awake.

Those figures are published for any date and any coordinate, and looking one up takes seconds.

Doing it turns a template into a message, and doing it for every booking is the difference between a sequence and a mailing.

None of that requires writing well, which is why it is the highest-return change available to most operations.

Where those addresses come from in the first place is described in the piece on collecting emails.

Where do you get the light times?

The Naval Observatory publishes them, free and without a key.

Its astronomical applications service answers a request for a date and a pair of coordinates with a full set of rise, set, transit and twilight times.

Asked for 15 August 2026 at a point off the upper Texas coast, it returns civil twilight beginning at 06:23, sunrise at 06:48, the sun's upper transit at 13:24, sunset at 19:59 and civil twilight ending at 20:24.

The same response gives the moon: rise at 09:46, transit at 15:51, set at 21:48.

Change the coordinates by a hundred miles and every one of those numbers moves, which is exactly what makes them worth quoting rather than approximating.

Two of them matter more than the rest for a guide: the beginning of civil twilight, which is when you can genuinely see, and sunrise, which is what a client assumes you meant.

Stating both, and saying which one your meeting time is anchored to, removes an entire category of morning confusion.

The service is documented by the US Naval Observatory.

Why include the moon at all?

Because it explains a decision the client cannot see you making.

The same response carries the phase and the fraction illuminated, and on that August date the answer was a waxing crescent at 11 percent, with the new moon three days earlier at 12:37.

Whatever your view of how much that matters to the fishing, it is a genuine input to how you plan a day, and clients find it interesting.

More usefully, it gives you a way to explain a start time that would otherwise look arbitrary.

A message saying you are starting earlier than usual because of what the tide and the light are doing that week reads as expertise rather than as inconvenience.

It also sets an expectation for a slow morning without ever promising a fast one, which is a difficult thing to do in a sentence.

Say nothing about what any of it means for the catch, because nobody can support that claim and clients remember the promise rather than the hedge.

How the same instinct applies to what you publish is discussed in the newsletter ideas piece.

Texas Coastal Adventures, TX

What about the heat?

It is the most underestimated variable a client brings aboard.

The weather service publishes a heat index, which it describes as a measure of how hot it really feels when relative humidity is factored in with the actual air temperature.

Its own worked example: at an air temperature of 96 degrees and relative humidity of 65 percent, the heat index is 121 degrees.

It adds a detail that matters enormously on open water: because heat index values were devised for shady, light wind conditions, exposure to full sunshine can increase them by up to 15 degrees.

A boat has no shade unless you brought some, which means the number a client checked on their phone the night before understates their day.

The service also publishes a measure built for active outdoor work, using temperature, humidity, wind and solar radiation together, described as a particularly effective indicator of heat stress for active populations such as outdoor workers and athletes.

Putting one honest sentence about this in the week-before message does more good than any packing list.

The index is published by the National Weather Service.

How should you say it without alarming anyone?

Name the risk factors, not the outcomes.

The occupational safety agency lists the risk factors for heat illness as heavy physical activity, warm or hot environmental conditions, lack of acclimatisation, and wearing clothing that holds in body heat.

Every one of those describes a client flying in from somewhere cooler, casting all morning, in whatever they packed.

The agency also notes that hazardous heat exposure can occur during any season if the conditions are right, and not only during heat waves, which is worth remembering for a spring trip.

Its recommendations for outdoor work, as summarised by the weather service, are acclimatisation from the first day, shade, scheduling work earlier or later in the day, work and rest schedules, limiting strenuous work and using relief when needed.

Half of those are things you already do and never explain: the early start, the run to shade, the enforced break.

Saying so in the welcome sequence turns them from oddities into evidence that somebody has thought about the day.

Do not diagnose anything or offer medical guidance, since that is not your job and a client with a condition needs their own advice.

The agency's material sits at the occupational heat exposure page, which cites a national emphasis programme directive dated 10 April 2026.

What goes in the first message?

Proof that a person read the booking.

The confirmation a booking system sends is a receipt, and a receipt is not a welcome.

What belongs in the first message from you is short: the date, the meeting place, the time, and one line that could only have been written by somebody who looked at the booking.

Naming the water, the target species or the fact that they booked the long day is enough, and it takes ten seconds.

Say plainly what happens next and when, because the second most common anxiety after the trip itself is whether they will hear from you again before it.

Give a number they can use and say what it is for, which is nearly always a text about a change rather than a call.

Then stop, because the first message is not where the packing list goes.

What the automated version of this looks like is set out in the automations piece.

What goes in the what-to-expect message?

The four questions nobody asks.

Whether they need experience, answered honestly and specifically for the trip they booked rather than generally.

What the day looks like hour by hour, because a client who knows there is a slow middle will not read it as failure.

What happens if the weather cancels, stated as your actual policy with the actual timing, not as a reassurance.

And whether to tip, which every guide dislikes writing and every client is relieved to read.

Add what is provided and what is not, in a list short enough to hold in the head.

Keep it to one screen, because a message that requires scrolling is a message that gets saved for later and never opened.

Send it in the same week as the booking, while the decision is still recent and the enthusiasm is high.

The wider question of what you publish and when is covered in the content calendar piece.

What goes in the week-before message?

Everything that is specific to that day.

This is the message the lookups are for, and it is the one that separates an operation from a form letter.

First light and sunrise, and which one your meeting time refers to.

What the heat is expected to do, with the honest note about sun exposure and no shade.

The moon, briefly, if it is affecting your plan for the morning.

The meeting point as a place rather than an address, with the detail that stops somebody arriving at the wrong ramp.

And the single sentence about what happens if it blows, repeated from the earlier message because this is the week it becomes real.

Everything else you were going to add belongs in the earlier message or in no message at all.

The reminder mechanics themselves are handled in the winter rebooking piece, which runs the same discipline off-season.

What goes in the message after?

Photographs, and one question.

Send the pictures the next morning while the day is still vivid, because a week later they are a memory rather than an event.

Say one specific thing about the trip that proves you remember it, which is easy the next day and impossible the following month.

Ask the one question you actually want answered, and ask only one, because two questions get zero answers.

If that question is about a review, say so plainly rather than dressing it as feedback.

Then say what you would like to happen next, which is usually a date rather than a vague invitation.

This message does more for rebooking than the whole rest of the sequence, and it is the one most often skipped because the guide is on the water again.

Write it the night before the trip, leave the specifics blank, and fill them in over coffee.

How to ask for the review itself is covered in the review request piece.

Should the sequence differ by trip type?

Enough that a half-day client never reads about the long run.

One sequence covering every trip an operation offers ends up describing none of them, because the only content safe for all of them is generic content.

Most guides need two versions rather than five: the short introductory trip and the full day.

The differences are concrete rather than tonal, meaning the meeting time, the amount of running, the food question and the honest description of how tired somebody will be.

A first-timer on a half day mainly needs reassurance; somebody who booked the full day mainly needs logistics.

Writing the second version takes an hour, since it is the first with six paragraphs changed.

Where a booking system supports it, tag the trip type at booking so the right version sends without a decision.

If it does not, keep two drafts and pick one, which is still faster than writing each time.

What about groups and children?

Two additions, and both prevent a bad morning.

A group booking has an organiser who is quietly anxious about everybody else, and the sequence should give them something to forward.

That means one message written so it makes sense to somebody who did not book, containing the time, the place, what to bring and what happens in weather.

Saying explicitly that it can be forwarded saves the organiser rewriting it badly.

Where children are aboard, the addition is a plain sentence about what the day asks of them and what the boat provides, without pretending to give safety advice you are not qualified to give.

The heat guidance matters more here rather than less, and the honest version is short: shade, water, and a willingness to go in early.

Say that you will go in early if it is not working, because an organiser who knows that will relax for the entire morning.

And ask for ages at booking rather than on the dock, which is a form field rather than a conversation.

The photographs from those trips are the ones most likely to be shared, as covered in the testimonials piece.

Which habits weaken the sequence?

Seven, and the first is writing about yourself.

Leading with a biography when the reader wants to know what time to wake up.

Sending a packing list as the first message, which reads as homework.

Writing one sequence for every trip type, so the half-day client reads about the offshore run.

Leaving the cancellation policy vague on the theory that specifics sound negative.

Personalising with a first name and nothing else, which every client now recognises as automatic.

Sending the after-trip message a week late, once the photographs have stopped meaning anything.

And never looking anything up, so nothing in four messages could only have been written for this person.

Sorting clients into groups this way is described in the segmenting piece.

What surprises operators here?

How much of it is a lookup rather than a decision.

The first surprise is that light, moon and heat are all published for any date and coordinate, free, without an account.

The second is that full sun can add up to fifteen degrees to a heat index built for shade, which reframes what a client should bring.

The third is that the questions clients most want answered are the ones they are least likely to ask.

The fourth is how short each message should be once you stop including everything.

The fifth is that the after-trip message, the one most often skipped, is the one that produces the next booking.

Taken together, a better sequence is mostly a matter of looking three things up and cutting half the words.

The photographs that make the last message work are discussed in the trip photos piece.

The sequence, in order

Four messages, three lookups, one screen each.

Send the confirmation within the hour, short, with one line proving a person read the booking.

Send the what-to-expect message the same week, answering experience, shape of the day, weather policy and tipping.

Look up first light, sunrise and the moon for their date and coordinates, which takes about a minute.

Check what the heat is expected to do, and say the honest thing about sun exposure on open water.

Send the week-before message carrying all of that plus the meeting point as a place rather than an address.

Send the photographs the next morning with one specific memory and one question.

Keep every message to a single screen, and move anything that does not fit into the message where it belongs.

Then write the four as templates with the lookups left blank, so the work each time is a minute rather than an evening.

Getting those photographs in the first place is covered in the photo permission piece.