Imagine this: a new job comes in via the call center, which is located close to service technician A, but far from technician B. B has spare capacity today, and A is booked today but has time tomorrow. You want the API to suggest going with technician A tomorrow because he is closer, rather than technician B today who lives far away.
Yes! What you want to do here is give more importance to the distance traveled than the speed of intervention. And at the same time take into account fairness, skills, availability, travel time, etc. This can be perfectly configured by giving specific weights to the various constraints when posting your solve request.