What is the difference between a group ecard and a group greeting card?

A group ecard usually means a single-page board layout with post-it style signatures that holds many contributors gracefully (twenty or thirty without anyone feeling lost). A group greeting card more often means the multi-page 3D-flip format, where each signer gets their own card-style page. Use the board layout for groups of seven or more, the multi-page format for smaller inner-circle groups of four to six. Pages stop scaling somewhere around six contributors, and a multi-page card with empty pages reads worse than a board layout that absorbs whoever shows up.

How long does it take to create a group ecard?

Setup is about ten minutes: pick the format, pick a cover, write your own first signed message (this is the part that takes the most time and matters the most), turn on the PIN, and schedule the delivery. The collection phase runs three to seven days on its own, with one reminder DM two days before delivery. Active time across the whole process is maybe fifteen minutes; the rest of the week the platform does the work.

Do I need to write my own message before sharing the link?

Yes. The first message on the card sets the implicit standard for every other signer. A blank card invites three-word filler from the first three people, and the rest match that floor. A card with one real two-to-four sentence first message that names a specific moment invites the same kind of specificity in response. The single line at the top is doing more work than any other element on the page; do not skip it.

What if some people I invite never sign the group ecard?

Expect about a third of invited signers not to sign, even after one reminder. Send one individual DM to each non-signer two days before delivery, then stop. Do not sign on their behalf; a fake first message from somebody who did not write it reads off and can be embarrassing if discovered. A card with fifteen real specific messages lands better than a card with thirty bland ones, and the recipient almost never notices which specific people did not sign.

How do I keep the recipient from seeing the group ecard before delivery?

Use a platform with a PIN-protected delivery. The share link only grants 'add a message' access; the assembled, signed card cannot be opened until the PIN unlocks at the delivery moment. Even if the link gets forwarded to the recipient by accident, the surprise survives. As a backup, scroll the channel member list before sending the invite and confirm the recipient is not in the chat.

When should I schedule the group ecard to deliver?

Morning of the recipient day in their time zone, not yours. For workplace ecards, send to the personal email rather than the work one (work email often gets disabled, especially for farewell cards on a last day). Avoid Friday afternoon deliveries for anything that is not anchored to that specific Friday; Friday afternoon deliveries get opened Monday morning, three days late. Tuesday morning is the safe default for an ecard not tied to a calendar date.

All articles

Group Cards

How to Create a Group Ecard (Step by Step)

Tom Bennett

May 26, 2026

The first real decision in a group ecard is not the cover. It is the question of whether what you are building is actually a group ecard, or whether it is a multi-page greeting card with a single signer, or whether it is the wrong format entirely and the situation calls for one solo note from one person. I have gotten this call wrong more than once. The most embarrassing example: a promotion celebration for an engineering manager named Devon who I had worked with on and off for about three years. I built it as a multi-page greeting card with the page-flip animation because I thought the format looked thoughtful. The card invite went out on a Tuesday afternoon from my hotel room in Austin (I was at a conference; the wifi kept dropping, which is its own problem). Nineteen people ended up wanting to sign. By the fourth page the format had stopped working; people started doubling up on the same page because they did not realize they could add another, and the final card delivered with two pages of dense signatures and four nearly-empty ones. Devon was polite about it. Margaux, who had organized roughly fifty of these in her actual day job and was the person who quietly told me afterward what I had done wrong, was less polite. This guide is the version of that conversation I wish I had read before clicking the wrong template.

Start a group card in 30 seconds

Free. No signup needed.

Jump to section6 sections

Group ecard vs. group greeting card: the format question first

Most articles on how to create a group ecard treat 'group ecard' as a single fixed thing, then walk you through clicking through a template. The format is not fixed. On most platforms (Reco included) the same product offers two genuinely different layouts under the same umbrella, and the choice between them is the most important decision you make. A board layout is a single page with post-it style signatures that holds twenty or thirty contributors without anyone feeling lost. A multi-page greeting card is a 3D-flip format with separate pages, where each signer gets their own card-style page. They look like the same product. They are not the same product.

After the Devon situation and three or four others like it, here is the rule that has actually held up: if the head count is six or under and the group is genuinely close (four siblings, a tight friend circle, the inner team), the multi-page greeting card format reads more thoughtfully because each person gets their own full page. If the head count is seven or above, or if you are not sure exactly how many people will sign because the invite is going to a wider channel, default to the board layout. Pages stop scaling somewhere around six contributors, and a multi-page card with two crowded pages and four empty ones is visibly worse than a board layout that absorbs whatever number of signers shows up.

A useful shortcut: ask yourself who the card is for. If the answer is 'the family' or 'the close team' (four to six people you can name without thinking), it is probably a greeting card. If the answer is 'the office' or 'the channel' or 'everyone who worked with her', it is probably a board. The board format is the one most people mean when they say 'group ecard'. It is also the one most platforms quietly bury under a different label, which is part of why people end up with the wrong format and the empty pages.

The invite: draft the first message yourself, pick the right chat, be specific

Here is the move I see new organizers skip, and I have skipped it myself plenty of times. They build the card, pick a cover, and immediately share the link. The card opens with nothing on it. The first three people who click see a page that is blank. They each write three words because that is what a blank page is asking for. By the time the fourth person opens it, the implicit register of the card has been set to 'three-word filler', and the rest of the signers match the floor those first three set.

The fix is straightforward and almost never followed. Before you share the link with anyone, sign the card yourself. Two to four sentences. Name a real moment. The single line at the top of the card is doing more work than any other element on the page, because it is silently telling every signer how much effort the room is expecting. A first message that says 'so happy for you, Devon!' invites lines that say the same. A first message that names a specific Wednesday when Devon stayed an extra ninety minutes to walk a junior engineer through a deploy script invites the same kind of specificity in response.

I once watched a group ecard for a senior designer get sixteen signatures inside three hours because the organizer had written a beautiful first message about a specific code review the recipient had walked her through two years earlier; the next sixteen people read that and felt obligated to bring something real. I would rather organize a group ecard with seven signers and seven real messages than one with twenty-five signers and twenty-five lines that say almost nothing. Do not skip this step. Do not promise yourself you will add yours later; later, after twelve other people have signed with three words each, your three-paragraph message is going to look weird and self-promotional rather than like the example it was supposed to be.

A small confession before the next part: I have broken this rule on purpose, and it has cost me twice. Both times I drafted a first message that was, in hindsight, too long and too good. The next four signers wrote one-line additions to mine ('what she said') instead of writing their own. Length-match is real. Two to four sentences is the right ceiling; a five-paragraph essay at the top is its own kind of empty page.

Now the invite itself. The recruitment step is where most group ecards quietly start dying. The typical organizer writes a generic note ('hey team, signing a card for Devon, please add a message!'), posts it in a generic place (a channel nobody opens regularly), and is then surprised when the signature count plateaus at four people. A few rules I have learned the slow way:

Post in the chat the group already uses. Slack channel for the team, WhatsApp thread for the friend circle, group iMessage for the family. A card needs to land in a thread people open without thinking about it, because the signing happens across three or four days and any thread that requires a separate trip to remember is a thread people will forget. Do not start a new channel for the card. And please do not DM the link to fourteen people one by one; that takes you forty minutes and gets the same response rate as a single channel post.
Ask for something specific. The word doing the work in the invite is 'specific'.
Name the deadline. Not 'soon'. Not 'this week'. A day and a time. 'I am scheduling delivery for Friday morning, please sign by Thursday night.' Without it, the message scrolls off the channel by Wednesday and the late signers never show up.
Say what the card is for, in the same sentence as the link, in five words or fewer. 'Card for Devon's promotion.' Not 'hey team, as you may have heard, Devon recently received some wonderful news regarding her career trajectory, and I thought it would be nice if we…'. The shorter the framing, the more people read it.

Before you hit send on the invite, scroll the channel member list. Make sure the recipient is not in the chat. I have made the wrong call here once, and the recipient was kind about it, but the surprise was effectively gone by the time the card delivered. The PIN mechanic (covered below) is the backstop for this, but the cleaner play is to never invite into a channel the recipient is in.

The thirty-percent rule: who will never sign

This is the section nobody writes plainly, and which I think is the most important thing for a new organizer to internalize: about a third of the people you invite will not sign the card, even after one reminder, even with a clear ask, even with three days of runway. They are busy. They meant to and forgot. They did not feel close enough to the recipient to know what to write. They had a bad week. None of those reasons are fixable with a fourth nudge. The fixable parts are the friction of remembering a thread they have to come back to, and the blank page that greets them when they finally do; both of those are handled in the section above.

The thirty percent is a structural feature of group ecards, not a bug of the platform you chose or a failure of your invite. The pattern that works is: post the link day one, send one individual DM to each non-signer two days before delivery (with the link and one specific sentence), then stop. A third reminder turns the card into a chore for everyone, including yourself, and reads as low-grade nagging in a way that erodes the warmth you are trying to produce.

One thing I will ask you to never do, no matter how tempting it gets in the final hour: do not sign on behalf of somebody who never signed themselves. A fake first message from somebody who did not actually write it always reads slightly off, the absent person can find out and be quietly mortified, and the recipient sometimes notices that the line does not sound like the alleged sender. Take the participation rate you get. Fifteen specific real messages is a great group ecard. The four absent names are not what the recipient is going to remember a week later.

The PIN: the mechanic that actually protects the surprise

A group ecard, almost by definition, is built by people who are not the recipient, for the recipient, while the recipient is supposed to not know it exists yet. The whole format depends on a clean separation between the building phase (where the card lives at a private URL the signers can reach) and the delivery moment (where the recipient finally opens it as one event). Most platforms treat the surprise mechanic as an afterthought. In practice it is the thing that decides whether the card lands cleanly or as an awkward shared secret.

The mechanism most platforms hide two clicks deep is a PIN-protected delivery. With the PIN on, the share link only grants 'add a message' access; even somebody who clicks through cannot actually see the assembled, signed card until the PIN unlocks at the delivery moment. The recipient can be forwarded the link by accident, can stumble onto it in a scrollback, can be added to the wrong thread, and the surprise still survives. Without the PIN, the share link is the card, and any leak is a ruined surprise. Reco's group ecards with multiple signers turns PIN-protected delivery on by default, which is the only sensible default for a format whose entire purpose is to be a surprise.

I learned to do this only after a couple of avoidable mistakes. The PIN lets you stop worrying about exactly which channel members might see the half-built card. It also lets you safely preview the card in front of the recipient without revealing it, useful in the awkward case where you are using your laptop in a shared workspace and need to add one more signer before the deadline.

After the invite: scheduling, delivery channel, and whether the cover actually matters

Set the delivery time before you share the invite, not after. The card keeps collecting signatures right up to the scheduled moment, so an invite sent five days early still picks up notes the night before. The feature that matters here is that the deadline you announce in the invite ('please sign by Thursday night') and the actual delivery moment ('Friday at 9am their time') can be different. The two-day buffer is what lets the late signers show up without scrambling.

The delivery moment itself is worth thinking about. For most workplace ecards, the right answer is the morning of the recipient day in their time zone, not yours. The recipient's evening is wrong because the card lands when they are already winding down. Their late afternoon is wrong because they are in meetings. Their morning gives them ten quiet minutes to actually read it. For farewell cards specifically, I deliver to the personal email rather than the work one, because the work email frequently gets disabled at some point during the last day and you do not want the card landing in a dead inbox. The piece on how to make a group card everyone signs covers the time-zone and delivery-channel choice in more detail.

One unglamorous note: do not deliver the card on a Friday afternoon, ever, unless the recipient is specifically leaving on that Friday. A Friday afternoon delivery for a birthday or a milestone gets opened on Monday morning, three days late, after the moment has passed and the cake is gone. Tuesday morning is the safest default for an ecard that is not anchored to a specific calendar date.

On the cover, briefly, because most guides oversell this part. Newer platforms can generate the cover image with AI from a short prompt, and that is genuinely useful for ecards that do not fit the stock-art categories: a thank-you for the team that helped you move apartments, a celebration for a coworker's first marathon, anything where the seventh balloon graphic from the template library feels off. A thoughtful cover signals to the first three signers that the organizer cared, and that signal propagates into what they write. Honestly, though: I would skip the AI cover for a standard coworker farewell. The people who would notice and appreciate a custom cover are not the same people who would actually open the link, and the time you spent prompting an AI image is better spent writing your own first message (covered above). The cover is the part of the card that gets one glance; the signatures are the part the recipient reads at 11pm two weeks later.

Turn it into a group ecard the recipient actually keeps

The version of this that works for almost any occasion is the group ecard built as a single coordinated send, not as a scattered patchwork of individual texts and a shared Google Doc. One person sets up the group card online with multiple signatures, picks the format (board for crowds, multi-page for small inner-circle groups), writes the first signed message, turns on the PIN, posts the link in the existing chat with a specific ask, sends one reminder, and schedules the delivery. The signatures collect themselves. The card delivers itself. You spend, total, maybe fifteen minutes across the week. (If you want the shortest path, you can create a card online and the first signed message is the longest part of the setup, which is also the most important part.)

For workplace farewells, a virtual farewell card in board layout is the default. For team birthdays and thank-you moments, the same board layout works; for a small family ecard of four to six signers, the multi-page greeting card format is the one I default to. If you want a longer reference on what to put in your own first signed message, the piece on how to sign a group card walks the signer side of the same question, and how to send an ecard covers the delivery-channel question (email vs. text vs. share link) in more detail than this piece does. If there is also a pooled gift involved, the piece on how to collect money for a group gift covers the amount and channel questions for that side of it.

One last thing, off-topic. The Austin hotel I was in when the Devon card went out had a small printed sign on the back of the bathroom door asking guests to reuse the towels. The sign had an illustration of a sea turtle on it, drawn in green marker, and a hand-lettered note from a kid named Eli, age seven, saying 'please save the turtles, they are very nice'. I did reuse the towel. I did not realize until I was on the plane home that there was a small enthusiastic checkmark sticker on the back of the door for any guest who participated, which I had not seen and therefore had not earned. I think about Eli's sea turtle sometimes when I am drafting an invite that I know is going to land in front of a lot of people who do not have to do anything. Most of them will not. A small handful will, with real warmth, for reasons that have nothing to do with the wording of the ask. The sticker is for the ones who did. There is no sticker for the organizer.

Frequently asked questions

What is the difference between a group ecard and a group greeting card?: A group ecard usually means a single-page board layout with post-it style signatures that holds many contributors gracefully (twenty or thirty without anyone feeling lost). A group greeting card more often means the multi-page 3D-flip format, where each signer gets their own card-style page. Use the board layout for groups of seven or more, the multi-page format for smaller inner-circle groups of four to six. Pages stop scaling somewhere around six contributors, and a multi-page card with empty pages reads worse than a board layout that absorbs whoever shows up.
How long does it take to create a group ecard?: Setup is about ten minutes: pick the format, pick a cover, write your own first signed message (this is the part that takes the most time and matters the most), turn on the PIN, and schedule the delivery. The collection phase runs three to seven days on its own, with one reminder DM two days before delivery. Active time across the whole process is maybe fifteen minutes; the rest of the week the platform does the work.
Do I need to write my own message before sharing the link?: Yes. The first message on the card sets the implicit standard for every other signer. A blank card invites three-word filler from the first three people, and the rest match that floor. A card with one real two-to-four sentence first message that names a specific moment invites the same kind of specificity in response. The single line at the top is doing more work than any other element on the page; do not skip it.
What if some people I invite never sign the group ecard?: Expect about a third of invited signers not to sign, even after one reminder. Send one individual DM to each non-signer two days before delivery, then stop. Do not sign on their behalf; a fake first message from somebody who did not write it reads off and can be embarrassing if discovered. A card with fifteen real specific messages lands better than a card with thirty bland ones, and the recipient almost never notices which specific people did not sign.
How do I keep the recipient from seeing the group ecard before delivery?: Use a platform with a PIN-protected delivery. The share link only grants 'add a message' access; the assembled, signed card cannot be opened until the PIN unlocks at the delivery moment. Even if the link gets forwarded to the recipient by accident, the surprise survives. As a backup, scroll the channel member list before sending the invite and confirm the recipient is not in the chat.
When should I schedule the group ecard to deliver?: Morning of the recipient day in their time zone, not yours. For workplace ecards, send to the personal email rather than the work one (work email often gets disabled, especially for farewell cards on a last day). Avoid Friday afternoon deliveries for anything that is not anchored to that specific Friday; Friday afternoon deliveries get opened Monday morning, three days late. Tuesday morning is the safe default for an ecard not tied to a calendar date.