How to use a Righthand with Salesforce
Prepare a Salesforce pipeline decision queue with opportunity IDs, stage and close-date checks, currency rules, and reviewed changes.
Make the pipeline review specific
Use Righthand with Salesforce to prepare a decision queue for opportunities whose close dates, stage, or next action need owner review. The useful result is a list of exceptions linked to records, rather than a generic statement that the pipeline is healthy.
Salesforce's opportunity field guidance documents the business record behind fields such as Amount, Stage, and Close Date. Custom fields and picklist meanings can differ by organization. Supply your team's definitions instead of asking the assistant to interpret every stage name as universal.
Connect the correct organization
Check integrations, then identify the Salesforce organization, account connection, and available read actions. A sandbox and a production organization can contain similar-looking records. The report should state which it used.
If native retrieval is unavailable, provide an approved opportunity report export with record IDs and filters. That supports a bounded review without claiming live CRM synchronization. Follow the connection permission guide before expanding access or write authority.
Choose fields around a decision
For an illustrative founder-led sales review, request opportunity ID, account, owner, stage, amount, currency, close date, and your organization's next-step field. Add the latest approved activity context only if the source is available.
Flag past close dates on open opportunities and missing next actions using the owner's policy. Do not change a stage because an email sounds enthusiastic, or combine currencies without an approved conversion rule. A forecast judgment remains the sales owner's responsibility.
A complete pipeline brief
On Monday at 8 AM America/Los_Angeles, review the approved open-opportunity report for the named Salesforce organization. Return a private decision queue for past close dates, blank next steps, and missing owners. Preserve record ID, stage, close date, amount, and currency. Link each exception and supporting activity where supplied. Send to me for sales-lead review. Draft field changes separately; do not apply them or contact prospects. Reconcile record count and currency subtotals against the source report.
This brief is illustrative. The report's date filters and access scope are part of the task, not incidental setup details.
What a useful row contains
A sample could read: “Opportunity record linked; close date passed; next step blank; owner must confirm revised date.” It should not predict a probability or invent the customer's intention. Include unknown fields explicitly so the owner can distinguish absent data from a negative assessment.
After approved changes, retrieve the affected records again and compare them with the approved worksheet. If the workflow uses an export, the owner applies the changes and supplies a refreshed report for reconciliation.
Handle false gaps and stale snapshots
A missing record can result from sharing permissions or report filters. Investigate the scope before describing it as deleted. A renamed custom field can break a mapping; return the mapping issue rather than substituting a superficially similar field.
Begin with one owner and one saved report. Expand only after its exceptions are accurate and useful. See pricing for the plan supporting the ongoing review; a prepared queue is distinct from a changed Salesforce record or a sent prospect message.