Intake and routing
No lead left without an owner
Leads come in from your forms, ads and booking pages, get scored by revenue and are assigned to the right triager in the same instant.
Business
Minimum €3,000 · Tier threshold €5,000 · Excluded: MLM
Latest leads
- Move the revenue and send a lead.
A simulation with sample data and the same rules the CRM applies.
The journey
From the first signal to its owner, in the same instant
- 1
It comes in
Through the API, a booking page or manual entry, with its source, revenue and campaign.
POST /ingest-lead - 2
It's filtered
Below your minimum revenue or from an excluded business, it's stored as disqualified and never routed.
Disqualified - 3
It's scored
Its revenue sets the tier: below or above your threshold, or by the ranges in your rules.
Tier 2 - 4
It's assigned
It goes to the triager in that tier with the lightest load over the last 30 days, relative to their weight.
→ Laura
Sources
Everything that generates leads, in one place
Your site
The form sends the lead to the API from your server.
Ads
Every lead arrives with the UTM of the campaign that brought it.
Zapier and Make
One HTTP step with your key in the header, no code.
Your systems
Any tool that can call a URL.
Booking pages
Whoever books comes in as a lead if they didn't exist yet.
Manual entry
Referrals and direct messages, from the board.
Lead intake
All your sources, one entry point
Connect forms, ads or your website to the intake API. Every lead arrives with its source, its revenue and the campaign data that brought it.
- Protected intake API. A single endpoint authenticated with a secret key, with field validation and rate limits.
- Source from minute one. UTM, referrer and funnel are stored with the lead, so you can later measure which source drives sales.
- Leads from bookings. Anyone who books on a public page becomes a lead if they weren't in the CRM yet.
- Manual entry. Referrals, direct messages or events: create a lead in seconds from the board.
curl -X POST https://closeford.com/api/public/ingest-lead \
-H "Authorization: Bearer $CLOSEFORD_KEY" \
-H "Content-Type: application/json" \
-d '{
"nombre": "Marta Ruiz",
"email": "marta@ejemplo.com",
"revenue": 30000,
"utm_source": "instagram"
}'201 Created
{ "id": "9b2e…", "status": "nuevo",
"triage": { "bucket": 2, "triager": "triager_1" } }Triage
Automatic triage by revenue
Define revenue brackets and which triagers handle each one. Every lead falls into its bracket and is assigned by each person's workload and weight.
Configurable brackets
Tune the thresholds to your offer and change the split whenever you need.
Split by workload and weight
The lead goes to whoever has the lightest load at that moment, weighted by the weight you give each triager.
Automatic disqualification
Leads below your minimum revenue or from excluded businesses are marked as disqualified and not assigned.
Leads
A board built for working
Kanban and table views with filters by status, source, category and triager. Every lead holds its history, calls and next steps.
- Inline editing. Changes save automatically, even offline.
- CSV export. Export the filtered view in one click.
Details
- Global search
- Find any lead by name, email, phone or business from any screen.
- Six statuses
- New, to call, called, booked, sale and disqualified: the board shows where every lead stands.
- No duplicate records
- If whoever books already exists with that email, the booking joins their record instead of creating another.
- Offline changes
- Edits are kept in the browser and sync when the connection comes back.
- Usage limits
- The intake API accepts 300 requests per minute per workspace, to stop abuse.
- No routing clashes
- Leads arriving at the same time are assigned one by one, so nobody gets two by mistake.
- Qualified leads
- Flag from the API or the record whether a lead arrives already qualified.
- Sample data
- Load a sample team and leads to try the routing; they're removed without touching your real data.
Intake and routing
Frequently asked questions
Where can leads come in from?
From the intake API (your site, forms, Zapier, Make or your own server), from public booking pages, and by manual entry from the board.
What happens to a disqualified lead?
It's stored with the disqualified status: it isn't routed and triggers no webhooks. It stays in the CRM in case you want to review it.
How many triage tiers are there?
Two. By default a revenue threshold (€5,000) separates them; with triage rules you set the ranges, which triagers take each tier and with what weight.
How is the owner of each lead chosen?
Whoever has the fewest assignments in that tier over the last 30 days, relative to their weight: with weights 2 and 1, the first gets twice as many. On a tie, the first in the team.
What if no triager is available for that tier?
The lead stays unassigned and its record says so, rather than going to someone who doesn't take that tier.