CallTools integration

Feature Snapshot

Summary:
The CallTools integration automates lead delivery from LeadConduit to the CallTools Power Contact Center by appending contact information directly to your call center platform.

Key Benefits:

• Simplifies call center management by automatically transferring lead data.
• Provides real‑time delivery with clear outcome statuses (Success, Failure, or Error).
• Enhances campaign efficiency by reducing manual data entry through precise field mapping.

Typical Use Cases:

• Adding leads from various marketing campaigns as contacts in CallTools.
• Managing multi-campaign call lists centrally in the CallTools Power Contact Center.
• Improving sales outreach by ensuring leads are promptly available to call center agents.

How the CallTools integration works?

The CallTools integration connects LeadConduit with your CallTools Power Contact Center via an API. By configuring the integration with your dedicated, non‑expiring API key and your CallTools Login Domain, LeadConduit automatically maps standard contact fields (such as phone numbers, email, name, and address) and delivers the lead data. The integration returns outcome codes that indicate whether the lead was successfully appended, encountered a failure, or if an error occurred due to connectivity issues.

Step‑by‑Step Instructions

1. Obtain Your API Key:
   Log in to your CallTools Power Contact Center, navigate to the “Integrations” section, and create a new API Key dedicated to LeadConduit. Copy the key displayed in the “Key” column.

2. Configure the Integration in LeadConduit:
   In your LeadConduit flow, add a new Integration Step and select the CallTools Power Contact Center integration. When prompted, paste the copied API key.

3. Enter Your Login Domain:
   Determine your CallTools Login Domain. For example, if you log in via “https://app.calltools.io/login”, enter “app.calltools.io” in the integration settings.

4. Add the Recipient Step:
   Within the LeadConduit flow editor, open the “Add to Flow” menu, click on “Integration”, choose the CallTools integration, and assign it a unique, descriptive name. This step will handle the delivery of lead data.

5. Map Additional Fields (if needed):
   Review and adjust the outbound field mappings to ensure that any non-standard fields are correctly aligned with the CallTools parameters. By default, LeadConduit maps up to three phone numbers, email, first name, last name, address, city, state, and postal code.

Expected Result:
Your LeadConduit flow will transmit lead data to CallTools, and you will see outcome statuses indicating:

• Success: Data was appended successfully.
• Failure: The service was reachable but encountered an issue processing the request.
• Error: The service is unreachable or an unexpected error occurred.

Validation & Monitoring (optional)

• Test the Setup: Submit a test lead through your LeadConduit flow and verify that the lead appears in your CallTools Power Contact Center with a “Success” outcome.
• Where to Monitor?: Check the LeadConduit events dashboard for delivery statuses and review your CallTools contact center logs for new contact entries.

Best Practices

• Use a dedicated, non‑expiring API Key in CallTools specifically for the LeadConduit integration.
• Double‑check that the CallTools Login Domain exactly matches your login URL (e.g., app.calltools.io).
• Regularly test the integration with sample leads to confirm that standard and any custom field mappings are accurate.
• If additional data is needed beyond the standard fields, configure and validate custom outbound field mappings accordingly.

Troubleshooting

Frequently Asked Questions (FAQ)

Do I need a dedicated API Key for the CallTools integration?

Yes. You must create and use a dedicated, non‑expiring API Key from your CallTools Power Contact Center for the integration with LeadConduit.

What should I enter for the Login Domain?

Enter the domain part of your CallTools login URL (for example, app.calltools.io if your login is https://app.calltools.io/login).

Which fields are automatically mapped by this integration?

The integration automatically maps standard fields, including up to three phone numbers, email, first name, last name, address, city, state, and postal code. Additional fields can be manually mapped if necessary.

What do the integration outcomes indicate?

• Success: Lead data was appended successfully to CallTools.
• Failure: The service processed the request but encountered an issue (details provided in the reason field).
• Error: There was a connectivity issue or unexpected error preventing the request from completing.

Glossary