Follow up
Definition and example
Follow up is the focus of this lesson. Most admissions are lost to silence, not to a competitor. A follow-up plan of day 1, 3 and 7 is enough — and it should be written by the bot, not remembered by a human. The task asks you to apply that idea in a small example: Why schedule the follow-up in code. Before you run the code, predict what should happen. Then Inspect the printed output and the values your program uses and compare it with your prediction. If the result differs, change one relevant line and run it again. Testing one change at a time makes the cause of a result easier to understand.
Run your code to see the output and the checks.
Submit your code to see results
Write your code in the middle column and press Run code.
Why this works
Checks on this task:
- The program output must match “Day 1: reminder to Bilal about admission Day 3: reminder to Bilal about admission Day 7: reminder to Bilal about admission”.
The task and step-by-step instructions are written as comments at the top of the editor. Change one relevant line, run it, and compare the result with these checks.
Sign in to use up to 8 optional task skips in this course.
Incorrect attempts before answer: 0 / 3
Track progress
0 passed of 56 tasks
Pass every check or use one of your available skips to open the next task.
Sign in to keep your code and certificates.
Need a hand?
Worked answer
You have made three incorrect attempts. Review this example, close the window, and continue practising.