Existing customer
Open a portal support thread
Use the authenticated portal for threaded follow-up, attachments, license context, and status tracking.
Support hub
Choose the right public Cerberus path before anyone needs to guess between sales, support, or rollout help.
Existing customers should stay in the authenticated portal thread. New prospects and pre-purchase teams can use a tracked public intake route for commercial contact, support add-ons, questionnaires, or migration planning.
Commercial
Start an enterprise conversation
Use the public commercial route for procurement review, rollout planning, support packaging, or custom limits.
Support add-on
Request response targets
Professional and Enterprise customers can request guided troubleshooting and escalation paths without giving up operational control.
Security questionnaire
Start a tracked intake for vendor review, compliance frameworks, privacy questions, and artifact verification requests.
Migration assessment
Use a public intake when you need rollout guidance, migration scoping, or phased deployment planning before production starts.
What good requests include
The fastest support and sales loops come from concrete deployment detail, not from broad problem statements.
- Cerberus version and deployment mode
- clear symptoms, rollout goals, or procurement blockers
- timelines, environment size, and attachments or logs where useful
Customer control stays intact
Support and rollout guidance should feed into your own approvals and change process, not bypass it.
- test high-impact actions before production where feasible
- keep backups, exports, or rollback plans for affected systems
- treat firewall, identity, and network changes as customer-approved operations
Support Add-on
Response targets and guided troubleshooting without turning Cerberus into a managed SaaS.
- Response targets and escalation path
- Installation and upgrade guidance
- Operational troubleshooting help
- Available for Professional and Enterprise
Policies