|
| 1 | +--- |
| 2 | +title: Create content from company knowledge |
| 3 | +description: Turn sourced answers into briefs, updates, emails, and other drafts in the conversation. |
| 4 | +--- |
| 5 | + |
| 6 | +import { Image } from '@/components/ui/image' |
| 7 | + |
| 8 | +On **Home**, use **Search** conversation mode. Once you've found the right information, ask Sim to turn it into something you can use. Draft a customer response, a meeting brief, an internal announcement, or an FAQ in the conversation. |
| 9 | + |
| 10 | +<Image |
| 11 | + src="/static/search/launch-update-draft.webp" |
| 12 | + alt="A refined Atlas launch update with links to the Google Drive launch brief and readiness update beside the supporting claims" |
| 13 | + width={1470} |
| 14 | + height={1000} |
| 15 | + variant="result" |
| 16 | + background="architecture" |
| 17 | +/> |
| 18 | + |
| 19 | +## Start with the evidence |
| 20 | + |
| 21 | +For work that depends on company facts, first identify the sources: |
| 22 | + |
| 23 | +> Find the Atlas launch brief and the latest rollout decision. Summarize the approved scope, intended audience, and confirmed dates with sources. |
| 24 | +
|
| 25 | +Review the answer, then ask for a draft: |
| 26 | + |
| 27 | +> Using those findings, draft an internal launch announcement for customer success. Keep it under 200 words. Include what is changing, who it affects, and what the team needs to do. Mark any unconfirmed details as questions. |
| 28 | +
|
| 29 | +You can combine both requests in one prompt when the scope is clear. |
| 30 | + |
| 31 | +## Specify the output |
| 32 | + |
| 33 | +Include four details: **source material, audience, format, and constraints**. |
| 34 | + |
| 35 | +| Detail | Example | |
| 36 | +| --- | --- | |
| 37 | +| Source material | “Use the approved onboarding guide and these account notes.” | |
| 38 | +| Audience | “Write for a new customer who hasn't used the product.” | |
| 39 | +| Format | “A welcome email with three next steps.” | |
| 40 | +| Constraints | “Under 150 words, friendly and direct. Don't invent dates or commitments.” | |
| 41 | + |
| 42 | +The draft appears in the conversation. You can copy it into the document or communication tool where you want to use it. |
| 43 | + |
| 44 | +## Choose a useful format |
| 45 | + |
| 46 | +### Briefs and updates |
| 47 | + |
| 48 | +> Turn the Atlas findings into a one-page project brief: goal, current status, decisions, risks, and unanswered questions. Keep source references next to factual claims. |
| 49 | +
|
| 50 | +### Emails and customer responses |
| 51 | + |
| 52 | +> Using our implementation guide, draft a response explaining the customer's next onboarding steps. Keep internal discussion out of the customer-facing text and list supporting sources separately for my review. |
| 53 | +
|
| 54 | +### FAQs and onboarding material |
| 55 | + |
| 56 | +> Create a new-hire FAQ from the onboarding guide. Include questions about access, equipment, and getting help. Flag questions the guide doesn't answer. |
| 57 | +
|
| 58 | +### Meeting preparation |
| 59 | + |
| 60 | +> Use the available Acme account notes to draft a meeting brief with context, open questions, and a proposed agenda. Distinguish documented customer requests from suggested discussion topics. |
| 61 | +
|
| 62 | +### Presentation outlines |
| 63 | + |
| 64 | +> Turn these findings into a six-slide outline for a team update. For each slide, give a title, three key points, and the sources supporting them. |
| 65 | +
|
| 66 | +## Refine the draft |
| 67 | + |
| 68 | +Continue with specific changes: |
| 69 | + |
| 70 | +- “Cut this to half the length without losing the action items.” |
| 71 | +- “Use the tone of this example: [paste an approved example].” |
| 72 | +- “Move the recommendation to the opening paragraph.” |
| 73 | +- “Make the terminology consistent with the product guide.” |
| 74 | +- “Separate confirmed facts from proposed next steps.” |
| 75 | + |
| 76 | +Provide a style example or brand guidance when consistency matters. Don't assume Sim already knows a team's preferred tone. |
| 77 | + |
| 78 | +## Review and use it |
| 79 | + |
| 80 | +Check names, numbers, dates, links, and commitments against the sources. For an external audience, also check that the draft includes only information intended for that audience. |
| 81 | + |
| 82 | +Copy the reviewed draft into the app where you want to use it. Sim Search creates the text in your conversation; you choose when and where to share it. |
| 83 | + |
| 84 | +[Explore more example prompts](/search/use-cases). |
0 commit comments