Requested And Shipped
Shipped changes as cards crediting the customers who asked, each footer stacking requester avatars beside the request count.
Shipped changes as cards crediting the customers who asked, each footer stacking requester avatars beside the request count.
Search blocks by description or jump to a page.
The source for every Marketing block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Requested and Shipped is the changelog that credits the askers. Four shipped changes run as cards, each with a date, title, and one sentence on the outcome, then a footer of requester avatars beside the count of teams who asked. A closing line points anyone with their own idea at the request board, so the section reads as a loop rather than a broadcast.
The entries are one array of date, title, text, request count, and a short list of requesters drawn from the shared avatars module. Write the sentences as the thing users can now do, and keep the request counts believable and uneven, identical numbers across cards read as invented. Three faces per card is enough to signal a crowd without crowding the footer.
Reach for this block when your roadmap is genuinely customer led and you want proof of it. Naming the people who asked turns a feature list into evidence that requests get built, the strongest reason a prospect has to leave one. It complements changelog-list-dated, which tells the same story without the social proof, and sits well beside testimonials that voice the outcome.
A natural flow around it on a Marketing Pro page:
Before
After
One strong use is the four most requested features you shipped. Other credited lists:
Tip: only show faces you have permission to show, the block reads as a promise kept, so the credit has to be real.