Get Help from the Temporal Team
info
This page is part of the Temporal Knowledge Hub.
Temporal Cloud support model
At ABC Financial, we have Enterprise support for Temporal Cloud. With Enterprise support, Temporal offers the following response time targets for support tickets:
| P0 | P1 | P2 | P3 | |
|---|---|---|---|---|
| Definition | Production impacted - Temporal Cloud service is unavailable or degraded with a significant impact. | Production issue - An issue related to production workloads running on the Temporal Cloud service, or a significant project, is blocked. | General issues - General Temporal Cloud service or other issues where there is no production impact or a workaround exists to mitigate the impact. | General guidance - Questions or an issue with the Temporal Cloud service that is not impacting system availability or functionality. |
| Response time target | 30 minutes (24×7) | 1 hour | 4 hours | 1 day |
How to submit a support ticket
- Go to support.temporal.io.
- If prompted, log in to Temporal Cloud using the same method you normally use (e.g., Google, Microsoft, email-password, or other methods).
- You will be presented with a screen where you can view open and closed tickets for your Temporal account, as well as submit a new ticket.
Temporal account team
note
Replace with your organization's Temporal account team contacts.
- Temporal Account Executive: Person
- Temporal Solution Architect: Person
- Temporal Dedicated Support Engineer: Person
Temporal expert-led sessions
As part of the Temporal Cloud Enterprise support model, the Temporal team will provide the following sessions to any application teams using Temporal:
- Lunch and Learn: Informal, high-level educational presentations to introduce Temporal concepts to broader engineering or leadership teams.
- Design Session: Collaborative whiteboard-style meetings to draft the initial system architecture and workflow logic.
- Proof of Concept (PoC): A hands-on engagement to build a limited-scope prototype that validates specific technical capabilities.
- Office Hours: Recurring, open-forum blocks for developers to drop in and ask adhoc implementation questions.
- Design Review: A formal deep dive where an architect critiques the proposed implementation plan against best practices to prevent future technical debt.
- Cost Optimization: identify opportunities for reducing Temporal Cloud spend and improve resource efficiency without sacrificing performance.
- Code Reviews: Review Temporal Workflow Definition in any supported SDK.
- Worker Deep Dive: A specialized technical session focusing on the internal mechanics, configuration, and lifecycle of Temporal Workers.
- Code Review: Line-by-line inspection of Workflow and Activity code to ensure correctness, error handling, and adherence to best practices.
- Worker Tuning: Performance optimization sessions focused on adjusting Worker configurations for production readiness.
- Load Testing: Strategy sessions to design and execute stress tests that simulate production traffic and identify bottlenecks.
- Capacity Planning: Using load test data to accurately provision the necessary infrastructure for current and future scale.