Email hello@orgchartstudio.com if something in Org Chart Studio isn't working as expected. Tell us what you tried, what you expected, and what happened instead.
Use the same address for a question or feature suggestion. You don't need a matching Help search result before contacting us.
What to include
- What you were trying to do: for example, change a person's department or export a PDF.
- The steps: where you started and which controls you used.
- What you expected and what happened: include the exact error text, if there is any.
- Your browser and device: for example, Safari on an iPad or Chrome on Windows. Include the browser version if you know it.
- When it happened: include your time zone if timing might help, such as for a save or payment problem.
- Which chart state you saw: say whether the chart showed Local draft, Saving, Saved, or a visible error. Use the chart name only when it contains no sensitive information.
Mention whether it happens every time or only sometimes. If you know the last step that worked, include that too.
A report you can copy
I was trying to:
Steps to reproduce:
I expected:
What happened instead:
Error text, if any:
Browser and device:
When it happened:
Chart status, if relevant:
Does it happen every time?
The link opens your email app. It does not send a message or attach your chart. Review the message and any attachments before sending. If no email app opens, copy hello@orgchartstudio.com into the email service you normally use.
When a screenshot or short recording helps
A screenshot is useful for an incorrect layout, a clipped menu, or a setting that doesn't match the result. Include enough of the interface to show which view or dialog is involved.
A short recording can help with a sequence, such as a menu closing unexpectedly or a drag ending in the wrong place. Show the starting state, the action, and the result.
Check images and recordings for information you don't want to share. You can reproduce the issue with fictional names if that shows the same problem. Don't include passwords, verification codes, payment-card details, or unrelated HR information.
If the problem involves saving or payment
For a saving problem, include the save status or error you can see. If you have unsaved work, keep the tab open while you note what happened. Use Retry save if it is available. Don't clear browser storage, discard the draft, or reset the chart just to gather a bug report.
For a payment problem, include the approximate purchase time, the email used for the purchase, and any receipt or order reference you already have. Do not send full payment-card details. You don't need to make another purchase to report the first one.
Feature suggestions
Tell us what you want to accomplish and what makes the current process difficult. A concrete example is more useful than a feature name alone. For example, explain which reporting relationship you need to show and who needs to read the chart.
For questions about your information, see our privacy policy.