Re-engagement

Help users resume unfinished work

Invite previously active users back to a saved task that still exists.

Who should get it

Choose people who meet all of these conditions.

Completed at least one report, but none in the last 30 days.
Has an unfinished report they can still open and continue.
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.

last_report_at must be the ISO date of a completed report, not the last sign-in.
report_count and unfinished_report_count must be numbers or numeric text. The unfinished count must describe saved drafts that still exist and remain accessible.
marketing_allowed must be an explicit yes/no field for this kind of email. These example custom fields need equivalent fields from your own product.

Leave these people out

Exclude deleted drafts, ended access, internal accounts and anyone recently contacted about the same task. Confirm the fields or exclusion segments for these cases.

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: Pick up your unfinished [task]
Preview: Your saved draft is ready when you are.

Hi,

You have an unfinished [task] in [Product]. The [saved details] are still there, so you can continue from that draft.

Open [draft location] to pick it up. You can review it before continuing.

Open my drafts

[Sender name]

Before you use it

Confirm the product and task names, which work is actually saved, the https draft-list URL and the sender name.
Choose an inactivity window that fits the product. Thirty days is only an example.

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 "Help users resume unfinished work" 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:
- last_report_at must be the ISO date of a completed report, not the last sign-in.
- report_count and unfinished_report_count must be numbers or numeric text. The unfinished count must describe saved drafts that still exist and remain accessible.
- marketing_allowed must be an explicit yes/no field for this kind of email. These example custom fields need equivalent fields from your own product.
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 product and task names, which work is actually saved, the https draft-list URL and the sender name.
- Choose an inactivity window that fits the product. Thirty days is only an example.
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 deleted drafts, ended access, internal accounts and anyone recently contacted about the same task. Confirm the fields or exclusion segments for these cases.
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 "Help users resume unfinished work" and this rule:
{
  "match": "all",
  "conditions": [
    {
      "field": {
        "kind": "custom",
        "name": "last_report_at"
      },
      "op": "older_than_days",
      "value": 30
    },
    {
      "field": {
        "kind": "custom",
        "name": "report_count"
      },
      "op": "gt",
      "value": 0
    },
    {
      "field": {
        "kind": "custom",
        "name": "unfinished_report_count"
      },
      "op": "gt",
      "value": 0
    },
    {
      "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": "Help users resume unfinished work",
  "templateId": null,
  "subject": "Pick up your unfinished [task]",
  "html": "<p>Hi,</p><p>You have an unfinished [task] in [Product]. The [saved details] are still there, so you can continue from that draft.</p><p>Open [draft location] to pick it up. You can review it before continuing.</p><p><a href=\"https://example.com/drafts\">Open my drafts</a></p><p>[Sender name]</p>",
  "preheader": "Your saved draft is ready when you are.",
  "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.