Course 07 · Lesson 9 of 12
When the demo breaks
Live failures happened in four of the nine recorded demos. Say what failed, move on, follow up. Never troubleshoot live or give a date for a fix.
| What happens | Say | Do |
|---|---|---|
| Holly slow or stuck | "It's working. A bigger request can take a minute." | After about 90 seconds, back to the pre-run calendar |
| Draft off-voice or generic | "That one isn't right, and I'd rather say so." | One instruction; still poor: concede, go to step 2 |
| Holly misreads | "Let me be more specific." | Retype once; then finish by hand |
| Test first instruction fails | Nothing about it | Manual route |
| Screen says "Pulse" | "Pulse was Holly's working name; you'll see it disappear as screens update." | Move on |
| Screen says "leads" | "That label is changing. It shows engagement on your posts, not a list of people to approach." | Move on; report the screen |
| A link breaks | "I'd rather you saw it here than found it later." | Remove it; log it |
| Thin feed | "Tell me two sites you read every week." | Follow one live |
| Outright error | "That's broken. I won't fix it live; I'll come back to you in writing." | Note time and screen; report it |
If the buyer reacts to a fault: "You'll see rough edges. That's the trade: you're getting a better rate because you're using it early and helping shape it, and you get a direct line to the team when something's wrong."
Progress is saved in this browser only.