Why use it
Use it when the answer is factual: a field is blank, a booking exists, or a lead is in a certain stage.
Picture this
After a booking attempt, a dental practice checks whether an appointment was actually created. Successful bookings get a confirmation; unsuccessful ones create a staff task.
Set it up
- Choose the single fact to test.
- Write labels that describe the outcome, such as “Booking created.”
- Add a deliberate path for everything that does not match.
- Test each branch with dummy data before adding live actions.
What comes next
After this block, use the matching action, usually an SMS, Email, task, or handoff.
Avoid this when…
Use Classifier when the workflow must interpret what a person means rather than compare a known value.
Before you publish or activate: verify the current builder labels in Votel and test with dummy data. This independent guide describes the purpose and a safe setup approach; it does not replace Votel’s current product documentation or compliance advice.