Choose Between a Real Photograph, Illustration, and Mockup
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A polished mockup can make a proposed layout look like a finished installation. A photograph can show an entire machine while leaving the recipient unable to find the control they need. Either image can look professional and still be the wrong representation.
Choose a real photograph when the recipient needs evidence of visible appearance or condition. Choose a schematic illustration when they need to understand a relationship, sequence, or location. Choose a mockup when they need to evaluate an explicitly proposed appearance or arrangement.
The deciding question is: What should the recipient be able to conclude from this image, and what must they not assume? This matters particularly in reusable business message templates, where a visual may remain in use after its original context has changed.
1. Define the decision before choosing the asset
Complete this sentence before opening an image library: “After seeing this message, the recipient should be able to…” Use an observable action, such as identify a damaged corner, locate a compartment, or comment on a proposed panel layout.
Then identify the information needed for that action. “Understand our display” is too broad to guide production. “Confirm whether the photographed chip is the damage being reported” gives the creator a subject, a viewpoint, and a boundary for the claim.
Write down the most consequential unsupported assumption, too. A recipient might assume that a sample photograph shows their order, that a diagram establishes dimensions, or that a rendered installation already exists. That assumption determines what context the message needs.
Sometimes the task requires two assets. Give each a separate job rather than asking one image to carry conflicting meanings. A photograph can locate a fault on the actual object; a companion drawing can explain which component is under discussion. If neither changes the recipient’s decision, omit it.
2. Check what the available evidence can support
A photograph records what was visible from a particular viewpoint at capture. It does not automatically establish current condition, hidden damage, dimensions, availability, or performance. Before selecting it, confirm the subject, capture date, relevant version, and whether the view includes the feature being discussed.
For condition-oriented messages, preserve the original image. Cropping can remove distractions, but it can also remove the label that identifies the unit or the context that locates a defect. Distinguish added arrows and highlights from features in the scene. Avoid edits that change the condition the recipient is assessing.
For a schematic, identify what simplification removes. Background furniture may be irrelevant; an access panel or orientation marker may not be. Use the same component names in the drawing and message. Calling something “upper tray” in one place and “Tray B” in another creates an unnecessary translation task.
For a mockup, identify which elements are confirmed and which are proposed before production begins. A realistic composite can blend those categories so convincingly that reviewers overlook the difference. Do not depict an unverified product capability as a working demonstration. Where information is missing, leave the uncertainty visible rather than filling it with plausible detail.
3. Use this filled representation-choice table
Fictional worked example: A supplier is helping a business customer review a replacement reception display. The customer needs to inspect existing damage, understand proposed shelf use, and comment on a possible front panel. Every detail in the following comparison is hypothetical.
| Criterion | Real photograph | Schematic illustration | Mockup |
|---|---|---|---|
| Recipient task | Identify damage on the existing display using a full view and a close-up of its chipped lower-right corner. | Understand proposed use of the upper shelf for incoming items and the lower shelf for items ready for collection. | Comment on the proposed front-panel arrangement shown in the reception setting. |
| Supported conclusion | The photographed unit has the visible chip shown in these views at capture. | The proposed operating arrangement assigns a different purpose to each shelf. | The proposed panel could have the depicted visual arrangement; the image is a discussion concept. |
| Limitation | Does not establish internal condition, dimensions, or damage outside the views. | Does not establish capacity, measurements, materials, or final appearance. | Does not verify fit, construction feasibility, availability, finish, or final color. |
| Labeling | “Existing display, unit R-17, captured 12 May 2026. Arrow added to identify chip.” | “Proposed shelf use. Front view; schematic, not to scale.” Use matching shelf names in the message. | “Concept mockup, proposal B. Not installed.” Identify the front panel as digitally replaced. |
| Review gate | Confirm both views show unit R-17 and the close-up can be located within the full view. | Have the responsible colleague confirm shelf assignments and the meaning of the movement arrow. | Confirm no caption or message describes the proposed panel as existing, installed, or confirmed for production. |
Fallbacks for this example: Request another angle if the close-up cannot be matched to the full display. Replace an ambiguous movement arrow with numbered text. If the contextual mockup still looks like a completed installation, use a flat panel layout instead.
This table is also a reusable brief: retain the criteria, replace the scenario details, and require a specific answer in every cell. An empty limitation or review-gate cell signals that the asset is not ready for production.
4. Work through the message, not just the images
In this hypothetical example, the supplier initially plans to send only the attractive panel mockup with the request, “Please approve the replacement display.” That wording combines three decisions: identifying the reported damage, agreeing on shelf use, and approving an appearance. It also leaves “approve” undefined.
The revised approach separates the requests. First, the supplier sends the full photograph and close-up with this text: “These images show unit R-17, captured 12 May 2026. The added arrow identifies the chipped lower-right corner. Is this the damage you reported?” The recipient can now answer a factual identification question without appearing to accept a replacement design.
After confirming the damage reference, the supplier shares the schematic and mockup as a proposal review:
Proposal B for discussion: the diagram assigns incoming items to the upper shelf and ready-for-collection items to the lower shelf. The concept mockup shows a possible front-panel arrangement; it is not an installed display, and fit and finish remain unconfirmed. Please comment separately on shelf use and panel appearance. Your response will guide the next specification review, not authorise production.
The worked result is a clearer decision boundary, not a claimed sales improvement. A useful response would identify which shelf assignment or panel detail needs changing. A response such as “Is this already installed?” would reveal that the mockup’s status still needs clarification.
If the recipient requests approval of dimensions or materials, the team should obtain the relevant specification rather than treating either visual as sufficient evidence. The representation has done its job when it reveals the next information needed, not merely when it attracts a positive reaction.
5. Write labels that identify the actual uncertainty
“For illustration only” gives little help if the recipient cannot tell whether the uncertainty concerns scale, color, configuration, or the entire scene. Name the limitation that could change their decision.
- Identify the subject: “Sample-unit photograph; packaging differs from your order” is more useful than “Image indicative.”
- Identify the omitted check: “Proposed layout; not measured for fit” tells the recipient what remains unresolved.
- Identify the changed element: “Front panel digitally replaced; surrounding reception area unchanged” separates the proposal from its context.
- Identify the relevant version: Put the proposal reference in the caption and message so comments can be matched to the correct asset.
These are hypothetical wording examples, not platform approval rules. Choose the shortest wording that preserves the necessary distinction.
Put essential status on the visual when separation from the caption would materially mislead. Explain additional limitations in adjacent text. Do not rely on an internal filename, a previous conversation, or text too small to read in the intended preview.
A label cannot rescue a contradictory presentation. If a large headline announces a finished installation while a small caption calls it a concept, change the headline and visual hierarchy before asking for review.
6. Run one combined preview and interpretation review
Review the assembled message, not just the source file. Use its intended crop, accompanying text, and likely viewing size. Do not assume the recipient will enlarge the image before deciding what it means.
- Check identity and version. Match the subject reference, capture information, proposal version, caption, and recipient context.
- Check task visibility. Confirm that the relevant damage, label, arrow, or proposed change can be found without searching through unrelated detail.
- Check independent interpretation. Ask a colleague who did not create the asset: “What does this establish?” and “What remains unconfirmed?” Do not explain the answer first.
- Check separation risk. Inspect the image without its caption. Add essential status to the image if forwarding or reuse could otherwise change its meaning.
- Check the text equivalent. State the key instruction or decision in message text rather than making image-only wording carry the whole task.
- Record the correction. Mark the asset ready, needing relabeling, needing replacement, or awaiting evidence. Name the owner of the next action.
Record concrete interpretation failures rather than aesthetic preferences: the reviewer mistook a proposal for an installation, could not locate the chip, or inferred measurements from the drawing. Recheck the corrected message against the same failure.
For reusable templates, also identify what must be refreshed for each use. A process diagram may remain suitable while an item-specific photograph must change. A recurring caption must never turn a sample image into an apparent record of the recipient’s order.
For WhatsApp use, keep visual accuracy, template approval, and actual delivery as separate checks. Template approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for messaging requirements; passing this visual review does not establish sending readiness.
7. Recover when the asset cannot support the task
No suitable photograph: Request the missing view or send a text-only update identifying what remains unconfirmed. Do not substitute a realistic mockup for evidence of condition. If only an older photograph is available, state its date and narrow the claim accordingly.
A cluttered photograph: Try a clearer capture or a restrained annotation. If a companion schematic is necessary, use matching labels so the recipient can connect it to the actual object.
An overloaded schematic: Split the explanation into stages. Remove decorative detail first, not distinctions that change the recipient’s action. If an arrow could mean either movement or a physical connection, replace it with an explicit label.
A mockup repeatedly mistaken for reality: Stop adding longer disclaimers to the same misleading composition. Separate the existing scene from the proposed layout or switch to a flat concept view.
If an ambiguous asset has already been shared, correct the specific misunderstanding. Identify the earlier version, state what was proposed rather than confirmed, and supply the replacement evidence or concept. Update the reusable source too, so the same problem is not reproduced in the next message.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications