Mobile
Dev

A Sales Floor That Logs Itself

Platform Type
Mobile App
Key Features
Automatic Call Capture
Industry
Healthcare

Intro

Enquiries for spine treatment arrive by phone, and what happens on those calls decides whether someone books. The call tracker puts the lead list, the call, the recording and the follow-up in one Expo app, and captures the call without asking the rep to log it.

The ANSSI call tracker is the sales-side companion to the ANSSI Wellness platform - an Expo and React Native application for the staff who work inbound and outbound enquiries for spine treatment.


The Background

Enquiries arrive on the phone, and the difference between a booked consultation and a lost one usually happens during that call. But the record of it depended on the person who made it stopping to type a note afterwards, and on a busy day that is the first thing to go. Managers were reviewing a pipeline that described a fraction of the calls actually made.


The Challenge

The fix could not be a better form. It had to remove the logging step entirely, which meant reaching into native call state on the device - detecting that a call started and ended, capturing the audio, and matching it to the right lead without any manual selection.

It also had to work as the rep''s only tool. If the lead list, the calendar and the messaging lived somewhere else, the app would be one more thing to keep in sync.


The Solution

Call detection and recording run at the device level through custom Expo config plugins that adjust native Android behaviour, with a recording service and permission handling built around them. A completed call is attached to its lead automatically, and the audio is playable in-app for review and coaching.

Around that sit the tabs a rep actually needs: a dashboard, the lead list with a detail view per lead, the call history, follow-ups, and appointments. WhatsApp messaging is wired in for the conversations that do not happen by voice, and push notifications keep follow-ups from slipping. Supabase carries the data, with edge functions and migrations kept in the repository alongside the app.

The Solution

  1. 01Automatic call detection at the device level, so a call is recorded because it happened - not because someone remembered to log it.
  2. 02Custom Expo config plugins adjusting native Android behaviour, making recording and permissions work reliably in a managed workflow.
  3. 03Recordings attached to the lead automatically and playable in-app, giving managers real material for review and coaching.
  4. 04The rep''s whole day in one app - dashboard, lead list with per-lead detail, call history, follow-ups and appointments.
  5. 05WhatsApp messaging built in for the conversations that do not happen by voice, from the same lead record.
  6. 06Push notifications on follow-ups so commitments made on a call do not quietly expire.

The Results

  1. 01The pipeline began reflecting the calls that were actually made rather than the ones someone had time to write up.
  2. 02Call review became possible at all - recordings sit against the lead instead of on the handset that made the call.
  3. 03Reps stopped switching between a lead list, a dialer, a calendar and a messaging app to work a single enquiry.

The Achievement

  • Automatic call capture and recording built on native Android call state through custom Expo plugins.
  • In-app audio playback of call recordings tied to the lead record.
  • Six screens covering the full sales workflow, with WhatsApp and push notifications integrated.
  • Supabase edge functions and migrations version-controlled alongside the app.

"

Any process that depends on a salesperson writing down what just happened will decay by Friday. The app was built so the record is a by-product of making the call rather than a task that follows it.

"

Explore other case studies

Creating digital
experiences that convert is
hard. We make it easy.

Grow my project
Get a free consulting call with our experts