Connect Salesforce

Connect Salesforce so a task can contact Leads, Contacts, or Opportunities, and so Nexor can write the stage, opt-out, and a Task back to the same record. One Salesforce connection is shared by the account. Each task chooses which records it contacts.

​

What the integration does

This is not a mirror of every Salesforce object. Accounts and custom objects are not the record Nexor contacts. A related field, such as Account.Phone, can still fill the Nexor lead when that field is available to map. The Salesforce card is shown when the integration is enabled for the account. If Integrations has no Salesforce card, ask Nexor to enable it.

​

Before you connect

The connect screen requires a Salesforce edition with API access. The person who connects must be able to sign in to that org and approve access for Nexor. Nexor then needs to:

• read the chosen object, its fields, and its stages;
• read campaigns, when a task contacts a campaign;
• read Opportunity pipelines (record types) and their stages, when the object is Opportunities;
• update the stage when Keep Salesforce stage updated is on;
• read and update the opt-out checkboxes you select;
• create a Task on the record;
• convert a Lead, when a task uses Convert the Lead when it reaches.

​

Connect Salesforce

The object is shared by every task. Changing it asks Change your leads to …? and names the tasks that stop receiving records until you pick their stage again. Confirm only when that pause is acceptable. Disconnect stops future syncing. Historical data in Nexor stays, and you can reconnect later. If Salesforce stops accepting the connection, the page asks you to reconnect before import can resume. A failed import is retried automatically.

​

Choose which records a task contacts

Open the agent, open the task, and go to Lead source. A task listed under Agents using Salesforce opens that same section. The Salesforce block there is Intake. Connection settings returns to Integrations → Salesforce. The sentence starts with Contact and the object. Then choose how records enter: For Opportunities, in stage also asks for a Pipeline. The stages in the list are that pipeline’s stages. Changing the pipeline clears the stages you had selected. Wait before contacting adds a minimum time in the stage before Nexor contacts the record. The wait is in minutes, up to 10080 (7 days). It applies to stage intake only. Nexor looks for matching records about every 5 minutes. A record is not picked up at the moment it changes in Salesforce. When you choose a campaign or stages that already contain records, Nexor asks whether to contact them:

• Only new ones contacts records that match after you save. This is the default.
• Contact them too also contacts records that already match.

New-record intake does not ask this question. It contacts records created after you save. A stage, campaign, or new-record mode already used by another task is marked Used by that task. Saving an overlap shows already contacts these records. Choose a different stage or campaign. Until a task has a campaign, stages, or new-record intake, its source stays Paused until you choose which records to contact.

​

Map fields

Field mapping is under Advanced on Integrations → Salesforce, and it is shared by every task. Select Edit on the field group (Lead fields, Contact fields, or Opportunity fields). Map each Nexor field to a Salesforce field: The standard map uses those five. Point a row at another field when the org stores the value somewhere else. A related field such as Account.Phone can be used when it appears in the list. The list does not include id, checkbox, or lookup fields. Not mapped leaves that Nexor field unset from Salesforce. Select Done to save.

​

Keep Salesforce stage updated

On a Lead or Opportunity task, open Salesforce updates and turn on Keep Salesforce stage updated. Each Nexor status then has a Salesforce stage. Choose the stage to write, or Don’t change to leave that status’s stage alone. Suggested rows can point a won Nexor status at a converted Lead Status such as Closed - Converted. Do not save that row. Salesforce does not accept a converted Lead Status from a stage update. Set that row to a status that is not converted, or to Don’t change. Convert the Lead when it reaches is the path onto a converted status. It appears for Leads, and it is saved only while Keep Salesforce stage updated is on. Choose the Nexor status that should convert the Lead, or Never. Conversion creates an Account, a Contact, and an Opportunity in Salesforce. A converted status cannot be reached by the stage rows above. Stop contacting when Salesforce closes the record is on by default. When Salesforce closes the record and it is not won, Nexor stops outreach and marks the lead lost. Contacts do not use this stage map. On a Contact task, Salesforce updates shows the Task logging sentence instead. Opportunity stage values belong to the pipeline selected on Intake. Pick the pipeline before you map stages.

​

Do not contact if checked

On Integrations → Salesforce, open Advanced and edit Do not contact if checked. A record with one of the selected checkboxes checked is never contacted. When a lead opts out in Nexor, Nexor selects those same checkboxes on the Salesforce record. The fields this setting is built to use are: These two are the defaults on a new connection whenever Salesforce shows them to the connected user. Confirm they are selected before you go live. The selector lists the checkbox fields Salesforce exposes for the connected user. None means no Salesforce checkbox is treated as do-not-contact. Salesforce hides Email Opt Out and Do Not Call until an administrator grants field-level security on them. If they are missing from the list, in Salesforce open Setup → Object Manager → Lead (or Contact) → Fields & Relationships, open each field, choose Set Field-Level Security, and make it visible to the profile of the user who connected Salesforce. Then open the selector again. The opt-out list is shared by every task, like the field map.

​

Tasks logged in Salesforce

Nexor logs every message, call, and status change as a Salesforce Task on the record. The connected page states this, and there is no separate switch to turn the log on. The Task is attached to the Lead, Contact, or Opportunity the task is working.

​

Troubleshooting

​

A record never arrives

Confirm the task’s Intake has a campaign, stages, or new records, and that the task is live. Nexor checks about every 5 minutes, and a stage wait adds more time. Records that already matched are skipped unless you chose Contact them too. Another task may already own that campaign, stage, or new-record intake. The row shows Used by.

​

The stage in Salesforce did not change

Keep Salesforce stage updated has to be on, and that Nexor status needs a stage other than Don’t change. Contacts do not write a stage. A converted Lead Status such as Closed - Converted fails from the stage map. Use Convert the Lead when it reaches for that outcome.

​

The Lead did not convert

Set Convert the Lead when it reaches to the Nexor status that should convert, with Keep Salesforce stage updated on. Mapping the status to a converted Lead Status does not convert the Lead. The Salesforce user who connected Nexor must be allowed to convert Leads. If conversion still does not run, contact Nexor. Do not point the stage map at the converted status as a substitute.

​

Salesforce opt-out is ignored

Open Advanced → Do not contact if checked and confirm Email Opt Out and Do Not Call are selected. None, or a different checkbox such as Unread By Owner, does not apply those two fields.

​

Nexor AI says Salesforce is not connected

Use Integrations → Salesforce. If that page shows the org as connected, do not reconnect from chat. Reconnecting creates another authorization.

​

A sandbox will not sign in

On the Salesforce sign-in page, choose Use Custom Domain and enter the sandbox domain, then return to Connect Salesforce.