Leads are entering RD CRM for the wrong salesperson

Created by Andre Greiner, Modified on Mon, 6 Mar, 2023 at 2:08 PM by Andre Greiner

Did THAT prospecting job and the lead went to the wrong salesperson in RD CRM? Calm down, we will guide you to the solution here ;)


Let's pass here all the points that need conference. Save these images to send us, in case it is not possible to solve everything through the article ;)


First of all, let's review the URL:

https://api.exactsales.com.br/rd/v1/SEUTOKEN/


This YOURTOKEN part is your Exact Spotter account token, you can find this information in the integrations menu .


So whenever you see YOURTOKEN in our materials, that's the code we're talking about, okay? Now, come on!


1st Conference: Check if the sellers are integrated

Yes, I know it sounds obvious, but the integration can be undone and that way, the salesperson doesn't receive the lead in the CRM.


Some terms and privacy policy updates break automation, forcing the user to manually re-allow communication between systems.


2nd Check:   Check if the sellers tokens are correct or repeated

Hypothesis: if two sellers are registered with the same token, only 1 of them will receive it, and it will be the seller whose token registered in Spotter corresponds to the token of that seller in the RD CRM.


3rd Conference:   Access the article  Clicking Here  and see how to properly integrate with RD CRM.

Some step may have been missed along the way, reviewing the integration can help you find the problem quickly and efficiently.


But if everything is still right in the settings and the lead does not go to the correct seller, remember to take images of all these screens and send them to us via chat or email. Without them, we won't be able to continue your service, okay?


Hope this helps. To the next!

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article