Tag: Scale & Automate

  • Centralizing Customer Communications into One Inbox

    Centralizing Customer Communications into One Inbox

    Messages get missed because they arrive in six places and no single person is responsible for any of them.

    TL;DR One inbox, every channel, threaded by customer. Assign every conversation to a named person. Track first-response time as your main metric. Tag automatically, respond manually.

    The problem in concrete terms

    A typical service business receives enquiries through

    • The website form, going to a shared address.
    • Direct email to whoever’s address the customer had.
    • Text to the owner’s mobile.
    • Facebook or Instagram messages.
    • Google Business Profile messages.
    • WhatsApp.
    • Phone, with voicemail somewhere else again.
    • The booking platform’s own messaging.

    No single view. No ownership. No record of who replied to what. The missed enquiry is not carelessness, it is a structural inevitability.

    What a unified inbox does

    Threads every channel by customer, so the text from Tuesday and the email from Friday sit in one conversation.

    Assigns ownership, so every conversation has a name against it.

    Records the history, so anybody picking it up has context.

    Measures response time, which is the metric that actually predicts conversion.

    Threading by customer, not by channel

    This is the feature that matters and not every platform does it well.

    Test during a trial: send yourself a message from three channels using the same phone number and email. Do they appear as one conversation or three?

    Matching keys

    • Phone number, normalised. This is why phone format standardisation matters.
    • Email address.
    • Social profile ID, linked manually the first time.

    Merge duplicates when they appear. A customer who texts from a second number will create a new record, and the merge should be one click.

    Assignment and ownership

    Every conversation gets an owner. No exceptions.

    Rules that work

    • Unassigned queue is checked by a named person at set times, not “whenever someone looks”.
    • First responder owns it until they hand it over explicitly.
    • Handover is a deliberate action, with a note, not a silent reassignment.
    • Nobody goes on holiday without reassigning their open conversations.

    Avoid round-robin auto-assignment in a small team. It sounds fair and it produces conversations owned by whoever happens to be up a ladder.

    Response time as the core metric

    First-response time is the number to manage.

    Set an internal target and publish it to the team

    Channel Target during hours
    Phone Answered, or called back within 30 minutes
    SMS and chat Within 15 minutes
    Social message Within 1 hour
    Email enquiry Within 1 hour
    Email, existing customer, non-urgent Same day

    Measure the median, not the average. One conversation left over a weekend distorts an average badly and hides the typical experience.

    An automatic acknowledgement is not a response. Count the first human reply. Acknowledgements are useful and they are not the metric.

    Automated tagging

    Tag automatically. Respond manually.

    Useful tags

    • Enquiry type. New job, existing customer, complaint, supplier, spam.
    • Urgency. Detected from keywords, with a bias toward over-flagging.
    • Service type, for routing to the right person.
    • Status. Awaiting us, awaiting customer, closed.

    The awaiting-customer tag is quietly valuable. It stops conversations sitting in the queue looking unanswered when the ball is with them, and it lets you chase properly after a few days.

    Do not auto-respond with anything substantive. An acknowledgement, yes. An answer, no.

    Templates without sounding templated

    Save the openings and the facts, not the whole message.

    Good snippet

    Our standard call-out is $95, which covers the first hour on site. Parts are quoted separately before any work goes ahead.

    Then write the rest personally. Snippets for the repeated factual content, human writing around it.

    Avoid full canned replies for anything beyond acknowledgement. They are recognisable and they read as dismissive on the receiving end.

    Out of hours

    • Set expectations in an auto-reply, with the emergency route.
    • Do not promise a response time you will not meet. Under-promise here.
    • Emergency path must be genuinely monitored. An emergency number nobody answers is worse than not offering one.
    • Turn off notifications for the team outside hours, deliberately. Always-on inboxes produce burnout and worse responses.

    Choosing a platform

    Check

    • Which channels are supported natively, especially Google Business Profile messages and WhatsApp, which are commonly missing.
    • Threading by customer, tested properly.
    • Mobile app quality. Most responses will be sent from a phone.
    • Does it connect to your CRM, so conversation history appears on the customer record.
    • Number portability. Can you keep your existing business number?
    • Export. Your conversation history is a business record.

    Many all-in-one platforms include this, which is usually the right answer at small scale rather than a separate tool.

    Measure it

    • Median first-response time, by channel, weekly.
    • Conversations with no owner, which should be zero at end of day.
    • Conversations open over 48 hours.
    • Enquiry to booking conversion, segmented by response time. This is where you prove the value of the whole exercise internally.
    • Messages received per channel, which frequently reveals a channel nobody was monitoring.

    Audit where messages currently arrive, listing every channel honestly. Most businesses find at least two nobody is responsible for, and that audit alone is worth doing before you buy anything.

    Need a pro to set it up? [BOOK A CALL]

  • Streamlining Field Technician Mobile Workflows

    Streamlining Field Technician Mobile Workflows

    Paper job sheets get lost, arrive three days late and are illegible. The information you need to run the business is sitting in a van door pocket.

    TL;DR Count the taps before you buy. Offline mode must genuinely work. Invoice from site, which transforms cash flow. Roll out with one technician before all of them.

    Count the taps

    The single best evaluation test, and almost nobody does it.

    Complete a full job in the app, on a phone, and count every tap and every screen.

    • Under 15 taps for a routine job: good.
    • 15 to 25: workable, expect some resistance.
    • Over 25: it will not be used properly and your data will be incomplete.

    Do this on a phone, not a tablet, not a laptop. Most technicians use a phone regardless of what the business bought.

    Do it wearing work gloves if that is realistic for the trade. Small touch targets fail in real conditions and no demo will show you this.

    Offline is non-negotiable

    Plant rooms, basements, lofts, rural properties, lift shafts. Signal fails routinely.

    Test properly

    1. Put the phone in airplane mode.
    2. Complete an entire job, including photos.
    3. Turn connectivity back on.
    4. Verify everything synced, including full-resolution photos.

    Failure modes to watch for

    • Photos queue but never upload.
    • The app appears to work but discards data on reconnect.
    • Sync conflicts if the office edited the same job.
    • A spinner that never resolves, forcing a force-quit that loses the entry.

    If offline mode fails this test, the platform is unsuitable, whatever else it does well.

    The mobile job sheet

    Structure it in the order the work actually happens.

    1. Job details and customer history. What was done last time, visible immediately.
    2. Arrival. Tap to start, which triggers the on-the-way text and the time log.
    3. Before photos.
    4. Findings. Fixed list plus free text.
    5. Work done. Fixed list.
    6. Parts used. Selected or scanned.
    7. After photos.
    8. Recommendations, for the next visit or a follow-up quote.
    9. Customer signature.
    10. Complete, which triggers invoicing and the feedback sequence.

    Fixed lists wherever possible. Free text does not aggregate, cannot be reported on, and takes longer to enter on a phone.

    Required fields on the things that matter, and nowhere else. Over-requiring produces junk entries as people work around it.

    Photos

    The most valuable data captured on site.

    • Minimum counts enforced. Two before, two after, at least.
    • Automatic tagging to the job, with timestamp and location.
    • Sensible compression. Full resolution on mobile data is slow and expensive.
    • Annotation on device, to circle the problem.
    • Same angle before and after.

    Photos are your defence in a dispute, your marketing content, and your customer communication. Treat the requirement as non-negotiable.

    Digital signatures

    On the phone, on site, before leaving.

    What it needs to capture

    • Signature and printed name.
    • Timestamp and location.
    • What exactly is being signed for. Work completed, or authorisation for extra work.
    • Automatic copy to the customer.

    The extra-work authorisation is the one that saves money. A signed on-screen approval for additional work found on site prevents the most common invoicing dispute in the trades.

    Invoicing from site

    The highest-impact change in this whole article.

    Traditional cycle: job done, paperwork returns to office, invoice raised days later, payment terms start, payment arrives weeks after the work.

    On-site cycle: job done, invoice generated on the phone, emailed or texted immediately, payment link included, frequently paid before the van leaves the street.

    What it changes

    • Days sales outstanding falls substantially.
    • Disputes drop, because the customer is standing there while the invoice is explained.
    • Admin time collapses. No re-keying.
    • Payment on the spot becomes normal rather than awkward.

    Enable card payment on the device. Tap to pay on a phone removes the last friction point.

    Rolling it out

    One technician first. The one most likely to engage, not the one who most needs fixing.

    1. Pilot with one person for two weeks. Real jobs.
    2. Fix what they hit. There will be things.
    3. Have them train the next two. Peer training beats management training substantially.
    4. Roll out with paper running in parallel for a fortnight.
    5. Set a hard paper cut-off date and hold it.

    The parallel period must end. Indefinite dual running means nobody commits to the app.

    Expect a temporary productivity dip. Say so in advance so it does not read as failure.

    Handling resistance

    Most resistance is reasonable and specific.

    • “It takes longer.” Often true at first. Count the taps and fix the genuinely slow parts.
    • “My phone battery dies.” Real. Provide chargers, and check the app’s background behaviour.
    • “I cannot see it in sunlight.” Real. Nothing you can do about the screen, but you can reduce how much reading is required.
    • “It is surveillance.” Address directly and honestly. Say what is tracked and what is not.

    Listen to the specifics. Blanket resistance is rare. Specific complaints are usually accurate and fixable.

    Measure it

    • Time from job completion to invoice sent. Should be minutes.
    • Days sales outstanding, before and after.
    • Jobs with complete records. Photos, parts, signature. Target near 100 percent.
    • Admin hours per week in the office.
    • Taps per job, revisited after a few months as the workflow settles.

    Time yourself completing one full job in your current app, on a phone, counting taps. If it is over twenty-five, fix that before rolling anything out further.

    Need a pro to set it up? [BOOK A CALL]

  • Automating Subcontractor Management and Onboarding

    Automating Subcontractor Management and Onboarding

    Every subcontractor relationship carries a compliance obligation, and the one you forget about is the one that turns up in an insurance claim.

    TL;DR Nobody works until the document pack is complete. Track every expiry date with automatic reminders at 60, 30 and 7 days. Pay fast and consistently. Score performance on data you already collect.

    The document pack

    Define it once and never accept a partial set.

    Typically required

    • Tax documentation appropriate to your jurisdiction. In the US this means a W-9 for a US-based contractor.
    • Public liability insurance certificate, with the expiry date.
    • Employer’s liability, if they have their own staff.
    • Professional indemnity, where the work warrants it.
    • Trade licences and certifications, with expiry dates.
    • Vehicle insurance covering business use.
    • Signed subcontractor agreement.
    • Bank details for payment, verified.
    • Health and safety documentation, where required.

    Requirements vary by jurisdiction and by trade. Confirm your list with an accountant and an insurance broker rather than copying a generic one, and revisit it annually.

    No documents, no work

    This is the rule and it has to be absolute.

    How it fails in practice: a job comes in, a subcontractor is available, the paperwork “will follow”, and it never does. Then something goes wrong.

    Automate the gate

    1. Subcontractor added to the system, marked “pending”.
    2. Automatic email with the document checklist and upload links.
    3. Reminders at 3, 7 and 14 days.
    4. Each document reviewed and approved individually.
    5. Status only flips to “active” when all are approved.
    6. Dispatch cannot assign a pending subcontractor. Enforced by the system, not by memory.

    The system enforcement is the important part. A policy that relies on somebody remembering during a busy week is not a control.

    Insurance expiry tracking

    The highest-risk item and the easiest to automate.

    On approval, record the expiry date as a structured date field.

    Then automate

    Days before expiry Action
    60 Reminder to the subcontractor
    30 Second reminder, copy internal
    7 Escalation, internal alert
    0 Status flips to inactive automatically

    The automatic status change at expiry is essential. Without it, reminders get ignored and expired cover is discovered after the incident.

    Working with an uninsured subcontractor can invalidate your own cover. This is not administrative tidiness, it is the risk that ends businesses.

    Payout triggers

    Fast, consistent payment is your competitive advantage in retaining good subcontractors.

    Automate the chain

    1. Job marked complete by the subcontractor, with photos and signature.
    2. Internal quality check, if required.
    3. Payment record generated automatically from the agreed rate.
    4. Approval, one tap.
    5. Payment scheduled in the next run.
    6. Remittance sent automatically.

    Set a fixed payment day and hold it. Predictability matters more to subcontractors than speed. The best ones prioritise the people who pay when they said they would.

    Self-billing, where permitted, removes the invoice chase entirely. You generate the payment record from the completed job. Check the tax rules that apply before adopting it.

    Rates and scope

    Document per subcontractor

    • Rate structure. Day rate, hourly, per job, percentage.
    • What is included. Materials, travel, waste disposal.
    • Payment terms.
    • Cancellation and standby terms.
    • Warranty obligations on their work.

    The warranty clause is the one most often missing. If a subcontractor’s work fails in eight months, who returns and who pays? Agree it in writing at onboarding, not at the point of failure.

    Performance scorecards

    Score on data you already collect. Do not build a survey.

    Metric Source
    On-time arrival Time tracking
    Job completion rate Job records
    Callback rate Complaints and return visits
    Photo and record completeness Job records
    Customer feedback Post-job survey
    Documentation currency Compliance status

    Review quarterly. Share the scorecard with them, because most performance problems are informational rather than attitudinal.

    Act on it

    • Top performers get first refusal on work. Say so explicitly, because it drives behaviour.
    • Mid performers get the specific feedback.
    • Consistent poor performers get one clear conversation, then removal.

    Volume of work is your strongest lever. Better than rates, and it costs you nothing.

    Classification risk

    Worth stating plainly. How you treat a subcontractor affects whether authorities regard them as a contractor or an employee, and the tests vary by jurisdiction and are applied strictly in many places.

    Factors commonly considered

    • Control over how and when the work is done.
    • Whether they can send a substitute.
    • Whether they work for others.
    • Who provides tools and materials.
    • How integrated they are into your business.

    Get advice specific to your jurisdiction. Misclassification is expensive and retrospective. This article is not that advice.

    Onboarding beyond compliance

    The paperwork is the gate. The onboarding is what makes them work well.

    • Your standards, in writing. What a completed job looks like.
    • Access to your training videos, at least the customer-facing ones.
    • Introduction to the systems they will use.
    • Named contact for questions.
    • A first job with a check-in, not a cold start.

    Subcontractors represent you to the customer. The customer does not know or care about the contractual distinction.

    Measure it

    • Time from first contact to fully approved. Should be days, not weeks.
    • Percentage with current documentation. Must be 100.
    • Expired documents caught before expiry, versus after.
    • Payment on agreed date, percentage.
    • Callback rate, subcontracted versus in-house work.

    Build the insurance expiry reminders this week. It is a date field and three scheduled messages, and it addresses the single largest uninsured risk most growing service businesses carry.

    Need a pro to automate it? [BOOK A CALL]

  • AI-Driven Proposal and Bid Generators

    AI-Driven Proposal and Bid Generators

    AI is good at the words around the number. It should never be allowed near the number.

    TL;DR AI drafts the scope narrative from your site notes. Pricing comes from your own calculator, always. Inject the case study that matches their situation. Assemble the contract from approved clauses, not generated text.

    The hard boundary

    AI drafts Never AI
    Scope of work narrative The price
    Explanation of the approach Contract terms
    Why option A over option B Compliance statements
    Case study framing Warranty wording
    Covering note Any statistic or claim
    Summary of findings Timescales you have not confirmed

    Everything in the right column is a legal or commercial commitment. Generated text there is a liability, not a time saving.

    Scope narrative from site notes

    The workflow

    1. Structured intake on site. Job type, findings, measurements, condition flags, access notes, customer priority.
    2. AI drafts the narrative using your template and your previous approved proposals as the style reference.
    3. You insert the price from your own calculator.
    4. You read every line and correct it.
    5. Send.

    The time saving is real: twenty to forty minutes per proposal on the descriptive sections, which are the parts you currently rewrite from scratch and resent writing.

    Feed it your own past proposals. The output quality difference between a generic prompt and a prompt containing three of your own approved proposals is enormous.

    Prompt structure that works

    Give it constraints, not creative licence.

    Draft the scope section of a proposal using the notes below and matching the tone of the three attached examples.

    Rules:
    – No prices. Leave [PRICE] placeholders.
    – No timescales other than those in the notes.
    – No statistics, percentages or research claims of any kind.
    – No superlatives about our company.
    – British spelling.
    – Under 400 words.
    – If information is missing, write [NEED: ...] rather than assuming.

    Notes: [paste intake]

    The [NEED: ...] instruction is the most useful line in that prompt. It converts the model’s tendency to fill gaps with plausible invention into a visible flag you can act on.

    Dynamic pricing, from your own logic

    Build the calculator separately and deterministically.

    • Rate tables per job type.
    • Quantity and measurement inputs.
    • Condition multipliers.
    • Materials at current cost plus your margin.
    • Travel and access adjustments.
    • Rounding rules.

    Then merge the calculated figure into the document. The AI never sees the pricing logic and never generates a number.

    Review the rate tables quarterly. Material costs move and a calculator with last year’s numbers produces confident, precise, wrong quotes.

    Case study injection

    Match the case study to their situation, automatically.

    Build a small library, tagged by job type, property type, and problem.

    Selection rule: closest match on job type first, then property type.

    Similar job: A 1930s semi on the other side of town, same boxed-in pipework problem. Two days, no disruption to the rest of the house. Photos below, and the owner is happy to be contacted if you want a reference.

    Offering the reference contact is the strongest element and it costs nothing if you have permission on file.

    Never let AI write the case study. Fabricated project examples are a serious problem. These come from your real completed jobs, with permission, and get injected as fixed blocks.

    Contract assembly

    Modular, from approved clauses. Never generated.

    How it works

    • A library of clauses, each reviewed by a solicitor once.
    • Rules selecting which apply. Job type, value band, customer type, jurisdiction.
    • Assembly into the document.
    • No generation, no paraphrasing, no summarising of legal text.

    Version and date every clause. Know which version each customer signed.

    Review the library annually with the same solicitor. Cheaper than reviewing every contract and far safer than generating them.

    The proposal document

    Structure

    1. The outcome, in one line. What they get.
    2. What we found, from the site visit. Photographs.
    3. What we propose, the AI-drafted scope, corrected.
    4. Options, if relevant. Two or three, never five.
    5. Price, broken into components.
    6. What is not included, explicitly.
    7. Timeline and availability.
    8. Similar job, with photos.
    9. Accept button.
    10. Terms, assembled.

    Accept button at the top and the bottom. Not only after the terms.

    Guardrails to build in

    • A verification checklist before send. Price checked, no invented claims, dates correct, name correct.
    • Search for [NEED: and [PRICE] before sending. Never send a document containing a placeholder.
    • A second reader for anything above a value threshold.
    • A log of what was sent, so a dispute can be resolved from record.

    The most common failure is sending a draft. Build the placeholder check into the send step mechanically.

    Measure it

    • Time from site visit to proposal sent.
    • Proposal acceptance rate, before and after. If it drops, the generated text is reading as generic.
    • Time spent per proposal, including editing.
    • Errors caught at review. Rising means the prompt needs tightening.
    • Questions from customers about proposal content, which indicate unclear sections.

    Build the structured site intake form first. AI-assisted drafting is only as good as the notes it works from, and better notes improve your proposals whether or not you ever automate the writing.

    Need a pro to build it? [BOOK A CALL]

  • Building an Executive Dashboard for Your Service Business

    Building an Executive Dashboard for Your Service Business

    A dashboard with forty metrics is a wall of numbers nobody looks at twice. Eight numbers with thresholds is a management tool.

    TL;DR Eight metrics maximum. Every one needs a threshold that triggers action. Weekly cadence, on a phone. Build it in a spreadsheet before you buy a BI tool.

    The eight

    Metric Why it earns a slot
    Cash position and overdue invoices Survival. Always first
    Revenue this month vs target The headline
    Jobs completed Volume, and the denominator for everything else
    Average job value Pricing and upsell health
    Enquiries received and converted Front of the funnel
    Median first-response time The strongest leading indicator you have
    Diary fill, next two weeks Forward visibility
    Complaints and callbacks Quality, and the earliest churn warning

    Response time is the one people leave off and should not. It moves before revenue does, which makes it actionable rather than historical.

    Resist adding a ninth. Every addition dilutes attention on the eight that matter.

    Thresholds, not just values

    A number without a threshold is trivia.

    For each metric define

    • Green. No action.
    • Amber. Look into it this week.
    • Red. Act today.

    Median first-response time
    Green: under 1 hour
    Amber: 1 to 4 hours
    Red: over 4 hours

    Overdue invoices
    Green: under 5% of monthly revenue
    Amber: 5 to 10%
    Red: over 10%

    Colour the dashboard by threshold. You should be able to read it in five seconds and know whether anything needs you.

    Direction beats snapshot

    Every metric needs a comparison.

    • Versus last week, for operational metrics.
    • Versus the same month last year, for anything seasonal.
    • Versus target, where a target exists.
    • A small trend line, ideally.

    Seasonal comparison matters enormously in service work. Revenue down 30 percent on last month means nothing if last month was your peak. Down 30 percent on the same month last year means something.

    Build it in a spreadsheet first

    Before buying any BI tool.

    Why

    • You will discover which metrics you actually look at, which is rarely the list you started with.
    • You will find out how hard the data is to get, which is the real constraint.
    • It costs nothing.
    • It is quick to change while you are still deciding what matters.

    A spreadsheet updated weekly, with twelve months of history, is more useful than a live dashboard nobody has configured properly.

    Move to a BI tool when manual updating exceeds about twenty minutes a week, or when several people need the same view.

    Connecting live data

    Most field service and accounting platforms offer either an API or a scheduled export.

    Practical approach

    1. Scheduled export from each system, daily or weekly.
    2. Land it in a sheet or a small database.
    3. Calculate the metrics in one place.
    4. Present from there.

    Do not chase real time. Weekly is the right cadence for owner-level decisions, and real-time dashboards encourage reacting to noise.

    Watch for definition drift. “Jobs completed” must mean the same thing every week. Write down the definition of each metric next to it, because the definition will otherwise change without anyone noticing and the trend becomes meaningless.

    The weekly email

    Push it, do not rely on people visiting.

    Same time every week. Monday morning works well.

    Contents

    • The eight numbers with their colours.
    • Anything amber or red, with one line of context.
    • One thing to do this week.

    Under one screen on a phone. If it needs scrolling twice, it will not be read.

    Include the one action. A dashboard that reports without prompting a decision is a report, not a management tool.

    Mobile

    Most owners read this on a phone, standing somewhere.

    • Vertical layout. Numbers stacked, not a wide table.
    • Large figures, small labels.
    • Colour doing the work, so it reads at a glance.
    • No hover interactions. They do not exist on a phone.
    • Test it on an actual phone before declaring it finished.

    Common mistakes

    • Too many metrics. The commonest failure by far.
    • Vanity metrics. Total customers ever served, social followers, website visits with no conversion context.
    • No thresholds, so nothing prompts action.
    • Averages hiding distributions. Median response time and average response time can tell opposite stories.
    • Never revisiting it. Review the metric set every six months and remove anything you have not acted on.
    • Building it and not reading it. Book the fifteen minutes in the calendar.

    Beyond the eight

    Deeper metrics belong in periodic reviews, not the weekly dashboard.

    Quarterly

    • Revenue and margin by service line.
    • Customer lifetime value by acquisition channel.
    • Repeat rate by cohort.
    • Billable percentage per technician.
    • Marketing cost per acquired customer.

    These inform strategy. The weekly eight inform this week. Keeping them separate is what stops the dashboard bloating.

    Build the eight-metric sheet this week and fill it in manually every Monday for a month. By the end you will know which metrics you actually use, and that is the specification for anything you build afterwards.

    Need a pro to build it? [BOOK A CALL]