How to use a Righthand with Outreach

Quick answer

Use Righthand to prepare an Outreach sequence exception list for the sales owner. Keep prospect identity, latest conversation, and due task together before proposing the next touch.

Start with a reviewable deliverable, keeping Outreach 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

Outreach documents REST API access, authentication, and account resources. See the official Outreach reference. Provider capabilities and Righthand's available tools are separate checks.

Use the approved prospect and sequence packet with owner, current stage, activity evidence, and the team's contact policies. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: prospect ID, sequence, owner, current step, due task, latest reply, account. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

The accepted sequence state stays in Outreach. Righthand's draft should not independently send a parallel message or change assignments.

Illustrative first-run brief

Use the owner-provided Outreach snapshot or approved read-only view. Review the supplied due-task snapshot for one sales team. Match tasks to current conversations, flag pauses and duplicates, and propose the next owner action. 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 sales-team lead 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

An overdue task may be obsolete because the prospect booked a meeting. The review identifies the mismatch rather than recommending another follow-up.

Match one due task to the prospect's latest thread and accepted owner. 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.

Common failure and recovery

A partial task view can omit work assigned to another user. Confirm filters and report unavailable coverage instead of declaring the team queue complete.

If a prospect is assigned to two sequences or owners, flag the conflict and withhold the follow-up proposal until sales operations resolves it.

FAQ

What should the reviewer verify first?

Verify prospect ID, sequence enrollment, latest activity, account owner, and reply context. Enrollment alone does not establish the proper next conversation.

How should a repeat run be scoped?

Retain prospect IDs and activity cutoffs; compare sequence state with actual replies on each review. Do not reuse an outreach draft after new buyer context arrives.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.