Follow up on Instantly interest by phone.
Route leads marked interested, with a mapped phone, into your calling queue.
Only lead interested events are admitted. Blocked leads stay visible for repair.
- Lead marked interested in Instantly
- Map phone and supported contact fields
- Lead enters a Redialler queue
What you need.
Authenticated source webhook
- An Instantly account with webhook configuration access.
- A Redialler queue and organisation admin access in Redialler.
- A real source phone field and the ability to use Instantly's Add headers option.
Set up Instantly.
Open Instantly setup in Redialler Settings and create a source connection for your queue.
Map the actual phone path and any supported contact or captured consent fields. Redialler reads lead and event IDs from supported provider fields.
Save the shared token. Copy the generated callback URL to a
lead_interestedwebhook in Instantly.Use Add headers to send the required authentication header with the token.
Inspect the last source result. Keep missing-phone records in a repair view and resend after correcting the source.
Confirm provider access and delivery in your account before rollout.
Data and permissions.
- Instantly sends the subscribed event to the authenticated source callback. Redialler maps it to normalized queue data.
- The saved shared token protects callback access. Keep it private in both tools.
- A positive reply does not establish express written consent to call. Preserve only consent evidence that the source actually captured.
Current limits.
- Only lead interested events are admitted. General reply events are ignored.
- A record without a mapped phone is blocked and does not enter the callable queue.
- This setup adds ordinary queue work. It does not create an email inbox or sync campaigns.
- Confirm event payloads, phone mappings, and delivery in your Instantly account before rollout.
Provider documentation
Questions about Instantly.
Can I send an Instantly payload to the public leads API?
Use the generated source callback for provider-native payloads. The public leads API expects Redialler's normalized lead contract.
Can Instantly send a custom authentication header?
The webhook setup includes Add headers. Configure the header required by the Redialler source connection.
Why is an interested lead blocked?
Check the last result. A missing or invalid phone, suppression rule, or invalid consent claim can block intake. Repair the source before resending.
Set up Instantly for your workspace.
Sign in to open this tool in Settings. An organisation admin connects it for your workspace.