{"id":"sales-follow-up-sequence-table","audience":"sales","category":"sales-work","technique":"format","track":"sales","level":"intermediate","title":"Plan a 3-touch follow-up sequence that adds value each time","free":false,"task":"Your cold email to Owen March at Castellan Hotels got no reply. Plan 3 follow-ups as a markdown table with columns Day, Channel, Message, one row each for Day 3, Day 7 and Day 14. Each touch must add something new from your notes, and none may say \"just checking in\" or invent a deadline. The Day 7 touch is a LinkedIn message. Under 140 words.","materialLabel":"Your outreach notes (attached to your prompt automatically)","material":"Original email (sent Mon Nov 3) to Owen March, Director of Guest Experience, Castellan Hotels (9 boutique hotels):\n\"Saw Castellan just opened the Marlow in Portland. Guests at new hotels often hit the front desk with the same 5 questions. Our guest messaging app answers them by text, 24/7. Worth a 15-min chat?\"\nNo reply.\n\nThings I could use in follow-ups:\n- New case study: Juniper Inns (7 hotels) cut front-desk calls 31% in 4 months\n- Owen's recent LinkedIn post: complained about \"review scores dropping at check-in\"\n- Our 2-min video: how a guest texts for late checkout\n- We have a free review-score benchmark for boutique hotels (PDF)\n- Owen is speaking at the HospTech meetup in Denver on Dec 4 (I'm going too)\n\nChannels I use: email, LinkedIn. No phone number for him.\nNote from manager: \"Every touch needs a reason to exist.\"","rules":[{"type":"maxWords","max":140}],"mistakes":[{"title":"Getting full emails","why":"The AI writes three long emails with subject lines instead of a plan you can scan.","fix":"Ask for the shape: \"A table with columns Day, Channel, Message, one row per touch.\"","checks":["r0"]},{"title":"Empty bumps","why":"AI follow-ups default to \"just checking in\" and repeat the first email.","fix":"Add: \"Each touch adds a new item from my notes. Never say just checking in.\"","checks":["r1","r2"]},{"title":"Inventing urgency","why":"The AI adds \"spots are limited\" or \"this week only\" to get a reply.","fix":"Add: \"No deadlines or expiring offers.\"","checks":["r2"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and runs long when you only give a total like 140 words.","fix":"Cap each part instead, like \"each message under 25 words,\" so the total lands well under 140.","checks":["maxWords"]}],"promptHints":[{"label":"Asks for a table","patterns":["table","columns"]},{"label":"Names the days","patterns":["day 3","day 7","day 14"]},{"label":"Sets the channel","patterns":["linkedin"]},{"label":"Bans empty bumps","patterns":["just checking in","new (value|reason|item)","adds? something"]},{"label":"Bans fake urgency","patterns":["no (deadline|urgency)","expir","fake"]}],"hint":"Follow-ups only work when each one gives a new reason to reply. Ask for a table with fixed days and tell the AI what each touch may not say.","rubricLabels":["Is a table with columns Day, Channel, Message and exactly 3 rows: Day 3, Day 7 and Day 14","The Day 7 row uses LinkedIn as its channel, and each message uses a different item from the notes (for example the Juniper case study, the benchmark PDF, the video or the Denver meetup)","No message says \"just checking in\", \"bumping this\" or \"following up on my last email\", and none gives a deadline or says an offer expires"]}