Write a draft you can revise and keep.
Draft text, then continue from the saved document.
Start creating in Chat ↗Give the draft a clear job
Illustrative launch email: name the reader, the blend and the message before you ask for prose.
Brief the first version
Ask for a concise introduction for returning customers using approved product facts. Review the Writing request and cost, then open the saved document.
Revise the exact draft
Read the result for tone and factual accuracy. Branch from that version to try a shorter opening, compare the two, and keep the one that fits.
What leaves the conversation
The chosen text remains a saved version. Add it to a delivery set or read how branching works. A generated draft still needs human fact checking.
An AskGL request you can try
Illustrative copy. Replace bracketed facts with approved details; availability, settings and credit cost are reviewed in the workspace.
Choose Writing. Approved event facts entered or selected as context.
Write a two-sentence invitation for the neighborhood food night. Use only the approved date, venue and time in the brief. Keep the tone warm and direct; do not invent ticket details.
Saved result: A saved writing draft. Then: Check each fact, then ask for a shorter opening in a separate request.
Continue the workflow
Compare writing and revisions models and their inputs →
Branch a conversation
Try another direction while keeping the original path.
Explore ↗Compare outputs
Put saved candidates next to each other before choosing.
Explore ↗Writing outputs
See how a saved draft can be revised, compared and selected.
Explore ↗Compare writing models
Compare model inputs, writing use cases and current availability.
Explore ↗Good to know.
Creation notes
Prepare your starting point
A writing request needs a purpose, audience, length and approved facts. Keep background information separate from the deliverable. Select current Knowledge or a content record when the draft depends on saved details, and require missing information to be omitted rather than invented.
Compare compatible modelsReview what you keep
Read names, dates and claims before judging style. Ask for one focused revision of the selected draft and compare what improved and what was lost. Native document editing is a separate supported action; a generated paragraph does not automatically update its factual source.
Saved writingCommon questions
Is every catalog capability enabled?
No. Catalog candidates, registered integrations and currently enabled workspace choices are different. Check support stage and the actual preparation controls.
How should I choose the next tool?
Use the contextual links for the source, artifact or decision you have now. A feature explains a tool, a workflow explains its steps and an output guide explains the saved result.