Getting Started in Salesforce

The most important thing about SignalRx is where it lives. Intelligence only changes a number when someone acts on it, and the thing people act on is the record already open in front of them, so SignalRx writes its scores, segments, health, Tags, and Revenue Play memberships onto the Salesforce Lead, Contact, and Account your reps and CSMs work all day. They never log into another tool, so the adoption tax that quietly kills most go-to-market intelligence purchases, great scores in a tab nobody opens, is zero.

It is also additive by design, which is the real answer to the question an admin asks before letting a model into the CRM. SignalRx fills blank GW fields only and never overwrites a human's edit, and it runs on a scoped service account that can see and change only what you grant it, so the risk is bounded before you install and it is safe to point at your whole database. The rest of this guide is the mechanics that deliver on that.

This guide covers installing the SignalRx managed package, the fields your team uses to run and reference SignalRx, adding the Intelligence Card to your record pages, and where to go next. It is deliberately short. The full field reference and operations guide are included with the package and described at the end.

What you get

SignalRx installs as a managed package called GoodWork (SignalRx's parent company and the technical namespace). The package creates a set of GW fields on Lead, Contact, and Account and writes SignalRx intelligence into them: Fit Scores, Buyer and Company Segments, Health Scores, Tags, and Revenue Play memberships.

• Your team. Never logs into SignalRx. Everything lands in Salesforce.
• Your tools. Flows, reports, marketing and sales tools already run on the GW fields.
• Your data. SignalRx fills blank GW fields only and never overwrites a human edit.

01 · Install the package

Prerequisites

• A Salesforce edition with API access: Enterprise, Unlimited, or Performance. Professional works with the API add-on.
• A dedicated service account in Salesforce, used only by SignalRx. A Salesforce Integration user license is a good fit and is least-privilege by design. Never a personal login, and exempt it from password expiry so the connection does not drop.
• A SignalRx workspace login for the administrator who will authorize the connection. Your SignalRx team provisions it before install.

Steps

1. Install the managed package from the link SignalRx provides. Choose Install for Admins Only; you will grant access with permission sets in step 4. The package appears in Setup → Installed Packages as GoodWork.
2. Create the service account and grant it access. Assign the SignalRx Integration permission set the package ships. It scopes the account to exactly what SignalRx needs (see below). Add the account to any sharing rules or role that give it visibility of the records you want scored, since SignalRx can only see what this account can see.
3. Connect Salesforce from inside SignalRx. Log in to SignalRx as the administrator, open Settings → Integrations → Salesforce, and choose Connect. Salesforce's OAuth screen opens: sign in as the service account, not as yourself, and approve access. SignalRx stores the resulting token, so no password is ever shared by email or chat. The integration page then shows Connected with the account name and the time of the last successful poll.
4. Assign permission sets to your team. SignalRx User for every rep and CSM (read on all GW fields, write on the action fields). SignalRx Admin for administrators (adds control over the packaged automations).
5. Add the SignalRx Intelligence Card to your Lead, Contact, and Account record pages in Lightning App Builder. The card shows Fit score and tier, segment, description, firmographics, and Tags at a glance, lists the Revenue Plays the record is in, and carries the Source Email and Source Phone buttons. Section 05 walks through it.
6. Build the automation you want. The package installs the fields; the Flows are yours to shape to your process. The capability guides in section 06 show the plays teams build first, and Using SignalRx Natively in Salesforce covers how list memberships and GW fields drive them.

What the service account needs

• API Enabled on its profile. SignalRx connects only through the API; the account never needs the Salesforce UI.
• Read and write on Lead, Contact, and Account, and create on those objects if you want SignalRx to generate records from uploaded lists.
• Read and write on every GW field, plus read and write on the GoodWork History object.
• Read on the standard fields it needs to match and score: name, email, title, website, address, plus the lifecycle, revenue, and product fields you nominate during onboarding.
• No Modify All Data, no admin profile, no Opportunity or Case write access unless a play you asked for requires it.

The permission set ships preconfigured for all of the above. If your security team wants to review it before assignment, ask your SignalRx team for the permission-set detail sheet.

If a validation or duplicate rule would block a legitimate SignalRx write, exclude the integration user from that rule. This is the standard pattern for integration accounts.

02 · Actions your team sets

Monitor is portal-managed. GW Monitor and GW Company Monitor are set by SignalRx from criteria your SignalRx team configures. They appear on the record for reference and are not triggered from Salesforce.

How every action runs

1. Set the field to Yes. On one record from the Intelligence Card, or in bulk with a Flow.
2. SignalRx runs on the next poll. SignalRx polls Salesforce about every 20 minutes and picks up the request.
3. The result writes back. Intelligence lands in the GW fields; the action field resets to No. GW Last Updated shows when.

Every action has a status field, so nothing runs twice and a re-poll never overwrites a human edit.

03 · The fields that trigger automation

These are your automation triggers. They are multi-select fields, updated as records join and leave lists. Flows watch them to route work the moment a record enters a Revenue Play: add to a Campaign, enroll in a sequence, create a Task, reassign an owner. Marketing automation platforms sync them as ordinary fields and key dynamic lists on them.

Contact lists write to the Contact field. Company lists write to the Account field. Build your Flow on the object the list is built on.

04 · The intelligence to reference

Reference these everywhere. Surface them on page layouts and list views, group reports by them, and use them as Flow entry criteria: route only High Fit contacts, alert when Health flips to At Risk, filter a campaign to one Company Segment.

05 · Add the Intelligence Card to your record pages

The Intelligence Card is the part of SignalRx your team will see most, so add it to the Lead, Contact, and Account record pages before you roll out. It reads the GW fields on the record and presents them the way the SignalRx app does, so a rep never has to hunt through a field list.

1. Open Setup → Lightning App Builder and edit the record page your team uses for Leads. If you have more than one, start with the page assigned as the org default.
2. In the component list on the left, scroll to the Custom section and drag SignalRx Intelligence Card onto the page. The right-hand sidebar or a tab of its own both work well.
3. Save, then Activate the page for the apps and profiles that should see it. Users also need the SignalRx User permission set from step 4 to read the fields the card shows.
4. Repeat for the Contact and Account record pages.

On an Account the card also ranks the associated people by fit, and on a Contact it shows the company the person belongs to with its own score. The Details tab lists the full field set, and the Plays tab lists the Revenue Plays the record is in.

06 · What to build next: the capability guides

Once the package is installed and the card is on your pages, the capability guides show what to do with the data. Each one takes a single business problem, shows how SignalRx changes it, and lists what the team sees and what to measure. Start with the one closest to your current priority.

• Win Back Lost Deals with an Always-On Nurture. An always-on nurture for closed-lost prospects that keeps its own audience current.
• Cross-Sell at Day 30 with an Outbound Sequence. A sequence that starts on day 30 for every qualifying account.
• Catch At-Risk Customers the Day They Turn. Tasks, emails, and leadership alerts the day a customer turns At Risk.
• Upsell Customers Outgrowing Their Plan. Customers running above their plan become an expansion play with a cadence.
• See Which Customers Are Slipping, and Where. One Salesforce dashboard that shows which customers are losing health, and where.

Admins who want the mechanics behind those plays, meaning how Revenue Play memberships and GW fields drive Flows, Campaigns, and routing, can read Using SignalRx Natively in Salesforce.

07 · Included with the package

• Field and Operations Reference. Every GW field by object, with type, meaning, and how teams typically use it; the packaged Flow templates; permission sets; the GW History object for reporting on score movement; the admin FAQ.
• Your SignalRx team. Implementation, list and tag design, Flow build, and tuning are part of the engagement. Contact them through your shared channel or at signalrx.ai.