AI agent team guide
AI Sales Agents for Inbound Qualification and First Response
A fit-and-response queue with evidence, owner and a reviewed first reply

AI lead qualification is most useful when it makes the next response more relevant. Start with the inquiry someone actually sent, your explicit fit criteria and the customer records you are permitted to use. A small AI sales team can separate a promising conversation from an incomplete request without pretending that missing information is a negative signal.
Lead Qualification Desk owns the fit brief. Researcher checks relevant context, Communicator drafts the response and CRM Steward identifies record issues. The return is a human-reviewable decision with a reason, an owner and a useful next question, not an automatically accepted or rejected customer.
Build your four-agent team
| Agent template | Its job on the team | Bring to its setup | Reviewable return | Team |
|---|---|---|---|---|
Lead Qualification DeskLead agent | Evaluate the actual inquiry against explicit criteria. | The inbound message, offer boundaries and agreed fit criteria. | Fit evidence, unanswered questions and a proposed next response. | Add to team |
ResearcherSupporting agent | Verify context that changes the conversation. | Permitted company sources and the specific research question. | A source-linked brief with facts separated from assumptions. | Add to team |
CommunicatorSupporting agent | Draft a relevant first response. | The accepted qualification brief, sender context and approved offer. | A concise response that answers the inquiry and asks the next useful question. | Add to team |
CRM StewardSupporting agent | Check the record before proposing changes. | Authorized CRM records and agreed record-ownership rules. | Potential duplicates, missing fields and a field-scoped cleanup proposal. | Add to team |
Set up your team in Finta
- Add each template individually. Use the Add to team action for each named coworker, review the import setup and complete its Getting Started skill.
- Give each role the right context. State the shared objective, then supply the authorized documents, notes or exports that role needs. Do not assume an unconnected system is available.
- Review the handoff. Accept or correct one return before giving its evidence and open questions to the next coworker. Importing four templates does not itself run a bulk team.
- Make recurrence deliberate. Complete a useful manual pass first. Review any supported routine and enable it only when the scope, inputs and permissions are right.
Prepare the evidence
- The original inquiry and received date, without unnecessary personal data.
- Written fit criteria and the limits of the offer you can actually provide.
- Existing customer or prospect records you are authorized to inspect.
- A named response owner and the source of any deadline or commitment.
Run the workflow
1. Read the request before scoring the account
Have the desk restate what the person is asking for. Separate an explicit requirement from your interpretation. If budget, timing or authority is absent, label it unknown and decide whether asking is useful; do not invent a disqualification.
2. Research only what changes the response
Ask Researcher for the small amount of context needed to clarify fit. Public company information can support a business description, not an inferred budget, private intention or buying authority. Keep the source and date alongside the conclusion.
3. Reconcile the customer record
Have CRM Steward compare any apparent matches before suggesting a new record or a merge. A similar company name is not enough to combine people. Preserve the original inquiry and ask the responsible owner to approve supported changes separately.
4. Respond to the person, not the score
Give Communicator the accepted facts and one next step. A useful reply can acknowledge a genuine limitation while offering a relevant question or route. Review the recipient, content and any promises before an authorized person sends it.
A fictional qualification brief with an unknown budget
This invented inquiry illustrates the workflow. It is not a customer record or a claim about conversion rates.
| Evidence | Desk interpretation | Next action |
|---|---|---|
| An operations lead asks whether a shared customer process can be organized. | There is a relevant business need. | Acknowledge the stated process and ask what outcome matters first. |
| The message does not include budget or a purchase date. | Budget and timing are unknown, not zero. | Ask only the question needed for the next useful conversation. |
| Two similar company records exist. | Potential duplicate; identity is not confirmed. | Prepare a review proposal rather than merge automatically. |
| A reply is drafted. | No response has yet been sent. | The accountable owner reviews the recipient, facts and next step. |
Qualification improves the handoff when it explains a decision. A high numerical score with no evidence is less useful than a short, specific brief.
Copy the team brief
Qualify this inbound inquiry for [actual offer].
Use [original inquiry], [explicit fit criteria], [authorized CRM records] and [permitted sources].
Desk: separate supported fit, explicit mismatch and unanswered questions.
Researcher: verify only context that changes the response.
CRM Steward: identify possible duplicates and propose narrow corrections without writing them.
Communicator: draft a first response that addresses the actual request.
Return evidence, proposed disposition, response owner and next question.
Do not infer budget or authority, create or merge records, send messages or promise availability.Review the return
- Every fit decision points to evidence or an explicit unanswered question.
- The response addresses the inquiry without adding unsupported product promises.
- Proposed record changes and actually completed actions remain separate.
Questions before you start
Should every inbound lead receive a score?
Not necessarily. A reasoned fit disposition and next question may be more useful than a score, particularly when the inputs are sparse or your criteria are still changing.
Can the team send the first reply automatically?
This guide prepares a reviewable reply. Sending requires the appropriate user authorization and a supported connected channel; importing the templates does not authorize external messages.
Sources and next steps
This playbook uses the current published Finta marketplace packages linked in the team table. Open each profile to review its instructions, context, Skills and any routines before importing.