Why the terms matter
Property-management teams often use the same words for different moments in the workflow. “Fast response,” “qualified lead,” and “handoff” are useful only when the team agrees on what each one means and what happens next.
Editorial scope: This is a practical reference for the workflow terms used across FilterPoint AI’s public resources. It does not report customer results, benchmark data, or legal and emergency guidance.
Core terms
Speed-to-lead
Speed-to-lead is the time between an inquiry arriving and a useful first response or next action. A useful response may be an acknowledgement, an answer, a qualification question, or a routed handoff. Measure it by channel and inquiry type instead of using one universal target. See the speed-to-lead guide for a practical measurement sequence.
Inquiry qualification
Inquiry qualification is the process of collecting enough context to decide what the inquiry needs next and who should own it. The relevant context depends on the request: a viewing inquiry may need property and timing details, while an owner-acquisition inquiry may need portfolio and service expectations.
Intent signal
An intent signal is a detail that helps a team understand the request, urgency, fit, or likely next step. Examples include a requested viewing time, a property location, a move-in window, or a direct request to speak with a person. A signal is evidence to consider, not a guarantee about what someone will do.
Inquiry routing
Inquiry routing is the decision process that sends an inquiry to the right queue, person, or workflow. Good routing uses the team’s approved rules for intent, urgency, location, property, availability, and ownership. It should have a fallback for cases that do not match a rule.
Follow-up ownership
Follow-up ownership means one person, team, or clearly named queue is responsible for the next action. A record can be assigned without being owned; ownership is clear when someone knows what to do, by when, and where the context is recorded. The lead follow-up guide covers this handoff in more detail.
Human handoff
A human handoff is a deliberate transfer from an automated interaction to a person with enough context to continue. The handoff should preserve the inquiry source, request, answers, urgency, promises made, and next action. Automation should support the transfer, not hide the boundary between automation and human judgment.
After-hours coverage
After-hours coverage is the approved response and escalation process used when the usual team is unavailable. It may include acknowledgement, basic information, qualification, urgency detection, and a clear next step. The process should follow existing service and emergency policies rather than improvising a promise. See the after-hours inquiry guide.
Context continuity
Context continuity means keeping the inquiry source, request, answers, decisions, and next action together across the workflow. Without it, a fast first response can still create duplicate questions, missed promises, and unclear ownership.
Qualified inquiry
A qualified inquiry contains enough relevant information for the team to decide its next action or owner. “Qualified” does not necessarily mean “ready to buy” or “ready to sign”; it means the record is actionable for the workflow being measured.
Turn vocabulary into a workflow
| Workflow moment | Question to answer | Useful record |
|---|---|---|
| Capture | Where did the inquiry arrive, and when? | Source, timestamp, contact, and original request. |
| Understand | What is the person asking for, and is anything urgent? | Intent, key details, urgency, and unanswered questions. |
| Assign | Who owns the next action? | Named owner, queue, due point, and routing reason. |
| Continue | What should happen next, and what context must travel with it? | Summary, promised action, status, and outcome. |
When these definitions are used consistently, teams can compare response time, qualification, routing, follow-up, and handoff without collapsing the whole workflow into one vanity number.