LeadExec
The Taalk Certified LeadExec Plugin enables seamless integration between Taalk’s AI-powered engagement platform and LeadExec by ClickPoint Software—a robust lead distribution system. This plugin allows you to route leads captured through Taalk directly into your LeadExec instance using a standardized and secure POST interface.
Whether you’re managing high-volume lead funnels or real-time campaign responses, this plugin ensures leads are enriched, properly formatted, and automatically distributed via LeadExec’s powerful routing logic.
🔧 Use Case
This integration is ideal for customers who want to:
•Connect real-time lead engagement captured via Taalk AI Agents to a downstream lead distribution engine.
•Automate routing of qualified prospects to the right teams or systems using LeadExec rulesets.
•Reduce manual handoff and increase lead-to-contact velocity in B2C or B2B workflows.
API Endpoint
POST https://lets.taalk.ai/api/proxy/leadexec
This endpoint acts as a secure proxy that transforms and routes structured lead data from Taalk into LeadExec’s system.
📨 Payload Schema
All fields below are either captured directly via Taalk’s AI Agents or enriched via backend contact enrichment.
Security
•This plugin requires a valid SecretKey which acts as an authentication token.
•All data is transmitted via HTTPS to ensure end-to-end encryption.
•Taalk’s proxy server logs errors and successes for auditability but does not store PII unless explicitly configured for compliance or QA.
✅ Example Use Flow
1.A Taalk AI Agent completes an outbound voice engagement with a user.
2.Based on the campaign logic, the AI agent collects or confirms key contact attributes.
3.Taalk formats this data into the expected payload and issues a POST to the leadexec endpoint.
4.LeadExec receives the data and routes it based on rules configured in the client’s LeadExec system.
{ "FirstName": "<firstName>", "LastName": "<lastName>", "Phone": "<contact.localPhone>", "ConferencePhone": "<conferenceNumber>", "Email": "<Taalk_Email>", "Address": "<Taalk_Address>", "City": "<Taalk_City>", "Zip": "<Taalk_Zip>", "State": "<Taalk_State>", "Country": "US", "ClientsPreferredLanguage": "<Taalk_Client_Language>", "GroupCode": "<Taalk_GroupCode>", "GroupName": "<Taalk_GroupName>", "DateLeadReceived": "<Taalk_DateLeadReceived>", "LeadId": "<Taalk_Lead_Id>", "LeadSource": "<Taalk_Lead_Source>", "ResponseCardURL": "<Taalk_ResponseCardURL>", "SecretKey": "<Taalk_SecretKey>", "Beneficiary": "<Taalk_Beneficiary>", "RefferedBy": "<Taalk_Referred>", "BeneficiaryRelationship": "<Taalk_Relationship>", "Market": "<Taalk_Market>", "SponsorOrg": "<Taalk_SponsorOrg>", "LID": "<Taalk_LID>"}
💡 Note: Fields prefixed with Taalk_ are dynamically populated from either the contact record or the AI Agent’s engagement flow.
🧪 Testing & Validation
To validate integration:
•Use Taalk’s internal sandbox mode to simulate POST calls.
•Confirm successful lead acceptance by checking LeadExec’s inbound lead logs.
•Monitor failed requests or transformation errors via Taalk’s integration logs dashboard.
📘 See Also
•Taalk Platform: AI Agent Configuration KB (internal)
•Contact Enrichment Settings