Grok Bot and Brevo onboarding: welcome subscribers, then help trials start

An illustrative Monday cohort has 40 new trials and 31 confirmed newsletter subscribers. Those are different groups, even when one person appears in both. Sending the same welcome email to all 40 would turn a product signup into an assumed marketing subscription.

Welcome the 31 only after confirmation. Help inactive trial users take one first action only when marketing consent covers that email. Keep service notices in the product’s approved service channel.

This adapts xAI Product Marketer: draft from known facts, flag unknowns, and leave publication to a person. Our Grok Bot and Brevo starter guide covers the untested connection.

Map the two entry points

For welcome, the source event is confirmed subscription, not form submission. Validate the required first name and business email at signup. Keep incomplete, nonbusiness and unconfirmed signups out of subscriber contacts; never invent a missing name. Verify the confirmation timestamp and source before placing an eligible address on a dedicated Brevo list. Brevo documents “Contact added to list” as an automation trigger. It also notes that moving a contact between lists does not fire that trigger. Test the exact entry route with a permitted test contact before activation. The double opt-in guide explains the confirmation boundary.

For trial activation, choose one observable product action, such as “created the first workspace.” An editorial mapping sheet might contain person_id, email, trial_started_at, first_workspace_at, trial_ended_at, marketing_consent_at, unsubscribe_at and locale. These are example source fields, not Brevo’s native schema. Map only stored fields; neither a business email nor a trial account proves consent. Before treating absent first use as inactivity, confirm the source feed is fresh and complete. Hold the reminder when it is stale, unavailable or incomplete. If Brevo lacks the event, use a bounded export for planning; do not claim an automatic trigger exists.

Path	Entry	Deterministic stop before each step
Welcome	Confirmed subscriber enters the chosen list	Unsubscribe, suppression, hard bounce, duplicate welcome, or missing confirmation evidence
Trial activation	Eligible trial started and first action still absent	First action completed, stale or incomplete action feed, trial ended, unsubscribe, suppression, hard bounce, or duplicate reminder

Keep a stable person key and a sent-step ledger. A replayed signup must not send a second welcome. Recheck stops immediately before dispatch.

Give Grok Bot a bounded writing job

Provide the approved offer, URL, first-use action, eligible audiences and tone examples. Do not export all contacts to draft copy. xAI’s Grok Bot 101 describes bots that can use tools and routines; a prompt is guidance, not a hard permission boundary.

Copy this prompt and replace the example facts:

Draft two separate emails for my review. Email A welcomes people whose email marketing subscription was confirmed. Email B helps eligible trial users complete the first action I specify. Use only the product facts, URL and audience rules I provide. Give each email one subject, preview line, short body and one call to action. Mark any missing claim, date or feature as unknown. Do not invent missing names; use a neutral greeting for eligible legacy records. Return copy and a stop-rule checklist in chat. Do not read other contacts, create a Brevo workflow, add anyone to a list, schedule or send anything.

The welcome email might link to a setup checklist; the trial email might show the first workspace action. Neither should promise an activation rate. Review each destination, neutral greeting and audience count. For more on deciding the audience and goal, use the campaign planning guide.

Hand the reviewed steps to Brevo

After copy review, a person opens Automations > Workflows > Create an automation in Brevo. For welcome, select the verified confirmed-list trigger. For trial activation, select a tested event or segment only if it is available in that account. Add delays, conditions and the documented Send an email action. Test with a permitted contact, check exits and audience, then approve activation. Active workflows send automatically. Draft approval is not activation approval.

The Brevo MCP guide covers its hosted tools. That catalog does not prove Grok Bot can create automation steps. Inspect actual operations before any tool-assisted write. The default handoff is a reviewed rule sheet and human activation in Brevo.

Measure one outcome per path

For the welcome path, count first-checklist visits within seven days of a delivered welcome email. The denominator is confirmed subscribers whose welcome email was delivered in the cohort. For trial activation, count first-workspace completions within seven days of an eligible, delivered reminder; the denominator is eligible trial users whose reminder was delivered. These are example measurement windows, not performance claims.

Report the cohort start and end dates, exclusions, delivery count and event-source delay. A click is not a first-use action. If the product event is missing, mark activation unknown rather than substituting clicks. The email metrics guide explains why numerator, denominator and observation window must travel together. The next step is a verified first action, not a prettier open rate.