Contact support
Reach a person at Hailo from inside the app or by email, and send the few details that get your problem solved in one reply.
There are two ways to reach us, and one of them is better than the other for almost everything.
The Feedback tile, from inside Hailo
Use this first. It arrives with the page you were on and, if you want, a picture of your screen already attached.
- Click Feedback in the sidebar footer. It sits above Settings, in every wing, on every screen.
- A box titled What's on your mind? opens. The page you are on is shown as a small chip, so we know where you were without asking.
- Type your note. The placeholder reads "A bug, an idea, anything at all".
- Tick Screenshot of this page to attach what you are looking at. Or click the picture chip to pick an image file from your Mac; a small × removes it.
- Click the send button.
You see Sent to Hailo and "We read every note and reply within 24 hours." Click Done.
Attach the screenshot whenever anything looks wrong. It saves a round of questions and is usually the difference between one reply and four.
Replies come to the email address on your account.
| Limit | Value |
|---|---|
| Note length | 8,000 characters |
| Screenshot | Around 8 MB |
| Notes per hour | 12 |
Your note, the page you were on, any screenshot and your version number are emailed to us with your address as the reply-to. Every note is logged on Hailo's side as well, so nothing is lost if the email is slow.
The contact page, for anything with a file attached
The Feedback box takes images only. So when you need to send a log file, write to us from the contact page instead and attach the file to our reply. Use it too when Hailo will not open far enough to show the sidebar.
What to include
The more of this you put in the first message, the fewer replies it takes.
| When | What to include |
|---|---|
| Every time | Your studio name, and the email you sign in with |
| Every time | What you clicked, and what you expected to happen |
| Every time | The exact message on screen, quoted word for word. "It said something about a connection" is not enough to search for |
| Every time | Roughly when it happened, in your Mac's local time |
| A desktop problem | The diagnostic file launch.log |
| A Deliver problem | The gallery link, and whether you or the couple saw the problem |
| An Edit problem | The couple's name and the stage the run stopped at |
| A payment problem | The invoice number and which payment rail was used |
You do not need to quote your version number when you use the Feedback tile: Hailo sends it. By email, include it. Click More at the bottom of the sidebar and read the last line, Version v1.2.140.
Attach a diagnostic file
For a problem with the Mac app, support asks you to attach launch.log. Logs and diagnostics has the Finder steps for finding it and attaching it to an email. If support needs a different file, they name it in their reply.
What not to send
Never send your password, a recovery code, a card number or a client's card details. Nobody at Hailo will ever ask you for any of them, and a message that contains one should be deleted rather than forwarded.
A diagnostic file contains your email address and the names of the folders you pointed Hailo at. It never contains your password or your footage.
If you think someone else has your password, change it yourself first, then write in.
Before you write
A few problems have a fix you can do faster than we can reply.
- Edit won't open or shows Reconnecting to the editor
- An analysis paused, stopped or failed
- An update failed
- Email isn't sending
- The couple can't open their gallery
If it didn't work
"Couldn't send. Try again". The note did not reach Hailo. Check your connection and send again. If it keeps failing, send the same text from the contact page.
"That file couldn't be read as an image". Pick a PNG or JPG. Screenshots taken by macOS are fine.
The send button is greyed out. The note is empty. Type something first.
You cannot open Hailo at all. Write to us from the contact page with your studio name, then attach launch.log to our reply.