{"id":"cs-adoption-nudge-table-day-7-14-30","audience":"customer-success","category":"support-work","technique":"format","track":"support","level":"intermediate","title":"Plan three adoption nudges as a compact table","free":false,"task":"Plan three adoption nudges for new users as a table with the header row exactly \"When | Channel | Message\" and three rows for Day 7, Day 14 and Day 30. Each Message is under 20 words and uses {{first_name}} and no other merge field. Use the channel that fits the data. Plain text, under 90 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"NEW-USER DATA, Q3 cohort (200 users)\n- Users who create a first project by Day 7 stay at a 3x higher rate than those who don't.\n- Email open rate: 41%. In-app message view rate: 78%. SMS is not enabled.\n- Day 14 drop: 35% of users who started a project have not invited a teammate.\n- Day 30: users who run their first report by Day 30 renew at 92%; others at 71%.\n- Support asked us not to send more than one message per user per week.\n\nTemplates in use today say things like 'Hi {{name}}, we noticed you haven't logged in!' (feels pushy).\n\nStyle: helpful, one clear next step, no guilt.","rules":[{"type":"plainText"},{"type":"maxWords","max":90}],"mistakes":[{"title":"Using the old merge field","why":"The template uses {{name}} and the AI copies it.","fix":"Say: \"Use only {{first_name}}.\"","checks":["r2"]},{"title":"Nudging the wrong action","why":"The AI writes a generic 'come back' message.","fix":"Say: \"Day 7 first project, Day 14 invite teammate, Day 30 first report.\"","checks":["r1"]},{"title":"Wrong table","why":"The AI adds columns or notes.","fix":"Give the exact header row.","checks":["r0"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]},{"label":"Gives the header","patterns":["when \\|","header"]},{"label":"Ties each day to an action","patterns":["first project","invite","first report"]}],"hint":"Nudges work when each one asks for one action. Tie each day to the data and name the merge field.","rubricLabels":["The header row is exactly \"When | Channel | Message\" and there are exactly three rows for Day 7, Day 14 and Day 30","Day 7 nudges creating a first project, Day 14 nudges inviting a teammate, and Day 30 nudges running a first report","Every message uses {{first_name}} and no other merge field, and is under 20 words"]}