Managed Services scope
Zuora Managed Services provides an operationalized service to manage your Zuora installation. We oversee day-to-day activity, monitor Zuora processes, and address issues that surface. Zuora Managed Services works with other back-end Zuora teams as needed in response to production issues.
Contact Us
You can contact Zuora Managed Services team by emailing us at turnkey@zuora.com.
How Zuora Managed Services Accesses Your Tenant
After you are onboarded with the Managed Services team, the Engineers and Enterprise Services Managers (ESMs) will access your tenant for the purpose of troubleshooting.
Zuora Managed Services currently uses zsupport[yourTenantId]@zuora.com as the user to access your tenant. This user is created the first time Zuora Global Support logs into your tenant. You can also opt to create individual users for the ESMs and Engineers if that is preferred.
Note that all Zuora Managed Services logins and other activities in your tenant are tracked and logged by Audit Trail.
Setup and Customizations
| Description | Supported | Self-Service |
|---|---|---|
|
Recommendations, best practices, troubleshooting and instructions on how to:
|
|
|
|
Enabling controlled release features and other actions which are not available to customers to perform in self-service mode |
|
|
|
Creating, modifying, and deleting any objects/entities in customer's tenant at customer’s direction |
|
|
|
Resetting customer user IDs and passwords |
|
|
|
Creating, activating, changing work email, or deactivating users in customer's tenant |
|
|
Reports and Templates
| Description | Supported | Self-Service |
|---|---|---|
|
Recommendations, best practices, troubleshooting and instructions on out-of-the-box reports, billing documents and their functionality |
|
|
|
Creation of custom reports |
|
|
|
Creating or modifying any custom report which was built by Zuora Global Services or an outside vendor |
|
|
|
Creating or modifying billing documents based on customer mockups/requirements |
|
|
|
Delivering weekly report on Zuora activity and Managed Services delivery |
|
|
|
Delivering Zuora out of the box reports |
|
|
|
Modifying templates based on customer mockups/requirements |
|
|
Mass Change Updates
| Description | Supported | Self-Service |
|---|---|---|
|
Instructions and troubleshooting on available UI operations that allow mass change updates, such as:
|
|
|
|
Creation of Mass Order Entry or Usage files |
|
|
|
Conducting mass changes across Accounts, Contacts, Subscription data (including pricing, payment methods, and usage records) |
|
|
|
Providing complete solution design logic on how to execute batch operations via API |
|
|
|
Data fixes due to incorrect/inaccurate data entered by Customer |
|
|
|
Add/update rules in tenant environment for Billing, SalesForce, Accounting, Tax codes, etc. |
|
|
|
Provide recommendations on rules |
|
|
|
Add/update MOD number for Payment Gateway |
|
|
|
Data loads using Zuora tools |
|
|
|
Complex data loads |
|
|
Development, Coding, Debugging, Connectors, Gateways
| Description | Supported | Self-Service |
|---|---|---|
|
Providing a reference to available sample code on https://github.com/zuora/ |
|
|
|
Troubleshooting of Zuora API (SOAP and REST) calls when complete XML Request/Response is provided, along with additional requested information as needed (e.g. WSDL version, timestamps, etc) |
|
|
|
Performance analysis of Zuora API calls when provided with a timeframe |
|
|
|
Consulting on how to modify sample code to meet specific use cases |
|
|
|
Consulting on how to upgrade sample code to higher WSDL version |
|
|
|
Installation/troubleshooting of integrated developer environments (IDE) |
|
|
|
Troubleshooting programming code errors in any language (Java, PHP, Ruby, C#, etc.) |
|
|
|
Troubleshooting client side (HTML, JavaScript) errors |
|
|
|
Solution design of Zuora API calls to meet specific use cases |
|
|
|
Code support for any custom tools development by Zuora Global Services, Zuora partner or outside vendor |
|
|
|
Performance optimization design for Zuora API calls |
|
|
Zuora for Salesforce
In order to effectively troubleshoot issues, Support may request access to the affected Salesforce org. If customer does not wish to provide access, the issue will fall under Self-Service.
| Description | Supported | Self-Service |
|---|---|---|
|
Support customer development efforts with Z-Force Builder. Customer must provide an explanation of the code classes, triggers, entry points, behavior expected and behavior outcome |
|
|
|
Creating, developing and debugging custom APEX code |
|
|
Payment Gateway Integration
| Description | Supported | Self-Service |
|---|---|---|
|
Providing Zuora transaction logs for authorizations, payments, refunds and void operations when logs are not available to customers in a self-service mode |
|
|
|
Identifying the source of an error: whether or not an error is originating from Zuora, gateway, processor or merchant bank or other third-party applications |
|
|
|
Debugging and providing resolution for payment failure errors originating from a gateway, processor or merchant bank |
|
|
|
Providing logs for payment failure errors originating from a gateway, processor or merchant bank, and assisting in troubleshooting with 3rd party initiated by customer |
|
|
Connectors/Third-Party Integration
| Description | Supported | Self-Service |
|---|---|---|
|
Identifying the source of an error: whether or not an error is originating from Zuora |
|
|
|
Explanation of Zuora data model, object and entity |
|
|
|
Review of Zuora application logs to determine inputs/output from and to Zuora |
|
|
|
Providing logs for failure errors originating from a 3rd party, and assisting in troubleshooting with 3rd party initiated by customer |
|
|
Networking, Availability
In order to effectively troubleshoot issues, customer should have a solid understanding of networking and internet technologies. Zuora Support may require IT personnel from customer's organization to participate in the debugging process.
| Description | Supported | Self-Service |
|---|---|---|
|
Identifying whether application requests are being received by the Zuora platform |
|
|
|
Identifying whether error messages are being sent by the Zuora platform |
|
|
|
Troubleshooting proxy server connection issues and other issues originating from customer-specific hardware and devices |
|
|
|
Determination of root cause for any networking issues outside of Zuora and our data center |
|
|
Data Migration
| Description | Supported | Self-Service |
|---|---|---|
|
Recommendations, best practices, troubleshooting and instructions on available Zuora API operations needed to conduct data migration activities |
|
|
|
Solution design for legacy accounts migration |
|
|
|
Assist with Credit Card / Payment Method migration * (subject to PCI restrictions) |
|
|
|
Migration of data from one tenant to another (sandbox->production or sandbox->sandbox or production->production) |
|
|
|
Request to clean-up/delete data (e.g. delete all Product, Accounts, Subscription) |
|
|
General Consulting/Guidance on Best Practices
| Description | Supported | Self-Service |
|---|---|---|
|
Guidance on where to find resources to obtain information on best practices and training materials. Requests for additional time may be accommodated upon completion of Zuora Training |
|
|
|
Provide recommendations on best practices when provided specific subjects to review |
|
|
|
Onsite support at customer location |
|
|
Features Requests/Defect Reporting/Incidents
| Description | Supported | Self-Service |
|---|---|---|
|
Determination of whether or not a specific feature/behavior is currently available in the application |
|
|
|
Submission of feature requests into the Product Management tracking system |
|
|
|
Determination of whether or not a specific issue/behavior is a defect in the current application |
|
|
|
Submission of defects into the Engineering tracking system |
|
|
|
Providing updates on status of any previously filed feature request or defect |
|
|
|
Continuous engagement with Engineering on behalf of customer until resolution is obtained for any Severity 0 or Severity 1 defect |
|
|
|
Providing an ETA for any feature request unless it is published in Product Release Notes |
|
|
|
Entering tickets for incidents |
|
|
|
Tracking ticket activity |
|
|
|
Receiving escalations and expediting ticket activity where necessary |
|
|