# How to use a Righthand with Instantly

Use Righthand to review an Instantly campaign's reply-handling queue before further outreach.

By Righthand Team · 2026-10-11

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-instantly

## Quick answer

Use Righthand to review an Instantly campaign's reply-handling queue before further outreach. The useful output is a stop, pause, or owner-review list tied to current lead events.

Start with a reviewable deliverable, keeping Instantly as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

## Evidence and access

Instantly documents API v2 and campaign, email, and lead events. See the [official Instantly reference](https://developer.instantly.ai/). Provider capabilities and Righthand's available tools are separate checks.

Use the approved campaign snapshot with lead IDs, actual message history, campaign state, and contact restrictions. Keep campaign review separate from authorization to send. Verify the required tools and owner-approved scope through [Righthand integrations](/integrations); use the supplied packet when a native read is unavailable.

## Define the objects and authority

Include these fields in the working input: campaign ID, lead ID, sender account, last send, latest reply, pause reason, owner. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Reply interpretation does not grant authority to enroll more leads or increase sending. Opt-outs and unresolved identities require the established stop process.

| Responsibility | Owner |
| --- | --- |
| Prepare source scope and access | Account owner |
| Organize evidence and proposed next steps | Righthand |
| Approve consequential changes | the outreach owner |

## Illustrative first-run brief

> Use the owner-provided Instantly snapshot or approved read-only view. Review the supplied campaign snapshot and current reply export. Identify declines, requested pauses, and commercial questions. Prepare proposed queue changes without sending or enrolling. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the outreach owner to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

## Expected result and verification

A prospect asking to reconnect next month appears as a pause; a decline is a stop. The report does not label either as an unanswered lead.

Compare a proposed stop with the latest thread and the actual campaign status. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.


### Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

| Source item | Supplied observation | Draft conclusion |
| --- | --- | --- |
| Lead A | Reply received | Remove routine follow-up |
| Lead B | History incomplete | Hold next-message draft |
| Lead C | Campaign paused | Ask owner about state |

## Common failure and recovery

An old export can miss a recent reply. Refresh the affected lead before action rather than continuing the original schedule.

If message history is incomplete, hold the proposed follow-up and ask the campaign owner to reconcile the lead's actual last contact.

## FAQ

### What should the reviewer verify first?

Verify the campaign, lead identity, delivered-message evidence, replies, and restrictions. A campaign status does not establish that a specific recipient received an email.

### How should a repeat run be scoped?

Retain campaign and lead IDs, reply cutoff, and last-contact timestamps. Exclude replied or restricted contacts under the owner's rules and review fresh evidence before another send.

For connection and permission details, use [Righthand Docs](https://docs.righthand.ai). Review [Pricing](/pricing) alongside any separate provider charges before expanding the workflow.