Skip to main content

Message Reply Tracking

Reply tracking allows the system to monitor for responses to a sent message and notify you via webhook when a reply is received. This is useful for automating follow-up workflows, tracking outreach campaigns, or alerting your users when a prospect responds.

Enabling Reply Tracking​

When sending a message through any messaging endpoint, include the track_reply parameter set to true:

{
  "accountId": "1234ab5678290....",
  "profile_id": "ACoABC1d2f...",
  "message": "Hi Jane, great connecting with you!",
  "track_reply": true
}

Setting Tracking Frequency​

You can optionally specify how often the system checks for replies using the frequency parameter (in hours). If not specified, the default frequency is 1 hour.

{
  "accountId": "1234ab5678290....",
  "profile_id": "ACoABC1d2f...",
  "message": "Hi Jane, great connecting with you!",
  "track_reply": true,
  "frequency": 2
}

How It Works​

Once tracking is enabled:

  1. The system periodically calls the /api/v1/personal_messages endpoint at the specified frequency to check the message thread
  2. If a reply is detected — a webhook notification is sent to your endpoint, and tracking for that thread automatically stops
  3. If no reply is found — tracking continues indefinitely at the specified frequency
caution

Tracking continues indefinitely if no reply is received. Consider implementing logic on your end to disable tracking after a certain period, or set an appropriate frequency to balance responsiveness and system load.

Disabling Reply Tracking​

You can stop reply tracking at any time using the update message tracker endpoint.

Endpoint: POST /api/v1/update_message_tracker

{
  "tracker_id": "your-tracker-id"
}

Replace tracker_id with the actual ID of the tracker you want to disable. This will stop reply tracking for the associated message thread.

Viewing Active Trackers​

To see all currently active trackers, use:

Endpoint: POST /api/v1/get_active_tracker

{
  "accountId": "1234ab5678290...."
}

When to Disable​

  • You no longer expect a reply
  • The user cancels tracking from your interface
  • You want to clean up trackers that are no longer needed

Tracking also stops automatically once a reply is detected.

Best Practices​

  • Set an appropriate frequency — Lower frequencies (e.g., 2–4 hours) reduce system load for low-priority messages. Higher frequencies (1 hour) are better for time-sensitive outreach.
  • Implement a timeout — Consider disabling trackers after a certain number of days (e.g., 7–14 days) if no reply is received, to avoid unnecessary polling.
  • Use with webhooks — Ensure you have the Message reply tracking trigger enabled in your webhook configuration to receive reply notifications.
  • Don't over-track — Only enable tracking on messages where a reply is expected or actionable. Tracking every outbound message increases system load unnecessarily.