Skip to content
Help Center
Submit a request Sign in

Manage companies and contacts with the full support relationship in view

Companies represent the organizations you support; contacts represent the people you work with. Keeping those relationships accurate helps a B2B team see repeated issues, understand account context, and continue a conversation when another person or agent takes over. A company’s history provides context that a single contact’s inbox cannot.

At a glance

For: agents, account owners, support operations teams, and customer-data administrators. Applies to: Supportbench Core.

Start here: Customers → Companies or Contacts

Choose the right record  ·  Find and inspect a customer  ·  Create or correct the record  ·  Use customer context in an account review  ·  Handle duplicates carefully  ·  Correct an existing company or contact  ·  Prepare an account review across several contacts  ·  Common customer-data problems

Choose the right record

RecordUse it forOperational benefit
CompanyThe customer organization and its configured relationships, support information, and account historyDifferent agents can understand the same account context.
ContactAn individual’s identity, contact methods, company relationship, and support historyReplies and case associations point to the intended person.
CaseA specific request, incident, or investigationOwnership, activities, tasks, and resolution remain traceable.
AssetA supported item related to the customer where applicableRecurring issues can be understood in the context of what the customer uses.

A relationship does not by itself grant someone access to every linked record. Customer visibility, agent permissions, divisions, and configured policies remain important.

Find and inspect a customer

  1. Open Customers and choose Companies or Contacts.
  2. Use search or the available Recently viewed, Assigned to me, and All companies or All contacts scopes. Use Filter, Columns, and Group to focus a longer list. “All” is still limited by your access.
  3. Open the record and check its identifying details and active state. Confirm that similarly named companies or people are not being confused.
  4. Review recent Cases and use View all Cases when you need a fuller history. The recent-case panel is not proof that no older issue exists.
  5. Review available account-health and related information in context. A summary is a prompt for investigation, not a substitute for reading the relevant cases.

Create or correct the record

Search before adding either type of record. A second spelling of the same company or a second contact for the same person can divide the history your team needs for an account review.

Create the company record

  1. Open Customers → Companies and search for the organization. Check its existing identity and history. Use New Company only when the intended organization does not already have a record. The app header also offers New → Company when you have the required permission.
  2. In Details, enter the organization’s Name. Review Status, Support level, Support expiry, Tags, Phone and Active where shown. Use the contracted support arrangement and your team’s classification rules; a value already selected in the form is not evidence of this customer’s entitlement.
  3. Review Mailing Details, Domains and Health scoring when relevant. Only associate verified domains with the intended organization. A shared domain or similar name is not sufficient evidence that two organizations should share support history or access.
  4. Complete any required fields in your customer policy. Select Create Company, then open the saved company and verify its name, active state and support information. Use Cancel and confirm Discard to abandon an unsaved example.

Create a contact for a specific company

  1. Open the verified Company record, choose Contacts, then New Contact. This company-scoped route preselects that company for a new contact. It is particularly useful when the global New Contact form does not show a company selector.
  2. Enter First name, Last name, Title, Email and the required contact details. For example, a technical contact’s title can help an agent identify who can provide diagnostics. Verify the real address before saving; do not use a training example address for a real person.
  3. If Primary Company is shown, confirm it is the intended organization. Customer Policy controls whether that field appears. If it is absent, do not search indefinitely for a hidden control or create duplicate contacts: use the company-scoped route for a new contact, then verify the relationship on the saved record. Ask an administrator about the policy when you need to change an existing association.
  4. Review the applicable Mailing Details, Community and Roles settings with the responsible administrator. Customer roles and portal access are separate from merely recording a person’s name and address. Do not copy another person’s access choices as a shortcut.
  5. Select Save Contact. Open the saved contact and inspect the tab named for its primary company (shown as Company when unassigned) and the relevant company’s Contacts list. Verify the intended association before creating a customer case or relying on the history in an account review.

The global New → Contact route is also available when permitted. If its customer policy hides Primary Company, it does not offer another control for choosing that association in the form. Start from the intended company when that context matters. Opening an existing contact from a company’s Contacts list does not automatically replace the contact’s saved primary company.

Creation and editing require the relevant customer permissions. When handling a request, use the available Create a Case for this Company or Create a Case for this Contact action from the correct customer record, or select the customer carefully during Case Add. Verify the resulting case association.

New Company editor with a fictional Harbor Manufacturing training name, status, support level, support expiry, tags, phone and Active controls.
The Company record represents the organization. This unsaved demo illustrates Details and the Create Company action. Select support information from the verified customer agreement; the demo’s Freemium selection is not a recommendation or a universal default.
New Contact editor with fictional Alex Example identity, a reserved example.test email address, contact details and Save contact action; no Primary Company control appears.
A Contact records the individual. This unsaved training example uses a reserved example address. This demo policy hides Primary Company, so use Company → Contacts → New Contact when creating a person for a particular organization, then verify the saved relationship. Do not use example.test addresses for real customer communications.

Use customer context in an account review

Example: several contacts, one recurring issue

A support lead sees separate cases from a customer’s operations manager and technical administrator. Reviewing the company history reveals that both concern the same supported equipment category. The team can coordinate the investigation and communication, while keeping each contact’s request and permissions intact. Record the agreed next steps in the relevant cases so the review produces accountable work.

  • Review open commitments before an account meeting, then check recently closed issues for repetition.
  • Use a customer-focused view for the meeting agenda and open current cases before making a promise based on an older export.
  • Use available favorites or watcher controls when ongoing attention is useful, and remove unnecessary monitoring when responsibility changes.
  • Correct outdated contact information through the approved record workflow; avoid leaving the only correct details in an internal note.

Handle duplicates carefully

Merge is consequential because it consolidates the relationship and history into a surviving record. Company merge can move cases, contacts, and assets to the survivor. Compare both records before using it; a similar name is not enough to establish that they represent the same organization.

  • Identify the intended surviving record and verify its authoritative details.
  • Compare company/contact identity, related cases, assets, and configured customer settings.
  • Use the permitted merge workflow only when the records genuinely represent the same entity.
  • Afterward, inspect the surviving record and important linked history. Confirm that the people and assets are associated as intended.

Bulk actions such as assignment, roles, synchronization, merge, and delete depend on your permissions and the selected record type. Review the actual selected rows and intended scope before applying them.

Correct an existing company or contact

  1. Find and open the existing record before creating anything new. Compare the organization name, contact email and relevant history when similar records appear.
  2. For an organization, choose Edit Company, correct the intended fields, and choose Save Company. For a person, choose Edit Contact, verify the intended details and Primary Company if that field is shown, and choose Save Contact. Customer Policy can hide Primary Company; in that situation, inspect the saved relationship on the contact’s tab named for its primary company (shown as Company when unassigned) and ask the responsible administrator about changing the association.
  3. Complete any required customer-policy fields and read validation messages. If a field or action is unavailable, ask the responsible administrator about permissions rather than creating a duplicate to work around the restriction.
  4. Reopen the record and check the saved values. Review related cases or customer access if the correction affects how support identifies the customer.

A primary company is the contact’s main company association; additional relationships can represent other organizations the person works with. For example, an external implementation consultant may work with two customers. Do not change the primary association merely to represent an additional relationship. Review the intended relationship and customer visibility with the administrator, using the contact configuration guide when that setup is required.

A shared email domain does not prove that two people belong to the same legal or support organization. Subsidiaries, consultants and service providers may use names that look related while having different service commitments and visibility. Verify the relationship from an authoritative customer source.

Prepare an account review across several contacts

Imagine the operations manager reports delayed orders while the technical administrator reports repeated connector retries. Start from the company record and compare the relevant cases across contacts. Read the original messages before deciding these are one issue: the shared company gives context, but it does not prove a common cause.

  1. Confirm the company identity and the contacts involved. Record who is the business decision-maker and who supplies technical evidence in the appropriate existing fields or case history.
  2. Use View all Cases when the recent panel is insufficient. Review open commitments and recent resolutions for recurrence.
  3. Identify the affected assets or product context and compare the facts across cases. Retain separate cases when they need separate owners, access or promises.
  4. Agree who communicates with each contact. Record the next actions in the cases, not only in meeting notes.
  5. Correct outdated customer details through the record editor so the next agent does not have to discover the correction in a note.

Before merging duplicates, identify the survivor and compare its customer settings and linked history. The merge controls distinguish the Company to keep or Contact to keep; review that choice before the final Merge Companies or Merge Contacts confirmation. A parent company and its subsidiary are not duplicates solely because the names overlap.

Common customer-data problems

ProblemChecks and correction
A contact is linked to the wrong companyVerify identity and correct the association through the permitted editor. Review affected case context before continuing.
History looks incompleteCheck record scope, division/access, recent-list limits, and possible duplicates; use View all Cases.
The edit or create action is missingAsk the administrator to check company/contact permissions and applicable customer-policy requirements.
A company’s contacts see unexpected casesReview customer roles, portal policies, and explicit visibility settings. Do not assume company association alone defines access.
Exports contain more information than neededChoose appropriate columns and filters, review the selected scope, and share only with the intended audience.

View Shopify purchases from the customer conversation

When the Core Shopify integration is enabled for your account, open the Contact’s Shopify tab or expand Shopify purchases in the Case customer pane. The view follows Contact access; Contact edit permission is required to change the Shopify customer link. Choose the correct store, expand an order for items and shipments, and use Load older orders to continue through history.

Administrators must connect the store and verify historical-order access first. Read Connect Shopify stores and verify complete purchase-history access for setup and Find customer purchases and shipment details from a Contact or Case for detailed steps, matching, refunds and troubleshooting.

Actual Core Contact Shopify view showing fictional customer Jamie Chen and an expanded partially fulfilled order
Actual Core Contact Shopify view with fictional demonstration data. The surrounding workspace frame is illustrative. This screenshot does not establish a live Shopify connection or approval for historical orders.

Was this article helpful?