Database reactivation: your old customers are the cheapest leads
You paid to win your past customers once. They know your work, and you have their number. A short, plain text asks them back.
→
Insights
Real process teardowns, notes from client builds, and plain explanations of the systems behind them.
You paid to win your past customers once. They know your work, and you have their number. A short, plain text asks them back.
→
Google can charge you for a call you missed, and missed calls can count against your ranking. Get every call picked up, and answer messages fast.
→
Say what you'll do, what it costs, and what it leaves out. Add the date the price holds until and one way to say yes. Then send it the day you see the job.
→
A no-show policy only works if the customer reads it before the appointment. Keep it short enough for a text, and put it in the booking confirmation and the reminder.
→
A quiet lead is often still deciding. Send a few messages, spaced out, on the channel they used, and stop when they answer.
→
Retyping a quote into an invoice is where small things go missing: a fee, the right price, the extra job. Make the invoice from the quote, and the bill matches what they agreed to.
→
A late payment often isn't a refusal. The invoice got missed, or nobody knows it was paid. Email it, text that it's there, remind on set days, and stop the moment it's paid.
→
Business texting works when the customer is already waiting for news. Six short texts cover most jobs, from the first reply to the review ask.
→
Voicemail records a call. It doesn't win the job. An after-hours answering service that books the caller in means you wake up to jobs in your calendar, not callbacks.
→
A virtual receptionist is a person. An AI receptionist is software. Most small businesses don't have to choose. Let the AI answer every call, and send the hard ones to a person.
→
The Google listing that brings your calls is often owned by someone outside the business. You find out the day you need to change it. Five minutes now settles it.
→
In the US, a business text from an unregistered number is blocked before it reaches the phone. Registration fixes it. It asks who you are and what you send.
→
The next caller reads a bad review before they ring you. Answer it the same day, short and in public. Only a review that breaks Google's rules comes down.
→
Good work earns a review, but it rarely collects one. Ask every customer, on the day, with the link in the message. Then ask once more.
→
Ask once, with the whole list and a date. Remind on a fixed schedule, in the one channel the client answers. Call on a set day. Then stop relying on anyone's memory.
→
A missed call text back stops the caller ringing the next name. One saved job a month pays for it many times. It stops working when nobody answers the reply.
→
A WhatsApp AI chatbot that only answers questions leaves the job where it found it. For a service business, the chat has to end in a booked slot, a record and a named person.
→
A new client's agency sent their Facebook leads once a week, on Friday. By then, a Monday inquiry was four days cold. The fix is a lead that never waits for a spreadsheet.
→
When chats live on personal phones, every sick day, leave and department handover drops part of the story. Put the conversation, quote and invoice in one place, and nobody has to remember.
→
The revenue is already sitting in quotes you sent. One client reported close to 30% more revenue after the chasing ran on a schedule instead of on memory.
→
The three kinds
01
A real process pulled apart, with the fix. Names changed, numbers kept.
02
Something learned on a build. Short, specific, published the same week.
03
What a mechanism actually is, written for the person who signs it off.
Rather talk than read
Tell us what is breaking and we will tell you what it would take to stop it.