A lead can be a perfect fit and still land with the wrong person. If that person is booked for three weeks, the route is operationally wrong even when the classification is correct.
Capacity-aware routing adds one practical question to form triage: who can take the next useful step within the response window you promised? It does not ask an AI model to run the business. It gives staff a visible rule for using fit, urgency, and current availability together.
The payoff is simple. Qualified inquiries spend less time waiting in a queue that looks correct on paper but cannot move.
Define capacity as an operating state
Do not start with exact calendars or a complicated workload score. Give each destination a small, controlled state that a manager can update without editing the form workflow.
| State | Meaning | Routing rule |
|---|---|---|
| Open | Can accept new work in the normal window | Use the usual fit and location rules |
| Limited | Can accept only high-value or urgent work | Require a higher fit or urgency signal |
| Paused | Cannot take a new inquiry now | Send to the approved backup or shared review queue |
| Unknown | The state is stale or missing | Do not guess; route to a named human owner |
The state needs an owner and an expiry. “Open until Friday at 5 p.m.” is safer than a switch that nobody remembers to reset.
Score fit and capacity separately
Fit answers whether the inquiry belongs with a team. Capacity answers whether that team can act now. Combining them too early hides the reason for the route and makes a later audit harder.
- Use service, location, budget range, and request type to describe fit.
- Use a current operating state and response window to describe capacity.
- Use urgency only when the form contains a clear signal that staff have agreed to treat differently.
- Keep a manual-review path for ties, missing states, and high-impact exceptions.
The Lead Scoring action can help prepare a fit signal. The Routing Recommendation action can help explain a suggested destination. Your capacity state and final assignment rule should remain visible to the people who own the queue.
Put capacity after classification
A useful sequence keeps the source record intact and makes each decision inspectable:
- Save the original form submission.
- Classify the request by service, location, and other agreed fit criteria.
- Check the destination’s current capacity state.
- Apply the documented backup rule when the preferred destination is limited or paused.
- Record the chosen owner, reason, and response deadline.
This order matters. A temporary staffing change should alter the handoff, not rewrite what the customer asked for or what the inquiry matched.
Keep the routing reason with the work
A route that cannot be explained becomes a support problem. Store a short reason such as “Commercial roofing fit; North team paused; assigned to Central backup until August 30.” That is enough for a reviewer to understand the decision without exposing a raw model response as the main record.
Limit access to submission and routing records to the people who need them. WordPress documents the standard roles and capabilities model; use it as a baseline, then check the permissions provided by the form plugin and review tools on the site.
Give stale capacity a safe default
The dangerous state is not “Paused.” It is an old “Open” value that everybody assumes is current. Add a review time to every capacity update. When it expires, send the next inquiry to a shared queue or named dispatcher instead of silently using the stale route.
Match that fallback to the response promise already attached to the form. If the site says someone will reply within one business day, the capacity process needs an owner who can still meet that window. The form response SLA guide shows how to make that promise explicit.
Test the rule with six submissions
Before using the rule on new leads, run a small redacted test pack. Include a strong fit with open capacity, a strong fit with paused capacity, a weak fit, an urgent request, a tie between teams, and a submission with an expired capacity state.
For each test, write the expected owner and the reason before running it. Review disagreements with the person who manages the queue. Change the rule only when the expected outcome was wrong or the current process could not explain its choice.
Review capacity before predictable changes
Update the states before vacations, campaign launches, service-area changes, and planned project starts. A weekly review may be enough for a steady team. Fast-moving sales or support queues may need a shorter expiry. Pick the slowest rhythm that still prevents stale routing.
Keep one person accountable for the state list. The submission ownership guide is a useful companion when the final handoff itself is unclear.
Capacity-aware routing considers both whether an inquiry fits a team and whether that team can act within the promised response window. The capacity state should be current, owned, and separate from the fit score.
Not by default. AI can prepare fit, urgency, or routing signals, but the business should define the allowed destinations, capacity states, backup rules, and manual-review cases.
Treat a missing or expired state as unknown. Send the inquiry to a named person or shared review queue instead of guessing that the preferred team is available.
Start with one destination list
Choose one high-value form. List its allowed destinations, the owner of each capacity state, the expiry time, and the backup route. Then test the six cases before the next real inquiry depends on the rule.
