Skip to content
Help Center

How can we help?

Choose the route closest to your issue. Workspace-specific help is fastest when you start from the related workspace because messages, files, action requests, progress updates, and receipts are already connected there.

FAQLive chat

Start here

Use the path with the right context

Workspace issues should begin inside the workspace. General questions can use FAQ, live chat, support tickets, or contact support.

Support ready
Open your workspaceBest first stepBest for workspace-specific messages, files, requirements, action requests, progress updates, and receipts.Review workspace updatesUse the relevant workspace page so your request stays attached to the correct course-support context.Check billing and receiptsReview billing records, receipts, and workspace-related totals before contacting support about a charge.

Other support paths

Use these when the issue is broader than a single workspace.

Browse FAQsQuick answers about timelines, files, confidentiality, adjustments, pricing, and academic support.Start live chatUse chat for fast clarification when you need help choosing the right support route.Use support ticketsFor tracked account-specific issues, use the ticket path and include the right context.Contact supportUse contact support for general questions not tied to a specific workspace or payment.

Where should I ask about an active workspace?

Start inside the workspace. It keeps messages, files, action requests, progress notes, and receipts connected to the same course-support context.

Open workspaces

What should I include when asking for help?

Include the workspace number, the exact issue, the file or message involved, and the outcome you need. Clear context reduces back-and-forth.

See support options

Where do I find policy answers?

Use the FAQ for confidentiality, responsible support, payment, and workspace-process questions before opening a support ticket.

Browse FAQ

Help routed cleanly

This page links to existing workspace, payment, FAQ, chat, ticket, and contact surfaces without introducing fake forms or duplicate support workflows.