Act as a practical specialist helping me with sales call notes to crm. My context: [your CRM; call recording tool; fields reps must fill; how notes look today; deals lost to bad notes; manager review process].
1. Write the extraction prompt: attendees, pain points, objections, commitments, and next steps with dates.
2. Map outputs to CRM fields so data lands where reports read it.
3. Set the quality bar: every call summary includes one direct customer quote.
4. Add the manager view: weekly digest of commitments made and kept per rep.
5. Build the follow-up trigger: next steps auto-drafted as tasks with due dates.
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#ai workflows#sales ops
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Sort a crowded inbox without losing the messages that matter.
Act as a practical specialist helping me with inbox triage blueprint. My context: [mail volume, categories, urgent senders, tools available].
1. Define priority tiers and exact inclusion rules.
2. Write example labels and false-positive cases.
3. Design a daily review queue and escalation path.
4. Give a five-message test set with expected labels..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Turn a broad question into a source-checked investigation.
Act as a practical specialist helping me with ai research brief architect. My context: [question, decision it supports, deadline, sources allowed].
1. Break the question into falsifiable subquestions.
2. Set a source hierarchy and recency requirements.
3. Create an evidence table with claim, source, date, confidence.
4. Specify when to stop researching and how to flag gaps..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Make messy documents yield clean, auditable fields.
Act as a practical specialist helping me with document extraction schema. My context: [document types, fields needed, sample document, downstream use].
1. Design a JSON schema with field types and null handling.
2. Write extraction rules with exact quote or page evidence.
3. List ambiguous cases and a human-review threshold.
4. Produce three test cases including a missing field..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.