Delivery Methods
Detailed instructions for configuring all delivery method types in LeadExec
By Chris and 1 other2 authors78 articles
Introduction to Delivery Methods
Overview of Delivery Methods
Webhook Delivery Method
Instructions on how to configure Webhook Delivery Methods
- Webhook Delivery Method ConfigurationSend leads via JSON, XML, or HTTP requests with real-time integration
- Webhook URL Endpoint TabConfigure where and how leads are delivered to your integration
- Webhook Authentication TabSecure your lead deliveries with multiple authentication options such as Basic, Digest, Bearer Token, and OAuth 2.0 authentication
- Webhook Field MappingsWebhook field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.
- Webhook Request Body TabJSON and XML schema configuration in the Webhook Request Body Tab
- Webhook Response Settings TabWebhook Response Settings tell LeadExec what to look for when searching the client’s response for an accepted lead.
- Webhook Retry Settings TabUse the Webhook Retry Settings to tell the system to retry delivery for failed delivery attempts.
- Webhook Portal Permissions TabClient Portal user webhook settings for IVR calls, File Attachments, and Analytic Data.
- Webhook Delivery Schedule TabThis tab allows you to create a specific schedule of when the client will be considered for lead delivery.
- Webhook Notifications TabUse the Webhook Notifications Tab to create notifications for you or another team member for failed deliveries to the client.
Ping-Post Delivery Method
Instructions on how to configure Ping-Post Delivery Methods
- Ping-Post Delivery MethodInital steps for creating an outbound Ping Post delivery method
- Ping Post URL Endpoint TabSet up the destination and format for complete lead data delivery
- Ping-Post Authentication TabsUse Basic, Digest, Bearer Token, and OAuth 2.0 authentication types in the Ping-Post Authentication Tabs.
- Ping-Post Field MappingsThe Ping-Post field mappings tabs allow you to configure the field names the receiving system expects to the fields set on your lead type.
- Ping-Post Request Body TabLearn more about the proper JSON and XML schema configuration in the Ping and Post Request Body Tabs.
- Ping Post Response Settings TabPing Post Response Settings tell LeadExec what to look for when searching the client’s response for an accepted lead.
- Ping Post Retry Settings TabUse the Ping Post Retry Settings to tell the system to retry delivery for failed delivery attempts.
- Ping Post Portal Permissions TabClient Portal user ping post settings for IVR calls, File Attachments, and Analytic Data.
- Ping Post Delivery Schedule TabUse the Ping Post Delivery Schedule Tab to create a specific schedule of when the client will be considered for lead delivery.
- Ping Post Notifications TabUse the Ping Post Notifications Tab to create notifications for you or another team member for failed ping-post deliveries to the client.
- Setting Up a Ping Post Lead Delivery in LeadExecLearn how to configure ping post delivery methods in LeadExec
Email Delivery Method
Instructions on how to configure Email Delivery Methods
- Email Delivery Method ConfigurationThis method delivers lead details in the body of an email template, including a Client Portal link.
- Email Field MappingsEmail field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.
- Email Delivery Email TemplateCreate a custom email template to send your client lead data
- Email Delivery SettingsTo and From settings for lead email delivery.
- Email Retry Settings TabUse the Email Retry Settings to tell the system to retry delivery for failed delivery attempts.
- Email Portal Permissions TabClient Portal user email settings for IVR calls, File Attachments, and Analytic Data.
- Email Delivery Schedule TabUse the Email Delivery Schedule Tab to create a specific schedule of when the client will be considered for lead delivery.
- Email Notifications TabUse the Email Notifications Tab to create notifications for you or another team member for failed email deliveries to the client.
SMS Notification
Instructions on how to configure SMS Notification Delivery Methods
- SMS Notification Delivery MethodDelivers the lead details in the body of an SMS text message template with a portal link.
- SMS Field MappingsSMS field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.
- SMS Template TabSMS Template Tab
- SMS Delivery SettingsPhone number settings.
- SMS Retry SettingsSMS Retry Settings
- SMS Portal Permissions TabClient Portal user SMS settings for IVR calls, File Attachments, and Analytic Data.
- SMS Delivery Schedule TabCreate an SMS Delivery Schedule of when the client will be considered for lead delivery.
- SMS Notifications TabUse the SMS Notifications Tab to create notifications for you or another team member for failed deliveries to the client.
FTP Delivery Method
Instructions on how to configure FTP Delivery Methods
- FTP Delivery Method ConfigurationProvides the ability to drop an Excel, CSV, or TXT file to an external FTP server.
- FTP Field MappingsFTP field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.
- FTP ServerFTP server endpoint settings
- FTP AuthenticationFTP credentials
- FTP Retry SettingsUse the FTP Retry Settings to tell the system to retry delivery for failed delivery attempts.
- FTP Portal Permissions TabClient Portal user FTP settings for IVR calls, File Attachments, and Analytic Data.
- FTP Delivery Schedule TabUse the FTP Delivery Schedule Tab to create a schedule of when the client will be considered for lead delivery.
- FTP Notifications TabCreate notifications for you or another team member for failed deliveries to the client
CSV Attachment
Instructions on how to configure CSV Attachment Delivery Methods
- CSV Attachment Delivery MethodDelivers individual leads in a CSV file attachment via email.
- CSV Field MappingsCSV field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.
- CSV Attachment Delivery Settings TabCSV Attachment Delivery Settings Tab
- CSV Retry Settings TabUse the CSV Retry Settings to tell the system to retry delivery for failed delivery attempts.
- CSV Portal Permissions TabClient Portal user CSV settings for IVR calls, File Attachments, and Analytic Data.
- CSV Delivery Schedule TabUse the CSV Delivery Schedule Tab to create a specific schedule of when the client will be considered for lead delivery.
- CSV Notifications TabUse the CSV Notifications Tab to create notifications for you or another team member for failed CSV deliveries to the client.
Batch Delivery Method
Instructions on how to configure Batch Delivery Methods
- Batch Delivery MethodScheduled delivery designed to send all leads received during a set time frame via email with an excel of CSV attachment.
- Batch Delivery Mappings TabBatch Delivery field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.
- Batch Delivery File Settings TabFile settings for batch delivery can vary based on your client’s requirements. This tab is used to configure the file settings.
- Batch Delivery Second File Settings TabThis tab allows you to configure the second file settings.
- Batch Delivery Email TemplateCreate a custom template for your Batch Delivery email.
- Batch Delivery Delivery Settings TabTo and From settings for lead email batch delivery.
- Batch Delivery Batch ScheduleSet the schedule of the Batch Delivery
- Batch Delivery Portal Permissions TabClient Portal user batch delivery settings for IVR calls, File Attachments, and Analytic Data.
- Batch Delivery - Delivery ScheduleUse the Batch Delivery Tab to create a specific schedule of when the client will be considered for lead delivery.
- Batch Delivery Notifications TabUse the Batch Delivery Notifications Tab to create notifications for you or another team member for failed batch deliveries to the client.
SalesExec Integration
Instructions on how to configure SalesExec Integration Delivery Methods
- SalesExec Integration Delivery Method ConfigurationBidirectional delivery to SalesExec.
- SalesExec Integration URL Endpoint TabIn the SalesExec Integration URL Endpoint tab, you will set where the leads post and what content is being sent.
- SalesExec Authentication TabUse Basic, Digest, Bearer Token, and OAuth 2.0 authentication types in the SalesExec Authentication Tab.
- SalesExec Integration Field MappingsIntegration field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.
- SalesExec Integration Request Tab
- SalesExec Integration Response Settings TabIntegration Response Settings tell LeadExec what to look for when searching the client’s response for an accepted lead.
- SalesExec Integration - Retry Settings TabUse the Integration Retry Settings to tell the system to retry delivery for failed delivery attempts.
- SalesExec Integration - Portal Permissions TabClient Portal user integration settings for IVR calls, File Attachments, and Analytic Data.
- SalesExec Integration - Integration Options TabThe LeadExec integration with SalesExec allows you to receive updates back from SalesExec when actions or updates take place.
- SalesExec Integration - Delivery Schedule TabUse the Integration Delivery Schedule Tab to create a schedule of when the client will be considered for lead delivery.
- SalesExec Integration - Notifications TabUse the Integration Notifications Tab to create notifications for failed integration deliveries to the client.
Lead Portal
Instructions on how to configure Lead Portal Delivery Methods
- Lead Portal Delivery MethodFor clients who only access leads through the client portal.
- Portal Permissions TabClient Portal user settings for IVR calls, File Attachments, and Analytic Data.
- Lead Portal Delivery Schedule Tab
- Lead Portal Notifications TabUse the Lead Portal Notifications Tab to create notifications for you or another team member for failed deliveries to the client.