Contact
Every other page here answers one question. This one is for the question that is not on any of them.
Write to support@friendtrack.net.
Before you write, two things worth knowing
It is one mailbox, read by one person. There is no ticket number, no queue position and no automatic acknowledgement, so a reply takes as long as it takes and silence does not mean the mail was lost. That is also why the pages here are written the way they are: a link to a page that answers the question is a better answer than a retyped one, and it arrives immediately.
A lot of what you might want checked cannot be seen from this side. Where your friend’s phone is, why it stopped producing a Position, whether a notification was delivered to a particular handset — none of that is recorded anywhere anyone here can look up. If a page tells you that nobody can determine the cause from this side, that is the honest answer rather than a brush-off, and a mail will not improve on it.
What to include
The more of this you can say, the shorter the exchange:
| What | Why it helps |
|---|---|
| What you were trying to do | It is the difference between a guess and an answer |
| What happened instead, in your own words | Including the exact wording of anything on screen |
| Which phone, and which operating system version | Behaviour around location and notifications genuinely differs between them |
| Your app version | It is printed at the bottom of the Profile screen, and it is the only version signal the app has |
| When it happened | Roughly is fine — a date and an hour |
| The page you were reading, if you were reading one | Its address, so a wrong page can be fixed rather than argued about |
If you were signed in, say which phone number you signed in with. That number is the account, so without it there is nothing to look anything up against.
The things worth writing about most
Three kinds of problem where a mail genuinely changes the outcome, because they need something only this side can do:
- No sign-in code arrived. Delivery of a text message can fail for one country, one network or one number and look perfectly healthy from here. Your report is the only instrument that sees it, so it is worth sending even if you got in on the second attempt. The app’s own sign-in screen offers to write this mail for you and fills in most of it.
- Something about another person worries you. Use Report a concern in the app where you can, because a report made there arrives with the context attached. Write instead if you cannot reach the app.
- A map, a subscription or an account did not end up in the state you asked for. Whether a subscription was actually charged, whether a map is still listed in the catalog, whether a deletion completed — those are answerable from here and not from your phone.
What this page is not
It is not a phone line, and there is no phone number to publish. It is not a place to report a security problem in someone else’s product. And it is not a way to get a feature scheduled — it is read, and it is genuinely useful for that, but nothing here promises a roadmap in reply.