# Enrich, score and route inbound leads in minutes.

A form needs only name and email. ListPlus adds the company from the domain, computes the fit score and hands A-leads to Slack and your CRM. The rest stays in the list – visible, not deleted.

https://listplus.ai/en/gtm-workflows/inbound-lead-routing-enrich-score-route

## Inputs and connections

A way into the list – a form, a webhook or an app event (Typeform, Calendly, a HubSpot form). Your ICP criteria and a pipeline to Slack or the CRM.

A form or webhook on the list, a Slack or CRM pipeline. An agent with the “Set up” right can create score and rules – paused until you switch them on.

## Steps

1. **A lead arrives** (ListPlus · runs automatically). By form, webhook or app event the record lands in the list – with its origin.
2. **Add the company from the domain** (ListPlus · runs automatically). The email domain yields company, industry and size. Personal domains trigger no company lookup; disposable addresses are caught by the checks.
3. **Compute the fit score** (ListPlus · runs automatically). A score column: industry +40, size +30, role +30 – plus an AI criterion where a rule is not enough. The score recalculates whenever data changes.
4. **Hand off A-leads, existing accounts to the owner** (Slack · CRM · runs automatically). Rule: score ≥ 80 and not in the CRM → status “A”, Slack and CRM pipeline. Already in the CRM → status “Existing” for the owner. Below 50 → tag “Nurture”.
5. **Review the unclear ones** (Your team · manual in ListPlus). Rows with an open finding (name and email do not match, company unclear) stay on “Review”.

## Expected sample result

Mia Winter: 100 points, not in the CRM → status A, Slack and CRM pipeline. Ava Stein is already a customer → Existing, the owner is notified. Noah Wolf: 40 points → Nurture. Tom Lenz: disposable address → review.

## Costs and boundaries

The company from the email domain costs 0.25 credits per lead ($0.01 on Pro); personal domains trigger no lookup. Checks, rules and a rule-based score cost nothing, an AI criterion in the score 0.02 credits per AI answer. A pipeline handoff is charged per record.

Routing runs only after normalisation and deduplication – otherwise “US” and “United States” land with two reps. A score is a rule, not a judgement; “Review” cases are seen by a person.

## Agent prompt

Set up the list “Inbound”: add the company from the email domain, a fit score (software industry +40, 51–500 employees +30, marketing or sales role +30), a match against the list “Customers”. Rules: score ≥ 80 and not a customer → status “A” and the pipelines “Slack #inbound” and “CRM”; customer → status “Existing”; score < 50 → tag “Nurture”. Create the rules paused and show me the cost per lead.

## Tools

`describe_setup`, `add_column`, `create_trigger`, `query_records`, `send_to_pipeline`

MCP: https://listplus.ai/mcp
REST: https://listplus.ai/a/v1/{action}
API: https://listplus.ai/a

## Sample calls

These calls use fictional IDs. Use the IDs returned by your workspace.

```text
create_trigger({
  "list_id": "<shared_list_id>",
  "name": "A-leads to Slack",
  "on": "match",
  "conditions": {
    "groups": [
      [
        {
          "field": {
            "kind": "column",
            "name": "Fit score"
          },
          "op": "greaterThanOrEqual",
          "values": [
            "80"
          ]
        },
        {
          "field": {
            "kind": "reference",
            "listId": "<customers_list_id>"
          },
          "op": "isNotIn"
        }
      ]
    ]
  },
  "actions": [
    {
      "kind": "status",
      "status": "A"
    },
    {
      "kind": "pipeline",
      "pipeline": "Slack #inbound"
    }
  ],
  "activate": false
})
```