Back to all articlesTemplate planning

Write a Template Content Brief That a Writer Can Use Without Guessing

Alactic Editorial9 min read

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

A request to ask customers for an appointment update is not yet a draftable brief. Has the customer booked, requested a time, or reported a problem? Does the business need a reply, or merely want to communicate a confirmed booking? A writer who supplies those answers is making business decisions, not just writing copy.

A usable template content brief specifies the triggering situation, recipient knowledge, essential facts, intended action, and prohibited assumptions. It also identifies who resolves missing information and what happens when a required value is absent.

The fictional worked example below turns a vague request into a service appointment confirmation. It covers commissioning and reviewing the content, not trigger implementation, service triage, or campaign planning. All businesses, booking details, and message samples in the example are hypothetical, not Alactic customer results.

1. Resolve the business decision before choosing words

An appointment message could acknowledge a request, confirm an accepted booking, remind someone about a visit, or ask them to choose a time. Each requires different facts and actions.

Ask the requester to complete this sentence:

When this situation is true, give this recipient the facts needed to take this action, or understand that no action is required.

If the answer still contains alternatives such as pending or confirmed, the request is not ready. Resolve the business state first. Saying an appointment is confirmed and asking the customer to confirm it are not interchangeable stylistic choices.

The brief need not explain how software detects the situation. It must describe the situation precisely enough that the writer can distinguish it from nearby cases.

2. Work through the vague request

Hypothetical starting request: Write a WhatsApp template asking customers for an update about their service appointment.

The requester and service coordinator resolve the following questions before drafting:

  • What happened? The customer selected an appointment window, and the coordinator accepted it. The booking is confirmed.
  • What does update mean? The business wants the customer to check the booked details and report errors. It does not need a routine status reply.
  • Who receives the message? The booking’s named contact. Do not assume that person owns the property or will attend the visit.
  • What does the recipient know? They requested a washing-machine service visit and selected a window. They may not remember the reference.
  • What is being confirmed? The visit’s date, arrival window, and address, not a diagnosis, repair outcome, price, or duration.
  • What should happen next? The recipient checks the details and replies only if something is wrong or a different appointment is needed.
  • What does a reply accomplish? A coordinator reviews the request. Replying does not itself change the booking.

The resolved task is therefore to confirm an accepted appointment and invite corrections, not chase an update. This change in purpose should be recorded in the brief rather than left in a meeting conversation.

3. Hand over this filled content brief

This hypothetical artifact is intended to be reusable: retain the headings, replace the business decisions, and rebuild the variable map for each message purpose.

Purpose and ownership

  • Message: Service appointment confirmation for fictional Northline Appliance Service.
  • Objective: Provide an accurate booking record and a clear way to flag incorrect details.
  • Qualifying situation: A service coordinator has accepted the selected window and recorded the booking as confirmed.
  • Excluded situations: Pending requests, reminders, changes, cancellations, arrival notices, and diagnostic questions.
  • Owners: The writer owns wording; the service coordinator approves booking facts and the reply process; the sending team checks permission and current channel requirements.

Recipient and action

  • Recipient context: The named contact requested a washing-machine service visit. Internal status terms and technician details are not assumed knowledge.
  • Language: English for this draft. Other language versions need their own wording review.
  • Primary action: Check the appointment details.
  • Conditional action: Reply in the same conversation if details are incorrect or a different appointment is needed.
  • No-action case: No reply is needed when the details are correct.
  • Reply handling: A service coordinator reviews replies in this fictional setup. No response-time promise is authorised.

Fixed content and constraints

  • Business identity: Northline Appliance Service is fixed wording, subject to the business owner’s approval.
  • Structure: Business identity, confirmed status, booking details, then the reply instruction.
  • Tone: Calm, direct, and service-focused.
  • Keep fixed: The meaning of the action instructions and the distinction between requesting and accepting a change.
  • Exclude: Promotions, payment requests, preparation advice, attachments, and unsupported links.
  • Do not imply: A guaranteed repair, exact arrival minute, free visit, technician assignment, response deadline, or automatic rescheduling.

Variable map and missing-value decisions

These are editorial placeholder names, not platform syntax or integration instructions. Every value below is hypothetical review data. Actual messages must use the corresponding verified booking values, never these examples.

  • {booking_reference} means the customer-facing booking identifier. Review value: NS-4821. Source: booking record; factual owner: service coordinator. If absent, block drafting approval and return for clarification. Do not invent an identifier or silently remove the reference line.
  • {service_description} means the approved customer-facing description of the booked visit. Review value: washing-machine service. Source: booked service record; owner: service coordinator. If absent or only an unexplained internal code is available, block approval until a description is supplied. Do not infer a repair or diagnosis.
  • {appointment_date} means the accepted visit date. Review value: 14 October 2026. Source: confirmed booking; owner: service coordinator. Absence blocks approval. Use a written month in this English version.
  • {arrival_window} means the accepted arrival range, expressed in local time at the service address. Review value: 10:00 am–12:00 pm. Source: confirmed booking; owner: service coordinator. Missing or ambiguous timing blocks approval. It is not a completion-time estimate.
  • {service_address} means the customer-verified visit location, including the unit where applicable. Review value: 18 Example Lane, Unit 4. Source: verified booking address; owner: service coordinator. Missing or unresolved address details block approval.
  • Confirmed status is a required eligibility fact, not a text placeholder. Review value: confirmed. Source: accepted booking; owner: service coordinator. Missing, pending, or contradictory status blocks use of this brief.

No booking-specific field in this version permits omission. If the business wants a reference-free version, it must explicitly approve that revised brief and its acceptance criteria. An empty value is not permission to create a shorter variant.

For commissioning, the hypothetical values above support wording review. Before use for any actual booking, missing required values block preparation of that booking’s message. A complete sample does not prove actual booking data is complete.

4. Compare the draft with the variable map

Reusable wording draft: The braces identify editorial variables only.

Northline Appliance Service: Your {service_description} appointment is confirmed.
Booking: {booking_reference}
Date: {appointment_date}
Arrival window: {arrival_window}, local time at the service address
Address: {service_address}
Please check these details. If anything is incorrect or you need a different appointment, reply here so our service coordinator can review your request. No reply is needed if the details are correct.

Hypothetical rendered sample: Each substituted value maps directly to the filled variable map.

Northline Appliance Service: Your washing-machine service appointment is confirmed.
Booking: NS-4821
Date: 14 October 2026
Arrival window: 10:00 am–12:00 pm, local time at the service address
Address: 18 Example Lane, Unit 4
Please check these details. If anything is incorrect or you need a different appointment, reply here so our service coordinator can review your request. No reply is needed if the details are correct.

The draft confirms an accepted booking without asking the customer to confirm it again. It also makes a requested change subject to review rather than promising immediate rescheduling.

Preparation instructions are absent because none were supplied. Plausible advice about moving appliances or arranging access would still be an unsupported business requirement. Likewise, a friendly promise to restore the appliance would exceed what a visit confirmation establishes.

5. Test missing information, not just completed fields

A populated field can still leave the writer guessing. Apply these checks before assigning the draft:

  1. State test: Is the booking accepted rather than merely requested? If both remain possible, stop.
  2. Recipient test: Does the wording make sense using only the knowledge specified in the brief?
  3. Ownership test: Does every material fact have a source and someone authorised to resolve uncertainty?
  4. Action test: Can the recipient tell when to reply, when to do nothing, and what a reply accomplishes?
  5. Blank-value test: Does every variable have an explicit blocking or omission rule?
  6. Contradiction test: Do the facts and action describe the same business state?

For example, removing NS-4821 from the hypothetical input must produce a clarification request, not a draft with an empty Booking line. Replacing the service description with an internal code also fails until the coordinator supplies customer-facing wording.

A useful question names the unresolved decision: ask whether the booking is already accepted or whether the customer’s reply makes it accepted. A broad request for more context may simply produce another vague answer.

6. Keep content acceptance separate from sending readiness

A clear brief does not establish recipient permission, template approval, or delivery. Booking context alone is not proof of permission to contact someone through WhatsApp.

For WhatsApp Business Platform messaging, approved templates are used to initiate conversations and outside the 24-hour customer-service window. That window opens or resets with a user message. Honour opt-outs and check the current WhatsApp Business Messaging Policy for precise requirements. Template approval does not guarantee delivery.

Keep content acceptance, campaign preparation, template review, and actual delivery as separate states. The writer should not be asked to certify operational readiness through polished copy. If replies are not monitored, the reply instruction needs a different approved route. If automation is involved, provide a clear path to human help.

7. Accept the draft against explicit criteria

For this fictional brief, accept the content only when:

  • The business and confirmation purpose are clear.
  • The service, reference, date, arrival window, and address match the approved hypothetical values during sample review.
  • Each placeholder maps to exactly the defined booking fact, source, owner, and missing-value rule.
  • Confirmed status has been established, not inferred from available dates.
  • The arrival range is not presented as a completion promise.
  • Correct details require no reply; change requests go for coordinator review.
  • No unsupported price, diagnosis, outcome, technician, or response-speed claim appears.
  • No actual booking message would substitute sample data for missing values.

There are deliberate trade-offs. Including the address lengthens the message but helps the customer spot a location error. Explaining the arrival window uses space but protects its meaning. If either is shortened, the factual approver should decide what can safely be removed.

When review exposes a business contradiction, revise the brief as well as the copy. Otherwise, another writer can reproduce the same defect.

8. Test the handoff on the next request

Complete the five core fields for the next vague request, then add a variable map before commissioning the writer. Assign an owner to every unresolved fact and stop at blocking gaps.

Record the writer’s blocking clarification questions and separate factual corrections from style edits during review. These observations show where decisions are still leaking into the writing stage; they are not performance guarantees. The immediate target is a draft that requires no invented business facts and a review that can trace every variable back to an approved meaning.

Template planningContent briefsWhatsAppBusiness communications

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