Qualify inbound leads and create CRM deals

Why use this

1. An inbound enquiry can lose momentum when its needs are scattered across a message, contact record and salesperson’s notes. Rushing to create a deal can also duplicate an existing opportunity or imply qualification that the prospect has not actually established.

2. This job could prepare a structured handoff with the evidence behind each fit judgment. Making missing information visible would help the sales owner decide whether to follow up, route the enquiry elsewhere or create a deal with a clearly provisional stage.

Why an agent / simpler alternative

Useful judgment

Interpret unstructured enquiries and map stated needs to explicit, reviewable qualification criteria.

Simpler alternative

Use a form and deterministic routing rules when enquiries already contain standardized fields.

Unsuitable when

Qualification relies on sensitive personal traits or unsupported assumptions about buying intent.

Proposed inputs

1. Name

   Inbound enquiry

   Owner

   Sales owner

   Minimum scope

   Authorized message, company details and relevant stated needs

   Quality check

   Keep prospect statements separate from salesperson inference.

2. Name

   Qualification and routing rules

   Owner

   Sales operations owner

   Minimum scope

   Fit criteria, required fields, owner mapping and duplicate rules

   Quality check

   Specify how incomplete or conflicting evidence should be handled.

Access and setup — proposed or unknown

Proposed minimum

1. Read the selected enquiry and scoped CRM matches; preview any new deal and internal summary.

Compatibility unknowns

1. Unknown: HubSpot field definitions, Slack destinations and current plugin permissions.

External actions requiring approval

1. Creating CRM records, assigning owners, posting summaries or contacting the prospect.

Expected deliverable and review checks

Proposed artifact

Qualification record and proposed CRM/Slack handoff with evidence, missing fields and duplicate status.

Critical checks

1. Contact and company identities are verified against existing records.

2. The deal stage reflects available evidence rather than an invented budget or commitment.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A returning prospect uses a different email address.

   Why it matters

   A duplicate deal may split history and confuse ownership.

   Proposed response

   Compare company and contact context, then hold ambiguous matches for review.

2. Signal

   A general information request is labelled purchase-ready.

   Why it matters

   The team may prioritize or message the prospect inappropriately.

   Proposed response

   Record the stated intent and ask for the missing qualification signal before changing stage.

Effort and cost — unknown

Setup work

1. Define fit criteria, identity matching and destination mappings.

Ongoing review

1. Review uncertain leads and reconcile duplicate or reassigned opportunities.

Unknowns

1. Unknown: connector charges, CRM limits and human qualification effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional enquiry matches an existing company, uses a new contact email and omits budget and timeline.

Acceptance checks

1. The existing opportunity is flagged before creating another.

2. Budget and timeline remain unknown in the proposed handoff.

Stop conditions

1. An unverified identity, external outreach or unapproved workspace write is required.

Limits

1. Recommended review gates do not establish the original operating safeguards or qualify any real lead.