DocToc: voicemail, messages and calls in one place.

DocToc is a mobile app that brings voicemail, messaging and calling together for doctors at multiple hospitals in the United States, under the line “Making healthcare simple”. It was designed with safeguards for patient information.

Three DocToc app screens: the DocToc logo, a home screen with voicemail, messages and calls, and a call history list
Market
Multiple US hospitals
Platform
iOS and Android, Azure backend
Core
Voicemail, messages, calls
Also
Patients, calendar, recent activity
The challenge

Why it needed building.

Doctors work across voicemail, text messages and calls, often on the move. When each lives in a different place, things get missed.

In a hospital, those messages are often about patients, so convenience cannot come at the cost of privacy. The aim: one app where every message and call is easy to find and act on, and patient information stays protected.

The product

DocToc, feature by feature.

01

One home screen

Voicemail, messages and calls side by side, with counts at a glance and a single recent-activity feed.

02

Voicemail

Voicemails show who called and when, ready to listen to from the activity feed.

03

Calls

Incoming and outgoing calls with search and a dated history, plus a button to start a new call.

04

Patients and calendar

Patients and a calendar sit in the same navigation, a tap away from communication.

Security by design

How DocToc protects patient information.

The safeguards built into the app and how it is released.

  • No intentional device storage

    Patient information is retrieved from the Azure-hosted backend and is not intentionally stored on the device.

  • Encrypted connections

    Every call from the app to its API goes over HTTPS with TLS encryption.

  • Sessions that expire

    Sign-in uses email, password and access tokens. Tokens expire, logging out ends the session, and inactive sessions lock or expire automatically.

  • Private notifications

    Push notifications carry generic messages only, never patient-specific details.

  • Clean logs

    Patient information and authentication tokens are left out of, or redacted from, application logs and crash reports.

  • Controlled releases

    Every release has a change ticket, an approved code review, QA testing and a release record before it reaches the App Store and Google Play.

Walkthrough · DocToc

Every message, one feed.

A doctor’s morning in DocToc: check the feed, listen, reply and call back.

DocToc● online

Good morning, Dr. Patel

Voicemail3 new
Messages12 texts
CallsStart a call
Illustrative walkthrough · sample data, not real client data
Why it matters

The difference it makes.

Communication that used to be spread across separate places sits in one feed, so a missed call or an unheard voicemail is visible straight away.

Privacy is built into how the app works, not added afterwards: patient information is retrieved from the server rather than intentionally stored on the phone, notifications stay generic, and logs exclude or redact patient details.

Web & mobile apps: how we do this kind of work

Start a project

Have something like this in mind?

Tell us what you're trying to solve and who it's for. We'll tell you how we'd approach it.