Choose Which Template Details Stay Fixed and Which Become Variables
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A reminder draft that says [message_text] leaves almost nothing for a reviewer to inspect. A draft that hard-codes an appointment time makes the opposite mistake: it treats a changing fact as stable wording. Both problems start with the same missing decision: what must this message always mean?
Use this working rule: keep the message purpose, relationships between facts, and recipient action fixed; make recipient-specific facts variable. Then read complete rendered messages to check whether those boundaries work. A readable skeleton is useful, but it is not enough.
The filled worksheet below concerns an appointment reminder. The business, people, dates, addresses, and messages are fictional; all examples are hypothetical. Bracketed names are editorial placeholders, not API syntax. This is a content-design exercise, not an implementation guide or approval prediction.
Start with the meaning that must survive substitution
Before marking variables, write a plain-language statement of the message’s job. For this hypothetical reminder:
Remind a recipient of their existing appointment with Northline Repairs, identify when and where it will happen, and explain how to request a change.
This establishes boundaries. The message is a reminder, not a booking confirmation, cancellation notice, or promotion. Changing a date should not change that purpose. Changing a location should not silently turn a workshop appointment into a home visit.
Next, identify the relationships the reader needs to understand. The date and time belong to the appointment. The address identifies where the recipient should attend. A reply requests a change; it does not complete one. Fixed wording should make these relationships explicit.
Distinguish stable meaning from potential reuse. A business name can stay fixed when the template serves that business alone. It does not need to become variable merely because another organisation could use a similar sentence. Design for the actual message family, not every imaginable future use.
Make the message’s job visible in the skeleton
Consider this hypothetical starting draft:
Hi [first_name], [appointment_sentence]. [location_sentence]. [next_step].
Most of its meaning is hidden. The appointment sentence could announce a reminder or cancellation. The location sentence could describe a workshop or home visit. The next step could ask for a reply, payment, or document.
A more inspectable editorial skeleton is:
Hello [first_name]. This is a reminder of your appointment with Northline Repairs on [appointment_date] at [appointment_time].
Your appointment is at [workshop_name], [workshop_address].
Need to request a different time? Reply to this message.
The purpose is now visible before values are supplied. The wording also narrows the use case to appointments at a workshop. That is a useful constraint: a home visit needs a different description of who travels where.
The reply instruction is appropriate only if the business handles those requests. If it does not, change the fixed instruction before using the draft. Do not conceal an unsupported process inside a free-text action variable. If replies enter an automated workflow, define a clear route to a human for requests the automation cannot handle.
Filled worksheet: what stays fixed
Hypothetical worksheet scope: reminders for existing, scheduled appointments at Northline Repairs workshops. Excludes cancellations, remote consultations, home visits, and appointments awaiting confirmation.
Stable intent: remind the recipient of an appointment that remains scheduled.
Expected action: attend as scheduled or reply to request another time. A reply does not mean the change has been accepted.
- Fixed: the greeting structure. Use “Hello” with a usable first name. If no suitable name is available, use a separately reviewed name-free opening rather than leaving broken punctuation or an empty slot.
- Fixed: the reminder statement and business identity. These establish why the message exists and who the appointment is with. A value must not replace them with cancellation or promotional wording.
- Fixed: the connecting words around date and time. “On” and “at” show how the values relate to the appointment. This skeleton is for English-language messages; another language requires its own sentence review.
- Fixed: the workshop attendance statement. It establishes that the recipient should attend the named site. It does not fit a technician visiting the recipient.
- Fixed: the change-request instruction. It gives a consistent action without promising an accepted change.
Recorded decision: this message family has one purpose, one attendance model, and one change-request route. If any changes, review another wording variant rather than expanding a variable to absorb the difference.
Filled worksheet: define each variable’s boundary
A variable needs more than a label. Record the fact it supplies, what is excluded, and the response to unsuitable data. The following entries form a reusable, filled annotation worksheet.
- [first_name]
Purpose: address the recipient.
Hypothetical value: Maya.
Boundary: a usable recipient name, not a greeting, account note, or instruction.
Failure response: use the reviewed name-free version if the name is missing or unsuitable. Do not insert an account reference or pretend that “customer” is a verified name. - [appointment_date]
Purpose: identify the appointment’s calendar date.
Hypothetical value: 18 November 2027.
Boundary: the date only, not “tomorrow,” a time, or a schedule-change explanation.
Failure response: resolve missing or conflicting dates before release. A written month helps avoid ambiguity between numeric date formats. - [appointment_time]
Purpose: identify the scheduled start time.
Hypothetical value: 10:30 am.
Boundary: a clock time, with a time-zone label where the audience needs one. It is not an arrival instruction or an arrival window.
Failure response: if only an arrival window exists, review wording for that scenario rather than presenting it as a precise start time. - [workshop_name]
Purpose: distinguish the appointment site.
Hypothetical value: Riverside Workshop.
Boundary: the site name, not directions, promotional language, or a location sentence.
Failure response: resolve an unclear site name against the appointment details before release. - [workshop_address]
Purpose: identify where the recipient should attend.
Hypothetical value: 24 Willow Lane, Eastford.
Boundary: a usable workshop address, without repeating the fixed introduction.
Failure response: hold a message with a missing address. Do not substitute the recipient’s home address into workshop wording.
These definitions allow different value lengths without allowing different message purposes. A multiword address can be a well-bounded fact; a short instruction can still be an unsuitable value.
Record rejected choices and their reasons
Preserve rejected options alongside accepted boundaries. Otherwise, a later editor may restore the same problem while trying to make the template more reusable.
- Rejected: [appointment_sentence]. It hides appointment status, date, time, and sender relationship in one value. Keep the reminder statement fixed and expose the changing facts.
- Rejected: [next_step]. It could switch the action from replying to calling, paying, or uploading information. Review a separate variant when the supported action differs.
- Rejected: [location_sentence]. It could change workshop attendance into a home visit without changing the visible skeleton.
- Rejected: [optional_note]. An unrestricted note could add instructions or contradict the appointment details. A recurring instruction needs a defined place in reviewed wording.
- Rejected design choice: a fixed “10:30 am”. This is not a correction to the displayed starting draft, which concealed timing inside [appointment_sentence]. It is an alternative considered and rejected because appointments occur at different times.
Northline Repairs remains fixed because the worksheet covers that business alone. Appointment time becomes variable because it changes within the intended message family. The distinction follows actual use, not a rule that every proper noun or number must be variable.
Inspect complete rendered messages
Use fictional values that exercise the boundaries, not just the shortest name and simplest address. Read each message as a recipient would, without referring back to the worksheet.
Hypothetical render: ordinary workshop appointment
Hello Maya. This is a reminder of your appointment with Northline Repairs on 18 November 2027 at 10:30 am.
Your appointment is at Riverside Workshop, 24 Willow Lane, Eastford.
Need to request a different time? Reply to this message.
Result: the purpose, date, time, location, and action remain explicit. No value introduces a new instruction. This render passes the content-boundary review, not a platform approval or delivery check.
Hypothetical render: longer site details
Hello Alexandra. This is a reminder of your appointment with Northline Repairs on 22 November 2027 at 4:45 pm.
Your appointment is at North Industrial Estate Workshop, Unit C, 86 Foundry Road, Westbridge.
Need to request a different time? Reply to this message.
Result: the longer values still fit the sentence. The reviewer should also verify that the site is identifiable from the supplied details. Grammatical completeness alone does not establish that an address is useful.
Hypothetical failed render: incompatible attendance model
Hello Sam. This is a reminder of your appointment with Northline Repairs on 24 November 2027 at 9:00 am.
Your appointment is at Home visit, 7 Meadow Close, Eastford.
Need to request a different time? Reply to this message.
Result: reject this use. “Home visit” is not a workshop name, and the sentence obscures who travels where. The remedy is separately reviewed home-visit wording, not a more permissive location variable.
Also test a missing name, missing address, and time containing extra instructions. A missing name can follow the defined name-free route. A missing address requires resolution. Extra instructions must not slip through merely because the time itself is correct.
Choose a narrower variable or a separate variant
More fixed wording makes meaning easier to inspect but can create additional variants to maintain. Broader variables reduce visible duplication while moving decisions into individual values.
Keep a variable when the difference answers the same question: which date, which time, or which workshop? Consider another variant when the question changes: where should the recipient go, or will someone come to them?
Remove the values and read the skeleton. Can a reviewer identify the purpose, attendance model, and requested action? Restore the values and ask whether they complete that meaning or introduce another instruction.
Do not split a coherent fact merely to maximise fixed text. Breaking a workshop name into fragments adds maintenance without necessarily improving clarity. Conversely, do not merge date, time, and a change explanation simply because they appear together.
Hand off the worksheet with a disposition record
The content handoff is complete when each variable has a boundary, representative renders have been reviewed, and each failure has a recorded response: correct the fact, use reviewed alternative wording, or hold the message.
Hypothetical filled disposition record:
- Finding: Sam’s render puts “Home visit” in [workshop_name].
- Classification: unsupported scenario, not a spelling or formatting error.
- Decision: hold this message; refer it for home-visit wording review.
- Owner: appointment operations reviewer.
- Release condition: confirm the attendance model and review the complete replacement render before authorised release.
This handoff covers content only. Keep campaign preparation, template review, and actual delivery as separate states. Recipient permission matters, and opt-outs must be honoured. Under the WhatsApp Business Messaging Policy, approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Check the current policy for precise requirements; template approval does not guarantee delivery.
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