Emergency work and planned work are two businesses sharing one phone

A plumber's phone carries two completely different businesses. One is somebody standing in three inches of water who will pay almost anything for somebody to come now. The other is a bathroom that needs doing in March, where the customer is comparing three quotes and taking a fortnight to decide.

Run as one business they undermine each other constantly. The emergency wrecks the planned work's schedule; the planned work makes you unavailable for the emergency; and the pricing that works for one is wrong for the other. Separating them, deliberately, is usually the single most valuable structural change a trade business can make.

What we'll cover

• Two businesses, one number
• The demand shapes are opposites
• Pricing that works for one breaks the other
• The customer is different too
• Building it with CodeWords
• Deciding your split before the phone rings
• Protecting planned work from the emergency
• Seasonal surges, which are predictable
• Saying no to the wrong kind of urgent
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Two businesses, one number

Set them side by side and almost nothing matches.

Emergency work is unplannable, short, high-value per hour, and wins on availability. The customer is not comparing quotes. They want somebody who answers.

Planned work is schedulable, longer, lower per hour but larger per job, and wins on trust and price. The customer is comparing, often for weeks.

The same van, the same skills and the same person, running two operations with opposite requirements. A business that has never separated them tends to be mediocre at both: too slow for the emergencies it loses, too disrupted to run the planned work smoothly.

The demand shapes are opposites

Emergency demand is spiky and largely weather-driven. The first cold snap, a heavy rain, a hot week. It arrives in bursts, concentrated in hours, and no amount of diary management smooths it.

Planned demand is steady, seasonal in a slow way, and can be shifted. A customer wanting a new consumer unit does not mind whether it is the 12th or the 19th.

That difference is the whole opportunity. Planned work is the thing you can move, which means it is the buffer that absorbs the spikes. A business that books planned work solidly six days a week has no buffer and every emergency becomes a broken promise.

Leaving genuine slack looks like lost revenue on a quiet week and is what makes the busy week profitable.

Pricing that works for one breaks the other

The mistake that costs the most: one rate for everything.

Emergency work carries costs planned work does not. Attendance at short notice, evenings and weekends, parts bought at retail because the factor is shut, a disrupted schedule and the goodwill spent on whoever got bumped. Priced at the standard hourly rate, it is loss-making at the exact moment the business is under most strain.

Planned work priced at emergency rates simply does not win, because the customer is comparing.

So they need separate prices, published in advance, stated plainly. Call-out and out-of-hours rates said before anybody calls, not discovered at the door at eleven at night. Customers accept an emergency premium readily when it is a known rate; they object strongly to one that looks invented on arrival.

The customer is different too

The emergency customer is stressed, not price sensitive at that moment, and deciding in minutes. They will remember how it felt more than what it cost. They are also the least likely to become a repeat customer unless you convert them deliberately, which is why the follow-up a week later matters.

The planned customer is comparing, wants detail, and is deciding over days. They want to know what is included, what it will be like having you in the house, and whether you will turn up when you said. Speed helps only in getting a considered quote out promptly.

One follow-up habit is worth more than any automation here: contacting an emergency customer a week later, when the panic has gone, to mention the thing that caused it. A large share of planned work in the trades starts as somebody's bad night.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: how an enquiry is sorted into urgent or planned, what each is told about rates and availability, and what reaches you immediately.
3. Authorize the connections to your calendar, wherever jobs and quotes are recorded, and your WhatsApp Business Platform account.
4. Describe the exceptions: anything unsafe, an existing customer, a landlord or agent, work you do not take, an area you do not cover.
5. Run it for a month and record what proportion of your hours went to each type, because most people are surprised by the answer.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Deciding your split before the phone rings

The decision to make when nothing is on fire: what proportion of your capacity is for each, and what you will and will not displace.

Four questions, answered once and written down.

What counts as an emergency for you? Water entering the property, no heating with somebody vulnerable, anything unsafe. Not a dripping tap, however annoyed the caller is.

How many planned jobs will you displace for one emergency? Having a number stops the decision being made by whoever is loudest.

What are the hours? If you do not do two in the morning, say so publicly rather than letting the phone decide.

What does it cost? Published, in advance.

Without those answers the split is made in the moment, under pressure, badly.

Protecting planned work from the emergency

Displacing somebody is sometimes right. Doing it carelessly costs you the customer who was displaced, which is the customer you had already won.

Three rules keep it survivable. Tell them immediately rather than when you get round to it. Offer something specific, a named alternative time rather than an apology. And track how often each customer gets bumped, because a customer moved three times is a customer already looking elsewhere and nobody notices until they have gone.

Where a job has a genuine deadline, a kitchen fitting, a tenant moving in, a sale completing, mark it as non-displaceable and mean it.

Seasonal surges, which are predictable

The first cold snap generates a week's worth of heating work in two days, every year, and every year it is treated as a surprise.

It is not unpredictable in kind, only in date. Which means the preparation is possible: stock the parts that fail in cold weather, clear discretionary work from the weeks it usually lands, decide in advance what you will and will not take during a surge, and have the honest message ready.

That last one is undervalued. A customer told on day one "we are at capacity until Thursday, here is the number of somebody who may be free" respects you. The same customer left in silence for two days does not, and they were going to end up elsewhere either way.

Saying no to the wrong kind of urgent

Not everything described as an emergency is one, and treating them all as such is how a business ends up working nights for standard rates.

Some are genuinely urgent and get the emergency treatment. Some are urgent to the customer but can wait until morning, and saying so clearly is a service: "that is safe to leave overnight if you turn the stopcock off, I can be there at eight" is a better answer than an expensive midnight visit.

Some are simply impatience. And some are urgent but not yours: out of area, wrong trade, an insurance job needing a different process. A fast, honest redirect costs nothing and is remembered.

The one category that never gets judged this way is anything potentially unsafe, which always escalates to a person regardless of what it might turn out to be.

Making it survive

Publish both rate structures and state them before anybody calls.

Keep genuine slack in the planned diary, since it is the only buffer you have.

Track displacements per customer, not just per week.

Follow up emergency customers a week later, once.

Review the split quarterly, because it drifts without anybody deciding to change it.

Limits worth knowing about

You cannot be in two places at once, and no automation changes that.

Emergency demand is weather-driven, so a quiet month is not a marketing failure.

Published rates lose some price-sensitive customers, which is the point.

A full planned diary has no buffer, and the revenue from filling it is often less than the disruption costs.

Anything potentially unsafe is not a commercial decision and escalates regardless.

What to build first

The sorting question, at the top of every enquiry, that separates urgent from planned. Everything downstream depends on it: what they are told about availability, what they are told about rates, and whether it reaches you in two minutes or two hours.

Two habits make the difference. Publish the emergency rate before anybody calls, because a premium people knew about is accepted and one discovered on a doorstep at midnight is a complaint. And protect slack in the planned diary, since the week you book solid is the week the weather turns and you break four promises to customers you already had.

Frequently asked questions

Why separate emergency and planned work?

They have opposite demand shapes, different pricing, different customers and different success conditions. Run as one business, each undermines the other.

How should emergency work be priced?

Separately and publicly. It carries costs planned work does not, including short-notice attendance, out-of-hours time, retail-price parts and a disrupted schedule. Customers accept a known premium and object to an invented one.

What counts as an emergency?

Decide and write it down before the phone rings: water entering the property, no heating with somebody vulnerable, anything unsafe. A dripping tap is not one however annoyed the caller sounds.

How much planned work should I displace for an emergency?

Set a number in advance. Without one the decision goes to whoever is loudest, and the customers you already won are the ones who pay for it.

How do I stop losing displaced customers?

Tell them immediately, offer a specific alternative time rather than an apology, and track how often each customer gets moved. Three bumps and they are already looking elsewhere.

Why keep slack in the diary?

Planned work is the only buffer against emergency spikes. A diary booked solid six days a week turns every emergency into a broken promise.

How should seasonal surges be handled?

They are predictable in kind if not in date. Stock the parts that fail in cold weather, clear discretionary work from the usual weeks, decide in advance what you will take, and have the honest capacity message ready.

What do I say when I am at capacity?

That you are, with a date, and ideally the name of somebody who may be free. Customers respect it; two days of silence loses them anyway and costs the goodwill too.

How do I turn an emergency customer into a regular?

Contact them once, about a week later, when the panic has passed, about the underlying problem. A large share of planned work in the trades starts as somebody's bad night.

What about enquiries that might be unsafe?

Those are never a commercial judgement. They escalate to a person immediately with the published safety advice, whatever they might turn out to be.

Related reading

• Missed calls, and which ones are worth having
• Messaging in a regulated trade
• Quotes, invoices and getting paid