Work Case study
Messaging & Conversion Tracking
01
The problem
Inbound forms triggered text messages, but nobody could tell which messages led to bookings, who clicked and didn't book, or where people dropped off.
02
What needed to change
Attribute every message, click, and booking to the person and the step it came from, and follow up automatically with the ones who stalled.
03
Architecture
Form submissions trigger a Make workflow that sends SMS through Twilio using tracked links. Clicks and Calendly bookings are recorded by a small Node.js backend, a dashboard shows the funnel, and non-responders get scheduled follow-ups.
04
What I built
- Make workflow from form submission to Twilio message
- A redirect endpoint that records each click before sending the visitor to the booking page
- Calendly webhooks tied back to the original contact
- Follow-up rules for people who clicked but didn't book
- A tracking dashboard showing sent, clicked, booked, and follow-ups by day
05
Stack
- Twilio
- Make
- Calendly
- Node.js
- Custom Backend
- Tracking Dashboard
06
Result
Every message, click, and booking is attributed, and follow-ups go out on schedule instead of when someone remembers.
07
What I learned
One small redirect endpoint turned a black box into a funnel. The simplest piece of custom code was the one that made the whole system measurable.