Re-engagement

Tell affected users a blocker is fixed

Invite users who encountered a specific problem to retry after you have fixed it.

Who should get it

Choose people who meet all of these conditions.

Experienced the export problem you have fixed.
Has a known retry status and has not retried since the fix.
Your records permit this kind of email.

Data you need

Your agent checks how your database records this information before creating a draft. Missing information does not count as a match.

Database field details

Custom field names below are examples to adapt to your product. Rowsend does not create or track this product activity for you.

encountered_export_timeout must identify users who actually encountered this problem.
retried_export_after_fix must be an explicit yes/no field. Missing retry data must not mean no.
marketing_allowed must record eligibility for this kind of email. Use equivalent custom fields for your own problem and fix.

Leave these people out

Exclude successful retries, ended access, internal accounts, workspaces without the fix and people already notified. Confirm current feature access and the exclusion fields or segments.

Rowsend also excludes people who unsubscribed from the selected topic or everything, bounced, or complained.

How audience rules work

The email to adapt

An example to customize. Brackets and example.com links need your product's details.

Subject: The [specific problem] is fixed
Preview: You can retry [the task that failed].

Hi,

[Specific task] in your [Product] workspace failed because of [known problem]. We have fixed that problem.

Open [task location] and [retry instructions]. If it still fails, reply to this email and we will help investigate.

Try again

[Sender name]

Before you use it

Confirm the exact failure, that its fix is deployed for every recipient, the retry instructions, the https product URL and the sender name.
Use a monitored reply address and confirm someone can investigate replies.

Your agent creates a segment and a draft after checking your data. It stops if required data is missing or the audience is empty. You review the draft in the app before sending.

Paste the prompt into an agent connected to Rowsend. It checks your data and prepares a draft for you to review.

Read or copy the prompt yourself

Agent prompt

Help me adapt the Rowsend recipe "Tell affected users a blocker is fixed" and create one draft campaign.
If Rowsend is not connected to you, fetch https://rowsend.com/get-started.md and follow its pairing instructions first. Never ask me to paste passwords or keys into chat.

1. Call list_projects and identify my intended project. Ask if ambiguous. Call get_setup_status and get_data_source_status. If the database is not connected, help me set it up before continuing.
2. Verify these requirements against the source's view or mapping and sample contacts, using list_contacts and list_database_fields where available:
- encountered_export_timeout must identify users who actually encountered this problem.
- retried_export_after_fix must be an explicit yes/no field. Missing retry data must not mean no.
- marketing_allowed must record eligibility for this kind of email. Use equivalent custom fields for your own problem and fix.
Missing or empty data is not evidence that a person qualifies. If a required field is unavailable, unmapped or its meaning is uncertain, stop and explain what is needed. Do not drop conditions, substitute sign-in dates for product activity, or broaden the audience. A sample alone cannot establish that an unmapped field exists.
3. Ask me to resolve these details before creating anything:
- Confirm the exact failure, that its fix is deployed for every recipient, the retry instructions, the https product URL and the sender name.
- Use a monitored reply address and confirm someone can investigate replies.
Replace all square-bracket placeholders in the subject, preheader and HTML with confirmed facts. Use real https product URLs. Escape inserted text for HTML. Do not invent personal verification tokens, features, customer activity or promises.
4. Confirm this kind of email is appropriate for these contacts. Review these exclusions:
- Exclude successful retries, ended access, internal accounts, workspaces without the fix and people already notified. Confirm current feature access and the exclusion fields or segments.
If exclusions require missing fields, stop. Combine required inclusion conditions in one All rule; multiple included segments are OR, not AND. Add exclusion segments explicitly if needed. Call list_topics and choose the existing topic with me. Never create a topic to bypass an opt-out.
5. Call sync_contacts. If it fails, stop. Call list_segments. Reuse a segment only when its entire rule matches the final rule, not just its name. Otherwise call create_segment with the actual projectId, name "Tell affected users a blocker is fixed" and this rule:
{
  "match": "all",
  "conditions": [
    {
      "field": {
        "kind": "custom",
        "name": "encountered_export_timeout"
      },
      "op": "is_true"
    },
    {
      "field": {
        "kind": "custom",
        "name": "retried_export_after_fix"
      },
      "op": "is_set"
    },
    {
      "field": {
        "kind": "custom",
        "name": "retried_export_after_fix"
      },
      "op": "is_false"
    },
    {
      "field": {
        "kind": "custom",
        "name": "marketing_allowed"
      },
      "op": "is_true"
    }
  ]
}
If source field names differ, confirm an equivalent mapping with me and preserve every condition. For Firebase confirmation status, use the custom email_verified field with is_set and is_false instead of emailConfirmedAt. Do not interpret Firebase's empty emailConfirmedAt as unverified.
6. Replace PROJECT_ID, SEGMENT_ID and TOPIC_ID below with the actual returned IDs, apply the confirmed copy and exclusions, and call preview_audience with the same projectId, audience and topicId. Report the eligible count. If zero, stop and explain; never remove the segment to get recipients. Call create_campaign using this payload:
{
  "projectId": "PROJECT_ID",
  "name": "Tell affected users a blocker is fixed",
  "templateId": null,
  "subject": "The [specific problem] is fixed",
  "html": "<p>Hi,</p><p>[Specific task] in your [Product] workspace failed because of [known problem]. We have fixed that problem.</p><p>Open [task location] and [retry instructions]. If it still fails, reply to this email and we will help investigate.</p><p><a href=\"https://example.com/reports\">Try again</a></p><p>[Sender name]</p>",
  "preheader": "You can retry [the task that failed].",
  "kind": "rich",
  "audience": {
    "includeSegmentIds": [
      "SEGMENT_ID"
    ],
    "excludeSegmentIds": []
  },
  "topicId": "TOPIC_ID"
}
Never omit audience or leave includeSegmentIds empty. Reuse an existing identical draft if this recipe was already completed; do not overwrite a person's draft.
7. Call preview_email with projectId and the saved campaignId, plus a matching contactId when available. Report warnings, the campaign name and ID, the topic, audience count and anything still needing review. Rowsend adds the project's mailing address and unsubscribe footer.
Stop at the draft. Do not send a test, send a campaign or schedule anything. Tell me to review the draft in Rowsend on my computer.