The dark Feedback button in the bottom-right corner of every page sends a note straight to the team building the back office. Use it whenever something is broken, confusing, could be better, or says the wrong thing. No report is too small.
When to use this
- Something didn't do what you expected.
- You have an idea that would save time.
- You're not sure how to do something, and this Help center didn't answer it.
- A word, label or sentence should say something else.
Send feedback
- Go to the page the feedback is about, so it's on screen.
- Select Feedback.
- Choose what kind it is: Bug, Idea, Question or Content/wording.
- For a bug, say how much it gets in the way (see below).
- Describe it. For a bug: what you did, what happened, and what you expected. A sentence or two is plenty.
- Optionally, select Include a screenshot of this page. You'll see exactly what will be sent; select Remove if you change your mind.
- Add your name and, the first time only, the tester code.
- Select Send feedback.
The panel adds the page address, your window size, your browser and the time on its own.
The tester code
The tester code is a short code the team gives each tester. It stops strangers from sending feedback into the team's tracker. You type it once; your browser remembers it, along with your name.
If you're told "That code isn't right", check it with the team and type it again. If you don't have a code, ask the person who invited you to test.
How much it gets in the way
| Choice | Means |
|---|---|
| Blocking | I can't do my job. |
| Annoying | There's a workaround. |
| Minor | Small or cosmetic. |
Be honest rather than generous: the team fixes Blocking items first.
Follow your feedback
After sending, you'll see Feedback #N is in; that number is how the team refers to it. The Feedback page (under Help in the menu) shows where each item stands: Open, In progress, Fixed or Closed. Mine shows only what you've sent from this browser.
Good to know
- Practice data only. Don't type real names, children, phone numbers or other personal details, and check the screenshot preview before you send it.
- If the panel says Feedback isn't set up yet, this copy of the back office isn't connected to the team's tracker. Tell the team directly.
Top tips
- Send it from the page where it happened, straight away: the page address and screenshot save a paragraph of explanation.
- One thing per report. Two problems in one note means one of them gets forgotten.
- For wording, write the words you'd use. "Close out the offering" is more useful than "this is confusing".
Troubleshooting
"That code isn't right." The tester code was mistyped or has changed. Ask the team for the current one.
The screenshot didn't attach. Screenshot storage may not be set up yet. Your note was still sent; describe what you saw instead.
Was this helpful?
Your answer helps us keep these guides clear and up to date.