Unified Inbox + Missed-Call Text Back for Front Desk Teams (2026)

Unified Inbox and Missed-Call Text Back for Front Desk Teams (2026)

A clinic's front desk handles incoming communication from multiple channels simultaneously: phone calls, SMS replies, emails, portal messages, and sometimes social media enquiries. Without a unified workflow, each channel is managed separately — the receptionist checks one inbox, then another, then the phone log, then the email. Messages get missed. Response times vary wildly by channel. Nobody knows which conversations have been resolved and which are still waiting.

The missed-call text back workflow addresses the highest-friction channel: voice calls. A patient who calls and reaches no one is the most common communication failure in busy clinics. If the missed call triggers an immediate SMS — "We missed your call. How can we help? Reply here or call us back at [number]" — the patient has an immediate alternative channel. Their reply enters the unified inbox alongside all other conversations. An owner is assigned. A response SLA applies. The conversation is resolved and tagged.

This guide covers how to design the unified inbox and missed-call text back workflow for a clinic front desk team.

Why Missed Calls Are a Booking and Revenue Problem

In most clinics, a missed call is a missed opportunity. Consider the typical scenario:

• Patient calls to book a new appointment. No one picks up.
• Patient hangs up. They may call back later, or they may call another clinic.
• The clinic's call log shows a missed call from an unknown number. Nobody follows up.
• The patient booked elsewhere.

Research across healthcare and service businesses consistently shows that callers who don't reach someone on the first attempt have a 50–80% likelihood of trying a competitor next — particularly for new patient enquiries where no prior relationship exists. For established patients, the tolerance for unanswered calls is higher, but repeated inability to reach the front desk erodes satisfaction and retention.

Automated missed-call text back converts a hard stop (unanswered call) into a soft start (SMS conversation that can be handled when the front desk is available).

Workflow Design

Step 1 — Missed call detected

When a call to the clinic's number is not answered within a configurable number of rings (typically 4–5), the system flags it as a missed call.

Triggering conditions to define:

• What counts as missed? (Rings without answer vs. calls that reach voicemail)
• Is after-hours the same workflow as during-hours, or different? (After-hours may have a different SMS template acknowledging that the clinic is closed)
• Are calls from known internal numbers excluded?

Step 2 — Automatic SMS sent within 60 seconds

An SMS is sent to the caller's number within 60 seconds of the missed call:

During hours template: "We missed your call. We're helping other patients — text us and we'll reply shortly, or call [number] if urgent."

After hours template: "We missed your call. We're closed until [opening time]. Text us and we'll reply first thing, or call [emergency number] if urgent."

The message is short, helpful, and contains no clinical information. It includes a clear call-to-action (reply to this message) and acknowledges the patient's experience (we're busy, not ignoring you).

Step 3 — Reply enters unified inbox

When the patient replies, the thread opens in the clinic's unified inbox alongside all other active conversations. The incoming message is tagged:

• Source: missed-call recovery
• Caller: matched to client record if the phone number is recognised; new enquiry if unrecognised
• Priority: configurable (missed-call recovery threads can be set to high priority to ensure rapid response)

Step 4 — Owner assigned with SLA

Every conversation in the unified inbox must have an assigned owner — the staff member responsible for resolving it. For missed-call recovery threads, the assignment can be automatic (to the current front desk staff member, or to a duty role that rotates) or manual (a manager assigns).

The SLA sets the expected response time: typically 15–30 minutes during clinic hours. Conversations approaching SLA breach surface as alerts in the owner's queue.

Step 5 — Outcome tagged and thread closed

When the conversation is resolved — appointment booked, question answered, callback arranged — the owner tags the outcome:

• Booked: new appointment created
• Existing query resolved: answered a patient's question
• Callback arranged: patient prefers a phone call; callback scheduled
• No response: patient did not reply within the configured window
• Wrong number: SMS was sent to a non-patient

The thread is closed. The outcome data feeds the missed-call recovery report.

Unified Inbox: Beyond Missed Calls

The missed-call text back workflow is most effective when it feeds into a genuine unified inbox — not just a separate SMS channel alongside all the other channels. A unified inbox consolidates:

• SMS conversations (including missed-call recovery threads)
• Email enquiries
• Portal messages from existing clients
• Internal notes and handoff comments visible only to staff

The key capability is context: when a staff member opens a missed-call recovery thread, they should be able to see the patient's recent appointment history, any open invoices, and prior conversation history — not just the current SMS exchange. Without context, staff are working blind, and patient experience suffers.

Key Metrics for the Workflow

Metric	What it measures	Target
Missed-call SMS send rate	% of missed calls that trigger an automatic SMS	100% (or close; technical failures should be flagged)
Recovery reply rate	% of missed-call SMSs that receive a patient reply	Benchmark: 30–50%
Time-to-first-response	Median time from patient reply to staff first response	Target: <15 minutes during clinic hours
Booking conversion rate	% of replied threads that result in an appointment	Track and improve over time
SLA breach rate	% of conversations that exceeded the defined response SLA	Target: <5%
Thread closure rate	% of conversations closed with an outcome tag within 24h	Target: >95%

Review all metrics weekly during the first 8 weeks. The most important early signal is the SLA breach rate — if more than 5–10% of conversations are breaching, the queue is understaffed or the SLA is set too aggressively.

Setting Up in Tregovia

Tregovia's Unified Inbox (EUR 12/month) and Missed Call Textback (EUR 8/month) modules cover this workflow:

Unified Inbox:

• SMS, email, and portal messages in a single queue
• Client record context in the conversation view (appointments, billing, notes)
• Owner assignment with SLA tracking
• Internal notes on threads (visible to staff, not sent to patient)
• Outcome tagging and thread closure
• Conversation backlog and SLA breach reporting

Missed Call Textback:

• Automatic SMS within 60 seconds of a missed call
• During-hours and after-hours templates (configurable)
• Incoming replies routed to Unified Inbox with "missed-call recovery" tag
• Client number matching against the client database
• Recovery rate reporting per period

Privacy controls: Configure access roles, consent records, exports, deletion requests, and retention rules before publishing this workflow.

Pricing: Unified Inbox EUR 12/month + Missed Call Textback EUR 8/month — flat rate, no per-seat fee. Base plan EUR 47/month (up to 2 staff, up to 100 clients (extra users EUR 10/month per 5 seats)). 14-day free trial.

GDPR Considerations for SMS Outreach

Sending an SMS to a patient who called but didn't leave a message sits within a legitimate interest framework under GDPR Article 6(1)(f) — the clinic has a legitimate interest in responding to a person who actively attempted to make contact, and the processing is proportionate (one SMS, clearly identified as coming from the clinic, with an opt-out path).

For EU clinics, the missed-call SMS should:

• Clearly identify the sender (clinic name)
• Include an opt-out mechanism ("Reply STOP to unsubscribe from texts")
• Contain no clinical information (never include appointment details, diagnoses, or patient record data in the SMS)
• Be logged with timestamp and delivery status for audit purposes

If the missed-call number cannot be matched to a known client, the SMS goes to an unknown contact. This is still permissible under legitimate interest — the person called the clinic's number — but should be documented in the clinic's Record of Processing Activities.

FAQ

What is the first KPI to track when launching the workflow?

Time-to-first-response for missed-call threads. This measures whether the workflow is producing faster patient contact — which is the core purpose. If the SLA is set at 15 minutes but the median first response is 45 minutes, the problem is owner assignment and queue management, not the automation. Identify the bottleneck (understaffed front desk, owner not monitoring the inbox, SLA alerts not configured) before adjusting the workflow design.

Why is the unified inbox more effective than managing channels separately?

It prevents handoff loss. A missed-call recovery SMS that converts to an email conversation that then requires a callback creates a context chain that spans three channels. If each channel is managed separately, the staff member handling the callback doesn't know the patient already replied by text and email. They call blind, the patient is frustrated at being asked to repeat themselves, and the clinic looks disorganised. Unified inbox means every touchpoint in a conversation is visible to whoever picks it up next.

When should a manual callback replace automated SMS recovery?

After a defined no-response window. If a patient received the missed-call SMS but hasn't replied within 2 hours, an automated follow-up SMS can be sent. If there is still no reply after 4 hours, a staff member should make a phone call — particularly for patients who may be elderly or less comfortable with SMS, and for any enquiry where the clinical context suggests urgency (a callback from a patient reporting symptoms should not wait indefinitely for an SMS reply).

What causes the workflow to fail most often?

No owner assignment and no closure taxonomy. The SMS fires correctly; the patient replies; the message sits in the inbox with no owner and no SLA pressure. Staff don't know who is responsible. The thread ages without a response. The patient gives up. The fix is mandatory owner assignment (automatic or within a defined SLA from message arrival) and a clear closure taxonomy (every thread must be tagged and closed — not just left idle). These are process discipline issues, not technology issues.

Can the same workflow apply to online enquiry forms?

Yes — any inbound message channel can feed the unified inbox with the same owner-assignment and SLA mechanics. A contact form submission, a Google Business Profile message, or a social media direct message can all route into the unified inbox and follow the same workflow. The missed-call text back is simply the highest-impact trigger because voice calls are the highest-intent channel — patients calling typically want to book or have an urgent question.