Getting started
Getting help when something is not working
Start with the in-app Help Assistant or the Help Center when you have a product question. Those answers are grounded in the same help articles you can open and verify yourself.
Use help articles for workflow questions
Questions like how sources work, how citations are built, where exports live, how syncing behaves, or which shortcuts exist should usually be answerable directly from the help articles. The Help Assistant is designed to point you to those articles instead of making promises it cannot verify.
Send it to the team when the issue is real
Signed-in users can open Help from the editor, dashboard, or settings. If something is broken, a billing or account case is blocked, or the Help Assistant cannot verify the answer from the help center, use the chat action to send it to the team. The report asks for a summary, what happened, what you expected, and optional repro steps, then attaches the current route, browser details, and recent help context.
What helps the report move faster
- A short summary in plain language
- What happened versus what you expected
- Repro steps if you can repeat the issue
- The essay or route involved, if it matters
The normal help experience is product guidance, not live chat. If the assistant says it cannot verify something, treat that as a sign to escalate the case instead of pushing for a guess. Reports create or update a support case first, then EssayGenius attempts to notify the configured support inbox.