Back to all articlesTemplate planning

Decide When Optional Content Requires a Separate Template Brief

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A collection message starts with a simple instruction: your order is ready; collect it here. Then someone adds an appointment time, another person adds instructions for a nominated collector, and a third suggests parking advice. The proposed template now depends on several combinations of details, and reviewers cannot tell which complete message a recipient will actually read.

Create a separate template brief when a detail changes the recipient’s required action enough that one common message becomes ambiguous, contradictory, or difficult to review. Keep a stable common message when the differences are only values, such as an address or collection reference. Remove optional content when it does not materially help the recipient complete the task.

For optional content in WhatsApp template planning, the decision should turn on readable messages and clear review examples—not on keeping the brief count as low as possible. The worked example below shows how to make that decision before anyone invests in implementation.

1. Separate optional data from optional instructions

A field can be optional in a business record without being optional in the message a recipient needs. If collection requires an appointment, the appointment time is essential for that recipient. Calling it optional because other orders do not need it hides the real composition problem.

Start by distinguishing three kinds of variation:

  • Value variation: the same instruction applies, but the address, date, reference, or other value changes.
  • Instruction variation: the recipient must do something different, such as attend a booked slot rather than arrive during general opening hours.
  • Supplementary detail: the information may be helpful, but its absence does not prevent collection.

Value variation usually supports common wording. Instruction variation deserves a closer comparison of complete messages. Supplementary detail must earn its place rather than being included simply because the business stores it.

The useful question is not “Can this information fit?” It is “Will the recipient understand what applies to them without interpreting a set of alternatives?” That question also gives reviewers a clearer job: assess a complete instruction rather than mentally assembling fragments.

2. Establish the common message before adding exceptions

Write the shortest complete message that serves the shared purpose. For collection instructions, that purpose is to tell the recipient that an order is ready and explain how to collect it. It is not to reproduce every collection-related field in the record.

Fictional worked example: A business called Cedar Supply is planning messages for ready-to-collect orders. All names, references, times, locations, rules, and messages in this example are hypothetical. They illustrate composition choices, not a product capability or a policy requirement.

Cedar Supply’s ordinary collection message could read:

Your order CS-184 is ready to collect from Cedar Supply, North Entrance. Collect during collection hours, Monday–Friday, 10:00–16:00. Bring your collection reference CS-184.

This establishes a stable spine: readiness, location, attendance instruction, and what to bring. The reference appears twice because it identifies the order and provides a concrete collection instruction. An editor could instead combine those functions if the resulting message remains clear.

Now introduce only the differences that matter. In this hypothetical business, some orders have a booked collection slot. Some have a nominated collector rather than the customer collecting personally. Parking advice is available for some orders, but the collection entrance is already clearly identified.

Those differences should not be treated as interchangeable blanks. A booked slot replaces the general attendance instruction. A nominated collector changes who needs the information and what that person must present. Parking advice may add nothing necessary.

3. Map every meaningful combination in one review table

The following filled content-combination table uses three yes-or-no details: a booked slot, a nominated collector, and an optional parking note. In this hypothetical scenario, the business requires nominated collectors to bring their own photo ID and the collection reference. That is an assumed business rule for the example, not a general requirement.

The table records the proposed editorial decision for every combination. It is a planning artifact, not a specification for conditional blocks or workflow construction.

Hypothetical collection-instruction combination table

Row | Booked slot | Nominated collector | Parking note | Decision
A   | No          | No                  | No           | Brief 1
B   | No          | No                  | Yes          | Brief 1; omit parking
C   | Yes         | No                  | No           | Brief 2
D   | Yes         | No                  | Yes          | Brief 2; omit parking
E   | No          | Yes                 | No           | Brief 3
F   | No          | Yes                 | Yes          | Brief 3; omit parking
G   | Yes         | Yes                 | No           | Brief 4
H   | Yes         | Yes                 | Yes          | Brief 4; omit parking

Shared wording within each pair:
A/B: Customer collects during general collection hours.
C/D: Customer collects at the booked slot.
E/F: Nominated collector attends during collection hours.
G/H: Nominated collector attends at the booked slot.

Shared purpose across all briefs:
Explain how to collect an order that is ready.

Rows A and B share wording because removing the parking note leaves exactly the same task. The same reasoning applies to C/D, E/F, and G/H. There is no reason to create a parking-specific brief if the note is unnecessary.

Rows A and C do not share the attendance sentence: “during collection hours” and “at your booked slot” carry different instructions. Rows A and E differ in the collector requirement. Those differences justify separate briefs in this example because a combined message would ask readers to determine which instruction applies.

The outcome is four purpose-preserving briefs, not eight briefs for eight combinations. Nor is four a universal target: if the real collection rules are simpler, fewer briefs may be appropriate.

4. Turn the table into complete, reviewable briefs

Each brief should state its use case, required information, and exclusions, alongside a complete example. A list of fields alone will not reveal whether the finished message reads naturally.

Brief 1: Customer collection during general hours

Use when: the customer is collecting and no booked slot applies. Required information is the collection reference, location, and collection hours. Exclude appointment language, nominated-collector requirements, and parking advice.

Your order CS-184 is ready to collect from Cedar Supply, North Entrance. Collect during collection hours, Monday–Friday, 10:00–16:00. Bring your collection reference CS-184.

Brief 2: Customer collection at a booked slot

Use when: the customer is collecting at an agreed appointment. Require the collection reference, location, and full slot details. Do not also invite attendance during general hours.

Your order CS-185 is ready to collect from Cedar Supply, North Entrance. Your booked collection slot is Tuesday, 14 July, 11:00–11:30. Bring your collection reference CS-185.

Brief 3: Nominated collector during general hours

Use when: a nominated collector will attend without an appointment. Require the reference, location, hours, and verified collector instructions. In this example, the message goes to the customer, who must pass the instructions to that collector.

Your order CS-186 is ready to collect from Cedar Supply, North Entrance. Please ask your nominated collector to come during collection hours, Monday–Friday, 10:00–16:00, and bring their photo ID and collection reference CS-186.

Brief 4: Nominated collector at a booked slot

Use when: the nominated collector must attend at the booked appointment. Require the reference, location, slot details, and verified collector instructions. Exclude general-hours wording.

Your order CS-187 is ready to collect from Cedar Supply, North Entrance. Please ask your nominated collector to come on Tuesday, 14 July, 11:00–11:30, and bring their photo ID and collection reference CS-187.

These examples preserve the same purpose while changing only the instructions that need to change. They also expose a recipient question that a field list would miss: is the business addressing the customer or the collector? A message addressed directly to the collector would need different pronouns and a separately considered use case.

5. Compare the three options before accepting more briefs

A stable common message is attractive because it concentrates editorial maintenance. For example, “Your order is ready at North Entrance. Check your collection details before travelling” avoids most optional wording. But it is only adequate if the recipient has an identified, reliable place to find those details. Otherwise, the apparent simplicity moves essential work onto the reader.

Separate briefs keep instructions explicit. Their cost is maintaining several related pieces of content. A location description or collection rule may need to be checked across all of them. That is a real trade-off, but it does not justify combining incompatible instructions.

Removal is the strongest choice for detail that adds length without changing successful collection. In this example, the optional note says that visitor parking is available beside the building. Because the entrance is already clear and parking is not necessary to complete collection, the editor removes it.

That decision would change if the supposed parking note actually said that vehicles must use a particular access gate. It would then be an access instruction, not a convenience note. Reclassify it and assess its combinations rather than continuing to omit it.

Use these comparison questions:

  • Can the common message state the full action without “if applicable” or competing alternatives?
  • Does splitting preserve the original purpose while making the action clearer?
  • Would removing the detail leave the recipient unable to complete the task correctly?
  • Can a reviewer determine the intended use from the brief and its example alone?

6. Test awkward cases, not just polished examples

A friendly example with short values can conceal a weak brief. Review complete messages using the longest plausible location description, a slot that spans a time range, and the most demanding collector instruction the brief genuinely needs to support.

Also test absence. If a message requires an appointment but no appointment is known, that is not merely a sentence-editing problem. The brief lacks information needed to fulfil its purpose. Do not replace the missing time with vague wording such as “at the agreed time” unless there really is an established agreement that the recipient can identify.

Useful failure signals include:

  • Stranded grammar: a phrase such as “bring your” remains without a meaningful object.
  • Competing instructions: a booked appointment appears alongside an invitation to arrive at any time during opening hours.
  • Unclear pronouns: “your ID” could mean the customer’s ID when the collector needs their own.
  • Overloaded fields: a value intended for a time sometimes contains a full explanation or another instruction.
  • Unreviewable samples: reviewers see fragments or blanks rather than the complete recipient-facing message.

When a test fails, return to the table. Correct the shared wording, move the combination to a separate brief, or remove nonessential content. Do not repair each sample independently while leaving the underlying brief ambiguous.

7. Keep editorial acceptance separate from platform review

A clear internal brief is not the same as an approved WhatsApp template, and approval is not a guarantee of delivery. For WhatsApp Business Platform messaging, approved templates are used to initiate conversations and to message outside the customer-service window. A user message opens or resets that 24-hour window. Recipient permission and opt-outs also remain relevant; a readable collection instruction does not replace those obligations.

Check the current WhatsApp Business Messaging Policy for precise requirements. Treat the composition decision, preparation for template review, and actual delivery as separate states. The combination table is evidence that the proposed content has been considered—not evidence of approval or delivery.

This exercise also does not determine whether a particular workspace supports optional content blocks or how a workflow selects a message. Resolve the writing first. Implementation choices should not silently decide which instructions the reader receives.

8. Finish with a bounded editorial review

For the next proposed template with optional details, produce one combination table and one complete example for each proposed brief. Assign every meaningful combination to shared wording, a separate brief, or an explicit removal decision.

Ask a reviewer who did not write the messages to identify, from each example, who collects, where they go, when they attend, and what they bring. Record unanswered questions and conflicting interpretations rather than accepting a general “looks fine.”

A practical completion measure is that every listed combination has a documented decision, every proposed brief has a complete example, and no essential collection instruction remains unresolved. If a reviewer still needs the author to explain which sentence applies, revise the brief before moving it forward.

Template planningWhatsAppMessage compositionContent review

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