Inbound form → sales-ready brief
Stop handing sales raw form fields after a lead asks for help.
Turn raw inbound form data into a short brief that shows who the company is, what the lead asked for, what is uncertain, and who should act next before the lead goes cold.
The leak
Raw inbound form data is not a handoff.
A form notification can arrive in seconds and still be slow operationally. Sales still has to inspect the company, decode the message, judge urgency, find the missing fields, and decide who owns the next step.
Speed without synthesis leaks revenue because the lead is fresh but the team is still translating scattered fields into a decision. The handoff becomes useful only when the record says what is explicit, what is inferred, what is unknown, and what to do next.
No company snapshot
The owner has to research before replying.
No intent read
The request is buried inside the submitted message.
No gap list
The first reply wastes time asking broad questions.
No next action
The record can sit unassigned while everyone assumes someone else is handling it.
Central action object
Inbound Lead Brief Prompt
Paste the form data, company URL, inbound message, and source context. The output should be a brief sales can use for routing, owner assignment, qualification, and the next reply.
Copy-ready prompt
You are a sales intake assistant.
Input:
FORM_FIELDS:
[PASTE NAME, EMAIL, COMPANY, ROLE, PHONE, REQUESTED USE CASE, AND ANY OTHER FORM FIELDS]
COMPANY_URL:
[PASTE COMPANY WEBSITE OR WRITE UNKNOWN]
INBOUND_MESSAGE:
[PASTE THE SUBMITTED MESSAGE]
CAMPAIGN_OR_SOURCE:
[PASTE CAMPAIGN, REFERRAL SOURCE, AD, PAGE, OR WRITE UNKNOWN]
Task:
Create one inbound lead brief that helps sales decide routing, owner assignment, qualification, and the next action.
Return this exact output format:
- company snapshot
- stated need
- inferred intent level with confidence
- possible routing lane
- missing information
- recommended next action
Rules:
- separate Explicit, Inferred, and Unknown information;
- cite the form field, message phrase, company URL, or source behind each important point;
- do not infer budget, authority, purchase certainty, or internal priority unless the lead stated it;
- if evidence is missing, write Unknown instead of filling the gap;
- keep the brief short enough to read before replying.
QA check:
Before finalizing, flag any line that sounds confident but lacks evidence. Rewrite that line as a hypothesis or Unknown.
Example input
Paste the actual form fields before AI summarizes anything.
- Company
- Northstar Operations Group
- Website
- northstarops.example
- Role
- VP Operations
- Submitted message
- We are getting more inbound demos but the sales team says handoffs are inconsistent. We need a way to summarize requests and route urgent ones faster.
- Source / campaign
- Inbound operations automation page
- Urgency hint
- Asked to review options before next month's sales planning meeting.
Example output
The brief should make the first sales decision obvious.
company snapshot
Explicit: Northstar Operations Group submitted the form with a VP Operations role. Inferred: likely operations-led services or consulting firm based on name and page context. Unknown: exact company size and CRM setup.
stated need
The lead says inbound demo handoffs are inconsistent and asks for a way to summarize requests and route urgent ones faster.
inferred intent
Medium-high confidence. The message names a workflow problem, a desired outcome, and a planning deadline, but does not confirm budget or decision process.
possible routing lane
Pursue / sales review. Assign to the owner who handles operations automation or inbound sales process requests.
missing information
CRM platform, current routing rule, average inbound volume, owner assignment model, and whether next month's meeting is a buying deadline or planning checkpoint.
recommended next action
Assign an owner today. Reply with one clarifying question about current inbound volume and offer a short review of the handoff workflow before the planning meeting.
Quality boundary
Separate explicit facts, inferred context, and unknown gaps.
Explicit
Anything the lead submitted, the source captured, or trusted CRM data already contains.
Inferred
A cautious classification from supplied evidence, such as likely intent level or possible routing lane.
Unknown
Any missing field or ambiguous claim that would be risky to invent, including budget, authority, urgency, and tool stack.
The brief is trustworthy when uncertainty stays visible. Polished guesses are worse than empty fields because they send the lead to the wrong next action.
Use the brief
Turn the summary into routing, ownership, qualification, and enrichment decisions.
Routing
Use the stated need, intent confidence, and possible routing lane to decide whether the record should go to pursue, nurture, review, or enrichment.
Owner assignment
Give the owner one reason they received the lead and one recommended next action so assignment does not become a silent queue transfer.
Qualification
Use the missing information list as the first qualification agenda instead of asking the lead to repeat everything.
Enrichment if needed
If the company, role, or routing lane is unclear, enrich only the fields needed for the next decision instead of expanding the CRM record for its own sake.