A personalised WhatsApp image is artwork made for one specific recipient, showing their name or booking details as part of the picture. People forward a greeting when their own name is part of the picture, and scroll past the same words sent as plain text. Design the template one time and each copy completes itself.
Included in the platform licence. Not a paid add-on.
The short version
Personalised WhatsApp image in brief
A personalised WhatsApp image from WappBlaster starts as one design with placeholders, and at send time the WhatsApp marketing platform renders a separate copy for each recipient, filling in their name, order, ticket or other contact data. The differentiator is where those images can be produced: in bulk campaigns, inside bot flows, or from data arriving on a webhook, so an event booking can generate its own ticket the moment it is made and deliver it in chat. The same engine creates PDFs, which suits invoices, certificates and travel itineraries. There are 4 setup steps: design the template, map each placeholder to a contact field or webhook value, choose the delivery route, and test with real data. Long names and unusual characters are where layouts break, and missing fields show up inside the picture itself, so clean the data before a large send. When every recipient would see an identical picture, a standard image template is the simpler choice.
A personalised WhatsApp image is generated separately for each recipient from one design, with their name, order, ticket or other details filled in at send time.
WappBlaster renders dynamic images and PDFs in bulk campaigns, inside bot flows or from webhook data, including per-booking tickets delivered on WhatsApp.
Festival artwork carrying the customer's name gets passed on.
Each attendee's ticket sits in a chat they check daily.
A whole course batch gets individual certificates at once.
Every account holder gets their own document without manual exports.
Dynamic experiences generate a personalised image or PDF for each recipient from a single design template, substituting their name, order, ticket or other data at send time. WappBlaster creates dynamic image and PDF experiences, sends them in bulk campaigns, uses them inside bot flows, generates images from webhook data, and produces per-customer tickets delivered over WhatsApp.
Trusted by 3,500+ businesses
Some of the businesses using WappBlaster products every day
Capabilities
Everything here is documented and shipping today, not on a roadmap.
Design once with placeholders and get a unique rendered image per contact.
Personalised artwork at campaign scale, not one at a time.
Generate and send the image mid-conversation, once the bot knows what it needs.
Per-recipient documents: invoices, certificates, statements, itineraries.
Create a ticket per booking and deliver it over WhatsApp, where people can actually find it later.
Your system posts the data, the image is generated and sent.
How it works
Place the fields that vary: name, code, date, seat.
Point each placeholder at a contact field or webhook value.
A campaign, a bot flow, or a webhook trigger.
Long names and unusual characters are where these break.
Where it earns its keep
Event tickets
Each attendee gets their own ticket in the chat they check every day.
Festival greetings
Artwork with the customer’s name in it, the kind people pass on.
Certificates
Completion certificates for courses and training, produced for a whole batch at once.
Invoices and statements
Every customer receives an individual PDF on a set schedule.
Loyalty cards
A card carrying the customer’s own points balance.
Booking confirmations
A visual confirmation with the details rendered in.
Ships in these products
Document-heavy senders also read bulk sending with attachments, best practice for payslips on WhatsApp and about loyalty points shown in chat.
| Feature | What it does | Best for |
|---|---|---|
| Dynamic image | Renders a unique picture per contact | Greetings and offers |
| Dynamic PDF | Builds a document per recipient | Invoices and certificates |
| Ticket generation | Creates a ticket per booking | Events |
| Webhook generation | Renders from data your system posts | Passes and confirmations |
Straight answers about Personalised WhatsApp image.
It is a picture built separately for each person from a shared design, where details such as their name are drawn into the graphic itself instead of typed into the caption. No two recipients get the same file.
Link to this answerYes. A bulk campaign can carry dynamic images, and while it sends, WappBlaster renders a fresh image for each contact in turn.
Link to this answerYes. Post the data to a webhook and the image is generated and sent, which is how per-booking tickets and passes are usually produced.
Link to this answerImage and PDF rendering is part of the platform licence, so personalising each copy adds nothing to the fee. Meta still bills each delivered message at its normal rate, which reaches you without markup.
Link to this answerYes. You design a template with placeholders once, map each to a contact field or webhook value, and it renders a unique image or PDF per recipient in campaigns, bot flows or webhook sends.
Link to this answerYes. Dynamic PDFs build a separate document for every recipient, which suits invoices, statements, certificates and itineraries sent on a schedule.
Link to this answerGreeting artwork with the customer's name rendered into it, since people share a picture that carries their own name. Test it with long names and unusual characters before the full send.
Link to this answerYes. A ticket is created for each booking and delivered on WhatsApp, where attendees can find it again easily on the day.
Link to this answerWhatever you map: typical placeholders are name, code, date and seat, filled from contact fields or values your system posts.
Link to this answerYes. Once the bot has collected what it needs, it can generate the image and send it mid-conversation.
Link to this answerStill not answered?
Ask a real person. We reply on WhatsApp, usually within the hour.
Engagement and retention
Related features
Same licence, same login. These work together out of the box.
A short call on your real list and your real templates. No card, no sandbox.