How to use a Righthand with HubSpot

Turn pipeline records into owner questions

Use Righthand with HubSpot to prepare a pipeline decision queue for one approved sales pipeline. The output should identify missing next steps, unclear ownership, and closing-date questions with source links. It should not make a forecast more optimistic or move deals forward without the sales owner's decision.

HubSpot's deal guide describes deal records and their properties and associations. Preserve deal identity and the actual pipeline and stage values. Stage labels and probabilities can depend on account configuration.

Define the pipeline and source mapping

Give the pipeline ID, included stages, owner mapping, and the properties relevant to the review. For an illustrative quarter-end queue, use deal name, amount and currency context, close date, stage, owner, and the approved next-step field. These inputs should reflect the portal's real property schema.

Check available HubSpot tools through integrations. If deal reads or association details are unavailable, supply an approved export or authorize a browser review. Native access to deals does not imply permission to enroll contacts, send email, or change pipeline stages.

A complete example brief

At 9 AM America/Los_Angeles on Monday, review open deals in the approved pipeline with close dates in the selected quarter. Produce a private owner queue with deal ID and URL, stage, close date, amount with currency context, explicit owner, and supplied next-step evidence. Flag missing fields and uncertain contact or company associations. Do not change records, enroll contacts, or contact customers. Send to me for sales-manager review. Reconcile deal counts and keep currencies separate.

This example is illustrative. A close date records a planning value; it is not a customer commitment or proof that the opportunity will close.

Define the expected decision queue

An example item might say: “Renewal deal; close date Friday; next-step field blank; contact association present; sales owner must confirm the next conversation.” The assistant should not create a customer-facing promise or infer that a meeting occurred from an association alone.

Separate missing evidence from negative evidence. An empty next-step field does not prove the rep has done no work. Ask for the missing source or update rather than criticizing activity that was not retrieved.

Reconcile changes before follow-up

Match deal IDs across runs, refresh properties, and update the existing queue entry. A renamed company or changed deal title should not become a new opportunity. A stale export should remain labeled with its snapshot date.

Permissions and pagination can hide records or associations. State incomplete coverage and hold totals that depend on missing pages. If approved supported updates are later applied, reread the exact properties and associations to confirm the result.

Set access through Righthand connection permissions. Review plans for recurring sales preparation and retain the sales manager as the decision owner.