Menu
Help centre

Write a support ticket that is easier to investigate

A useful ticket explains the task, the result you expected and the result you actually saw. Specific evidence helps the team reproduce the problem without guessing.

Before you start

Find the page address, approximate time and the record reference if relevant. Remove credentials and unnecessary personal information from any screenshot.

Follow these steps

  1. Open the support request form.
  2. Use a subject that names the task and problem, such as Invoice filter returns no matches.
  3. Describe the steps in order and include the exact visible error.
  4. Explain whether the issue affects one record or several and mention your browser/device.
  5. Submit once and keep the reference and any verification instructions shown.

Check the result

The form should show a success result or field errors. Follow the support channel instructions; a ticket does not itself change your ERP records.

If you get stuck

If submission fails, note the error and preserve your description before retrying. Avoid sending duplicate requests with different details for the same problem.

One thing to remember

Never include API keys, passwords, recovery codes or full payment details. There is no guaranteed response-time promise in this guide. Urgency should be explained through its actual business impact.

Keep going

Still need a hand?

Tell us what you tried, what you expected and what happened. Keep passwords, API keys and private customer information out of your message.

Open a support ticket. Visitors without a workspace can contact us.

Still stuck?

Before contacting support:

  1. Confirm the workspace, record number, date range and status.
  2. Check your role permissions and the source document.
  3. Refresh once and search for the record before repeating a submission.
  4. Check the relevant guide for the next action; do not force a match, posting or approval.

If you still need help, include the page address, exact message, time, expected result and checks already completed. Never send passwords, API keys, payment-card details or provider secrets.

Was this article helpful?