Support Team Call

ERP Support Best Practices: What Great Support Looks Like After Go-Live

Most ERP content focuses on implementation. That makes sense; go-live is a milestone. But, ERP success is decided after go-live. 

Post go-live is where uptime is protected, cash flow stays moving, the month-end close stays predictable, and teams avoid slipping back into spreadsheets and workarounds. And it’s where your ERP partner either earns long-term trust, or slowly loses it. 

We regularly ask clients about their support experience in a post support-case survey. Below are 22 quotes pulled from those surveys. 

Key Takeaways: What Great ERP Support Looks Like 

  • Response times that match business impact, not just ticket priority 
  • Clear case ownership and proactive updates 
  • Root-cause troubleshooting, not guesswork 
  • Documentation and clarity on what changed 
  • Clean escalation paths when a ticket becomes a project 
  • Enablement so your team learns, not just waits 
  • Consistency you can count on month after month 

Table of Contents

ERP Support Response Time: Speed and urgency when work cannot wait 

In ERP, time matters because operations do not pause. When something breaks, the goal is simple: get the team moving again. 

Crestwood client quotes: 

  • “Support was great, quick to resolve our issue, and very kind.” 
  • “This was handled within minutes of submission so no improvement needed.” 
  • “Great response time and accurate work.” 
  • “Very quick to react and respond. A+ support.” 
  • “This was resolved very promptly.” 

What this tells us: response time is not a “nice to have.” It’s part of operational reliability. 

ERP Troubleshooting Expertise: Root cause, not workarounds 

Clients can tell the difference between someone who is guessing and someone who understands the system. Great support feels calm, direct, and confident. 

Crestwood client quotes: 

  • “Support is very sharp and efficient.” 
  • “Support was very knowledgeable and found a solution to my problem in 10 min.” 
  • “The support and customer service we received were top notch. Very knowledgeable and extremely helpful.” 
  • “This case was well researched and confirmed the cause of the issue.” 
  • “I’m satisfied with the services and the strong knowledge. He seems truly passionate about his work.” 

What this tells us: the best support is not just answering questions. It’s solving the right problem the right way. 

Support Communication: Updates, documentation, and follow-through 

Great support is not just “fixing.” It’s explaining what happened, what changed, and what to do next. Clients want clarity, especially when the system touches billing, payroll, inventory, security, and financial reporting. 

Crestwood client quotes: 

  • “The experience was perfect. Good communication and we received the results that we were expecting.” 
  • “No complaints with this case. Easy to submit the case, good communication back on status, and solution was quickly developed. Very much appreciated.” 
  • “I’m not sure. The communication has always been excellent. Keep it up!” 
  • “Continue to provide great support and follow-up.” 
  • “He gave us all the relevant information we needed to fix the issue we were having and understand how it worked.” 

What this tells us: communication is part of the fix. Without it, a resolution does not feel complete. 

ERP Partner Mindset: Ownership and professionalism clients can feel 

ERP support is stressful when people feel dismissed or rushed. It’s powerful when clients feel heard, respected, and supported by someone who acts like they’re on your team. 

Crestwood client quotes: 

  • “Support was incredibly helpful and listened to our needs thoroughly and guided us to a solution that we all felt confident about.” 
  • “Support was very patient and helpful to make sure this was resolved.” 
  • “Keep doing what you are doing! I appreciate your responsiveness and professionalism… Having a collaborative, reliable partner with our ERP system is critical to our success…” 
  • “Not much. Just keep employing awesome, competent people.” 
  • “Crestwood is always quick to help us with any issues that occur.” 

What this tells us: clients don’t just want a ticket closed. They want ownership. 

Support Enablement: Helping your team learn, not just handing back a fix 

The best support reduces future tickets. Not because clients stop having needs, but because they gain confidence and capability. 

Crestwood client quotes: 

  • “They listened and came up with ideas and reports I could use going forward… They also helped me to understand some of the functions we have available…” 
  • “Very knowledgeable and gave clear directions on how to proceed and resolve the issue.” 
  • “I figured out most of the issues but your team was a good sounding board.” 
  • “You were very helpful!” 
  • “My experience was great. Hence, no suggestions.” 

What this tells us: great support helps teams become stronger operators inside the system

Consistency: What reliable ERP support looks like over time 

Anyone can have a good day. What clients actually buy into is consistency across months, cases, and different types of issues. 

Client quotes: 

  • “Support is always responsive and resolves our issues quickly.” 
  • “Support resolves our issues in a timely manner. Awesome.” 
  • “Excellent job by Support!” 
  • “Excellent service. Prompt and efficient.” 
  • “The Crestwood team was on it and the support was great.” 

What this tells us: trust is built in repeats. Consistency is the brand. 

What to ask any ERP partner about support (before you sign) 

If you’re evaluating an ERP partner for Acumatica, Business Central, or any ERP platform, ask these questions. The answers will tell you how post go-live will feel. 

  1. What are your support SLAs by impact level (not just “urgent” vs “normal”)? 
  2. How will I know who owns my case, and when I’ll hear back next? 
  3. Do you provide progress updates while work is underway? How often? 
  4. How do you document resolutions so we can reuse the fix later? 
  5. What happens when a support ticket becomes a project? Who owns the handoff and communication? 
  6. How do you handle security-related issues and escalations? 
  7. Do you help us prevent repeat tickets through training or enablement? 
  8. How do you staff industry/module expertise so the right person lands on the right issue? 

Click Here to Explore Crestwood’s ERP Partner Selection Checklist 

What we do on purpose to make ERP support feel like this 

These comments are not accidental. Great support has to be built and maintained. 

A few things we focus on consistently: 

  • Clear ownership so clients know who is working the case and what happens next 
  • Practical triage so urgency is handled like urgency 
  • Documentation that explains what changed and why 
  • Escalation paths when a ticket becomes a project (with clarity, not silence) 
  • Enablement mindset so clients can repeat the fix confidently when appropriate 
  • Feedback loops so we improve response, clarity, and overall experience 

Support & Customer Success Overveiw Page 

ERP Support FAQ 

What is ERP support after go-live? 

ERP support is the ongoing help and guidance you receive after implementation to resolve issues, troubleshoot errors, adjust configurations, support users, and keep operations running reliably. 

What should ERP support SLAs look like? 

SLAs should reflect business impact. A “payments can’t run” issue should not have the same response expectation as a reporting question. A good partner will define response targets and escalation paths clearly. 

What’s the difference between ERP support and ERP managed services? 

Support typically focuses on reactive issues and questions (tickets, troubleshooting, fixes). Managed services often includes proactive monitoring, optimization, enhancements, ongoing admin support, and continuous improvement. 

When does an ERP support ticket become a project? 

When the work requires deeper development, integration changes, complex reporting, workflow design, or multi-step testing and deployment. The key is a clear handoff and transparent updates so the client isn’t left guessing. 

How do I evaluate an ERP support partner beyond reviews? 

Ask about SLAs, documentation standards, escalation paths, case ownership, how updates are delivered, and how they enable your team. Then look for proof that clients consistently value those behaviors. 

My final thoughts on Support 

Go-live is a milestone, but ERP value is protected after go-live. 

If you’re evaluating partners, don’t just ask “can you implement.” Ask “what does support look like when it’s urgent, when it’s complex, and when our team needs to learn.” 

If you want to talk through what a healthy post go-live support model should look like for your business, reach out. We’re happy to do a quick fit check and help you benchmark expectations. 

**How we compiled this: Quotes are anonymized and compiled from Crestwood client support survey responses. 

Not sure if your current partner is delivering the support your team needs?

Let’s review your response times, escalation process, and long-term support model.

Get Your Free ERP Assessment | Explore Our Services | Learn More About Crestwood

Connect With Us: X | LinkedIn | Contact Us 
More Resources: Acumatica ERP | Business Central | Blog Home 

© 2025 Crestwood Associates. All rights reserved. 

Author

Share the Post:

Related Posts