Most messages we get fall into a few shapes: someone finishing a first module on variables and loops and unsure what to build next, someone moving from a support role into development work, or a team lead who needs a clearer sequence for onboarding junior developers. A short brief helps us point you to the right module instead of a generic reply.
We read every brief ourselves. Replies usually go out within two working days, and if your question needs a longer answer we will say so rather than send a one-line response.
Questions about a module, a cohort start date, or how the learning tracks are sequenced usually land with our student support desk first. If you would rather write than call, the inbox is checked on weekday mornings and again before the end of the day.
Pick the channel that fits what you need.
We do not run a walk-in desk, so please arrange a visit by phone or email before coming to the office.
Most issues that reach us are small: a module that will not unlock, a video that stutters on a slow connection, a certificate with a misspelled name. Others take longer, like a payment record that does not match your enrollment or a lab environment that refuses to start. Pick the route below that matches your case, and include the module name and the email on your account. That single detail usually saves a full round of back and forth.
Write to info@myactivationcoach.com with the email you registered under. If a module stays locked after you finish the previous one, tell us the module title and the date you completed the prerequisite. We check progress records manually when the tracker disagrees with what you see.
Send the lesson number and a short description of what failed. Screenshots of the error help, but paste the console text if you have it. Content corrections go into the next revision of the module, so you may see the fix land a few days after we reply.
Include the order reference from your confirmation email. We do not handle card data directly, so anything involving a bank statement is routed to our billing desk and answered from there. Keep the original receipt until the matter is closed.
Tell us your operating system, the editor you use, and the exact command that failed. Problems with virtual machines and package installs are the slowest to diagnose, so the more of your setup you describe up front, the fewer messages it takes.
87518 Fisher Island Suite 986
Stoltenbergfort, SD 54704-5393