Feature Snapshot
Summary:
Trestle Add‑Ons are pre‑built LeadConduit integration steps that leverage Trestle’s advanced data validation and enrichment technology to verify, normalize, and enhance lead address and contact details before they proceed further in your flow.
Key Benefits:
- Improves lead data quality by rigorously validating and standardizing physical address components.
- Reduces costly errors by ensuring incoming lead addresses are canonicalized for downstream processing.
- Enhances lead conversion potential with enriched details, including validated addresses and confirmed contact information.
Typical Use Cases:
- Verifying customer addresses before shipping or service delivery.
- Confirming that leads’ contact details match the intended recipient using right party contact verification.
- Appending normalized address fields (e.g., Street, City, ZIP+4, latitude, longitude) to lead records before CRM integration.
How the Trestle Add‑Ons work?
Trestle Add‑Ons operate as dedicated steps within your LeadConduit flow. When activated, these add‑ons send submitted address details (and optionally contact data) to Trestle’s external API. The Trestle Address Validation add‑on examines components such as street, city, state, and postal code, then returns a normalized, validated address along with supplementary data like ZIP+4, latitude, and longitude. In parallel, Trestle offerings for right party contact verify that the lead data matches the intended recipient. The validated and enriched data is then appended to the lead record for subsequent filtering, routing, or final delivery.
Step‑by‑Step Instructions
- Log into LeadConduit and open the desired flow, then navigate to Edit Flow.
- Click “Add to Flow > Add-Ons” and select the appropriate Trestle Add‑On (e.g., “Trestle: Address Validation” or “Trestle: Right Party Contact”) from the add-ons library.
- Configure the add‑on by selecting the parameters required to flag specific responses as failures.
- Drag and drop the newly added step to the correct position in the flow—ideally after any preliminary enhancement steps that supply necessary data.
- Click “Finish” and save your flow.
Expected Result:
Incoming leads are processed by the Trestle Add‑On, which appends normalized address components (such as Street Line 1, City, Postal Code, ZIP+4, State, Country Code, Latitude, and Longitude) and validation statuses to the lead record.
Validation & Monitoring (optional)
- Test the Setup: Submit test leads featuring both valid and intentionally flawed address data to verify that accurate normalization occurs and that invalid data is flagged appropriately.
- Where to Monitor?: Review the Flow’s Events tab and integration logs to track appended fields, success statuses, and error messages returned by the Trestle Add‑On.
Best Practices
- Position the Trestle Add‑On after any enhancement steps required to supply prerequisite data (e.g., raw address components).
- Regularly monitor lead event logs to promptly catch integration errors or unexpected warnings from Trestle.
- Choose the appropriate Trestle Add‑On variant based on your needs—use Address Validation for standardizing physical addresses and Right Party Contact for verifying lead recipient details.
- Document your add‑on configuration, including parameter settings and expected outcomes, to facilitate troubleshooting and future updates.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| Missing normalized address fields in lead record | Submitted lead did not include all required address components (e.g., street, city, ZIP) | Ensure every lead submission contains the complete set of required address details. |
| Trestle Add‑On returns an error status | Invalid API credentials or mis‑configuration of the add‑on parameters | Verify your Trestle API key, check network connectivity, and review the integration settings. |
| Unexpected validation warnings (e.g., “Address Not Found”) | Incorrect or improperly formatted address data leads to validation issues | Reexamine the submitted address details for typos or formatting errors; adjust configuration if needed. |
| No enriched data appears in the lead record | The add‑on step is placed too early or missing prerequisite data from previous steps | Confirm that the Trestle Add‑On is correctly positioned after steps that provide necessary input data. |
Frequently Asked Questions (FAQ)
Q: What are Trestle Add‑Ons?
A: They are pre‑built integration steps in LeadConduit that call Trestle’s external API services to validate, standardize, and enrich lead address and contact data, ensuring high-quality data before subsequent processing.
Q: Why are Trestle Add‑Ons important?
A: By ensuring that the data entered is accurate and standardized, Trestle Add‑Ons help reduce errors, improve downstream data quality, and enhance overall lead conversion rates.
Q: How do I add a Trestle Add‑On to my flow?
A: Edit your flow in LeadConduit, click “Add to Flow > Add-Ons”, select the desired Trestle add‑on from the add-ons library, configure it with filtering parameters, then position and save the flow.
Q: Which Trestle Add‑On should I use for verifying addresses?
A: Use the “Trestle: Address Validation” add‑on to normalize and validate physical addresses. For confirming that contact details match the intended recipient, opt for the “Trestle: Right Party Contact” add‑on.
Q: Can Trestle Add‑Ons improve my lead data quality?
A: Yes, they append verified and standardized address fields to your lead data, reducing processing errors and enabling more efficient downstream filtering and routing.
Q: What is a good Trestle Real Contact grade, and how do grades work?
A: Trestle provides five grades, from A to F, that determine the quality of the lead and whether it is contactable. A Grade E or F lead is considered a bad lead and should be deprioritized, while a Grade A lead is considered real, contactable, and should be prioritized.
| Grade | Meaning |
|---|---|
| A | The phone provided is valid and connected with consistent activity in the last 12 months and belongs to the person’s name provided, meaning the lead is who they say they are. |
| B | The phone is valid and connected; however, the name doesn’t match the subscriber name data in Trestle’s database but is a Mobile number. This can still be a good lead and might be the case that the phone is part of a family plan, and hence Trestle has a different subscriber name associated with the phone. Depending on the team’s bandwidth, these leads can be accepted but should be prioritized below Grade A leads. |
| C | The phone is valid and connected; the name doesn’t match the subscriber data in Trestle’s database and is a Landline or FixedVOIP. Generally, these leads are difficult to reach and should be prioritized relatively low. |
| D | The phone is valid, but the associated activity has been inconsistent, or it can be a Tollfree/Premium number which generally indicates it is a bad lead. Typically, these leads should be deprioritized along with Grade E leads. |
| E - F | The phone is invalid or disconnected or a Nonfixed VOIP (Google Voice or Twilio number) phone not associated with anyone in Trestle’s database. These leads should be deprioritized. |
Q: What is a good Trestle Activity Score, and what should be typical cut-offs for good/bad leads?
A: Trestle’s activity scores range from 0 to 100. A score of 100 means consistent activity in the last 12 months, and a score of 0 means a disconnected number or no activity has been seen in the past year.
An activity score of 70 or above means there is a high confidence that the phone is connected, assigned to a subscriber, and someone has been taking calls consistently.
An activity score of 30 or below means there is a high confidence that the phone is either disconnected or no one will answer the call when the number is dialed in.
An activity score of 50 means Trestle doesn’t have enough signals to predict whether the phone is connected or disconnected/inactive.
If you want to filter leads based on the activity score, the following rules can be recommended:
- Prioritize dialing good numbers with consistent activity: Scores 70 or above.
- Weed out leads with disconnected/inactive numbers: Scores of 30 or below.
Q: Which Trestle Add-On should I choose based on my use case?
A:
| Add-On | Typical Requirements | When to Use / Pain Points |
|---|---|---|
| Phone Validation | Phone number validation and identifying whether a phone number is active or disconnected. | Complaints of disconnected phones (invalid or not in service) and looking for a simple, lightweight solution. |
| Address Validation | Address validation and standardization. | Address data inconsistently formatted or invalid. |
| Caller Identification | Phone append to understand the owner’s name, address, and demographics. | Append name and address data to lead for verification or workflow optimization. |
| Real Contact | Validate and verify multiple lead inputs to assess the contactability of a lead. | Filter out the leads most unlikely to be reachable. |
| Right Party Contact | Verifies if the lead name information matches Trestle’s database. | Verify phone ownership as a compliment to TrustedForm.sed to authenticate requests to Trestle’s external API services. |
Q: How can I access all the data fields provided in the Technical Details from Right Party Contact response?
A: Right Party Contact is a lighter version of Trestle’s Real Contact service with a lower price, to get access to the complete set of response fields, you should use the Real Contact Add-On instead.
Glossary
| Term | Definition |
|---|---|
| Trestle Add‑On | A pre‑built integration step in LeadConduit that leverages Trestle’s data services to validate and enrich address data. |
| Address Validation | The process of verifying, standardizing, and enriching physical address information to ensure its correctness and usability. |
| Right Party Contact | A verification process that confirms whether the provided contact details correspond to the intended lead recipient. |
| API Key | A unique identifier used to authenticate requests to Trestle’s external API services. |
- trestle-addons.png100 KB
Comments
0 comments
Please sign in to leave a comment.