This Support page provides comprehensive information on how to obtain help, report issues, and make the most of Vertex CRM in your organization. Our support approach is designed to meet the needs of production deployments, from small teams to enterprise customers. Whether you are an end user, an organization administrator, or a technical implementer, the following sections outline support channels, service expectations, troubleshooting guidance, and escalation paths.
Support for Vertex CRM may be provided by the team that deployed your instance (e.g., your organization's IT department, a system integrator, or the vendor who licensed or hosts the product). The contact details and service levels that apply to you are typically defined in your service agreement or order form. This document describes general support practices and self-service resources that are commonly available regardless of your specific support tier.
Before contacting support, we recommend using the following resources: (1) Documentation — The Documentation page and, where provided, in-app help and admin guides cover setup, features, RBAC, and operations. (2) Privacy Policy, Terms and Conditions, and Terms of Usage — These documents address legal, compliance, and acceptable-use questions. (3) Your organization's administrator — For access issues, role or permission changes, and organization-specific configuration, your Vertex CRM administrator is the first point of contact. (4) Release notes and known issues — If available in your deployment, check for workarounds and fixed issues in the current version.
When you need to contact support, use the channel(s) designated for your deployment (e.g., email, support portal, or ticketing system). Include the following to speed up resolution: your name and organization name; the environment (e.g., production, staging); a clear description of the issue or request; steps to reproduce (for bugs); any error messages or screenshots; and, if relevant, the time and timezone when the issue occurred. For security-sensitive issues, use the designated secure channel and do not include sensitive data (e.g., passwords) in unencrypted email.
Response and resolution times depend on your support plan and the severity of the issue. Typical classifications include: Critical — Production down or major functionality unavailable; High — Significant feature impaired or workaround difficult; Medium — Feature impaired but workaround available; Low — Minor issue or question. Specific targets (e.g., initial response within 4 hours for Critical) are usually defined in your SLA. Support teams prioritize Critical and High issues and work to restore service or provide a workaround as quickly as possible.
Cannot log in: Verify your username and password; ensure your account is active (not disabled by an administrator). If you forgot your password, contact your administrator to reset it. If the login page does not load, check your network connection and that you are using the correct URL. For "invalid credentials" errors, ensure caps lock is off and that you are using the correct organization context if the system prompts for it.
Missing menu items or "Access denied": Your visibility to sidebar items and pages is controlled by your role and profile in the current organization. If you do not see Accounts, Leads, or other items, your profile may not include list permission for those objects. Contact your organization administrator to have your role or profile updated. If you believe you should have access, ask the administrator to verify your user-org-role assignment and profile permissions.
Slow pages or timeouts: Large datasets or complex reports can affect performance. Try narrowing filters or date ranges. Administrators can review database size, indexes, and server resources. For hosted deployments, the provider may need to scale resources or optimize queries.
Data not showing or incorrect: Confirm you are in the correct organization (check the org switcher). Verify filters and search terms. If data was recently added or updated, ensure you have the appropriate permissions and that the record is saved. For imports or integrations, check that the process completed successfully and review any error logs.
API or integration errors: Verify authentication (e.g., valid session or token), endpoint URL, and request format against the documentation. Check rate limits and that the integration (e.g., OAuth) is configured correctly. Review server logs for detailed error messages. For third-party integrations, ensure the external service is operational and that credentials have not expired.
Cannot assign roles or access Setup: Only users with admin update permission (or super administrators) can assign roles and profiles. If you are an org administrator and cannot see the "Assign role" button, ensure your profile has admin with update permission. Super admin access is typically reserved for the global administrator account; contact the party that deployed your instance if you need this level of access.
When reporting a bug, provide a clear description, steps to reproduce, expected vs. actual behavior, and any error messages or logs (with sensitive data removed). Include your environment (browser, OS, Vertex CRM version if known). This helps the support and development teams reproduce and fix the issue. Feature requests are welcome; describe the use case, desired behavior, and any alternatives you have considered. Prioritization depends on product roadmap, impact, and resource availability; not all requests can be implemented.
If you suspect a security vulnerability (e.g., unauthorized access, data exposure, or a flaw in the application), report it through the designated secure channel as specified in your agreement or on the Security page (if available). Do not disclose the vulnerability publicly before it has been addressed. We take security seriously and will work with you to understand and remediate valid issues in accordance with our security policy. For personal data breaches or privacy incidents, follow your organization's incident response process and any applicable regulatory reporting obligations.
If your issue is not resolved within the expected time or you believe it has been mishandled, request an escalation through your support channel or account manager. Escalation paths and contact details are typically defined in your service agreement. For critical outages, escalation may be initiated immediately to ensure appropriate priority and communication.
Successful adoption of Vertex CRM depends on training and change management. Use the Documentation and in-app guidance to train users on core objects (accounts, contacts, leads, opportunities, activities, tasks, reports) and on role-based access. Administrators should be trained on Setup: users, roles, profiles, queues, SLA rules, and integrations. Consider internal FAQs, quick-reference guides, and periodic refreshers to keep the team productive and compliant with usage policies.
For support contact details specific to your deployment (email, portal, or phone), refer to your order form, service agreement, or the information provided by your organization's IT or the vendor who supplied Vertex CRM. If you are the deployer and need to configure support contact information for your users, update the Support page or help resources accordingly so that users know where to turn for help.
Last updated: 2025. This Support page is designed to support production use and industry best practices. Your actual support entitlements and procedures are governed by your agreement with the party that provides your Vertex CRM instance.