Use cases · Field service & home services
The van is on the way — and your product said so
Software for plumbers, HVAC, electricians, and cleaners lives or dies on communication: arrival windows, reschedules, photos of the finished job. Handset lets your platform send and receive those messages on a real local number per business — without you becoming a phone company.
Customers screen unknown numbers
Each business texts from its own local number — the same one that answers when customers call back.
"On my way" is your feature now
Job-status triggers in your product become compliant texts with one API call; replies thread back into your UI via webhooks.
Missed calls become voicemail tickets
After-hours calls roll to voicemail with transcripts your product can turn into next-morning jobs.
Compliance is invisible
STOP/HELP, opt-out enforcement, and 10DLC registration run at the platform layer — your customers never see them.
// Your job-dispatch workflow, texting like a local await sendMessage({ body: { from: job.tenant.numberId, to: job.customer.phone, body: `${tech.name} is 15 minutes out. Reply here with gate codes or questions.`, }, }); // customer replies → webhook → your job timeline → message.received "Gate code is 4417, dog is friendly"
Platforms for home services are Handset's home turf — the founding design-partner slots are built around this exact use case.
How it maps to the API
1 · Tenants & numbers
One tenant per business
Bayview Dental, Ridge Plumbing — each with isolated threads, hours, and opt-out lists.
Learn more2 · Messaging
Trigger texts from your job workflow
Status changes call POST /v1/messages; delivery and replies come back as webhooks.
Learn more3 · Voice
Ring the tech, then voicemail
Business-hours routing per tenant, in the tenant's own timezone.
Learn moreSound like your platform?
Three design-partner slots: free early access, white-glove 10DLC, and a founder on the call.