Convert a call record into traceable customer evidence without promoting seller interpretations to facts. 제공할 내용: Call record, Deal context, Output rules. 예상 결과: A source-linked call record with needs, objections, decisions, commitments, risks, unknowns, and CRM fields.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Extract a faithful sales-call record from the supplied material.
Transcript or notes, speakers, timestamps, corrections, consent, and inaudible sections:
[record]
Stage, participants, account facts, goal, product boundaries, prior commitments, and CRM terms:
[context]
Fields, quote limits, confidence, privacy, owner confirmation, and sharing audience:
[output]
Treat the call record as primary evidence and context as secondary. Separate direct customer statement, direct seller statement, observed example, explicit decision, explicit commitment, seller interpretation, hypothesis, contradiction, and unknown. Never convert interest into intent, a question into an objection, a role into authority, a date mention into a deadline, or polite agreement into a commitment. For every need, constraint, consequence, objection, alternative, success criterion, stakeholder, decision process, risk, and next step, include speaker and timestamp or exact note locator. Record commitments only when owner, action, and timing were explicitly accepted; otherwise mark confirmation needed. Preserve uncertainty and competing statements. Do not invent CRM values. End with a concise follow-up agenda, confirmation questions, privacy audit, and fields safe to enter versus fields to leave blank.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Call record
00:40 Seller: What made the review useful? 01:02 Priya, Operations Director: Our brand projects sometimes sit in client review because the team is not sure who can accept changes. Last month one launch waited two days. 02:10 Marco, Project Lead: That happened once; most reviews move. 05:22 Priya: We use Teams. IT requires SSO. I don't know about hosting. 08:15 Seller: Would an 18% reduction be valuable? 08:21 Priya: Of course, but we'd need to see our own baseline. 12:04 Marco: Can you send the security overview? 12:20 Seller: Yes, I'll send it tomorrow. 16:30 Priya: A mapping session sounds reasonable. 17:10 Seller: Shall we book Tuesday at 2? 17:18 Priya: I need to check with IT; email me options. Recording consent confirmed at start.
Deal context
First discovery call. Product supports Teams; SSO Enterprise only; no on-premise. Seller is Alex. No existing budget or deadline. CRM terms: pain evidence, current process, required capability, next step, decision participant.
Output rules
Internal CRM summary and customer follow-up prep. Short quotes allowed internally with timestamps. Redact no supplied names. Use high/medium/low confidence. Do not name owners or meetings unless explicit.
예시 출력
Customer evidence
• Workflow issue — high confidence: Priya said brand projects “sometimes sit in client review” because acceptance authority is unclear (01:02). One launch waited two days last month. Marco added that it happened once and most reviews move (02:10); preserve this limiting evidence. Frequency and broader impact remain unknown.
• Current environment — high: Teams is used; IT requires SSO (Priya, 05:22). Hosting requirement is explicitly unknown. Enterprise-tier fit and on-premise exclusion require clarification.
• Success evidence — medium: Priya wants Northstar's own baseline before judging improvement (08:21). The seller's prompted 18% number is not a customer target or expected result.
• Request — high: Marco asked for the security overview (12:04).
Explicit commitment
Alex will send the security overview tomorrow (12:20). Confirm the calendar date and link before customer-facing use.
Not yet a commitment
Priya called a mapping session reasonable (16:30) but did not accept Tuesday; she must check with IT and asked for emailed options (17:18). Record next step as “send scheduling options; customer to check IT availability,” with no meeting date or customer owner confirmed.
Safe CRM fields: pain evidence with both Priya and Marco's statements; Teams; SSO requirement; security request; Alex's send commitment. Leave budget, authority, hosting, deadline, target outcome, and scheduled meeting blank. Follow-up should confirm hosting, relevant IT participant, baseline measure, exact date for the promised security email, and mutually accepted mapping time.
효과가 있는 이유
1
Evidence types prevent conversational signals from becoming inflated pipeline claims.
2
Commitment tests protect both parties from invented owners and dates.
결과 확인
Does every material field point to a speaker and locator?
Are interpretation, hypothesis, and unknown visibly separate from customer statements?
Do recorded commitments include explicitly accepted owner, action, and timing?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Extract needs, objections, and commitments from a sales call”?
For “Extract needs, objections, and commitments from a sales call,” prepare Call record, Deal context, and Output rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Extract needs, objections, and commitments from a sales call” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A source-linked call record with needs, objections, decisions, commitments, risks, unknowns, and CRM fields—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Extract needs, objections, and commitments from a sales call”?
The published test record for “Extract needs, objections, and commitments from a sales call” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
