Lead routing and delivery · hosted in Canada
A lead posts once. RouteDeck normalizes it, walks your tiers in order, and sends it to the buyer that matched as ADF and branded email. The rule version that decided is stamped on the record, so when a dealer calls to ask why he got it, you read him the answer.
RouteDeck is pilot stage with a Canadian auto finance lead company. Every screen on this page is the shipped product, running the demo workspace. No customer data, no borrowed logos.
Diagram: a lead posts to one intake endpoint, descends a tier ladder that evaluates rules in order, and is delivered to the buyer whose tier matched first. A partial lead waits in Falloff and re-enters routing once it completes. A complete lead that matches no tier waits in Catchall and is worked in the built in CRM.
lead type · auto finance applications
Send the same reference twice and the second post enriches the first lead. Partials go early and complete later. A phone or email match against someone already on file is stored as a linked repeat, never dropped, never quietly re-sold.
POST /api/intake/leads
x-api-key: rd_live_········
{
"reference": "apply-2026-07-24-8831",
"fields": {
"province": "Alberta",
"monthly_income": "$5,400.00",
"credit_consent": "Yes"
},
"consent": { "text": "I consent to a credit check", … }
}
200 { "status": "accepted", "outcome": "tiered:Near prime" }
200 { "status": "updated" } // same reference, same leadFour stages between a form submit and a buyer saying thanks. Scroll and the ladder walks itself.
An application dies half finished at 11pm. Most systems throw it away. RouteDeck keeps the partial, holds it in Falloff for the window you set, and completes it the moment the rest of the fields land under the same reference. Money, phones, provinces and durations normalize on the way in, and the raw value you sent stays on the record.
idempotent on reference · unparseable values flag, never reject · CASL consent snapshot with ip, url and timestamp
Tiers evaluate top down. The first rule that fits places the lead and stops the walk. Rules are data you edit in the browser, in plain language you can read out loud, and every save mints a new version. The lead carries the version number that decided it, forever.
dry run any lead before you save · pause a tier without losing its rung · completeness rules gate the walk
ADF plus branded email to the buyer that won. Failed attempts retry on their own. A dead buyer falls back to the next in line. Delivery windows keep leads out of a closed dealership at 2am, multi sell respects exclusivity, and an approved return can redistribute instead of becoming a credit memo.
every attempt is a row you can read · return windows per buyer · retries with backoff
A complete lead that matched no tier is not a report footnote. It waits in Catchall as a queue your team works, with tasks, notes and an owner. Stalled partials sit in Falloff. Both re-enter routing with one tap once something changes. Nothing goes silent, which is the whole reason this exists.
queues, not exports · re-route without re-typing · append only history on every hop
Note from Dana: called at 9:10am, she has a co signer. Asked her to re submit with the co signer income.
Nova Scotia has no buyer yet. Two more like this and tier #5 gets a province added.
Catchall and Falloff are queues on a board, not rows in a report. Sequences, texting through your own Twilio or Telnyx number, tasks that feed a calendar your phone subscribes to, and a mobile app your reps install with push.
Texting is yours. Bring your own Twilio or Telnyx credentials and your own number. Threads land on the lead, not in somebody’s personal phone.
Tasks reach the phone. Appointments publish to a calendar feed your reps subscribe to, so the 4pm callback shows up next to their kid’s game.
Installable. The CRM is a PWA with push. A rep working Catchall from a truck gets the same queue as the desk.
Demo workspace, July 2026. Imported history is folded in and labelled as imported, never blended into a growth claim.
| tier | sold | returned | net |
|---|---|---|---|
| #1 Prime AB / SK | 412 | 6 | 406 |
| #2 Near prime | 733 | 21 | 712 |
| #3 Subprime, sells ×2 | 468 | 33 | 435 |
| Catchall, unsold | 81 | · | · |
Spend comes from the ad account, revenue from the tier that placed the lead. One screen answers whether the campaign is worth running tomorrow.
Four claims, and the record each one leaves behind. Open any lead in a trial workspace and these are the fields you will find on it.
The exact wording shown, when, from where, and on which page. An unsubscribe applies before the next send rather than after somebody complains.
Not free text somebody typed as ALB. Hosted forms adapt per province, and routing Quebec differently takes one rule and no developer.
Income and date of birth are not readable by everyone who can open the lead. A rep sees what their role allows and the rest stays masked.
sensitive fields encrypted one by one, with rotatable key versions
Nothing edits the past. Every hop a lead takes is a row somebody can read back to a buyer six weeks later, in order.
The database, the file storage and the backups all run in a Montreal data centre, and the app itself runs in that region too. Outbound email is the exception: our sending provider processes it in the United States. A dealer principal asking where his customers’ income and dates of birth live gets one answer with a city in it, and the exception in the same breath.
written for PIPEDA · Quebec Law 25 · CASL
None of this is a feature you will use. It is the list your buyer’s IT person asks for before they will accept a lead feed, and the reason a bad afternoon is recoverable.
coming soon · app store and google play
RouteDeck CRM is being packaged as a real app for iPhone and Android. Same account, same contacts, same history. You sign in and your deck is already there.
one email when it ships · nothing else
tap to call, logged
The call goes out from your phone and writes itself into the history, with the duration.
camera onto the record
Photograph a signed page in the driveway and it attaches to the lead before you drive off.
showings on your calendar
Book a showing in the app and it lands in the calendar your phone already wakes you up with.
face id, with a way around it
Biometric unlock for a phone that gets handed around, and a password fallback every time.
The app is the CRM. Routing setup, the tier ladder and the rule builder stay on the desktop, where that work belongs.
Today’s deck
Wed Jul 29 · 18 waiting
iphone · app store
history · nothing typed twice
logged from your phone, on the record, no typing
confirmed Thursday at 6:30, Willow Ct
wants the garage, will not go over 640
Thu 6:30p, written to your phone calendar
4 listings, 3 bed under 620k, Sherwood Park
galaxy · google play
hover to look around · click a phone to bring it forward
included in the trial
Prove the routing before you pay for it.
$149 a month
For shops moving real daily volume.
$299 a month
Headroom for growing lead desks.
$599 a month
Volume pricing for full-scale operations.
Every figure on the pricing page renders from the admin plans catalog. A dollar amount typed into a page fails the build.
where this stands, july 2026
RouteDeck runs a Canadian auto finance lead company today. That is one pilot, not a customer list, and I am not going to pretend otherwise on my own homepage.
So here is the offer instead. Point one source at the intake endpoint, add one buyer, and build the two tiers you argue about most. If the first routed lead does not feel like relief, close the tab and keep what you have.
If it does, the rest of the machine is already built and waiting behind the same login.
30 day trial · no card · your data is stored in Canada
Selling the leads is one half. Working them is the other.
The CRM inside RouteDeck is also sold on its own, by vertical, to the realtors and dealerships your leads land on.