Map the lifecycle and permitted contact

We review the journey from first interest through the stages relevant to your offer. The plan identifies known events, customer states and the messages that could help at each point. A workflow should not assume an event is available simply because it would be convenient. We review contact sources, permission records and unsubscribe handling before defining sending rules. The client supplies or approves the factual basis for contact and customer information. Existing messages are compared for gaps, duplication and contradictory promises. This creates a flow map grounded in the operation rather than an automatic sequence sent to everyone regardless of context.

Write messages and resolve destination friction

Each message has a specific purpose, trigger and next step. Copy explains the relevant information without invented urgency or unsupported claims. The email design and landing destination are reviewed together so the transition feels coherent and required details are easy to find. We examine forms, navigation and other barriers in the agreed journey, using available evidence to prioritise changes. Variations test a defined question about message or interaction rather than changing several elements with no way to interpret the result. Templates, provider configuration and site implementation are separate deliverables that can be connected within the engagement.

Measure observable actions and keep control

Implementation planning covers trigger data, sending configuration, exclusions and recovery from failures. We distinguish delivery, recorded interaction and verified business outcomes, noting where provider or browser signals are incomplete. The site’s own contact flow prepares an email draft; opening that draft does not establish that the visitor sent it. Any lifecycle sending system therefore requires its own explicit scope and data source. Account ownership, access and launch responsibilities are agreed before activity begins. Handover includes flows, copy, templates and measurement definitions, with ongoing sending and optimisation arrangements stated rather than implied by the delivery of an initial email design.

We specify suppression rules alongside triggers. A person who has completed the relevant action, opted out or moved to a different lifecycle stage should not automatically receive the same prompt again. Testing those exclusions is part of checking the flow, since an apparently successful send can still be the wrong message for its recipient.