Published August 28, 2026.
Intake is a context problem
Lead intake is often described as collecting names and contact details. The harder problem is preserving enough context for the next owner to respond thoughtfully. A lean growth team may need to understand what prompted a request, which workflow is involved, what timing matters, and what the person is actually asking for. BusinessGrowthAssistant can help teams establish that routine, but an assistant should not invent urgency, qualify someone beyond the available evidence, or promise a particular outcome. Good intake makes a human decision easier.
Name the source and consent
Start by recording where the inquiry arrived and what communication the person requested. Distinguish a direct request from a referral, an imported record, or a research prospect. Only collect fields necessary for the stated next step. A source label gives the owner context without pretending that all channels have the same intent. Consent and retention rules vary by setting, so the responsible business owner must define the applicable policy. The intake operator follows that policy and escalates uncertainty rather than improvising.
Capture the problem in the person’s words
Use a short problem statement before adding internal categories. The wording may reveal whether someone needs daily article support, an SEO review routine, lead-list preparation, or a broader operations conversation. Keep quotation marks for exact words and label paraphrases clearly. This protects the handoff from becoming a confident interpretation. The assistant may summarize and ask a clarifying question; it should not turn a vague request into a diagnosis. Context is useful precisely because it preserves what remains unknown.
Separate fit from priority
Fit asks whether the request belongs to the company’s service scope. Priority asks when the owner should review it. These are different decisions. A request can fit the niche but have no stated deadline. Another can sound urgent while requiring a service the company does not provide. Use separate fields and explain the evidence for each. Never assign a priority merely because a lead used emphatic language. A small team protects trust when the intake system records uncertainty instead of manufacturing a queue position.
Create a safe qualification rubric
The rubric should contain observable signals: stated problem, relevant workflow, decision owner, desired next step, and missing information. It should not rely on stereotypes, hidden scoring, or unsupported assumptions about budget or authority. A trained assistant can apply the rubric consistently and mark “needs clarification.” The owner decides whether to advance, redirect, or close the inquiry. If the rubric begins to act like a promise or exclusion policy, review it. Qualification is a service boundary, not a substitute for conversation.
Make the response useful
An intake response should confirm receipt, reflect the request accurately, and state the next known step. Avoid claiming that a result is likely, guaranteed, or already achieved. Avoid public pricing or rate language unless the owner has explicitly approved the exact content and context. In many cases, a simple message that asks one focused question is better than a long automated explanation. The assistant prepares the draft and checks that it does not expose internal notes; the accountable person owns the final communication.
Preserve the handoff packet
The handoff should include source, timestamp, problem statement, relevant workflow, qualification evidence, open questions, sensitivity flags, and suggested owner. It should also say what the assistant did not verify. This makes the packet useful to someone who was not present at intake. Remove unnecessary personal information and restrict access to the minimum needed. A handoff is complete when the next owner can act without asking the intake operator to reconstruct the conversation from memory.
Handle ambiguous and unsuitable requests
Ambiguity needs a question; an unsuitable request needs a respectful boundary. If someone asks for a service outside scope, do not stretch the description to create a fit. If the request concerns confidential credentials, regulated advice, or a claim that cannot be supported, escalate or decline according to the owner’s policy. Record the reason internally without making public statements about private interactions. Clear boundaries protect both the team and the person making the inquiry.
Review the rubric from real cases
Once several intakes have passed through the routine, review where humans corrected the record. Repeated corrections may indicate a missing field, a misleading label, or a question that arrives too late. Change one part of the rubric at a time and note the reason. Do not optimize for the number of inquiries advanced. Optimize for context quality and appropriate ownership. That distinction keeps the routine aligned with BusinessGrowthAssistant’s broader mission of dependable daily growth operations.
The operating rule
Preserve the request, state the evidence, label the unknowns, and leave the decision with the right owner. This rule makes lead intake faster without making it mechanical. It gives a founder a clear packet, gives an assistant a safe boundary, and gives the person inquiring a more accurate response. The result is not a promise of conversion. It is a disciplined starting point for a useful conversation and a healthier growth routine.
Further operating detail
Before handoff, compare the summary with the original intake. Confirm source, request, timing, and open question. Remove assumptions that entered during categorization and label unverified fields. This quick comparison prevents a small interpretation from becoming the official story of an inquiry and gives the next owner context they can trust.
Review note
Qualification notes should remain useful after the first response. Record the next owner and the question that will confirm fit, but do not create a permanent judgment from a preliminary conversation. This preserves flexibility and prevents an early label from becoming a hidden exclusion.
