Skip to main content
When a prospect replies to one of your campaign emails, Leadterra automatically classifies the intent of their message — interested, not interested, out of office, and more — so your agents or automations can take the right action without manual triage. This guide shows you how to poll for replies, interpret classifications, and route them into downstream workflows.

Poll for replies

Call GET /v1/replies to retrieve all classified replies across your workspace. Responses are paginated and sorted by receivedAt descending, so the most recent replies always appear first.
To narrow results to a single campaign, append the ?campaignId= query parameter:
A successful response returns an array of reply objects, each enriched with Leadterra’s classification:

Act on classifications

Leadterra’s classification field lets you branch your logic without building a custom NLP layer. The most common classifications you’ll encounter are: Use the classification field to route each reply to the appropriate handler in your application or agent:

Use webhooks for real-time replies

Polling works well for low-volume campaigns or batch processing workflows, but if you need replies routed within seconds of receipt, use the reply.received webhook event instead. Register a webhook endpoint and Leadterra will POST each classified reply to your URL the moment it arrives. See Register Webhooks for setup instructions and payload examples.
For production workloads, prefer the reply.received webhook over polling. Webhooks give you sub-second delivery latency and eliminate the overhead of scheduling repeated API calls. Polling is best reserved for debugging, backfill jobs, or low-frequency reporting.