Featured Success Story
By Product
By Industry
By Use Case
Healthcare Solutions for Salesforce
Learn
Blog
Discover the latest Titan product and company news
Titan 101
Getting started with Titan, Best Practices, and Use Cases!
Titan Academy
Sign up for interactive courses to learn Titan
Webinars
Watch Titan Previous Webinars
Support Documentation
Check out Titan’s latest release notes and product documentation
Integrations
Learn all about Titan's Integrations
Compliance
Learn all about Titan's Certifications
Connect
Customer Success
Read all about Customer Success Stories
Professional Services
Let Titan experts help you take the project to a new level
Titan X Lab
Have a feature request? This is the right place to post and vote for other ideas
Everything you need to know about Titan!
Hawk-eye editor with a passion for trailblazing Salesforce experiences
At some time or the other, you have attended at least one, two, or three webinars. Once you sign up, your information is provided and autofill in your browser.
Do you have a system to ensure that duplicate leads need to be marked as such, with all their information correctly merged and clear notes about any follow-up without creating a new record in Salesforce?
Let’s take it one step further.
What if the same person comes back but now gives you an additional piece of contact info?
Each time a lead must send information to our CRM, we must consistently improve our data or, at the very least, not create more clutter.
Of course, there are different ways to deal with duplicates.
You can have Salesforce handle the duplicates within the system using duplicate rules, which means that the incorrect data already got into your CRM. A duplicate record was created, and you need to clean up the system from the inside.
Whether they’ve been sitting in Salesforce for a while, duplicate leads are begging your attention. So could you give it to them?
We have a solution that makes us one step ahead of the competition.
Sometimes forms not only collect data to create new records but also enable or require fillers to update their data. To efficiently update data and avoid duplicate records, you need to cross-check every filler.
You need to find out if he’s registered as a contact or Lead, and if so – update the information in the relevant object. If he is neither – you need to create a new record.
Titan enables you to create flexible, conditioned Get/Push integrations, where you can try and match your filler entered data against your Salesforce records and only then update the information accordingly.
Since the integration works in real-time, it can make an identification right then and there, auto-populate data if you wish, and then update your Salesforce account.
It simply means the bad data never gets into Salesforce, and no admin has to comb through the database looking for duplicates. It also means your sales reps don’t lose valuable time cross-referencing leads they had a vague memory of seeing a few months earlier.
Titan gives you the flexibility for customers to interact with Salesforce in the way that best fits your business needs.
Choose what field or fields you want to use to check against your current records, and then decide what should happen if there is already a record with that Email, last name, phone number, or whatever data point you chose.
Drag and Drop elements in the form builder onto your canvas to create the user experience you want for collecting lead information.
In this example, we used a straightforward design of text boxes to collect each data point. Let us name the fields, First Name, Last Name, Company, Email, and Phone.
Take note, that on the right-hand side, under element settings, you need to check the mandatory field under the basic settings for Last Name and Company and Email.
Once your form is set up and styled the way you want, head over to your Salesforce Integrations and set your PUSH to Salesforce.
Select the object to that you want to send your data. In this case, we chose Lead because we are creating new leads in Salesforce. However, you can set the action to update so that you can check the Email that the user inputs against other emails already in your Salesforce.
On the right-hand side, toggle “create“ under “if not found any match.”
Click on “Set Conditions” under the update action and decide how you want to identify the Lead against your CRM. Should you want to check the email – choose “Email Equals Email.”
Now we need to map our fields. Mapping fields is the way that you pair up the fields in your form with Salesforce.
Click on “Set Mapping” under “Map Fields” and choose which field you want to send your data to in Salesforce.
Click “Apply & Finish” and then go ahead and publish your form.
Test it out by filling out the form as if you were a user and then go to your integrations logs, at the bottom of the Salesforce Integration tab under settings. Once there you will be able to see if a new record was created or updated based on the rules that you put in place.
Watch the short video where we used the Email field to check against other records in Salesforce. There you can see that if the Email is already in Salesforce we asked it to update the information in that record instead of creating a new lead. This is great in scenarios where leads will sometimes give more contact info upon their second time filling out a form.
It is that simple with Titan, in just a few clicks of your mouse declutter and stop duplicate leads in Salesforce, also available in our Salesforce appexchange page
You can reach out by visiting:
Do you like this Use Case?
Schedule a demo to get started with Titan today!