With offices around the globe, Coupa’s Customer Support organization is dedicated to your success. Our highly trained support experts are ready to answer your questions, provide advanced troubleshooting, and share best practices to help you maximize the value delivered by your Coupa platform.
We’re here to help
Global Customer Support
With support centers around the globe, our team of certified support experts is available to help resolve issues and share best practices.
Full featured coverage
With Premium Support, you have 24/7 access to technical assistance and support resources for the help you need when you need it.
Answers and assistance anytime
Search support articles for immediate answers or submit and track support requests anytime here in the Coupa Compass Portal
Support for Suppliers
Visit the Supplier Help Center for details about engaging with your customers on Coupa. For additional supplier support, chat live with us via the Coupa Supplier Portal.
More Information & Guidance
Check out the Coupa Support Portal Guide for more information and guidance. In the guide, you'll find more information on support roles, and how your Designated Support Contacts can submit and track cases in the Coupa Support Portal.
Seeing this message? Can't click the links above? Sign in to get all our content.
- Business Impact
- Help support understanding the current business impact of the reported case by answering the (applicable) following questions: how much visible is the issue? how many time is occurring on a daily/weekly basis? is the workaround sustainable? how much noise does it generate inside the company? how much disruption does it cause on your activities? if the issue is encountered during test phase, is there a fixed time for deploying the functionality in production? Report the issue ASAP...
- Engaging with Support - Best Practices
- Report the issue promptly. Ensure a person that does not know your environment is able to understand the issue as you have reported it.Provide us with the file which you loaded and that generated the unexpected behaviour. What are you trying to achieve? Dit it ever work according to your expectations? Which documentation did you follow? What are the steps you already tried to solve it? What's the impact for your business? Track communications within the ticket