Help center Access and connected tools Connect Salesforce customer context to Supportbench: plan, configure and verify synchronization Updated Wednesday, October 28, 2026 · Marc Staine The Salesforce integration helps support and account teams work from connected customer information. Salesforce Accounts can become Supportbench Companies, customer contacts can be synchronized in the configured direction, and supported product and asset records can provide context for service work. Supportbench cases and their activities can also be exported through the configured integration. The operational value comes from agreeing which system owns each piece of information and checking the resulting records—not simply switching on every synchronization option. At a glanceFor: support operations administrators and Salesforce administrators responsible for shared customer data. Applies to: Supportbench Core.Start here: Settings → Integrations → Salesforce Understand the supported directions · Check current Salesforce compatibility before creating credentials · Agree on ownership, scope and a test customer · Configure and test the Core connection · Configure each object and its field mappings · Run synchronization and verify representative records · Example: support an installed product with shared account context · Diagnose the failing layer Understand the supported directions Salesforce recordSupportbench relationshipSupported direction to planAccountCompanyImport Salesforce Accounts into Supportbench Companies. Customer relationships underpin other customer-linked synchronization.ContactContactImport, or import and export as configured. Decide which system owns editable contact fields.Product2Shared asset catalogImport Salesforce products into Supportbench assets. This is different from assigning a customer-owned unit.AssetCompany assetImport customer-owned Salesforce Assets into company asset relationships. Check the associated Account and product.CaseSupportbench caseExport eligible Supportbench cases using the integration’s trigger and field mappings. Verify the company’s Salesforce relationship.Task activity used by the integrationSupportbench case activityExport supported activity data associated with the synchronized case. Review the actual fields and content sent.These directions do not mean that every field is automatically synchronized in both directions or that every change is instantaneous. A connected company, enabled object, valid mapping, provider permissions and the relevant synchronization path all matter. The Salesforce configuration reference covers the individual controls, custom data tables and dependencies. Check current Salesforce compatibility before creating credentials Core’s current connection uses an existing compatible Salesforce connected app, its consumer key and secret, and an integration user’s username/password authentication. The Supportbench field expects the password immediately followed by the security token. This is not an interactive browser authorization screen, and the current connector does not offer an External Client App, client-credentials or JWT setup path in this editor.New connections need a compatibility checkSalesforce restricts creation of new connected apps from Spring ’26 and blocks username-password flow by default in newer organizations. Existing compatible connected apps can continue, subject to the organization’s policies. If your organization does not permit this method or cannot create the required app, stop and ask your Salesforce administrator and Supportbench Support for a supported connection path. Do not substitute credentials from another flow or weaken an organization policy just to follow an old screenshot.Check the current connected-app requirements and Salesforce authorization-flow controls. Provider requirements reviewed on 28 October 2026. Use the API access and compatibility procedure before entering credentials. Agree on ownership, scope and a test customer Choose the Salesforce organization and Supportbench account you intend to connect. Use Sandbox only for a Salesforce test organization and Production for the live one.Identify the fields each team owns. For example, the account team may maintain company addresses in Salesforce while support maintains case updates in Supportbench. Document what agents should do if imported information is wrong.Select the minimum object directions needed. Importing customer context and exporting support activity have different business purposes and access requirements.Choose a representative approved test company with a contact, a product and a company asset if those objects are in scope. Include an eligible case for the export test.Have the Salesforce administrator confirm API availability, the integration user’s object/field permissions, record access and required custom fields. A successful login does not prove those permissions are complete.Decide who will review failures, credential expiry or rotation, mapping changes and duplicate records. Keep an operational owner on both sides.For B2B organizations with multiple contacts and installed products, check both the shared product and the customer-owned asset. A product called Controller Model A is not by itself evidence that a particular customer owns a particular unit or has a particular service entitlement. Configure and test the Core connection Open Settings → Integrations → Salesforce with permission to administer this integration. Review the saved connection and current status before changing an existing working setup.In Connection, choose Salesforce environment. Enter the compatible app’s Consumer key and Consumer secret, and the actual Salesforce username for the integration user.In Password and security token, enter the password immediately followed by the security token, with no separator. Use the credential issued for that integration user and environment. Do not paste an unrelated browser session token.When updating an existing record, leave a secret field blank only when the screen indicates a stored value is configured and you intend to preserve it. Stored secrets are not displayed for copying.Select Test connection. This tests the current form values without saving them. If it fails, resolve the environment, authentication policy or credential issue before proceeding.Save the intended settings, reopen the connection and verify the saved configuration. Do not treat the earlier connection test as a save or a completed synchronization. Configure each object and its field mappings Open the relevant Companies, Contacts, Products, Company assets or Cases section. Choose its supported Synchronization mode deliberately; leave unused domains disabled.Review Only import active records where offered. For Companies this depends on the Salesforce Account field Active__c; contact filtering depends on the mapped active field. Confirm these fields exist and contain the intended values before enabling the filter.Under Field mapping, choose or enter the exact Salesforce API field name for each Supportbench field. A field’s display label is not necessarily its API name. Confirm custom field names with the Salesforce administrator.Review object filters and dependencies. A filter that excludes the test Account can also prevent meaningful verification of its related contact or asset records.For case export, verify the required case linkage and configured fields. The standard mapping includes fields such as bench_case_id__c, bench_owner__c, bench_queue__c and bench_outcome__c. The integration exports activities to Salesforce Task records and uses fields such as bench_activity_id__c. Check the full mapping reference and Salesforce field permissions rather than relying on the old screenshots.Save the configuration. Reopen the object sections and compare their saved directions and mappings with your agreed data-ownership plan.Do not map a text description into a picklist field merely because the labels sound similar. Field types, allowed values and write permissions still apply at Salesforce. A mapping can be syntactically saved while the provider rejects actual record data. Run synchronization and verify representative records After saving changes, select Synchronize now. Read the response: synchronization runs on the existing service cycle. This action does not directly enqueue a new job or prove that records have finished processing.Review Last synchronized, progress and any failure indication. Allow the configured processing path to run, then inspect the actual records in both systems.Check that the test Account becomes or updates the intended Company, with the right identifying information. Confirm its contact remains associated with the correct company.For product and asset imports, inspect the shared catalog item and the company-specific asset separately. Confirm the account relationship, identifying fields and mapped values.For enabled contact export, make an approved representative contact change in Supportbench and confirm the intended result in Salesforce. Do not test by changing a real customer’s email address without an agreed change.For case export, verify the eligible case under the synchronized customer and inspect the resulting Salesforce Case and associated exported Task activity. Check content and customer association, not just that a record exists.Use full resynchronization deliberatelyResynchronize all marks enabled objects and data tables for a complete synchronization on the existing service cycle. It does not directly enqueue an immediate job. It is not a narrow retry for one record. Review the scope, mappings and operational timing before confirming it, particularly after changing imports or fields. Example: support an installed product with shared account context An equipment vendor keeps account and contact details in Salesforce. Its support team imports that customer context and the relevant catalog and company-asset information into Supportbench. When an engineer reports a recurring controller failure, the agent confirms the contact’s company, identifies the installed unit and works the case with an accountable support owner.If case export is configured, the account team can review the exported support record in Salesforce during an account review. The support agent still owns the customer update and verifies the actual issue. The integration’s benefit is connected context and less manual re-entry; it does not automatically establish warranty eligibility, resolve the defect or transfer ownership of the customer commitment. Diagnose the failing layer SymptomWhat to verifyConnection test failsCorrect organization/environment, supported authentication method, API access, consumer credentials and the integration user’s password/token. Ask the Salesforce administrator to review the actual provider error.Connection succeeds but records do not appearSaved object direction, filters, record access, required related Account, processing status and actual object permissions.Some fields are empty or rejectedExact API names, data types, allowed values, field-level access and required custom fields. Compare one failing record with a successful example.A contact appears under the wrong companyInspect the Account relationship and integration mapping. Resolve identity before merging or recreating records.Cases do not exportConfirm the enabled case path, eligible synchronized company relationship, case mappings and the integration user’s Case/Task access.An edit appears to be overwrittenCompare synchronization direction with the agreed field owner. Correct the operational ownership or mapping before repeating edits in both systems.A password change breaks an existing connectionUpdate the stored integration credential through the approved rotation process and run Test connection before relying on synchronization again.Capture the object type, sanitized external record ID, time with timezone, expected direction and observed error when asking for help. Do not include consumer secrets, passwords or security tokens in a case, screenshot or shared guide. Continue learning Prepare Salesforce API access and connection compatibilityConfigure every Salesforce synchronization settingManage companies and contactsManage assets and asset categories Was this article helpful? Yes No Thank you for your feedback.