Hub Lead Triage & Management

Inbound demand arrives as email, and email is where it decays. Someone has to read each message, work out whether the sender is already a customer, decide whether it is worth pursuing, and route it to the right owner — and every hour that takes is an hour the lead spends cooling. Existing relationships are the ones most often missed, because the message arrives from a personal address with no account reference, and the person triaging has no way to make the connection quickly.

• Triage means reading an inbox, so response time is bounded by whoever is on rota.
• Inbound messages from existing accounts are treated as new leads because the link is not obvious.
• Prioritisation is by arrival order, so a high-value enquiry queues behind a newsletter reply.
• The CRM falls out of date immediately, because updating it is a separate manual step.

Hub automates the mechanical parts of inbound lead management and leaves the selling to people. Incoming communications are extracted and enriched with enterprise context, so a message is linked to an existing account or contact where one exists rather than treated as a cold enquiry. Enrichment, assignment and prioritisation then run automatically, which means an owner sees a ranked, contextualised worklist rather than an inbox. The ontology and its connectors orchestrate with the systems of record — Salesforce, HubSpot, Monday and comparable CRMs — so lead information stays synchronised without a manual update step. Because the same ontology carries campaign and next-best-action workflows, a triaged lead flows straight into ongoing cultivation, and what happens to it feeds back as signal on the campaign that produced it.

Identity resolution is the part that needs a model. An enquiry from a personal address, signed with a first name, mentioning a project rather than a company, is recognisably from an existing account to a person who knows the book — and invisible to a rules engine matching on domain. Extracting intent from free-text email is the same class of problem. Neither is glamorous, and both are the reason inbound triage has stayed manual. The routing and write-back beneath are ordinary integration work; they simply could not be automated until the reading step was.

INTAKE

Inbound email and comparable communications, extracted automatically

ENRICHMENT

Enterprise context — linking to existing accounts and contacts

TRIAGE

Automated qualification, prioritisation and assignment

WRITE-BACK

Salesforce, HubSpot, Monday and comparable CRMs kept in sync

CONTINUITY

Feeds campaign optimisation and next-best-action workflows

1. 01Incoming communications extracted and enriched with enterprise context automatically.
2. 02Messages linked to existing accounts rather than treated as unrecognised enquiries.
3. 03Qualification, prioritisation and assignment automated, so owners receive a worklist.
4. 04CRM systems of record kept in sync through ontology connectors, with no manual update step.
5. 05Triaged leads flow directly into cultivation and next-best-action workflows.
6. 06Outcomes fed back as signal on the campaign or channel that generated the lead.

Ranked

Worklist delivered, against an inboxdesign intent

Synced

CRM state, without a manual update stepdesign intent

• VOICE-FIRST ENTERPRISE OPERATING SYSTEMMivaanOS→
• PRICINGHub Dynamic Pricing for Retail→
• DEMAND PLANNINGHub for Demand Forecasting→