Winning Back Lapsed Clients

The federal aviation rules define the exact moment a qualified person stops being current purely because time passed. Three takeoffs and three landings in the preceding ninety days, and competence has nothing to do with it.

A pilot with twenty thousand hours is non-current on day ninety-one, and the way back is not an examination. It is a flight with nobody aboard. Which is the most useful available model for a lapsed client: a defined moment at which the relationship stops counting as live, and a deliberately low-stakes route back that asks for far less than the thing that lapsed. None of it binds a fishing guide. What it supplies is a way to think about a client who has not booked in three seasons that is neither pretending they are still active nor writing them off. Below the currency provisions are read from the regulation, then the win-back sequence. This is not legal advice. Sibling pieces sit at the running the business hub.

What does the currency rule say?

Ninety days, three takeoffs, three landings, and no exceptions for skill.

Section 61.57(a)(1) of Title 14 provides that, except as otherwise stated, no person may act as pilot in command of an aircraft carrying persons unless that person has made at least three takeoffs and three landings within the preceding ninety days.

It adds conditions: the person must have acted as sole manipulator of the flight controls, and the takeoffs and landings must have been performed in an aircraft of the same category, class and type where a rating is required, with a full-stop requirement in a tailwheel airplane.

Nothing in the provision refers to experience, hours flown, or demonstrated ability. The clock alone decides.

Paragraph (b) applies a separate ninety-day currency requirement for night operations, with the takeoffs and landings made to a full stop in the defined night period.

Part 61 is carried on the eCFR.

Why elapsed time is a poor basis for writing anybody off is covered in the client database piece.

Go Outside Expedition Company, TX

What is the route back?

A flight with nobody aboard, which is the whole insight.

Section 61.57(a)(2) provides that for the purpose of meeting the general experience requirement, a person may act as pilot in command under day visual or day instrument flight rules provided no persons or property are carried on board other than those necessary for the conduct of the flight.

Paragraph (a)(3) allows the takeoffs and landings to be accomplished in an approved full flight simulator or flight training device used in an approved course at a certificated training centre.

So the regime pairs a hard expiry with a deliberately undemanding route back: you regain currency by doing the thing alone, at low stakes, rather than by proving anything to anybody.

Which is the exact opposite of how most operations treat a lapsed client, where the first contact after three years is the full seasonal pitch.

The lesson is that the way back should ask for less than the thing that lapsed, not more.

What the ordinary announcement asks for is covered in the winter email piece.

Lady Guide, FL

Why not just delete them?

Because time alone is not evidence of anything.

The tax regulation on worthless debts makes the point in a different domain: in deciding whether a debt is worthless, all pertinent evidence is considered, including the value of any collateral and the financial condition of the debtor.

Elapsed time appears nowhere on that list, and the provision allowing a creditor not to sue first is expressly conditioned on the surrounding circumstances indicating that the debt is worthless and uncollectible.

Which is a useful discipline transplanted into a client list: a person who has not booked for three seasons may have moved, changed jobs, had a child, or simply not been asked.

Writing them off on the calendar alone is the same error the regulation refuses to permit, and it is the more expensive one because a lapsed client is cheaper to reactivate than a stranger is to acquire.

The regulation is at the eCFR.

How the list should be segmented instead is covered in the client database piece.

What should the first message be?

A question, not an offer.

The instinct is to lead with a reason to come back, and the effect is to make a three-year silence feel like a sales opportunity.

Script: It has been a while since we fished. No pitch, I am just tidying my list and wanted to ask whether you are still chasing them and whether I should keep you on it.

That message asks for almost nothing, which is what makes it answerable, and it gives the recipient a graceful way to say no.

It also produces three genuinely useful outcomes rather than one: a booking, an explicit yes to staying in contact, or a removal that improves everything you send afterwards.

What it must not contain is a rate, a date, or an offer, because any of those converts a question into a pitch.

Why the plain ask outperforms is covered in the text scripts piece.

What should the second message be?

There should not be one, unless they answered.

A lapsed client who ignored an honest, low-stakes question has answered it, and a follow-up converts a tidy exit into an irritation.

Which is the discipline most operations lack, because a non-response feels like an unfinished conversation rather than a reply.

Where somebody does answer yes to staying on the list, they return to the ordinary sequence and get the announcement like everybody else.

Where somebody answers with a reason, that reason belongs in the record, because it is the only market research you will ever get for free.

And where somebody books, the win-back worked and the sequence ends.

How the ordinary sequence runs is covered in the rebooking pack piece.

When should it be sent?

Off-season, and away from the announcement.

A win-back arriving in the same week as your season announcement reads as part of the campaign, which is exactly what it is trying not to be.

Which puts it either well before the announcement, in late autumn, or well after it, in early spring once the general push has finished.

Late autumn is better, because it gives somebody who says yes time to appear in the announcement group and be treated normally.

Sending it in the middle of the season is worst of all, since a message about not having seen somebody for years lands oddly while you are visibly busy.

One send, one month, once a year.

What the autumn work should otherwise contain is covered in the fall wrap-up piece.

What defines lapsed?

Pick a number and apply it, because the alternative is memory.

The aviation rule uses ninety days for a reason that has nothing to do with fishing: it is short enough to matter and long enough to be fair.

For a seasonal business the equivalent is two full seasons without a booking, which allows for one missed year without treating somebody as gone.

Three is defensible and generous; one is too quick, because a client who skipped a summer for a wedding is not lapsed.

What matters far more than the number is that it is a number rather than an impression, since a list managed by memory will always keep the memorable and lose the quiet.

And the quiet ones are frequently the ones who would have come back if asked.

How the last-trip date drives it is covered in the spreadsheet CRM piece.

Why does the low-stakes route work?

Because it removes the reason not to answer.

A pilot regaining currency does not have to demonstrate anything to anybody; they take an aircraft up alone and land it three times.

Which is a deliberate design choice, because a demanding route back would leave people non-current for longer rather than getting them current sooner.

The same logic governs a lapsed client. A message asking whether they want to stay on a list can be answered in three words; a message asking them to book a day requires a decision, a diary and a partner conversation.

So the easy question gets answered and the hard one gets ignored, and the easy one is the one that surfaces who is still interested.

The booking comes afterwards, from the ordinary sequence, to somebody who has just told you they are still fishing.

What that ordinary sequence contains is covered in the winter email piece.

Does the medium matter?

Yes, and a text outperforms an email here specifically.

A win-back is one short question with a one-word answer, which is the shape a text handles and an email dilutes.

An email invites you to explain yourself, add a picture and mention the season, all of which convert the question back into a campaign.

It also arrives among everything else, whereas a text from a name somebody half-remembers gets read.

Where you have no mobile number, the email version should be three sentences and nothing else, with no signature block, no images and no links.

Plainness is the entire mechanism, and any decoration reintroduces the thing being avoided.

Why the plain ask converts is covered in the text scripts piece.

Should anything be offered?

Not in the first message, and rarely at all.

A discount attached to a win-back tells the client the relationship was worth a percentage, and it sets the rate for everything that follows.

Which is a bad trade for a booking you might have got by asking, and a worse one for a client who returns for years at a reduced number.

Where you genuinely want to make the return easy, offer a date rather than a price: a specific week held for them, or a midweek day that suits.

That costs nothing, reads as personal rather than promotional, and does not touch the rate card.

The exception is somebody whose last day went badly, where a specific gesture is owed rather than offered.

Why non-price benefits work better is covered in the discount scripts piece.

What about somebody who had a bad day?

Name it, once, without defending it.

A client who lapsed after a poor trip is a different case from one who simply drifted, and treating both identically wastes the only chance you have.

Script: The last day we had was not what I wanted for you, and I have thought about it since. If you would give me another go I would put you on the best water I have and there would be nothing to pay if it went the same way.

The offer of nothing to pay is a real commitment and should only be made if you mean it, which is why it is reserved for this case.

What the message must not do is explain the conditions or relitigate the day, because the client remembers it differently and arguing loses them permanently.

Acknowledging without defending is the whole technique.

How the day itself should have been handled is covered in the no-fish day piece.

What should be recorded?

The answer, in the same four states as any other ask.

A yes to staying on the list, a booking, a no, and a silence are four different outcomes and they drive four different treatments next year.

Which means the win-back needs a field in the client record, filled the day the answer arrives rather than reconstructed later.

A no in particular must be recorded and honoured across every list you keep, since a second message after an explicit no is the one thing that turns a lapsed client into a hostile one.

Silence should be recorded too, because somebody who ignored two annual win-backs is a different case from somebody who has had one.

Two silences is where a genuine removal becomes defensible, which is the evidence the tax regulation would have wanted.

Where that field should live is covered in the spreadsheet CRM piece.

What does a good answer look like?

Anything at all, including a no.

The purpose of the message is to convert a list of unknowns into a list of knowns, and every reply does that regardless of content.

A no is genuinely valuable, because it removes somebody who was costing you delivery reputation and skewing every open rate you look at.

A yes to staying on the list, with no booking, is the most common good outcome and it puts somebody back into the ordinary sequence where they belong.

A reason, whether an injury, a move or a change of interest, is the one piece of market information nobody in this trade ever collects.

And a booking is a bonus rather than the objective, which is why the message converts better than one written to produce bookings.

What the list should look like afterwards is covered in the spreadsheet CRM piece.

Where do win-backs go wrong?

Five ways, and the first is the pitch.

Leading with an offer, which converts an honest question into a campaign and gets ignored accordingly.

Sending it alongside the season announcement, so it reads as part of the same push.

Following up on a silence, which turns a graceful non-answer into an intrusion.

Attaching a discount, which buys one booking and sets the rate for every one after it.

And deleting people on elapsed time alone, which is the error the worthless-debt regulation declines to permit and which throws away the cheapest bookings available to you.

What the annual habit should look like is covered in the tradition piece.

How the ordinary winter email differs is covered in the winter email piece.

How big should the lapsed list be?

Bigger than most guides think, and shrinking is the point.

An operation in its sixth season has typically fished with several hundred people and hears from a fraction of them, which means the lapsed group is usually the largest segment on the list.

Which makes it the biggest single opportunity and the biggest single source of the delivery problems that quietly reduce everything else you send.

Running the win-back annually converts a growing pile of unknowns into a maintained list, and the pile stops growing.

After two or three annual rounds the lapsed group settles at a small, honest size, and every message you send performs better as a result.

The first round is the hard one because it covers years of accumulation; the ones after are twenty minutes.

Why a smaller list outperforms is covered in the season announcement piece.

What is the working sequence?

One honest question, once a year, answer honoured.

Define lapsed as two full seasons without a booking, and apply the definition from the last-trip date rather than from memory.

Send one message in late autumn, away from the announcement, asking whether they are still fishing and whether you should keep them on the list.

Offer nothing, unless the last day went badly, in which case acknowledge it plainly and make a real commitment.

Record the answer as one of four states and honour a no everywhere, immediately.

Do not follow up on silence, and treat two consecutive silences as the evidence that finally justifies removal.

The aviation currency provisions rest on authority described at 49 U.S.C. 44703, published in parallel on govinfo.

How the reactivated client should then be treated is covered in the priority booking piece.