{"id":11564,"date":"2017-07-11T19:27:02","date_gmt":"2017-07-11T19:27:02","guid":{"rendered":"https:\/\/www.process.st\/templates\/strax-rapid-check\/"},"modified":"2024-02-28T20:45:55","modified_gmt":"2024-02-28T20:45:55","slug":"strax-rapid-check","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/strax-rapid-check\/","title":{"rendered":"Strax Rapid Check"},"content":{"rendered":"
\n

Introduction <\/h2>\n
\n
\n <\/a>
\n <\/figure>\n<\/p><\/div>\n
\n

The Demo support staff have a lot to deal with; we all know that. You have to remember the ins and outs of every Strax subsystem under the sun, on top of expectations that you will be able to fix any issue which comes your way.<\/p>\n

"Being a support tech often means being invisible until something goes wrong. Ironically, if you're doing an awesome job... you're less likely to be noticed"<\/em> - Becky Roberts<\/a><\/p>\n

You're some of the most unsung, seldom helped heroes of the tech world<\/a>, so isn't it about time someone made your job a little easier, rather than harder?<\/p>\n

Thankfully, instead of furiously Googling for the solution or wracking your brain for that elusive solution, this time you can scroll through this checklist and find the answers, whether you're a newbie or a seasoned pro. (That's because we've already done the furious Googling)<\/p>\n

Without further ado, let's get you started battling buggy systems and quelling user complaints.<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Basic Demo Data: <\/h2>\n<\/section>\n
\n

Record the case's data <\/h2>\n
\n

The first step in the Strax demo support process is to record all important information<\/strong> about the support case in question. This can be done by filling out (or editing) the form fields<\/strong> below.<\/p>\n<\/p><\/div>\n

\n
\n