Behind every successful RISA project for our customers is a technical support team ready to help users troubleshoot unexpected results, explore new workflows, and keep projects moving. But what does that work actually look like from the other side of the inbox, phone call, and model file? Follow along for a day in the life of a RISA Technical Support Engineer.
With coffee in hand, I get started for the day. The RISA support team is available from 6 AM to 5 PM Pacific, so by the time I log on, my colleagues have already been helping customers for a couple of hours.
I check emails and internal messages for updates from the morning team, then make myself available for incoming calls and hop into our shared inbox at support@risa.com. This email is monitored by our team so we can work together and respond to customers quickly.
First, I check on any conversations already assigned to me. Did a customer have a follow-up question? Did the instructions I sent yesterday solve the issue? I always want to close the loop with existing conversations prior to jumping into any new requests.
Once a week, our technical support team comes together to compare notes, discuss schedules, review product updates, and coordinate with other RISA teams including product, customer success, and marketing.
We also share a recent technical question or workflow. These “technical shares” often focus on less frequently used features, interesting modeling situations, or lessons learned from customer questions. It is a chance to talk through best practices, learn more about the behind the scenes functionality in the software, and make sure every customer receives a clear, consistent answer. These discussions are always lively with a side of friendly debate over the best way to explain something.
Now it’s time to dive into customer emails. The questions cover all of RISA's 10+ products and just about every stage of a project: getting started, exploring new features, troubleshooting integrations or error messages, reviewing an unexpected result, or checking a modeling assumption before finalizing the design. Some answers are quick like showing the user a new tool, while others require deeper investigation into their model.
Today, a customer is receiving a P-Delta error in their model. These error messages are common, but can bring a design to a halt if you don’t know how to fix it. I start by recreating the error message. Then, I review the framing and model setup for any common modeling issues and consult relevant RISA resources such as our Tips & Tricks Blog. I work through the model until I identify the potential cause. I always strive to get the model to run without receiving the error message.
Once I have the answer, I send the customer a response with step-by-step instructions and screenshots. The goal is not simply to answer the direct question, but also help the engineer understand what the model is doing and feel confident about the moving forward.
For quick questions, the technical support team is also reachable at 800.332.RISA. Email is great for detailed questions and to share model files, but sometimes a quick phone call is all that is needed.
Today’s call is about view settings in RISAFoundation. The customer wants to better understand the options available and how to use them in their workflow. We walk through the tools in real time, answer a few questions, and get them pointed in the right direction.
Back to the inbox. Some questions come up regularly as customers become familiar with RISA tools, workflows, and integrations. The good news for everyone is that the more often we see a question, the more resources we have for the topic and the faster we can connect users with a useful answer or resource.
Today, that means helping several customers with the RISA-Revit Link, troubleshooting the integration between RISA-3D and RISAConnection, getting loads to transfer from RISA-3D to ADAPT-Builder, and sharing RISA-3D training resources.
RISA offers online help across its software products as well as learning resources for users who want to build skills beyond the immediate question at hand. A support response may solve today’s problem. The right training resource can make tomorrow’s workflow faster, too.
Our team coordinates lunch breaks so someone is always available to take customer calls and offer prompt responses. Since most of our engineering support team works remotely, I use the break to get outside for a walk and reset before the afternoon deep dives begin.
RISA has several teams ready to help customers, including sales, customer care, and engineering support. Each team handles different needs, from adding licenses and managing renewals to installation help and engineering support.
Part of my afternoon includes reviewing the engineering support inbox to make sure each request reaches the team best equipped to help. Today, a RISA-3D user is interested in adding RISAFloor licenses, so I connect them with our sales team.
The afternoon brings a more detailed question to the inbox. A customer is comparing seismic loading generated in RISAFloor and RISA-3D with their expected load. The loading does not match what they anticipated, and they want to understand why.
This is where support becomes a real engineering investigation.
I begin with the models themselves, reviewing the applied loading, member information, and selected code settings. I consult the Help File to confirm the design methodology, look through past support discussions for similar questions, and compare the program’s results with the customer’s expectations. When needed, I also bring in RISA’s product team to provide more insight on how the software is performing the analysis.
After tracing the source of the discrepancy, I send the customer a detailed explanation of the program assumptions and results. A question like this may take longer than a quick interface question, but it is also where an experienced technical support team can make a major difference. We are here to help users understand not only what they are seeing, but why they are seeing it.
As the day winds down, I respond to final customer emails, leave notes for any ongoing conversations, and check in with the team before logging off.
No two days in technical support are exactly alike, but the goal remains the same. We strive to help RISA users get answers, understand their models, and keep their projects moving. I end my day knowing I've helped engineers solved problems and get to be a small part of countless projects along the way.