Skip to main content
Use case · Customer comms

Five channels. One inbox. Nobody waiting.

Messages arrive on WhatsApp, Insta, email, the form, the phone — and walk-ins arrive at the desk. We consolidate the front desk so the customer never knows the wiring behind it. Routed by skill, owner, and SLA. Owned by you.

WhatsApp17 messages live:30s
Email3 new replies2m
Phone2 voicemails queuedqueued
Instagram5 DMs unread1m
Web form1 enquiry — unownedmissed
Walk-in2 waiting at desknow
Owner inbox · liveOne queue.

Routed by skill, owner, and SLA. The customer never knows which channel they came from. Nobody is left waiting.

Open28
Owned22
SLA at risk3
One queue Five+ channels routedSLA gating Owner, skill, urgencyHouse voice Reply library, trained on yoursWalk-in Captured at the desk
What's in the build

Six pieces, one front desk.

From the message hitting any channel to the response landing in front of the right person. Built for the chaos of how customers actually contact you.

01 · Channel ingest

Every channel, one queue.

WhatsApp, Insta DM, email, web form, phone, walk-in — all routed into a single owner queue. The customer's history follows them across channels.

  • WhatsApp Business API
  • Insta & Messenger DM
  • Email · web form · phone
  • Walk-in capture at desk
02 · Routing

Skill-based, by SLA.

Routes by skill (booking, complaint, supplier), by owner availability, by SLA priority. The right person sees it first; nobody else has to.

  • Skill tagging (auto + manual)
  • Owner-availability rules
  • SLA-priority queue
  • Out-of-hours escalation
03 · Suggested replies

Two-tap responses, in your voice.

Suggested-reply library trained on your past responses. The owner taps to confirm, edits if needed, sends. Reply time falls without quality dropping.

  • Voice-trained reply library
  • Two-tap confirm-and-send
  • Variable insertion (name, slot)
  • Per-channel formatting
04 · SLA & escalation

The clock everybody can see.

Each enquiry gets an SLA based on channel and type. As it approaches, owners see it; as it breaches, it escalates. The clock is visible, not invisible.

  • Per-channel SLA targets
  • At-risk & breach alerts
  • Escalation chain
  • Weekly SLA dashboard
05 · Customer view

The history, in one place.

Per-customer history across every channel. Last visit, last message, open threads, lifetime value. The owner sees the whole relationship, not the latest message.

  • Cross-channel customer profile
  • Last-visit & LTV summary
  • Open-thread roll-up
  • Notes & preferences
06 · Owner panel

What got missed, what got booked.

Daily summary: enquiries in by channel, replied, converted, missed. The owner sees what the front desk did this week without asking.

  • Channel volume & conversion
  • Missed-enquiry log
  • Reply-time trend
  • Per-owner workload
Method

Read · Find · Write.

Two weeks watching how the messages actually flow before we wire up a queue. The build follows the missed enquiry — not the brief.

  1. 01

    Read

    Two weeks logging which channel gets which type of message, who owns the reply, where the gaps are. The pattern emerges quickly. We share what we see.

  2. 02

    Find

    The biggest leak gets prioritised — usually one or two channels with no clear owner after hours. We scope the smallest build that closes the gap.

  3. 03

    Write

    We build, integrate every channel, train the reply library on your voice. Ninety days of stabilisation included. Documented, exportable, owned by you.

Sample engagement

The lettings agency that stopped chasing tenants on WhatsApp.

Forty-two doors. Three property managers. SLA breach above 60% before the rebuild.

An independent lettings agency took maintenance reports across three personal phones, Instagram DMs, the website form, and a shared Gmail. Tenants chased managers; managers chased contractors. Three-week build: a single routed inbox with priority gating (gas/electrical first), contractor SLA tracking, an automated tenant status thread, and an out-of-hours triage flow with escalation rules. Six months in: SLA breach rate down from 68% to 26%, mean response time to safety-critical issues from 3.2 days to under 18 hours.

How we measure: 312 maintenance tickets sampled across the engagement, mapped to historical priority codes; baseline drawn from the prior 90-day window in the agency's legacy spreadsheet.

68% → 26%SLA breach rate
3.2d → 18hsafety-critical response
0tickets lost weeks 4–24
Other use cases

Five more builds, same method.

Each one a tightly-scoped fix for a row that's bleeding on the P&L.

Connect the channels.

One call. No deck. We come prepared.

Send the brief