- © 2026 Mailsoftly Inc. The name "Mailsoftly" and the Mailsoftly logo are registered trademarks of Mailsoftly Inc.
Every verified channel, the fastest path to a real person, and self-serve fixes for the issues that send writers hunting for help in the first place.
by Esma Calis · Last updated: 2026-08-24Substack customer service runs through one primary channel: the online Help Center at support.substack.com, where you search articles and submit a support request that is answered by email. There is no public Substack phone number and no general live chat. Available options can vary by publication and plan.
That single fact frustrates a lot of writers. When a payout looks wrong, a publication gets locked under review, or a newsletter suddenly lands in spam, most people want to talk to someone quickly. With Substack, the reliable move is knowing exactly where the request form lives, what to include, and which problems you can fix yourself faster than a ticket ever will.
This guide sticks to verified channels only. Where a support option cannot be confirmed on Substack’s own help resources, it is left out on purpose rather than guessed at.
New here? Start with our primer on Email Platform Comparisons for the fundamentals, then come back to this guide.
Quick context: Mailsoftly offers transparent pricing, free hands-on migration, and human support. 500 contacts and 2,000 emails per month with your Gmail, Outlook, Google Workspace or Microsoft 365 account, no credit card.
Start free with Mailsoftly →
Key Takeaways
Substack concentrates support into self-serve resources plus one contact path. The table below lists only channels that can be confirmed through Substack’s own help resources. Phone and live chat are deliberately absent because there is no verified public option for either.
| Channel | Where to find it | Best for |
|---|---|---|
| Help Center | support.substack.com | Searching articles for setup, billing, and publishing questions |
| Support request form | Submit a request from the Help Center | Account-specific issues that need a human reply by email |
| In-product help links | Dashboard and Substack app menus | Reaching the right article or form from inside your account |
| Phone | Not available | No public phone number is published |
| Live chat | Not verified | No confirmed general live chat for publishers |
You can browse and search the official Substack Help Center resources without logging in, which is the best starting point before you open a ticket. If self-serve articles do not resolve your issue, the support request form in the same place routes your message to the team, and responses arrive by email.
Read enough? Try Mailsoftly free with 500 contacts and 2,000 emails per month with your Gmail, Outlook, Google Workspace or Microsoft 365 account, no credit card.Start free with Mailsoftly →
The fastest path to a human is a single, complete support request submitted through the Help Center, not a hunt for a hidden hotline. Because replies come by email, the quality of your first message determines how many round trips it takes to reach a resolution.
Vague tickets get generic responses or clarifying questions, which stretches a one-day answer into a week. A specific ticket, with the exact publication, the exact error, and the steps you already tried, gets a targeted reply. Treat the form like a bug report, not a chat opener.
One more accelerator: submit from the email address that owns the publication. Tickets sent from a secondary address often trigger identity verification, which adds a delay before anyone even looks at the actual problem.
Before you open a ticket, gather the account details and evidence that support will inevitably ask for. Having these ready in the first message removes the most common cause of slow resolutions: the back-and-forth to confirm who you are and what actually happened.
Keep a copy of your ticket text and any reference number in a note. If a thread stalls or gets closed, you can reopen or resubmit with the same details in seconds instead of reconstructing the story from memory. Documentation is leverage when support is asynchronous.
Four categories drive most support requests: billing surprises, account locks, deliverability drops, and import problems. Several of these you can resolve yourself faster than a ticket cycle. Here is what each one looks like and where to start.
Most billing confusion comes from renewal timing, tax handling, or the platform fee on paid subscriptions. Before you file a ticket, check your subscription and payout settings in the dashboard, where charges, connected payment accounts, and upcoming renewals are listed. Reader-side charges are often self-cancelable from the reader’s own account page, which resolves double-charge worries without support at all. If a number genuinely looks wrong, that is a legitimate ticket, and your screenshot of the charge is the single most useful attachment you can include.
A publication placed under review or restricted is usually tied to a policy check on content, payments, or a sudden spike in activity that looks unusual. There is rarely a self-serve override for this. The productive move is a calm, factual support request that states your publication, confirms your identity, and asks specifically what is required to restore access. Avoid submitting multiple duplicate tickets, which can push you to the back of the queue. One clear thread, updated with any information they request, resolves these faster than a flurry of angry messages.
If open rates fall or readers report emails in spam, start by ruling out the causes you control. Ask a few subscribers which provider flagged the message, check whether you recently changed your sending name or added heavy image or link content, and confirm your custom domain is verified if you use one. Because Substack sends from shared infrastructure, an individual publisher has limited control over the underlying sender reputation, so support may not be able to move the needle on inbox placement the way a dedicated setup could.
Import trouble usually traces back to CSV formatting, duplicate rows, or unverified addresses that get skipped on upload. Re-export a clean file from your source, confirm the email column header matches what the importer expects, and remove obviously invalid rows before trying again. If the import still fails, a ticket that includes the exact error and the row count you attempted gives support enough to diagnose it. Keep your own backup of the subscriber list too, so you are never dependent on a single platform to hold your audience.
Sometimes the honest answer is that support cannot help, and that is useful information. When the resolution to a real need is “that is not something the platform does,” no ticket will change it. Recognizing that early saves you weeks of escalation.
Watch for two patterns. First, when the recommended fix for a core workflow is to accept a hard limitation, you have hit a product boundary, not a support gap. Second, when repeated, well-written tickets go nowhere and the thread simply closes, the channel itself is the constraint. Neither is a failure on your part; both are signals about whether the tool fits the way you actually work.
Substack is excellent at what it is built for: publishing and simple paid subscriptions. But if you need segmentation, richer automations, deliverability control, or a human you can reach when revenue is on the line, the friction you feel with support is often really a friction with fit. That distinction is worth naming before you invest more effort fighting the queue.
If asynchronous, email-only support and platform limits are the real problem, a tool built around reachable humans changes the day-to-day. Mailsoftly answers with real people on every plan, including the free tier, and offers free hands-on migration so moving your list is not a solo project. We do not publish response-time promises we cannot guarantee, but you will not be stuck talking to a form.
Pricing is transparent and starts free with 500 contacts and 2,000 emails per month with your Gmail, Outlook, Google Workspace or Microsoft 365 account, no credit card required. If you are weighing the switch on cost, you can compare tiers directly on Mailsoftly’s transparent pricing page and see exactly what human support and migration are included at each level, rather than discovering limits after you commit. The Starter plan is $15 a month (billed yearly) for 1,000 contacts and 10,000 emails, and lets you send from your own domain.
For the broader picture on this topic, see our complete Email Platform Comparisons guide, which covers strategy, fundamentals, and advanced playbooks.
No. There is no verified public Substack phone number for customer service. Support is handled through the Help Center and an email-based support request form. Any third-party site claiming to offer a Substack support hotline should be treated as unofficial.
You reach Substack support by submitting a request through the Help Center at support.substack.com, and the team replies to your email. Sending from the account email that owns the publication, with your publication URL and a clear description of the issue, gives you the fastest useful response.
There is no confirmed general live chat for Substack publishers. The verified options are self-serve Help Center articles and the email-based support request form. Available support can vary by publication and plan, so check what appears inside your own dashboard.
Substack does not publish a guaranteed response time, so any specific number you see elsewhere is not official. Response speed can vary with volume and issue type. A single, complete, well-documented ticket is the most reliable way to shorten the exchange.
Talk to a human at MailsoftlyStart free with Mailsoftly →
500 contacts, 2,000 emails per month with your Gmail, Outlook, Google Workspace or Microsoft 365 account. Free hands-on migration. No credit card.
Looking for an alternative?
Mailsoftly offers the features you need at a price that makes sense.
Switch to MailsoftlyFree migration on paid plans