Arrow Define the minimum useful inquiry
List the fields needed to identify the request and route it responsibly. Choose a duplicate key appropriate for your business; this tool does not connect to a CRM or check actual duplicates.
Free tool05 / Reliable handoffs ↗Every request needs
Every request needs
a responsible next step.
Define what a complete inquiry looks like, who should own it and what happens when a rule does not match. Test a fictional lead before handing the blueprint to your implementation team.
Your inputs
Build and test lead routing rules.
Define lowercase field names, then ordered exact-match rules in CSV. Every rule field and duplicate-key field must be required. Test with synthetic JSON data. The first matching rule wins.
Fictional property-diagnostics data for demonstration. These are not France DPE results or business facts.
Order the ownership rules
Rules compare one field with one exact value after case and whitespace normalization. When several rules match, the lowest priority number wins. Provide a fallback owner for every unmatched case.
Test incomplete, duplicate and unmatched paths
Use the simulator and the exported test checklist. The blueprint requires review before outbound messages, price commitments and booking confirmation. A response goal is your target, rather than an enforced service-level agreement.
Calculation rules & scope
The builder validates the rule table, blocks repeated field-value conditions and tests the lead JSON locally. Required fields must be non-empty strings or finite numbers. Duplicate keys are encoded normalized value arrays, avoiding ambiguous concatenation. A duplicate checkbox simulates an existing record; it does not query a database. Retry and review steps in the blueprint are requirements for implementation, not running integrations.
Across industries, from question to action.
A property service can route by location before specialty, or reverse that order if specialist handling has priority. A SaaS team can route by plan or request type. A hotel can route by property. Make the precedence explicit, then review real exceptions before enabling actions in a connected system.
For the property-diagnostics example, explore the France DPE case study: public source quality and an actionable request belong in the same journey. The sample values in this tool are fictional.
Good questions.
Clear answers.
Will the tool send messages or change CRM records?
No. It generates and simulates a blueprint in your browser. The exported plan still needs implementation, integration credentials and testing in your chosen systems.
What happens if two routing rules match?
The first matching rule in the CSV wins. Priority follows row order, starting at one. The simulator displays the chosen priority and owner.
How are duplicate requests handled?
The plan defines a normalized composite key. The simulator can model a known duplicate with a checkbox; actual duplicate lookup must be implemented in the connected system.
Can AI decide prices or confirm appointments?
This blueprint requires human review before outbound messages, price commitments and booking confirmation. AI-assisted summarization or drafting can be scoped separately within approved business information.
Continue the loop
All free tools ↗The next useful move.
02 — AI Systems / scoping
Automation Capacity Calculator
Model automation with review and exceptions.
Workload scenarios + capacity reportOpen tool ↗
GEO / source quality
Brand Facts Checker
Check conflicting business facts.
Conflict report + source-of-truth JSONOpen tool ↗
Your next step / Arrow review
Make the result actionable.
Tell us what you want to improve with Lead Routing Blueprint Builder. Your request goes to the Arrow team. You choose whether to include a short result summary.