{"id":"cs-ttfv-glossary-three-answers-current-definition","audience":"revops","category":"support-work","technique":"grounding","track":"support","level":"beginner","title":"Answer three metric questions with the current definitions","free":false,"task":"Answer the three questions in pairs of lines \"Q1:\" and \"A1:\" through \"Q3:\" and \"A3:\". Each answer is under 22 words and uses only the current glossary (rev. Oct 1). Plain text, no intro or sign-off.","materialLabel":"Your material (attached to your prompt automatically)","material":"CS METRICS GLOSSARY (rev. Oct 1)\n- Time to first value (TTFV): the number of calendar days from contract start to the first customer-confirmed outcome. The outcome is logged in the CRM field \"First outcome date\" by the CSM, after the customer confirms it in writing.\n- Time to live: calendar days from contract start to go-live.\n- Weekends and holidays count; both metrics use calendar days.\n- OLD DEFINITION (before Oct 1, no longer used): TTFV was days to the customer's first login.\n\nQUESTIONS from a new RevOps analyst\n1. What does TTFV measure?\n2. How is it different from time to live?\n3. Do weekends count?\n\nExample in the glossary: contract start Mar 1, first outcome Apr 12, go-live Mar 29. TTFV = 42 days; time to live = 28 days.","rules":[{"type":"plainText"},{"type":"maxWords","max":100}],"mistakes":[{"title":"Using the old definition","why":"The AI says TTFV is days to first login.","fix":"Say: \"Use the current glossary only.\"","checks":["r1"]},{"title":"Skipping confirmation","why":"The AI drops the customer-confirmed part.","fix":"Say: \"Mention the customer-confirmed outcome.\"","checks":["r1"]},{"title":"Dropping the labels","why":"The AI answers in a paragraph.","fix":"Say: \"Use Q1:/A1: to Q3:/A3: lines.\"","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":"The AI runs long and cannot count its own words.","fix":"Cap each part (\"each line under 12 words\") and add \"under N words in total\".","checks":["maxWords"]},{"title":"Leaving a requirement unstated","why":"The AI follows its own defaults unless the prompt spells this out.","fix":"State it plainly in your prompt: A3 says yes, weekends count because both metrics use calendar days, and each answer is under 22 words.","checks":["r2"]}],"promptHints":[{"label":"Sets labels","patterns":["q1","a1"]},{"label":"Current glossary only","patterns":["current","only the glossary","rev"]},{"label":"Caps the answers","patterns":["under 22","22 words","each answer"]},{"label":"No intro","patterns":["no intro","no sign-off"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a word cap","patterns":["\\d+\\s*words","under \\d+","word"]}],"hint":"When definitions change, tell the AI to use only the current one and fix the output labels.","mission":"Answer three metric questions using the current glossary definitions.","musts":["Rev. Oct 1 glossary only","Answers under 22 words","No intro or sign-off"],"rubricLabels":["The output has three Q and A pairs labeled Q1: to Q3: and A1: to A3: with no intro or sign-off","A1 says calendar days from contract start to the first customer-confirmed outcome (not first login), and A2 says time to live ends at go-live","A3 says yes, weekends count because both metrics use calendar days, and each answer is under 22 words"]}