A wholesaling team sends offers across a full batch of listed properties. When replies come back, straight acceptances stay in the automated path, counters go to an acquisition manager, and anything that asks for a call gets surfaced immediately.
Dottid AI Glossary
Lead Routing
Definition
Lead Routing
Lead routing is the process of sending each lead or inbound response to the right person, queue, or workflow path based on rules you set. In acquisition teams, that usually means deciding which replies need immediate human review, which can stay in an automated flow, and which should move to the next step in the offer process.
In high volume acquisition, response handling gets messy fast. A clean routing setup keeps promising replies moving, keeps objections from stalling, and keeps humans focused on the conversations that actually need judgment. Without it, good opportunities sit in inboxes, follow up gets inconsistent, and the team loses speed where speed matters most.
Lead routing shows up right after an offer goes out or when an inbound reply comes back. A system can route a seller or listing agent response by type, for example a straight acceptance, a counter, a request for proof of funds, or a message that needs context before anyone answers. In Dottid AI's acquisition workflow, that routing layer helps teams process a large stream of replies without treating every message the same. The agent can keep routine states moving, surface real negotiation moments, and hand off only the cases that need a person to weigh in. In an underwriting API setup, routing can sit around the API output, sending certain property cases into a human review queue after ARV, rehab, or MAO comes back from the underwriting layer.
A response from a listing agent includes a price counter and a note about closing timeline. The routing rule sends it to the human closer instead of leaving it in the general inbox with the rest of the reply volume.
A PropTech builder plugs Dottid AI's underwriting API into its own system. The API returns ARV, rehab, and MAO, and the builder routes properties above a margin threshold into a human review queue while the rest continue through its internal pricing workflow.
Is lead routing only about inbound replies?
No. It can also route new leads, underwriting cases, offer states, and follow up tasks. In acquisition workflows, routing is the rule layer that decides what happens next, whether that is automation, review, or a direct handoff.
How is lead routing different from lead filtering?
Filtering removes records. Routing moves records to the right place. In a serious acquisition workflow, the goal is usually to keep volume moving, not cut the set down early.
Where does routing sit in Dottid AI's workflow?
In the agent product, routing sits around underwriting, offer sending, response monitoring, and escalation. In the API product, routing is something the customer can build around underwriting outputs, since the API itself returns pricing logic and deal outputs rather than running the full outreach workflow.