Systems we build

Every enquiry answered in under a minute.

Your business has five or six front doors. The phone, the website form, WhatsApp, email, the ads inbox, somebody's direct line. Each one has a different wait, a different owner and a different chance of being dropped on the floor, and no one place knows about all of them. This is one pipeline behind the lot. A call nobody reaches becomes a text in thirty seconds, and after hours a voice agent answers and books against the real calendar. A form, a message or an email is read, scored and answered on the same clock. All of it lands as one record with one owner, one next step and a timer running, and anything that goes quiet gets chased without a single person remembering to.

CallFormWhatsAppEmailOne placeanswered in 60 secondsBookedin your diaryFollowed upuntil they reply

The problem

The phone rings while somebody is under a sink, up a ladder or with a patient. Nobody picks up. The caller does not leave a message, because nobody under fifty leaves messages, and by the afternoon they have booked whoever answered next. Meanwhile a form comes in at nine at night and is read at eleven the following morning. A WhatsApp goes to the phone of somebody who is in Portugal. An email lands in a shared inbox where three people each quietly assume one of the other two has it.

None of that is a phone problem or a form problem. Your business has six front doors and no hallway. Every channel has its own wait, its own owner and its own way of failing, and nothing anywhere can answer the only question that matters: how many people tried to give us money this month, and how many of them did we get back to in time?

The real damage is that none of it is visible. There is no voicemail to return. No missed-call list anybody reviews. No line in any report. The job was lost in eleven seconds and nothing, anywhere, recorded that it ever existed. Which is why every owner underestimates this, and why the first week of the build tends to produce a number that ruins somebody's afternoon.

You can buy pieces of this, and they are cheap. Missed-call text-back is thirty euros a month. A form-to-Slack notification is free. A chat widget comes with the website. Buy all three and you have six tools, six inboxes, a monthly bill and exactly the same hallway problem you started with. The hallway is the thing being built here: one pipeline, one record per person, one clock, one owner, one place that knows the whole story.

The enquiry you never knew about is the one that costs most. You cannot chase it, count it, or learn anything from it.

How it works

Seven things happen. Only the first one is about the phone, and the last one is the reason the rest keep working.

  1. Every channel arrives at the same placeCalls, the website form, WhatsApp, the shared inbox, the ads lead forms and the chat widget all terminate in one pipeline rather than six. Your number is ported to a programmable one, or forwarded to it, so calls ring the handsets exactly as they do now and the system only acts on the ones that fall through. Nothing about how the team answers the phone changes, which is what makes this installable in a working business rather than a project the staff have to be trained through.
  2. A missed call becomes a text in thirty secondsNot an apology. A question: what they need, and whether they want a slot. Thirty seconds rather than instantly, because a text that lands while the phone is still warm reads as automated, and because it gives the colleague reaching for the handset time to get there. If somebody picks up on the twelfth ring the message is cancelled before it sends.
  3. Out of hours, a voice agent answers insteadIt is bounded: it works from what you actually do, the areas you cover, the jobs you decline and your price ranges. Asked anything outside those bounds it says it does not know and takes a message, which is the single most important line in the configuration. An agent that improvises a quote at eleven at night has cost more than the call was worth. Inside the bounds it qualifies the job and books the slot.
  4. Everything else is read on the same clockA form, a WhatsApp or an email is scored for intent, urgency and fit against the work you actually want, enriched from public company data where there is a company to enrich, and answered or routed. The same clock means the same promise: an enquiry at two in the morning is dealt with at two in the morning, and a bad-fit enquiry is answered honestly and quickly rather than sitting in a pipeline for a fortnight.
  5. The calendar is held, then confirmedA slot goes on hold the moment somebody picks it and is only confirmed when the conversation completes, with the hold expiring by itself if the call drops. Without it, the voice agent and the web form will eventually sell the same Tuesday morning twice and somebody drives to a job that is not there.
  6. One record, one owner, one next stepContact, transcript, recording, channel, what was agreed and the slot, deduplicated across channels so the person who rings, then texts, then fills in the form is one lead rather than three. Every record lands with a named owner and a task, not in a shared inbox. This is the step that separates the system from the tools: a recovered enquiry nobody follows up is one you lost politely.
  7. Silence is treated as an eventA lead that goes quiet is chased on a cadence, a quote that is not answered is followed up, and an owner who has not touched a record inside the agreed window gets a nudge before the customer does. Nothing here depends on anybody remembering. The weekly number (enquiries in, answered inside a minute, booked, lost, by channel) arrives in a channel on Monday whether anyone asked for it or not.

What it's built from

Six pieces, and any of them swaps for its nearest rival if you already pay for one. The shape of the system is the deliverable; the logos are an implementation detail.

  • Twilio, the number, the calls and the messagesProgrammable voice and SMS under your existing number. It is what turns a missed call into an event something can listen for, and it carries the compliance floor: opt-outs honoured at the point of request, quiet hours respected, delivery receipts recorded.
  • ElevenLabs, the voiceThe agent that answers out of hours, with low enough latency that callers do not talk over it. Multilingual, which matters more in the Nordics than almost anywhere: the same agent takes the call in Swedish or English without being asked which it should be.
  • n8n, the part that decidesThe orchestrator, self-hosted on European infrastructure, and the actual product. Every branch, retry, hold, score and escalation lives here as something you can open and read, which is the difference between a system you own and six subscriptions you rent. When a rule changes, one person changes it in one place.
  • Claude, for intent, drafting and the summaryReads each inbound message for what the person actually wants, scores it against the work you want, drafts the reply in your wording rather than a template's, and writes the two-line summary on the record so whoever picks it up at nine does not have to read a transcript.
  • HubSpot, where it landsOr Pipedrive, or whatever you already run. One record per person, deduplicated across every channel, transcript and recording attached, owner and task against it. If there is no CRM, putting the simplest thing that works in place is part of the build.
  • Slack, the handoff to a personAnything the system will not decide arrives in a channel with the context already attached, and genuinely urgent calls page whoever is on duty by SMS rather than waiting to be noticed. A handoff that needs somebody to go and look is not a handoff.

What it's worth

Do this sum with your own numbers rather than ours. It takes a minute, and it is the only version of it worth believing.

  • You take 200 calls a month and the published average holds, so 62% reach nobody.124 people a month tried to reach you and did not. You currently have no list of them.
  • A text inside the first minute recovers the low end of the published range, 25%.31 conversations a month that would not have happened. At a €400 average job and a one-in-three close, that is around €4,100 a month.
  • Four people each spend 45 minutes a day retyping enquiries between inbox, CRM and calendar.3 hours a day, about 90 hours a month, roughly 11 working days of somebody's time returned every month.
  • One in twenty booked jobs is currently lost to a double-booking or a dropped handoff.On 60 jobs a month that is 3 jobs, plus the callout, plus the review you do not get.

These are illustrations using published averages and round figures, not results we are reporting. Your call volume, job value and close rate will move all four lines, which is why the first week of the build is spent measuring them instead of assuming them.

The research behind those assumptions

Published industry figures rather than ours. They describe the size of the problem, which is the number worth knowing before spending anything.

Speed is not a nice touch here. Inside the first minute it is most of the entire effect.

What it costs

This is sold as one system at the automation price on the services deck, and what moves it is how many things it has to hold together rather than how many hours it takes. The bottom of the range is one number, one calendar, one CRM, two or three channels and one language. It climbs when the calendar is really a whiteboard, when the CRM does not exist yet, when three trading names share a phone line, or when the agent has to work in two languages and know which without being told.

The running cost is not a seat licence. Voice is billed by the minute and messaging by the message, so it scales with how many enquiries you are currently dropping. That is the right shape: it gets cheaper as the business gets better. On the volumes above it costs a small fraction of one recovered job a month, and we work the real number out with you before anything is built rather than presenting it afterwards.

Deliberately outside the build price is the part most of this market bills hardest for: somebody watching it. That is the care retainer. It is the reason this is still running in a year, not the reason the invoice is bigger.

What goes wrong, and what happens then

Every one of these is in the build because it happens, not because it came up once.

  • Somebody answers on the twelfth ringThe text is cancelled before it sends. A caller who has just spoken to a human and then gets 'sorry we missed you' has learned that nothing here is paying attention.
  • The same person rings, then texts, then fills in the formDeduplicated across channels on number and email inside a rolling window, so that is one lead with three touches rather than three leads competing for the same slot, and one owner rather than three people ringing them back.
  • A reply arrives two days late, against a dead threadConversation state is held per contact with a timeout, so a late reply opens a new thread rather than continuing a stale one. Replies that make no sense against the thread go to a person instead of being guessed at.
  • The voice agent is asked something it does not knowIt says so, takes a message and ends politely. It is bounded to your services, areas and prices and instructed not to improvise past them.
  • Two channels book the same slotThe hold-then-confirm step covers it. Without it, this is the failure that eventually happens to everybody who wires a booking form and a phone agent to the same calendar.
  • A carrier delays a message, or an API rate-limitsRetries with backoff, and a delivery failure raises an alert rather than disappearing. The pipeline is monitored, so a step that stops firing is something you hear about that night rather than notice in next month's numbers.
  • Somebody texts STOPHonoured immediately, recorded against the contact, and nothing in the system messages them again. Not a setting, and not optional.
  • An owner sits on a lead for three daysThe record's timer fires and escalates before the customer gives up. The system's job is not only to catch the enquiry. It is to notice when the humans drop it.

Still wondering

The questions this one raises.

  • It is an automation that texts the caller when a call to your business goes unanswered, usually within thirty seconds, so the conversation continues instead of ending at voicemail. On its own it is one message. Here it is one node in a pipeline that also reads the reply, answers or books it, writes it to the CRM with an owner, and chases it if it goes quiet.

  • Yes, and if that is genuinely all you need then buy it. We would rather say so than sell you something. What those tools do not do is answer the reply, know your calendar, take a call at ten at night, hold a booking, deduplicate the same person across three channels, write to your CRM, escalate an emergency to a person, chase a lead that goes cold, or tell anybody when they have stopped working. Six tools that each do one of those is six subscriptions and six inboxes, which is the problem this replaces rather than an example of it.

  • Thirty seconds for a missed call, and the same minute for a form, message or email. Published research puts callback rates above 90% when the reply lands inside the first minute, so speed is most of the effect. Firing instantly reads as robotic though, and it races the colleague who is about to pick up.

  • It annoys them if it pretends to be a person or will not let them reach one, so it does neither: it says what it is, it is bounded to what you actually do, and anything it cannot answer becomes a message and a callback rather than a loop. The comparison that matters is not the agent against your receptionist. It is the agent against the voicemail that call currently reaches at nine at night.

  • It takes a message and hands over to a person with the transcript and a two-line summary attached, so whoever picks it up already knows what was said. Genuinely urgent enquiries skip that queue entirely and page whoever is on duty by SMS.

  • The orchestration is self-hosted on European infrastructure and the call and message data stays in the EU. Recordings and transcripts are kept on a retention window you set, callers are told the call is recorded, and opt-outs are honoured at the point of request rather than at the next sync. If your sector needs the models on your own hardware as well, that is the private-agent route rather than this one.

  • Four to five weeks from the first conversation to the whole pipeline running, with the missed-call half usually live inside the first week so the measurement starts immediately. The long pole is almost never the technology. It is agreeing what the agent is allowed to say and who owns which kind of lead.

  • Yes, and it is a common starting point. Records have to land somewhere with an owner against them, so part of the build is putting the simplest thing that works in place, which is often the CRM you already pay for and do not use.

  • Then we keep it. Most companies arrive with two or three of the pieces already bought and nothing joining them, and the audit that starts the engagement is partly about working out which existing tools stay. Replacing working software is expensive and unpopular; the value is in the hallway, not in the doors.

  • Ask an AI about us

Keep looking

Discover more automations

Find out what you are missing.

Tell us how you take enquiries now. We will come back with the number you are currently losing.

We use this to reply to you and nothing else. No list, no marketing, deleted after two years if it goes nowhere. See the privacy policy.