Guests are going to ask what you want anyway. Answering «whatever you like» sends five people to buy five things you will quietly give away. The awkwardness is not in the request itself — it is in how it is worded.
The three-part formula
- Remove the obligation. «Gifts are absolutely not expected» has to come first, or everything after it reads as an invoice.
- Name the goal. «We are saving for a trip» turns a request into a shared plan. A vague request feels like begging; a specific one feels like a project.
- Give the details last. The link or card number goes at the end, in one line, without repetition.
What never to do
- Name a figure. The moment there is a number, there is a price of admission.
- Remind people who have not transferred.
- Publish a list of who sent what.
- Be visibly disappointed in someone who brought an object.
If several people want to combine
When guests decide to pool into one larger gift, someone has to keep the running total. A shared group by link does that without a spreadsheet — in DeliBabki the organiser logs contributions and sees the total, and only the total goes back to the chat.
Frequently asked questions
Is it acceptable to ask?
Yes, when it answers a question guests are already asking and does not set a price.
How do you avoid sounding pushy?
Remove the obligation, name the goal, give details last, and skip the figure.
What about wedding invitations?
Keep money out of the invitation itself; put the request somewhere separate and soft.
What if someone brings an object?
Accept it warmly. The request was a hint, not a rule.
If people are pooling together
One group by link keeps the running total without a spreadsheet.
Create a group