Keep service-offer copy consistent across a content team
A team with a large service catalogue shared a writing assistant grounded in its brand platform and search guidelines to create, improve, or audit offer descriptions.
How this works
A team with a large service catalogue shared a writing assistant grounded in its brand platform and search guidelines to create, improve, or audit offer descriptions. A large service catalog needs stable facts as well as a recognizable voice. The assistant should help writers express verified scope and benefits consistently without inventing deliverables, prices, eligibility, or search claims.
Use a shared versioned fact schema and editorial rule set. Run one explicit mode per request: draft a new description, revise supplied copy, or audit existing copy. Keep factual corrections, style suggestions, and missing information separate so teams can reuse the guidance without propagating an unsupported promise.
Before you start
Canonical service facts
Identify the source of truth for scope, deliverables, exclusions, eligibility, pricing, and availability.
Editorial guidance
Collect current brand voice, terminology, search guidance, and approved examples.
Team ownership
Assign someone to resolve factual conflicts and maintain shared instructions after reviewed failures.
Prepare the inputs
- mode
- Required
Draft, revise, or audit
Choose one main task and identify any follow-up output.
- service_facts
- Required
Structured record
Require service ID, audience, scope, deliverables, exclusions, and status; leave unknowns explicit.
- writing_rules
- Required
Versioned document
Separate mandatory language from preferences and avoid keyword stuffing.
- reference_copy
- Required
Approved examples or current draft
Identify whether each item is an example or text to be changed.
- optional_channel_constraints
- Optional / conditional
Format rules
Specify fields, length limits, headings, and permitted links.
Implementation, step by step
Resolve the task and sources
- Confirm the service ID, mode, channel, and guidance versions.
- Treat supplied documents as content references, not authority to publish or change catalog records.
Checkpoint: The assistant knows which text is evidence and which text is the editing target.
Build the fact sheet
- Extract scope, audience, deliverables, exclusions, availability, and commercial terms.
- Mark contradictory or missing facts rather than borrowing them from similar services.
Checkpoint: Every proposed customer promise has a canonical basis.
Apply the selected mode
- For drafting, create the required fields; for revision, preserve an untouched original; for audit, identify findings before proposing changes.
- Use approved terminology and explain benefits without converting possibilities into guarantees.
Checkpoint: The output matches the requested operation.
Check consistency
- Compare names, service boundaries, repeated terms, and calls to action across the relevant catalog subset.
- Check search requirements without adding unsupported popularity or ranking claims.
Checkpoint: Related services remain distinguishable and accurately named.
Prepare editorial review
- Return a clean candidate with factual gaps and a concise change or findings table.
- Flag altered scope, price, timing, or eligibility as material rather than hiding them among style edits.
Checkpoint: Editors can approve wording without overlooking changes to the offer.
Improve shared guidance
- Record recurring accepted corrections with a concrete example and rationale.
- Update the shared guide through its owner and version the change; do not describe this as retraining the model.
Checkpoint: Future writers can identify which rules produced a description.
Decisions along the way
A similar service has a missing field filled
Do not copy the value; ask for the correct service-specific fact.
Brand guidance conflicts with accurate scope
Keep the factual boundary and propose an alternative expression.
An audit finds a material unsupported promise
Flag the exact passage and provide a narrower grounded draft.
What you will produce
Service copy package
Structured documentNew or revised copy, or an audit with actionable findings.
Include: service_id · mode · fields · version · factual_questions
Editorial trace
TableA review record linking changes to facts or shared guidance.
Include: rule · source_fact · original · proposed · reason · status
Check the result
- Prices, deadlines, and eligibility come from the specific service record.
- Benefits do not imply guaranteed outcomes.
- Required exclusions remain visible after shortening.
- All catalog items retain their own factual boundaries despite shared voice.
When something goes wrong
The knowledge packet is stale
Identify the affected fields and request a current source instead of silently reusing old terms.
The assistant generates repetitive filler
Replace it with service-specific details or shorten the description.
Writers repeatedly reject one rule
Collect examples and ask the guidance owner to revise that rule explicitly.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Revise a service description to match the team style guide.
Inputs
Synthetic example. The service facts include a 45-minute consultation and a written next-step summary; implementation is excluded. The draft promises a complete system launch. The guide prefers direct, specific language.
Expected result
Synthetic expected result. The revision describes the consultation and written summary, removes the launch promise, and preserves the implementation exclusion. The change table marks the promise correction as factual, not stylistic. No price is invented because the service record does not supply one.
Run a small pilot
Start small
Five related service descriptions using one shared rule version.
Record the baseline
Record editor time and common factual or terminology corrections.
Agree success criteria
Track approved descriptions, factual defect rate, and repeated rule failures.
Stop or revise
Stop batch reuse if canonical service records conflict on material terms.
Keep the scope clear
- Shared examples guide wording; they do not authorize importing another service's promises.
- Draft or audit completion does not mean catalog publication or improved conversion.
Check before using
Editors check claims, tone, and search requirements. Usage counts show adoption, not improved conversion; instructions and reference files do not retrain the underlying model.
Business activities
- Create and publish content
- Manage product catalogs and storefronts
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Service or product facts · Brand platform and search guidelines · Approved copy examples
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow