● Demo 01 · Lead triage
An enquiry lands.
Everything else is automatic.
Paste a customer message — a real one, or one of the samples. The pipeline extracts the commercial facts, scores the lead with rules you can inspect, and decides who should own it.
Pipeline
trigger → extract → score → route
0 / 4000
What it actually does
- Extracts. A language model reads the message and returns a fixed schema: intent, urgency, budget, company size, decision-maker flag.
- Normalises. Every value is coerced into an allowed set. A model that invents
"very_urgent"cannot leak an invalid value into your CRM. - Scores. Six explicit rules add up to 0–100. The breakdown is printed so you can audit the number instead of trusting it.
- Routes. Band A goes to the founder within the hour, B to sales the same day, C into nurture, D to archive.
Limits of this demo
- No CRM is contacted. The record is assembled in memory and rendered here.
- Budget extraction is only as good as the text. If no figure is stated, the field stays empty — it is never estimated.
- A live build replaces the in-memory record with a real write to HubSpot, Pipedrive or Airtable, plus a Slack or email notification.
Want this scoring your real inbox?
Same logic, wired to your form, your mailbox and your CRM.