Centro assistenza

Supporto, fatturazione e risposte workflow

Questa pagina esiste per ridurre l’attrito con il supporto e rendere il prodotto pubblico più comprensibile.

Percorsi rapidi

La maggior parte delle domande di supporto riguarda in realtà il workflow. Questi link portano prima alla pagina giusta.

Aspettative del piano

Confini chiari del piano riducono la frustrazione degli utenti Free e i ticket inutili degli utenti paganti.

  • +Free plan: 10 general summaries/day, 3 PDF summaries/day, and up to 3 saved library items.
  • +Pro: 100 summaries/day, 50 PDF summaries/day, 300 chat messages/day for supported chats, and unlimited library saves.
  • +The Chrome extension uses the same account rules as the web app, so saved items and plan limits stay consistent.
  • +If a checkout succeeds but Pro is not active immediately, the status usually catches up shortly after the webhook finishes.

Paid-user support checklist

Pro users should not have to guess what information support needs. This also improves internal triage quality.

When to contact support

Contact support for billing errors, failed activation, missing saved summaries, broken share links, or extension sign-in issues. The response target is currently 24 to 48 hours.

What to include

  • •Include the email address on the account and the time the issue happened.
  • •If the issue is tied to a source, include the exact page URL or YouTube link.
  • •If the problem is billing-related, mention whether the issue is renewal, cancellation, activation, or invoice access.
  • •If a saved item or share link is missing, include the summary title and the page you were on when it failed.

Ads, privacy, and public pages

Ad review quality is tied to how the site behaves. Public content pages can carry ads; user workflows and paid experiences should not.

Ad boundaries

Ads are intended for selected public marketing and educational pages. They are not intended for library workflows, account flows, checkout flows, or active Pro users.

Support channel

For anything account-specific, email hello@5tldr.com. Include enough detail for support to reproduce the issue on the first reply.

Publisher standards

How support and public guidance are maintained

Help content should read like real user guidance, not a thin SEO wrapper. We keep these pages tied to plan rules, support patterns, and product behavior.

Hands-on workflow coverage

These pages are built from real 5tldr workflows, support questions, and product behavior instead of thin keyword templates.

Updated when the product changes

We refresh guidance when plan rules, supported sources, failure states, and learning workflows change.

Content and ad boundaries stay separate

Educational pages may carry ads. Product workflows, pricing, library, checkout, and paid-user journeys should remain ad-free.

Centro assistenza | Supporto, pagamenti e workflow | 5tldr | 5tldr