Send a text or email to an applicant

Message sending and reply capture require an authorized provider and a successful workspace-specific test.

Steps

1Open the applicant record from the pipeline or the Candidates list.
2Confirm the workspace owner has authorized and configured the provider for the selected channel.
3Confirm required applicant consent, review the recipient and preview the final message.
4Use an approved test recipient to verify delivery status with the configured provider.
5Test an inbound reply and confirm it attaches to the correct applicant before candidate outreach.

The public message preview is simulated. In a live workspace, delivery and reply capture depend on provider configuration, webhook routing, access scope and acceptance testing.

Delivery statuses

Queued: stored as a pending attempt. Check the final provider result before assuming it was delivered.
Sent: the provider accepted it. For SMS, Twilio's delivery receipts update this to Delivered or Failed.
Simulated: a demo preview only; do not treat it as a message sent from a live workspace.
Failed: the provider rejected it. The error is shown on hover. Common causes are an invalid number, a landline, or an unregistered sender.

Why can't I text this applicant?

SMS is blocked when the applicant has opted out, has no phone number, lacks recorded consent, or the workspace/provider is not configured. A quiet-hours block is not queued for later; check the result before retrying.

Still stuck?

Contact support.

Tell us what you tried. A person replies from [email protected].