Do you guys integrate with Salesforce?
Do you guys integrate with Adobe?
Do you guys integrate with Hubspot?
Do you guys integrate with etc. etc. etc.?
We hear these questions nearly everyday. In an increasingly complex marketing technology landscape it is critical, even necessary, that SaaS tools talk to each other, that they share data, and that they do this seemlessly. So, these questions are natural.
But here’s the thing: these are the wrong questions to ask.
Because the only question that’s really important is this: do you have robust Webhooks functionality and API?
If the answer to that question is ‘yes’ than the answer to ALL of the questions above is also ‘yes.’
Some of our competitors tout their ability to integrate with tools like Salesforce. Obviously, a custom integration with Salesforce is a big deal.
Integrations are important.
Our tool integrates with Salesforce too….but it also integrates with Sugar CRM, Zoho, and any other CRM you can think of. Convirza integrations are not limited to just custom integrations…like Salesforce. We can integrate with any SaaS because we offer Webhooks.
“But wait,” you say. “Custom integrations don’t require any additional work to set up. Webhooks do.”
This isn’t entirely accurate.
If you’ve ever set up a custom integration–even a plug-and-play integration that supposedly requires no set up–you’ll quickly find that significant work is often required.
And, yes, while Webhooks do require some customization, that customization is generally minimal. The amount of development time is minimal. Sending a Webhook to trigger an action within a CRM, for example, takes minutes…not hours.
Oh…and you’ll pay extra for custom integrations.
Webhooks are essentially HTTP posts that carry data into any SaaS or dashboard in the world. This data can simply display OR it can actually trigger actions within the SaaS that receives the data.
Convirza has Webhooks that can send data to any SaaS.
Thus, we don’t spend a bunch of time or energy developing a custom integration with any one tool. Instead, we spend time developing a robust and simple Webhooks functionality so our clients can easily integrate with ANY tool.
Thus, questions like: do you integrate with ‘xyz’ aren’t even applicable. The answer to every question is, yes.
For our competitors to say ‘We integrate with xyz CRM’ is like a runner saying ‘I run on roads’. Well, of course you run on roads. But…hopefully that’s not the only place you can run. Can you run on trails, on tracks, on courses, etc.? Are you able to run when it’s rainy, sunny, and snowing? Or, are you just able to run on roads when it’s 65 degrees?
Individual integrations are limiting.
Again this list is infinitely long because the number of things that can be done with Webhooks in infinitely long. But, we’ll list a few things:
– Webhooks can send and post call detail information like call source or referring campaign into any CRM including Salesforce, Zoho or industry specific CRMs like DealerSocket.
– Webhooks can change prospect information, prospect status, or account data within a CRM.
– Webhooks can send and post call recordings themselves into CRMs.
– Webhooks can post conversion data inside of tools like Marin or Acquisio. A conversion Webhook could be triggered by a call itself, or an actual Converted call that is analyzed by Conversation Analytics. In other words, a conversion could actually be a call that has resulted in a follow-up appointment or a purchase.
– If Conversation Analytics® automation determines that there was a Missed Opportunity on a call–by analyzing the words and phrases spoken on the call itself–a Webhook can be sent to a call center tool or a CRM that automate a call back to salvage the revenue.
– If Conversation Analytics® automation determines that a caller was a good lead–by analyzing the words and phrases spoken on the call itself–a Webhook can be sent to a marketing automation platform that triggers an email that’s sent to the caller. Or, a Webhook could even assign the lead to an entirely different email series.
– If Conversation Analytics® automation determines that the caller is price senstive–by analyzing the words and phrases spoken on the call itself–it can send a Webhook to a mobile retargeting tool that only displays ads that talk about low pricing to that specific caller.
– Webhooks can be triggered if Conversation Analytics® automation hears that the agent was not polite on the call. These Webhooks can trigger learning modules from an LMS.
You get the idea. Why limit yourself to just one or two integrations when Webhooks allow integration with every SaaS?
Integrations don’t matter. Automation does.