What's actually happening to your ticket
Your Base44 support ticket probably was not ignored — it was out of scope. Base44's support documentation states that support "does not provide hands-on debugging or fixes for your individual app code, prompts, or architecture," and routes app-level work to Discord or to a Base44 partner instead. Base44 also publishes no response-time commitment: its own FAQ answers "why has support not responded to my ticket yet?" with "response times vary based on ticket volume and issue urgency." So the decision in front of you is not how to escalate harder. It is whether your issue was ever something support would take, and if not, how quickly you replace the wait with someone who can read the stack.
Your app broke on a Wednesday. You filed the ticket Wednesday afternoon. It is now the following Tuesday and you have received nothing — no status change, no human acknowledgement that anyone read it. Your business loses revenue every hour the app stays broken, and the silence reads as neglect.
It usually is not neglect. It is a category error, and Base44 documented the category in advance. The reason this distinction matters is that the two situations have opposite correct responses. If the ticket is genuinely queued, waiting and escalating politely is rational. If the ticket describes something support has published a policy against touching, then every hour you spend waiting is a pure loss — no amount of follow-up converts an out-of-scope request into an in-scope one.
Public review aggregates capture the feeling but not the mechanism. Trustpilot's Base44 profile showed 2.8 out of 5 across 877 reviews when checked on 2026-09-13, and "support is non-existent" is a recurring theme in them. Those reviews describe the symptom. Base44's own documentation explains the cause, and the cause is the part you can act on.
What Base44 support does and does not cover
The scope line is published, in writing, on the page that ranks first for "base44 support". From docs.base44.com/Community-and-support/Contacting-support, fetched 2026-09-13:
Base44 support focuses on making sure the Base44 platform works as expected and on helping you with billing, account, and other platform-related questions. It does not provide hands-on debugging or fixes for your individual app code, prompts, or architecture.
The same page lists six things support does cover: general guidance on how to use Base44 features; billing questions and account management; Base44-offered connectors and GitHub sync — explicitly "not third-party or open-source integrations"; platform bugs and errors; workarounds or solutions to known issues; and clarifying which part of an issue belongs to Base44 versus an external system or your own implementation. For anything outside that list, the docs say to get guidance from the community in Discord "or work with a Base44 partner."
Read symptom-first, the boundary looks like this:
| What you filed | In Base44's published scope? | Who actually resolves it |
|---|---|---|
| The builder is down, or you cannot log in to base44.com | Yes — platform bugs and errors | Base44. File the ticket; the wait is legitimate. |
| Double charge, plan change, invoice, account access | Yes — billing and account management | Base44. The ticket is the only route. |
| "How do I connect a custom domain / set up auth?" | Yes — general guidance on using features | Base44, or the docs AI assistant, faster |
| GitHub sync or a Base44-offered connector stopped working | Yes — connectors and GitHub sync | Base44 |
| White screen with a 405 after login | No — your app's code | You or a developer — white screen 405 after login |
| Row-level security drifted after an AI edit and data leaked | No — your app's architecture | You or a developer — RLS out of sync after an AI edit |
| Stripe charges succeed but the subscription grants no access | No — your implementation plus a third party | You or a developer — Stripe subscription not granting access |
| A backend function returns 404 in production | No — your app's code | You or a developer — backend functions 404 |
| A Zapier or webhook integration silently stopped firing | No — third-party integrations are excluded by name | You or a developer — Zapier integration not working |
Every row in the bottom half is a ticket that will not get a fix no matter how long it sits, because Base44 said so before you filed it. Their documentation routes that work to a partner rather than a queue — which is exactly what a fixed-price bug-fix sprint is: one high-impact bug, diagnosed and shipped in 48-72 hours, money back if it is not resolved. There are 47 documented fix playbooks on this site, and the bottom half of that table is what they are for.
Why the reply never comes
First, scope — not queue depth. If your ticket describes app code, a prompt, your architecture, or a third-party integration, no amount of queue drainage produces an answer. It is outside the service. Support staff triaging it correctly means closing or deprioritising it.
Second, there is no response-time commitment to breach. Base44's FAQ addresses the unanswered ticket directly and says only: "Response times vary based on ticket volume and issue urgency. If your issue is ongoing, reply to your existing ticket with any new details so we can continue troubleshooting." That is a first-party confirmation that no SLA exists — stronger evidence than any review. The support documentation publishes no first-response target, no resolution target, no escalation matrix, and no remedy for non-response at any plan tier. The same absence of contractual commitment shows up on uptime, documented in no-sla-outage-risk.
Third, the published path puts AI ahead of a human on purpose. The docs tell you to click "Ask a question" at the bottom of any documentation page, then work a seven-item troubleshooting checklist — search the docs, try incognito, check the changelog, clear cache, reproduce in a minimal test app — and only then submit a ticket. That design answers documented questions well and loops on novel ones. If your problem is novel, you reach the queue already several days into the incident, and the queue is the part with no clock.
The Wix acquisition (June 2025) changed this less than people expect. Base44 support still runs on its own ticket system at app.base44.com/support/conversations, under its own Support Terms of Use, with its own scope policy — none of which reference a Wix support apparatus.
How long is too long
There is no universal number, because the right answer depends on two variables: how old the ticket is, and what it is blocking. Run it as a lookup.
| Ticket age | What it is blocking | What to do now |
|---|---|---|
| Under 24 hours | Nothing customer-facing | Wait. Reply on the thread only if you have genuinely new detail. Duplicate tickets make it worse, not faster. |
| 24-72 hours | One non-revenue feature | Reply once on the existing thread with repro steps and timestamps. Work the five self-serve checks below in parallel. Assume nothing arrives. |
| Over 72 hours | Revenue, login, or customer data | Stop treating the ticket as your recovery plan. Leave it open for the paper trail and start a parallel fix track today. |
| Any age | You cannot reproduce the fault | Reproduction is the blocker, not the queue. A $497 diagnostic audit returns a written report in one business day and is refundable against fix work. |
The row that catches most teams is the last one. A ticket that says "it is broken sometimes" cannot be actioned by anyone — Base44 asks for expected versus actual behaviour, steps to reproduce, links and screenshots, and without those the thread stalls on both ends. If you cannot produce a repro, buying one is cheaper than another week of silence.
The escalation ladder that does not risk your support access
A correction, stated plainly: an earlier version of this page advised readers to post on the feedback board, tag Base44 on Twitter/X, and message the founder on LinkedIn when a ticket went cold. That advice was wrong, and Base44's published Support Terms of Use are the reason. The list of requests Base44 states it will not tolerate includes "support requests contesting Base44's policies" and "publicly lobbying against Base44 actions and policies," and rule 4 states that Base44 "reserves the right to restrict, suspend or permanently revoke access to Base44 Support for anyone who wilfully violates these Terms of Use," with the Base44 team as "the sole arbitrator" of what violates them. Public-pressure tactics put the one channel you still have at risk. We do not recommend them any more.
The in-scope ladder, in order:
- Reply on the existing thread — never open a second ticket. The docs say to "avoid opening duplicate tickets for the same issue. Instead, reply to your existing ticket with any updates," and the Terms of Use name "intentional attempts to disrupt the workload of the Base44 Support team by multiple or duplicated support request submissions" as intolerable. A duplicate is not a nudge; it is a listed violation. Track the thread under My Support Tickets at
app.base44.com/support/conversations. - Give the reply the five things Base44 asks for. The link to your app, what you expected to happen, what is actually happening, what you did immediately before it started, and a screenshot. Add timestamps and logs. A reply that adds new evidence is a legitimate reason to re-surface a thread; "any update?" is not.
- Write in English. The docs state that the platform and AI chat support multiple languages but "our human support team operates in English only," and that a ticket in another language may be sent back for rewriting. A non-English ticket can lose days to that round trip alone.
- Take app-level questions to Discord, because that is where the docs send them. The scope section names Discord and Base44 partners as the route for help building your app. Peer answers dominate, which is fine — the people who hit your bug last month are there.
- Use
feedback.base44.comfor what it is. The docs position the feedback board and roadmap for feature requests and voting. It is not an incident channel and it starts no clock. Posting an outage there is not an escalation. abuse@base44.comis for one thing only. The docs list it as the address to contact "if you believe your support access was mistakenly restricted." It is an appeals channel, not a faster queue.
If you need the full inventory of Base44's official channels and what each one is actually good for, that lives on the full Base44 support channel map rather than here.
Run these five checks while the ticket sits
Five minutes each, and they resolve a surprising share of tickets before anyone replies:
status.base44.com— confirm whether this is a platform incident. If it is, the ticket is in scope and waiting is correct.- Function logs — open the editor, find the function, read the most recent errors.
- Browser console and network tab — failed requests and client-side errors, with the exact status codes.
- Third-party dashboards — Stripe, your email provider, your auth provider. Their error messages are usually more specific than anything Base44 surfaces.
- The matching fix playbook on this site — search the symptom, not the guess.
If the app is down right now and you want these run as a timed sequence rather than a checklist, the 60-minute emergency triage walks the whole diagnostic in order. Do not re-run it here; go there.
When to stop waiting and pay someone
The decision rule is the scope test, then the clock. If the ticket is out of scope, the wait has no expected value at any duration and you should move today. If it is in scope and past 72 hours with revenue, authentication, or customer data affected, treat the ticket as failed and open a parallel track while leaving the thread alive.
Whether you fix it yourself or hand it over is a separate question with its own rubric — the DIY-versus-hire scoring in the debugging guide answers it without a sales call. Hire when self-serve diagnostics confirm the problem but you cannot ship the fix:
- Stripe integration broken — see stripe-integration-breaks-update.
- Backend functions returning 404 — see backend-functions-404-routing-broken.
- Data missing or corrupted — see data-loss-return-to-app.
In each of those, Base44's response time is not the variable that matters, because none of them were ever going to be answered by the queue.
One more case is worth naming. If this is the third silent ticket this quarter, the ticket is not the problem — the problem is that nobody on the account can read the stack when something breaks at 2am. That is the point where teams hire a Base44 developer on a standing basis instead of filing another ticket and hoping.
Need this fix shipped this week?
Base44's own documentation says app-code debugging is out of scope. That is the whole reason the ticket is quiet, and it will not get louder. A fixed-price fix sprint starts at $1,500, ships in 48-72 hours, and is money-back if we cannot resolve the issue. If you cannot reproduce the fault yet, start with the $497 audit — one business day, written report, refundable against fix work.
Book an urgent fix sprint for production emergencies: payments down, auth broken, app unreachable.
Related problems
- No SLA — outage risk — the support pattern is one symptom of base44's broader no-contractual-commitment posture.
- Functions stop working after hours — a common reason teams file tickets that then go unanswered.
- Performance editor hangs and crashes — another high-frequency ticket category that tends to receive no useful response.