When something looks wrong in a family app, there is usually something else waiting for your attention: dinner, a shopping trip, or a child asking where their shoes went. You can ask for help without spending the evening investigating the software.
A useful message tells support what you were trying to do and what happened. The template below gives you a place to record that, while keeping unnecessary family details out of the conversation.
Start with the official support route
The official Nestify support page lists hello@nestifyapp.org and asks for your device model and app version.
Nestie is the assistant in Nestify. If you arrived through the assistant’s name, you are looking for help with the Nestify product; our introduction to Nestie explains that relationship.
Start your message by saying where the issue happened: in the phone app, on a tablet, or on a Family Hub. If more than one screen is involved, describe what you saw on each. “The item looks different on my phone and the other screen” gives support something concrete to ask about. “Sync is broken” is a diagnosis you may not have enough information to make.
Choose one issue for the message and give it a recognizable subject, such as “Shopping list item appears twice on my phone.” Then describe the actual sequence you remember. You do not have to repeat a calendar change, send another invitation, or add more list items just to prove the problem happens again.
If you already tried something, include it briefly. If you did nothing after noticing the issue, that is useful context too. It is fine to say that you cannot remember the exact order of two taps.
You can also explain the question you need answered: “Should I leave these two items as they are while you look into this?” That describes your immediate uncertainty without assuming a particular cause or fix.
Copy a short report that shows what happened
Separate what you wanted from what you observed. Mozilla’s report-writing guidance uses steps, expected results and actual results as distinct parts of a description. The following template adapts that idea into an ordinary support message.
Copy it into your email and fill in what you know:
- Subject: A short description of the issue.
- Where it happened: Phone app, tablet app or Family Hub.
- Device model:
- Installed Nestify app version, if known:
- Operating-system version, if known:
- When: Date, approximate time and time zone.
- What I wanted to do:
- What I did: Two or three short steps, in order.
- What I expected:
- What I actually saw: Include relevant error wording, with private details removed.
- What happened afterward: Any further observation during ordinary use, or “I have not tried again.”
- My question: What I need help understanding or doing next.
An operating-system version and an app version are different fields. For iPhone or iPad, Apple explains how to find the iOS or iPadOS version in Settings → General → About. Google’s Android version guide points to Settings → About phone or About tablet → Android version.
If those labels do not match your device, leave the field unknown for now. The newest version shown in an app store is not necessarily the one installed on your device. Copy a version you can identify rather than guessing, and avoid attaching the entire device-information screen.
Here is a fictional example of the description, not a report of an observed Nestify bug:
On September 24, 2026, around 6:15 p.m. Pacific time, I opened our shopping list on my phone. I entered “apples” once and returned to the list. I expected one item named “apples.” I saw two rows with that name. I have not added or deleted anything since. I do not know whether another person was editing the list. Should I leave both rows in place while you investigate?
The example gives an observation and acknowledges what the person does not know. It does not require a theory about the cause. Use your own actual sequence, and mark approximate times as approximate.
Share only what helps, and keep the family plan moving
An attachment is optional. A short description may explain the issue without showing your family’s calendar, conversations or account screen.
If you choose to attach a screenshot, include only the area needed to show the problem. Crop out unrelated entries and check for children’s names, faces, contact details, home or school addresses, and private notes. Leave passwords, verification codes and recovery codes out of the message and every attachment.
Save the edited image, then open that saved copy and inspect it before attaching it. Check which file you actually selected in the email. If you cannot confidently exclude private information, send a text description instead. A marker drawn over text is not a reason to assume the information has been removed.
You can replace identifying words in a written description with neutral labels such as “family member” or “school event.” Mention that you changed those labels, so support can distinguish the illustration from the exact text shown in the app. Keep any useful error wording intact where you can do so without including private information.
While waiting, make the immediate family arrangement directly with the adult involved. If the shopping list is uncertain, agree on a short paper list with the person going to the store. If a calendar time is unclear, confirm the time together and record it in the place you are both using for that plan.
Sending a support message does not itself change those arrangements. Keep a copy of your report, add a brief factual update if something changes, and let your family continue with the plan you have agreed on.