Using Interseller with Top Echelon (unsupported)

Important Note: We have discontinued technical support for all Interseller integrations. Moving forward, users are welcome to continue using these integrations at their own discretion but our Technical Support team will no longer provide assistance or guarantee compatibility with future updates.

For general troubleshooting suggestions, please refer to the guide below or visit our Help Center.

Interseller's integration with Top Echelon (formerly Big Biller) allows you to automatically sync contacts into Top Echelon whenever they're added to an Interseller sequence.

Connecting to Top Echelon

To connect Top Echelon to Interseller, visit the integration settings tab and select Top Echelon from the list. From there, enter in your Top Echelon email and password to login.

Adjusting the sync settings

After Top Echelon is connected to Interseller, you can choose how all contacts sync over from Interseller to Top Echelon by selecting one of the following sync options:

  1. Off - Contacts will not sync over to Top Echelon
  2. Sync contacts when added to a sequence - Contacts will sync over to Top Echelon when they are added to a sequence
  3. Sync contacts only when they reply back - Contacts will only sync over to Top Echelon when they reply to a sequence

Disabling syncing sequences

You can also disable syncing individual sequences over to Top Echelon by toggling off the "Sync to Top Echelon" feature in the "Syncing" tab within the sequence's settings.

If you don't want contacts to sync over to Top Echelon, you will need to make sure this setting is enabled first before adding contacts into the sequence.

Resyncing contacts to Top Echelon

If contacts have been added before Top Echelon was connected, contacts can be backfilled later through the “Resync to Top Echelon” feature. You can resync contacts to Top Echelon individually or in bulk.

Note: The "Resync to Top Echelon" feature does not update contacts who have already synced over to Top Echelon. This feature will only sync contacts who have not yet synced over to Top Echelon.

Enable/disable deduplication for Top Echelon

You can toggle on the the "Deduplication" setting for Top Echelon to be warned if a contact already exists in Top Echelon. This will mark the contact with the error "Exists in Top Echelonif we find the same email address already exists in Top Echelon prior to being added into Interseller.

If deduplication is turned off, then we will not warn you if the contact already exists in Top Echelon.

Below are two common scenarios of when a new contact record will be created and when it won't be created when the contact has synced over to Top Echelon:

  • If the same email address exists in both Top Echelon and Interseller, a duplicate contact record will not be created in the integration.
  • If there are two different email addresses for the same contact (one in Top Echelon and one in Interseller), a second contact record will be created with the second email address when they sync over from Interseller to Top Echelon.

Selecting the default job

You can set the default job posting that all contacts across all sequences are synced to at the account level by adjusting the  "Job" sync setting.

We recommend leaving this blank if you're syncing contacts to specific jobs for each sequence.

Selecting the job per sequence

You can override the default job by adjusting this setting for each individual sequence.

To adjust the job setting, open up the  sequence's settings, click on the "Syncing" tab, and select the specific job for contacts to sync over to within Top Echelon.

Be sure to  select the correct job first as contacts cannot be re-synced if they were added first and then a job is selected for the sequence at a later time.

You can also add the  same contact into multiple sequences with a different job. A single contact record will be created within Top Echelon when they sync over while being assigned to multiple jobs.

Did this article answer your question? Thank you for your feedback! There was a problem submitting your feedback. Please try again later.