Appearance
Contact support
Email
Before you email
Two places answer most questions faster than we can:
- Troubleshooting covers the problems that actually come up, with the usual cause first.
- FAQ covers the questions that come up before you have a problem.
- The status page at printersfriend.com/status shows whether the platform itself is degraded, with a machine-readable version at
/status.jsonif you want it in your own monitoring.
What to include
Four things, and most tickets are resolved on the first reply:
- Which screen. The path is ideal, for example
/app/quotes/482. - What you expected to happen.
- What actually happened, with the exact wording of any error.
- The record number. The order, quote or invoice number, or the customer name.
If it is a pricing question, say what the number should have been and what it came out as. If it is an email or SMS question, include the recipient address or number.
What we will ask for if you do not include it
- Your workspace name.
- Whether it happens for every user or one user.
- Whether it happens for every record or one record.
- When it last worked.
Things support can do that you cannot self-serve
| Request | Notes |
|---|---|
| Change your tax rate or label | Your region derives from your billing currency. Send the correct rate and label |
| Enable portal access for a customer contact | There is no self-serve invite screen today |
| A data processing agreement | For GDPR, UK GDPR or APP compliance |
| Recover something deleted | Say what and roughly when. Sooner is much better |
Urgent, and not urgent
Urgent is anything stopping you shipping or taking money: you cannot log in, invoices will not issue, payments are not recording. Say so in the subject line.
Not urgent, but worth sending: a number that looks wrong, a wording change you want, a feature you keep wishing existed. The last one is genuinely useful. Most of what gets built next comes from shops describing a specific job that was harder than it should have been.