LearnGrokUse these prompts to turn scattered campaign inputs into a sequence your lifecycle team can review before it reaches the CRM builder. They suit CRM managers and lifecycle marketers who need the logic, copy and ownership visible in one place.
Start with the source material you already have. That usually means the product brief, approved claims, audience definition, entry event, existing journey rules and the landing page destination. Do not start by asking for subject lines. The sequence will drift if the trigger, exclusions or conversion event are not settled first.
Key point
Build the rules before the copy
An email can read well and still be wrong if it reaches the wrong person, arrives after conversion or has no valid exit rule.
1. Make one campaign source sheet
Run Campaign inputs into a source sheet when your inputs sit in meeting notes, product documents and CRM tickets. Paste the material without trying to tidy it first. The prompt separates approved facts from assumptions and identifies the data fields needed for the journey.
Treat BLOCKER, NOT PROVIDED and ASSUMPTION differently:
- Resolve a
BLOCKERbefore final approval. It means two sources conflict. - Assign an owner to
NOT PROVIDEDif the missing item affects sending, targeting, claims or measurement. - Keep an
ASSUMPTIONonly where the team accepts the proposed safe default.
Watch out
Do not turn missing data into a personalisation plan
If the first name, product interest or last activity date is not reliably available, it is not an approved email field.
Keep this source sheet with the campaign record. It is the reference document for reviewers when somebody later asks why a contact entered the journey or stopped receiving it.
2. Agree the journey before drafting
Paste the agreed source sheet into Journey stages and decision rules. This produces the operational map: who enters, how long they wait, what each email does, and which event ends the sequence.
Check the Next step column particularly closely. A common failure is a journey that knows what to send next but not when to stop. Your map should exit a person after the primary conversion and suppress them for any exclusion already agreed.
Use the PROPOSED label as a review queue. It is useful for a practical default, such as a delay where the brief gives no timing, but it is not an approval. Assign the open question to the person who owns the decision, not to a generic “marketing” owner.
| If you see this | Do this before copy review |
|---|---|
Data needed contains a missing field |
Remove that branch or obtain the field and confirm its source. |
| No conversion exit condition | Define the event, timestamp and destination journey. |
| A sales or support hand-off is vague | Name the trigger, receiving team and contact outcome. |
| Multiple emails have the same purpose | Merge them or give each one a distinct job. |
Check
The logic is ready when every row answers three questions
Who receives this email, what stops it, and what event sends them somewhere else?
3. Produce copy that can be built
Use Sequence copy for build only after the journey map is accepted. It preserves the operational fields next to the copy, so a builder does not have to infer the send condition from a paragraph of campaign notes.
Read the CTA destination and Fallback copy fields as carefully as the email body. A persuasive CTA pointing to an unapproved page is not ready. Likewise, a first-name greeting without a blank-value fallback can produce a broken send.
The prompt uses [REVIEW: ...] for gaps rather than filling them with plausible wording. Keep those markers in the review file. Replace each one with an approved answer or remove the dependency from the email.
4. Add variants without changing the journey
Use Subject line and CTA variants when you have a stable control email and a defined reason to compare alternatives. It changes one element at a time. That lets the reviewer see whether the proposed test is about the subject line, preheader or CTA, rather than several changes bundled together.
Do not use this step to introduce a new offer, audience segment or landing page. Those are journey changes. Return to the source sheet and stage map if the campaign strategy has changed.
Note
Keep measurement tied to the campaign objective
An engaging subject line is not automatically the better one if it produces activity without the agreed conversion.
5. Run the approval audit
Finish with Lifecycle review and hand-off checklist. It gives you a final build sequence, plus a list of defects that must be resolved before launch. Send the Final build sequence to the CRM builder and retain the review table for the campaign owner.
To tell whether the output is wrong, compare each final row with the source sheet, not just with the previous prompt. Look for an entry event that does not exist in your data, an email that continues after conversion, a claim absent from the approved materials, or a CTA with no destination. Also check that the tracking event measures the stated primary conversion rather than only opens or clicks.
If the prompts return generic stages, duplicate emails or too many PROPOSED rules, stop and improve the inputs. Add the actual trigger name, suppression events, destination URL or page name, approved claims and named owners. For implementation features or product behaviour that may vary, check the xAI documentation overview before relying on a capability. Then rerun the source sheet and journey map before drafting the final sequence again.
