Product architecture

How Altum Drive turns leads into sales.

A walkthrough of every component in the pipeline — from the landing-page form to the BDC dashboard — and how the qualification engine routes each lead.

Question scoring engine

Routing filters (A / B / Reject)

Locations operating in parallel

End-to-end flow

🌐

Landing page

5-question form

Scoring engine

Route A / B / Reject

CRM record

Stored with score & history

Auto-greeting + agent

Dealer follow-up

Appointment & sale

Qualification engine — scoring rules

Question	Inputs	Max points
Credit score	Excellent / Good / Fair / Poor / None	30
Down payment ($)	0 → 7,500+ (linear)	25
Bank account	Yes / No	15
ID type	License / Matrícula / Passport / None	15
Trade-in vehicle	Yes / No	15

Filter A

≥ 70 points · High-priority, fast-track to appointment

Filter B

40–69 points · Worth fighting for, nurture via WhatsApp

Reject

< 40 points · Polite decline, archived

Multi-location

Houston, TX and Wheeling, IL operate as independent data domains with their own inventory, BDC team, and metrics — rolled up at the manager level.

WhatsApp via 360dialog

Inbound webhooks land in the agent inbox in real-time. Outbound templated messages auto-trigger on status change (created, qualified, appointment, no-show).

Auto-replies & nurture

A bot sends greeting and re-engagement messages in Spanish. The BDC team takes over once the lead replies.

Notifications & SLAs

Leads idle > 2h trigger a manager alert. Filter A leads route to the next available agent within seconds.

Data model

Lead

Table

· id
· name
· phone
· email
· location
· score
· filter
· status
· source
· createdAt

Vehicle

Table

· id
· make
· model
· year
· price
· miles
· location
· status
· vin

WaMessage

Table

· id
· leadId
· from
· body
· at

Activity

Table

· id
· leadId
· type
· text
· at
· by

User

Table

· id
· name
· email
· role
· location

Dealership

Table

· id
· name
· address
· phone
· lng
· lat