Getting help

If the documentation has not answered it, write to us, but two minutes of checking first usually makes the first reply the useful one.

Before you write

Two checks that resolve a good proportion of reports:

1. Status: if something is degraded, it will be there.
2. Common problems: the triage index for every symptom this documentation covers.

Where to write

Contact support. Most questions are answered within one business day.

If you believe you have found a security vulnerability, use the reporting channel on the security page instead: not a support ticket.

What to include

The first reply is only as useful as the report. Please include:

• What you were doing: the screen, and the action you took.
• What you expected, and what happened instead.
• The exact message you saw, copied rather than paraphrased. Error strings identify causes; "it said there was an error" does not.
• Which brand it was, if you have more than one.
• When it happened, roughly, with your timezone.
• For a failed post: the platform, and the failure reason shown on the post.

A screenshot of the whole window, including the URL bar, is worth several paragraphs.

What not to send

Never send your password, and never send a social account's credentials. Nobody at TrendSuite will ask for either. We do not need them to investigate anything.

Feature requests

Send them to the same place, and say what you are trying to achieve rather than the feature you have in mind. The underlying goal is frequently something the product already does differently.

Elsewhere

• Guides: narrative walkthroughs of whole tasks
• Playbooks: strategy rather than product behaviour
• Changelog: what has changed recently