Overview
CloseBot is able to update CRM fields automatically when you link objectives to contact fields or properties. If you ever find yourself in a situation where contact fields are not updating to the value that you would expect, start here with this article to dig into why that might be.
Objective Without an Output Variable
Sometimes you may think that you've selected an output variable, but you may not have. Navigate to the objective that should be updating your field or property and click it to see if there's an output variable selected for that objective.
Objective Hasn't Completed (Sensitivity Too High?)
CloseBot will only update a field or property when the objective has completed and it will not back-track to update a field again that it has already passed by. Keep in mind that objectives only complete when the AI checks and determines that it's percent certainty is a number above your selected sensitivity level. See the below example where the sensitivity level on an objective was set high enough that the objective didn't pass, even though it seems like it should have. This is why sensitivity defaults to 50 and is in the advanced settings area of an objective.
Confusing Custom Field or Property Title or Options
CloseBot looks at the title of your field and options (if it's something like a radio button or multi-select) and uses your chosen AI Provider to determine what the update value should be. In the same way that you can click See All Logs to see why your agent said something you can click to see why a field was updated to the value it was.
Summary
The most likely cause of field updates not working the way you'd expect is either confusing field titles and/or options or having turned the sensitivity up too high. Check those things to make sure you're not making some of these common mistakes!