Marketing automation for a ten-person firm: the three workflows to build first

A ten-person firm should automate three things first: a reply to every new enquiry, a follow-up to every missed call, and a reminder to repeat buyers when they are due to reorder. These three plug common leaks, and each is simple enough to run from a shared sheet and a messaging tool.

Why these three and not a bigger list?

At ten people, nobody has the job of "marketing operations". The owner, a sales person and a coordinator share it with everything else, so the first automations should remove a daily worry and be cheap to fix when they break.

Each of the three guards a different door: the front (new enquiries), the side (calls that nobody picked up) and the back (customers who bought before). A firm that sends a clear reply to new enquiries and returns missed calls, and nudges old customers, has a working loop. Scoring, multi-step campaigns and chatbots depend on that loop being in place.

For routing and clocks, see how to automate lead assignment and follow-up.

Workflow 1: the enquiry acknowledgement

Trigger: a new enquiry arrives by form, WhatsApp or email. Action: a message goes back straight away, saying who has the enquiry and what happens next. Owner: the person named in the message. Stops when: a person replies by hand.

"Thank you for contacting us" is the message everyone ignores. Try: "Hello [Name], I am [your name] at [Firm]. I have your enquiry for [product]. I will call you [a time your team can keep], or tell me a better time." It names a person, a product and a window.

Do not promise a window you cannot keep. If your team is out on site until evening, say "this evening".

Workflow 2: the missed-call follow-up

Trigger: a call to the business number goes unanswered, or a caller hangs up before anyone answers. Action: a text or WhatsApp goes to the caller: "Sorry we missed your call. How can we help? Reply here or tell us when to call back." A task also lands on the coordinator's list. Owner: the coordinator. Stops when: a person calls back and logs it.

Firms can lose enquiries here without knowing, because there is no record of a call that never connected. A phone system or cloud telephony service that logs missed calls is the first thing to check. If you cannot get the numbers, ask your phone provider what reports they offer, and do not guess.

Workflow 3: the repeat-order reminder

Trigger: a set number of days after delivery, based on how long your product lasts or how often the buyer reorders. Action: a message to the buyer: "Your last order of [product] was on [date]. Shall we book the next one?" A task goes to the account owner. Owner: whoever looks after that customer. Stops when: the buyer orders, says no or asks to be left alone.

This one needs the most honest thinking. Set the delay from what you know. A packaging supplier knows its buyer's stock cycle; a water-can supplier knows weekly use. If you cannot say, ask five customers how long a delivery lasts, and use the middle answer.

The spec sheet for all three

If nobody can explain a workflow in two sentences, it is too complicated for ten people.

For example: a CCTV and access-control installer in Kozhikode

This case is invented. An installer in Kozhikode has ten staff, mostly technicians. Enquiries come from Google, a few dealers and the phone. The owner does the first replies, usually from site, usually late.

The firm had built too much too early. A freelancer set up a chatbot with a six-step menu on WhatsApp. Customers got stuck on step three, and the owner never saw the stuck ones.

The firm removed the chatbot and built the three simple workflows. Enquiries go to a shared sheet, and the sender gets a named reply from the coordinator, Anitha, with a call window. Missed calls trigger a "sorry we missed you" message and a task for Anitha. The annual-maintenance customers, whose service visits fall due at set times, get a reminder two weeks ahead that asks them to reply with a visit date. Each piece plugs a leak the owner could point to, though the missed-call log turns out to be patchy, because the old phone line cannot record calls that drop before ringing. The owner has to ask the phone provider about a better line.

How do you test a workflow before you trust it?

Before a workflow touches a real customer, put yourself through it. Submit a test enquiry from your own phone, call the business number and hang up, and add a dummy customer with an old delivery date. Then check that the message arrived with the right name and product, the task landed with the named person, and the log shows what happened. Test again after any change to the form, the phone system or the sheet.

What should stay by hand?

Anything involving money, a complaint, or a decision. If the buyer is asking for a lower rate, a person must answer. If a customer is angry, a person must call. Automation should reduce the number of times a person has to remember something, not the number of times a person talks to a buyer.

Stay by hand, too, while you do not know where your enquiries come from. Fix the record first. If you get only a few enquiries a week, replying by hand may serve you as well as any workflow. Late-night replies are a neighbouring problem, discussed in WhatsApp enquiries at night and no reply until morning.

Build one this week

Pick the door where you lose the most. If it is the front, write the acknowledgement message and send it by hand for a week before you automate it. If it is the side, switch on missed-call logging. If it is the back, list your twenty best customers with their last order date. When the manual version works, the tool simply takes it over, and marketing automation is the service that builds it. The marketing hub shows where it sits. To talk through which door leaks most in your firm, tell us what you need.