Specify the decision the pilot serves
A pilot should answer a bounded question: can an appropriately permitted audience receive a clear non-emergency notice while staff manage the resulting work? It should not be a vague attempt to prove that SMS increases attendance. Write the required behaviors and the conditions that would lead you to keep the existing channel instead.
Use a controlled scope
Follow the service’s rules and obtain the necessary permissions before any actual messages. Use non-sensitive content and a small appropriate scope. Include the sender workflow, recipient view, reply routing, preference handling and the relevant accounting behavior. Do not enroll real people without authorization or repeat a send because a report has not updated yet.
Record expected, observed and unknown
For each requirement, keep the expected outcome separate from what actually happened. A message appearing in the sender interface is not proof that a recipient received or understood it. A successful single test does not establish all-device compatibility or reliable future delivery. If a transmission is uncertain, reconcile it before considering another action.
Make the resulting decision
Continue only if the required workflow is adequate and the remaining uncertainty is acceptable for the ordinary use. Fix a demonstrated defect or choose a simpler route when appropriate. Do not commit annually on the strength of a smooth interface alone. Keep the original expectations so a later review can distinguish a changed requirement from an implementation failure.
Use a small acceptance table
For a fictional pilot, list recipient view, reply ownership, preference handling and billed units as separate rows. Give each an expected result, an observed result and an owner for unresolved questions. Do not mark the entire pilot passed because one message appeared on one phone. The final purchase decision should identify which requirements were actually demonstrated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- TXT180 feature documentation — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02
- TXT180 pricing — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02