|
| 1 | +--- |
| 2 | +title: Support |
| 3 | +description: Learn how to reach the Mergify support team, understand coverage, and explore enhanced support options. |
| 4 | +--- |
| 5 | + |
| 6 | +At Mergify, we treat support as a core part of the product experience. Our goal |
| 7 | +is to keep your merge automation running smoothly by making it simple to contact |
| 8 | +the right team, set expectations, and understand the additional services |
| 9 | +available to larger organizations. |
| 10 | + |
| 11 | +## Contact Support Immediately |
| 12 | + |
| 13 | +If you are stuck, use one of the following channels: |
| 14 | + |
| 15 | +1. **Email: ** < a href="mailto:[email protected]"> [email protected]</ a>. |
| 16 | + Include the affected repository, pull request number, and a short description |
| 17 | + (screenshots/log excerpts encouraged) so we can reproduce quickly. |
| 18 | + |
| 19 | +2. **In-app ticket:** From the Mergify dashboard, go to **Help → Contact |
| 20 | + support** to submit a request. We automatically attach account context, which |
| 21 | + speeds up triage. |
| 22 | + |
| 23 | +3. **Status follow-up:** Track platform availability at <a |
| 24 | + href="https://status.mergify.com">status.mergify.com</a> and reference |
| 25 | + incident IDs in your ticket for targeted updates. |
| 26 | + |
| 27 | +These options are available to every Mergify user. |
| 28 | + |
| 29 | +## Support Overview |
| 30 | + |
| 31 | +We provide assistance to authorized users directly through the service as well as by email. While |
| 32 | +resolution times can vary depending on complexity, our team commits to best-effort responses within |
| 33 | +one (1) business day for every incoming request. You will always receive a human acknowledgement |
| 34 | +confirming the scope and next steps. |
| 35 | + |
| 36 | +Enterprise plans unlock additional collaboration channels beyond the default email queue: |
| 37 | + |
| 38 | +- **Dedicated Slack channel:** Eligible enterprise customers receive a shared |
| 39 | + Slack channel with the Mergify team for higher-touch incident response, |
| 40 | + proactive reviews, and faster iteration. |
| 41 | + |
| 42 | +- **Named support contacts:** We partner with your engineering leads to keep |
| 43 | + context warm and reduce time to resolution on recurring workflows. |
| 44 | + |
| 45 | +Reach out to your account manager if you would like to enable or adjust these enterprise options. |
| 46 | + |
| 47 | +## Premium Support |
| 48 | + |
| 49 | +Organizations that need round-the-clock coverage can subscribe to our optional 24/7 Premium Support |
| 50 | +package. This add-on provides prioritized routing, after-hours incident handling, and direct access |
| 51 | +to on-call engineers. Contact < a href="mailto:[email protected]"> [email protected]</ a> to scope the |
| 52 | +package and ensure it matches your operational requirements. |
| 53 | + |
| 54 | +## What to Expect |
| 55 | + |
| 56 | +When you open a support request, we: |
| 57 | + |
| 58 | +1. Acknowledge the ticket and confirm the scope within one business day. |
| 59 | +2. Investigate using the artifacts you provided and any telemetry available on our side. |
| 60 | +3. Publish corrective updates when needed and confirm the outcome with you. |
| 61 | + |
| 62 | +If a request requires product changes or in-depth consulting, we will clearly |
| 63 | +outline the effort and any additional agreement needed before proceeding. |
0 commit comments