Home / Insights / Operations and security
Who can help when your SaaS stops working?
Summary
Start with the support route available on your plan and a way to recover account access. monday.com Enterprise and Asana Enterprise / Enterprise+ publish numerical response commitments, but those are deadlines for an initial response, not for restoring your business. An upgrade needs to solve a specific support requirement.
Work out who owns the failure
A failed page can come from the SaaS service, a browser, a payment provider or an installed app. Record the affected screen, time and time zone, error text, and whether other colleagues see the same problem. This gives support something reproducible and helps you avoid opening the same enquiry with the wrong provider.
For Shopify, third-party apps and paid third-party themes go to their developers; Shopify supports its own apps and themes within the stated scope. Paying for a higher store plan does not make Shopify responsible for every integration. Keep those developer contact details with your store's support route.
| Situation | Prepare this route | Why it helps |
|---|---|---|
| You cannot sign in | Shopify publishes a separate Can't log in form. monday.com lists contact routes outside the platform. | A login failure does not mean every contact route is closed. |
| An integration fails | Identify which vendor or app developer owns the connection. | The main SaaS subscription may not cover third-party code. |
| A service-wide incident | Check the vendor status page and contact support through the eligible channel. | A published incident can distinguish a broad outage from an account-specific problem. |
| A free user needs product help | HubSpot directs free users to help and community; Semrush limits free enquiries to non-product matters. Asana lists direct support from Starter. | Choose a paid support route only if you need it; self-service may be enough for setup. |
Scroll the table horizontally on a small screen.
Read a response deadline literally
The monday.com Enterprise SLA classifies errors and sets first-response limits: Critical within 30 minutes, High within one hour, and Medium or Low within 24 hours. monday.com determines the severity. Critical issues receive continued work around the clock, but the table is not a promise of recovery in 30 minutes.
Asana's addendum applies to Enterprise and Enterprise+. It provides English support around the clock and a response within two business hours, excluding US, Ireland and Australia holidays. The enquiry needs an account-associated email address and enough detail to reproduce the problem. This is not a two-hour resolution commitment or Japanese-language coverage.
Shopify describes email responses as typically 48 hours for Plus and Retail. That is an estimate for email, not the wait for all-plan chat. HubSpot's mobile email instructions say replies generally arrive within one working day. Neither wording should be turned into a guaranteed restoration time.
Compare the contract with a workable fallback
If an order cannot be processed, assign someone to handle customer communication and decide which work can continue outside the service. For customer records or project work, keep an approved backup and a way to record updates while access is unavailable. These are operating choices to design for your business, not features that an SLA supplies.
An enterprise response commitment may be useful when you must have an enquiry acknowledged within a defined period. It is less useful if the main problem is custom code, missing login credentials or a lack of someone who can describe the error. Obtain a quote for the required plan and support scope before comparing its annual cost with the interruptions you are trying to reduce.
If help articles and next-business-day assistance fit the work, keep the lower plan and document the contact route. If you need a written response deadline, evaluate the Enterprise terms above and any negotiated terms in the order. If Japanese support is required, use the language and channel comparison as a separate check. The right support plan is the one that covers your failure scenario.
Sources checked 10 October 2026
Shopify: scope and login recovery / monday.com: external contacts / HubSpot: eligibility and mobile email / Semrush: free enquiries / Asana: support by plan / monday.com: error response SLA / Asana: service level addendum
What changed on this page
- correction11 October 2026 Incident support — EN/JA article review
No-login means no contact; response equated with recovery → Login recovery form, ownership triage and precise SLA scope
Official evidence checked on 10 October 2026.
Every recorded change to this site is in the change log.
More in Operations and security
All of operations and security →Where is your SaaS customer data stored, and can you change the region?
A selected region does not cover every category of data or every processing location.
Read → Operations and securityHow many times a month will your automations run, before you sign?
Estimate automation demand by trigger, actions per run and active days; verify quotas with a pilot.
Read → Operations and securityWhat do you hand over when a client asks how you manage information?
Match the client questionnaire to security reports, contract terms, account data location and your own access controls.
Read →