What to say after someone supports your work

A thank-you and a progress update do different jobs. A thank-you lets someone know you appreciate their help. A progress update tells them what happened with the work they chose to support. You can send the first when a contribution is confirmed and the second when you have something to report. There is no need to invent a milestone so the first message sounds more impressive.

Start with what you actually know. Check what the person helped with, which details they agreed to share and whether you have an appropriate way to contact them. The message can be short when it says something the reader recognises.

Say thank you while the request is still familiar

Use a channel the person expects. If you were already talking about the project and they told you they contributed, a reply in the same conversation may be enough. If the contribution is anonymous or you do not have permission to contact them, thank people together in a public update. Do not try to identify someone who chose to keep their name off the page.

This is a fill-in prompt for a private acknowledgement. Use it once you can confirm what you are thanking the person for.

Thank you for helping with [the actual purpose]. I appreciate [what you can say sincerely about their help]. I’ll share [the next update you can commit to] when I have news.

It is fine to leave the last sentence out. You can appreciate the support without knowing a completion date. If someone helped by reviewing a draft, sharing the link or introducing you to a collaborator, thank them for that action. There is no need to imply they gave money. Specific thanks show that you saw what they did.

Make a short video if it suits the page

atpesa lets page owners add an optional thank-you video link for people who have completed a contribution. If you use it, keep the video short and speak directly to the person watching. Start with the thank-you. Then name the work and the part their support helps with. Keep the language current enough that it still makes sense if someone watches later.

Record somewhere you can be heard. Watch the entire clip before you add the link and check that nothing private appears in the frame or audio. If the hosting service gives you privacy settings, use a link that can play for visitors without asking them to sign in. Verify that on another device. Keep a written thank-you for people who cannot play the video or prefer to read. If you revise the request, check the video as well as the text.

Avoid addressing a viewer by name or mentioning their amount in a video that everyone will see. You can thank the person who has just contributed without pretending to know who they are. If a group appears in the video, get their agreement before publishing and confirm that the finished clip represents them accurately.

Share a milestone with evidence people can see

Read your original request before writing the update. What did you tell people their support would help with? Start there. Report what is complete, what is still happening and what the reader can see if they want to check. A link to public work or a photo you have permission to share can do that job. A private record may help you get your facts right, but you do not need to publish it.

Use this structure and fill it in with a confirmed event. Leave out the link or image if you do not have one you can share.

Since the last update, [what happened and when]. Your support helped with [the part it actually helped with]. Here’s [something readers can see or where the next update will appear]. Thank you for [the help you received].

If the work was possible because of several people or sources of help, describe each one accurately. You can say that contributions helped without claiming they covered the whole thing. Keep a copy of the dates and facts you use. When someone asks a question later, you will have the same account in front of you.

Explain what changed when the plan moves

Write the update once you know enough to be useful. Name the original plan, the change and what you are doing about it. If a new date is pending, say it is pending. If the work cannot go ahead, say whether you have stopped asking for support and where contributors can send a question. Give a next update date only if you can keep it.

If a reader has an individual payment question, take that out of the public thread. Use the site’s support route and share only what is needed to identify the record. Before making a promise about a refund or a new use for the money, check which options actually apply to the request. It is better to tell someone you are checking than to promise an outcome you cannot deliver.

Keep the original wording where you can refer to it, and update the live page so a new visitor sees the current purpose. If an earlier message is still likely to be forwarded, put a short explanation high on the destination page. That helps both new readers and people who already contributed understand why it changed.

Keep a record of what you promised to share

After sending a thank-you, make a short note if you promised a later update. Record the milestone and where you said it would appear. There is no need to record the supporter’s name if the update is for everyone. When you publish it, check any link from a signed-out phone. A thank-you that promises a public result should lead to a page the recipient can actually open.

If you are taking a break, decide whether there is anything people need to know before you go quiet. A note that says the work is paused and explains when you can say more can be more useful than posting a general update that leaves the original question unanswered.

Thank people without turning the note into another ask

A public thank-you can be the last message for a project. People do not owe you a second contribution just because they gave the first. If you start a separate request later, make the change explicit and give people time to decide. Use the places where they already expect to hear from you. Do not add someone to a mailing list because they made a contribution.

Before sharing a list of names, ask each person how they want to be credited. Keep the option of receiving no public credit. Check screenshots for names, account information, amounts and references before publishing any image. When you can show the work itself, use that instead of a transaction screen.

Decide when to check in again. A dated milestone works if there is a sensible one. A final note works if the project is done. If the work is ongoing, make it part of an update people already look for. A thank-you feels personal when it is about real help and real work. It does not need a large audience or a polished speech.