Use cases · Recruiting & staffing

Candidates answer texts they'd never answer as calls

ATS and staffing platforms move at texting speed: interview invites, shift offers, document chasing. Handset turns your workflow triggers into compliant SMS from per-client numbers, with campaigns and numbers provisioned by API as fast as you add customers.

Start freeRead the docs
shift-offer.ts
// A workflow trigger in your ATS
await sendMessage({
  body: {
    from: client.tenant.numberId,
    to: candidate.phone,
    body: template("shift_offer", { shift, rate }),
  },
  headers: { "Idempotency-Key": trigger.id },
});

In staffing, the first platform to reach the candidate wins. A shift offer that arrives as a text gets answered in minutes; the same offer as a voicemail gets answered never. The constraint isn't your product, it's how fast you can provision compliant texting for each new client.

Client onboarding

A new client is a script, not a ticket queue

Everything a staffing client needs to start texting (tenant, brand, campaign, numbers) is an API object. Run the four calls below from your own signup flow.

1POST /v1/tenants

Create the client

Each staffing client becomes a tenant: its own numbers, threads, opt-out lists, and hours. Isolation is the data model, not a convention.

2POST /v1/brands → /v1/campaigns

Register their 10DLC campaign

Brand and campaign are API objects with status webhooks. In test mode they approve instantly, so onboarding is code you can run in CI.

3POST /v1/numbers

Buy numbers in their markets

Search by area code, buy programmatically. A client opening a Dallas office is a loop iteration, not a procurement thread.

4POST /v1/messages

Start texting candidates

Your workflow triggers fire the sends; replies thread back per conversation, ready to render in the ATS timeline.

Built for platform scale

Templates stay in your app

Interview invites, shift offers, document chasing, your templating engine renders the body; Handset handles delivery, threading, and the opt-out check at send time.

Idempotency for workflow engines

Send with an Idempotency-Key tied to the trigger ID. Retried jobs and replayed queues never double-text a candidate.

Replies thread per candidate

Every message carries a conversation_id. “Can I take the Friday shift instead?” lands in the right candidate's timeline, not a shared inbox.

Numbers by market, per client

Candidates answer local numbers. Provision area codes per client market as they expand, and every number answers voice calls too.

onboard-client.ts
// Your signup flow, provisioning a client end to end
const tenant = await createTenant({ name: co.name });
const brand = await createBrand({ tenant, ein: co.ein });
await createCampaign({ brand, use_case: "staffing" });
await buyNumber({ tenant, area_code: "214" });

→ campaign.approved // webhook; instant in test mode
→ client is texting candidates: live

This page exists because a staffing platform asked for exactly this, and couldn't get it from their UCaaS provider. We built Handset so the answer is yes.

Onboard your next client by API.

Design partners get free early access, white-glove 10DLC for their first clients, and a founder on the call.

Start freeSee all use cases