Enrich Company and Contact records with HunterIO while protecting customer context

HunterIO can supply additional person and company information for your Supportbench customer records. This can help an agent understand a new business contact or fill useful organizational context before an account conversation. Enrichment is a data update, however, not an identity-verification or entitlement decision. Use it deliberately: returned values can replace information your team has already entered, and customer relationships still need to be correct for support work.

Choose a useful support-operations use case  ·  Understand what can change before refreshing  ·  Connect the intended Hunter account  ·  Refresh one saved Contact  ·  Refresh one saved Company  ·  Understand the three automation switches  ·  Example: onboard a new customer engineer carefully  ·  Verify data changes and keep ownership clear  ·  Troubleshoot the actual refresh result  ·  Remove the integration deliberately

Choose a useful support-operations use case

The benefit is better context alongside the case history: the support team can understand the organization and person without repeatedly researching basic details. A more complete profile does not establish a diagnosis, a contractual service level or the right to disclose private customer information.

Understand what can change before refreshing

Optional returned data can include location, social/profile links and an image. Company classification values apply only where the required matching choices exist in your account. Review the resulting record instead of assuming every provider field will be populated or that absence of a value means “unknown customer.”

Connect the intended Hunter account

1. Confirm your Supportbench role permits administering integrations and editing the HunterIO section. Ask the Hunter account owner to confirm the intended account, plan and available enrichment usage.
2. Obtain the API key from the Hunter account’s API section through your approved process. Keep it private; do not paste it into a documentation article, screenshot or ordinary customer case.
3. Open Settings → Integrations → HunterIO and select Connection. Enter the API key. A blank field on an existing installation preserves the saved key; the saved key is not returned to the page. The reveal control applies only to a newly entered value.
4. Open Automation and review the three switches described below. Start with a deliberately chosen scope; do not enable every option as a prerequisite for a manual refresh.
5. Save using the integration toolbar’s Save action. A new or replaced key is verified through a real provider Company lookup before saving, so verification is not merely a check of the key’s text format. It may count toward provider usage according to your plan. There is no separate Test connection button on this page.
6. Reopen the configuration, read the status and verify one approved manual refresh before relying on automation. If Needs attention reports more than one configuration, contact Supportbench to resolve that conflict before changing the installation.

Provider instructions reviewed on 28 October 2026: find your Hunter API key, Hunter API guidance and Hunter API for Data Plans. Usage and credits vary by plan; check your actual account rather than assuming a fixed cost per refresh.

Refresh one saved Contact

1. Open Contacts, find the intended person and verify the Company relationship and saved email. Do not enrich a shared mailbox as though it were a confirmed individual identity.
2. Open Edit Contact. Save any pending changes first. The Contact refresh path requires a saved record without unsaved edits.
3. Open Integrations and review the overwrite implications above. Your role must permit editing this Contact; a visible action does not bypass the server’s permission check.
4. Select Refresh from HunterIO once. It sends the request immediately. Wait for the result and read the returned status.
5. Review the reloaded saved Contact: name, biography and relevant optional fields. Confirm that the Company association is still correct; this manual action does not perform Company creation/linking.
6. If the result says HunterIO did not return Contact data, review the saved email and provider/account status as appropriate. Do not keep refreshing solely because a valid person has no match.

Refresh one saved Company

1. Open Companies and verify the intended customer organization. Review its saved domains and their ownership, especially where a customer has subsidiaries, shared brands or service providers.
2. Open Edit Company. Save your pending changes before continuing. The refresh response can refill the Company editor, so unsaved local changes must not be treated as protected.
3. Open Integrations. Confirm your role permits editing the Company and that replacing the supported fields is appropriate.
4. Select Refresh from HunterIO once. The action queries the saved domains and uses the first usable result. A Company without a saved domain has no domain to query through this path.
5. Read the result and inspect the saved Company, including name, description, phone, relevant location/classification values and domains. Confirm that returned context represents the intended customer organization.
6. If no data is returned, review the actual saved domain and provider availability. Do not add a domain belonging to another business simply to obtain a result.

Understand the three automation switches

There is a separate current behavior to understand when existing-contact updating and Company creation are both enabled: an unlinked existing Contact may cause Company creation, but that post-update path does not explicitly assign the returned Company ID back to the Contact. Verify the actual result rather than assuming the Contact is linked or its person fields were refreshed. This is a reason to keep a deliberate acceptance test and an integration owner.

These controls do not provide a bulk-refresh button for all existing customers. Plan any broader data-cleanup requirement separately rather than repeatedly editing records to trigger enrichment.

Example: onboard a new customer engineer carefully

A new engineer contacts support from a business email address. Your team already has a Company for the customer and knows its domains. The agent checks the incoming Contact relationship and uses approved enrichment to add context where useful. The agent compares returned names and profile details with the customer’s supplied information, then confirms that the case belongs to the existing customer Company.

If the provider returns a parent brand or a similarly named business, the agent does not create a new service entitlement from that suggestion. The team preserves the actual support relationship and resolves discrepancies with the customer/account owner. The value of enrichment is reduced research effort around the record, while customer-confirmed relationships continue to guide the support decision.

Verify data changes and keep ownership clear

1. Record the selected path, record identity and important before-values using an approved internal change record. Do not copy unnecessary personal data into public documentation.
2. Run one controlled manual refresh or one specifically selected automation path. Keep new-contact and existing-contact tests separate because their save behavior differs.
3. Compare saved fields, Company association and domains with the expected result. Include a no-match case and a record with meaningful existing values in the acceptance plan.
4. Check Hunter usage and any returned failure status. A saved configuration or connected label does not guarantee that every future lookup has quota or returns data.
5. Assign responsibility for correcting unsuitable enrichment and reviewing provider/key changes. If a field is critical to customer identification or routing, decide whether automation is appropriate for that field’s current overwrite behavior.

Troubleshoot the actual refresh result

Remove the integration deliberately

Uninstall HunterIO removes the saved key and automation settings while retaining existing Contacts and Companies. Review the affected users and automation before confirming removal. Uninstalling does not restore values previously overwritten by enrichment; use your approved record-correction process for those values.

Keep the current HunterIO setup and usage instructions separate from retired Clearbit material. Retained historical configuration data is not evidence that the Clearbit provider remains available in Core.

Continue learning

• Configure HunterIO connection and automation controls
• Manage Company and Contact relationships
• Configure and maintain Contacts
• Manage Company details and domains