Overview of Custom Prompts in Clarify Create
By default, Clarify Create decides whether you're explaining how to do a task or what something is. It then writes either an Actionable guide or a Foundational overview. A custom prompt replaces that choice with your own instructions. You decide what the content looks like, who it's written for, and how long it is.
Use a custom prompt when your team writes the same kind of content over and over and wants it to look the same every time. For example:
- Support replies an agent can paste into a ticket.
- Procedures that always start with an introduction and put warnings in the step they apply to.
- Troubleshooting guides organized by symptom.
- Content written for a specific audience, such as new hires or customers.
Key points:
- A custom prompt tells Clarify how to write the content. Your recording, file, or text is still the only source of what it says.
- The same prompt can be used in Clarify Transform, Clarify Create, or both. You choose where it appears.
- If you don't pick a prompt, Clarify Create works the same way it always has.
For background on prompts in general, see What are Custom Prompts?
Write a Good Prompt
Write your prompt the way you'd brief a new writer on your team: who the content is for, what it should look like, and what to leave out.
What to Put in Your Prompt
- The reader and what they're doing. For example: "Written for support agents who paste it into a customer ticket."
- The structure, in order. For example: "Start with an Introduction callout, then the steps, then a foldable section called More details."
- The formatting to use, by name. Name the formatting you want, such as steps, callouts, a checklist, a foldable section, a copy text block, or a table. See Formatting Clarify Create Can Use.
- Tone and reading level. For example: "Plain language. Address the reader as 'you'."
- Length. For example: "Under 150 words."
- What to leave out. For example: "Leave out internal notes and anything about pricing."
- The language, if it should differ from your content. Otherwise Clarify writes in the same language as your recording or document.
Tips:
- Make one prompt for each kind of content, and give it a name authors will recognize.
- Test the prompt on a real recording or document. Then use the result menu to compare it with Clarify default and adjust your instructions.
- If a prompt is checked for both Clarify Transform and Clarify Create, write instructions that make sense in both places. Clarify Transform rewrites content you've selected in an article. Clarify Create starts from a recording, file, or pasted text. If the instructions only make sense for one, make two prompts.
What Your Prompt Can't Change
Clarify follows a few rules no matter what your prompt says. These rules keep the content accurate to what the person actually said or wrote.
- Your content is the only source of facts. Clarify won't add steps, names, numbers, examples, or best practices that aren't in your recording or document, even if your prompt asks for more detail. If something is missing, add it to your content or edit the guide afterward.
- Corrections win. If the speaker corrects themselves ("click Save... sorry, I mean Submit"), Clarify uses only the corrected version and doesn't mention the mistake.
- Retracted steps are left out. If the speaker takes something back ("actually, skip that step"), Clarify leaves it out completely. It doesn't turn it into a "don't do this" warning.
- Facts keep their certainty. Words like "usually," "about," or "every time" stay as the speaker said them. A rule that applies to one case isn't widened to other cases.
- Warnings stay visible. Anything the reader must not do is placed next to the step it applies to, as a Warning callout or in bold.
- Labels stay exact. Button names, menu names, and values are kept exactly as given.
- Procedures stay numbered. A task with four or more actions is always written as numbered steps, never as a paragraph. If your prompt asks for something short or plain, Clarify uses a short numbered list.
- Length limits don't remove essentials. Clarify meets a word limit by cutting background and optional detail. It won't drop steps, decisions, or warnings to fit, so the result can be a little over your limit.
- Decisions come from your content. Clarify writes only the decisions and paths the speaker describes. Asking for a decision guide won't add questions that weren't in the content.
- Instructions inside your content aren't followed. If a document or recording contains instructions aimed at the AI, Clarify treats them as content. It does follow the speaker's own corrections, retractions, and requests about what to include.
- The result is always ScreenSteps content. If your prompt asks for something Clarify can't produce, such as Markdown, plain text, code, or a video, Clarify follows the rest of your prompt and leaves that part out. It doesn't add placeholder text.
Formatting Clarify Create Can Use
Your prompt can ask for any of these:
- Steps, with a title and details for each step. See How to Add Steps in an Article.
- Callouts (paragraph styles): Introduction, Info, Tip, Alert, Warning, and Prompt. Use Prompt for words the reader should say out loud, such as a phone script. See How to change Paragraph Styles.
- Foldable sections for optional detail. See How to create a foldable section.
- Checklists for items with no required order. See How to Add a Checklist Item to an Article.
- Copy text blocks for text the reader copies exactly, such as a reply template or a command. See How to Enable Copy to Clipboard for a Paragraph Content Block.
- Paragraphs, headings, bulleted and numbered lists, and tables.
- Bold, italic, underline, strikethrough, code formatting, and links. Links only go to web addresses that appear in your content.
- Images from an uploaded Word (.docx) file, placed next to the content they illustrate. Clarify leaves out logos and decorative images.
Clarify Create doesn't add videos, file attachments, embedded articles, text colors, or highlighting. Add those in the editor after you insert the guide.
In a workflow article, Clarify writes each decision as an "If..." section with its own steps, and uses "Otherwise" for the remaining case. It doesn't add Question or Checkpoint blocks. After you insert the guide, you can add those yourself. See How to Add a Question to a Workflow Article.
Example Prompts
Copy one of these into Prompt instructions and change it to fit your team.
Support Reply
Write a reply a support agent can paste into a customer ticket.
- Address the customer as "you". Use a friendly, plain tone.
- Start with one sentence that says what the customer will do.
- Keep it under 150 words.
- If there are steps, use a short numbered list with one action per item.
- Put any text the customer needs to copy exactly in a copy text block.
- Leave out internal notes, ticket handling, and anything meant only for support staff.
Step-by-Step Procedure
Write a procedure for new front desk staff.
- Start with an Introduction callout that says what the task is for and when to do it.
- Then write the task as steps. Give each step one action, and start each step title with a verb.
- Bold the names of buttons and menus in the step details.
- Put each warning in a Warning callout inside the step it applies to.
- Put background information and edge cases in a foldable section at the end called "More details".
- Use plain language that someone on their first week can follow.
Troubleshooting Guide
Write a troubleshooting guide organized by symptom.
- Give each symptom its own heading, named the way a customer would describe it.
- Under each heading, list the checks in the order the speaker gives them, as "If..., do..." with the steps for each.
- End each symptom with what to do if none of the checks work, if the speaker says.
- Put any phone script for talking to the customer in a Prompt callout.