When this is useful
Pick the sales role and stage. A representative updating an opportunity has different needs from a manager reviewing a forecast. Use sample values that are easy to read and avoid presenting them as real revenue or customer evidence.
Plan the product story
- Choose a fictional opportunity with a simple history. Prepare the correct permissions and starting stage before capture.
- Show one action and its consequence. Updating a field, setting a follow-up or moving a stage should lead to a visible saved state.
- Explain the next person or view affected. If a manager’s dashboard changes, show the relevant result without implying every report updates immediately in every configuration.
An illustrative workflow
Begin with a sample opportunity that needs a follow-up date. Set the date, save the record and show where it appears in the activity queue. That illustrates a repeatable task without recording a real prospect’s contact details.
Limits and checks
Saving records, sending messages and changing sales stages may have real side effects. Use a demo environment and authorised actions; do not assume an agent may modify a live pipeline.
Your next step
Write the task as “When this happens, this person does this, and this view changes.” Use that sentence to select the minimum necessary shots.
References and scope
Examples are illustrative production guidance, not measured customer results. General workflows are not promises of product compatibility. Read our editorial approach and current Demovela scope.