Criteria on purchases (amount, count, date of last purchase), town or address, customer type, gender or amount due, recounted every time they are used.
Your best customers of the year, those who have not returned in three months, those in one town.
WhatsApp replies land in a shared inbox, where several people can answer.
An invalid number or a customer not on WhatsApp shows in the campaign’s failure list, with its reason.
What you will see when you open it
Screenshots taken on our demo shop, with sample data. Tap a screen to enlarge it.
A campaign
Its channel, its recipients, what went out and what failed, its estimated cost in credits, and the message as the customer will receive it.
- 1The channel and the campaign’s state
- 2Launch when everything is ready
- 3The segment’s recipients
- 4The estimated cost, in credits
- 5The message as the customer will receive it
On a phone
The campaign can be followed and launched from a phone too.
- 1The campaign’s channel
- 2The segment’s recipients
- 3The estimated cost, in credits
- 4Launch when everything is ready
Templates
Reusable messages for WhatsApp, SMS and email, with their variables. Biddew can write one from what you describe to it.
- 1WhatsApp, SMS and email
- 2Described to Biddew, written for you
- 3Variables: the name, the product
Segments
An audience built from filters on your customers, spelt out plainly, with the number of people it reaches today.
- 1A segment, built from filters
- 2The filter, spelt out
- 3Today’s audience, by channel
How it works
Pick a step to see what it sets off along the way.
-
Segment recounted every time
-
at the same time
- WhatsApp your number
- SMS
-
Scheduled send paced, never at night
-
either
- Sent one credit used
- Failed with its reason, to retry
-
WhatsApp reply in the shared inbox
-
01
Build the segment
From what you already know about your customers, no export or spreadsheet.
-
02
Write it and preview
One message per channel, with its variables, seen as the customer will receive it.
-
03
Send it and reply
The campaign goes out, and WhatsApp replies come into the shared inbox.
What you can do with it
A template written once per channel, personalised with the customer’s name, the amount they owe or the products and price of the offer.
WhatsApp, SMS and email from the same screen, one message per channel, and a preview worked out for a real customer before sending. Biddew can fill the campaign in from a sentence.
A send date, or right away. On WhatsApp, messages go out at a reasonable pace, never at night, to spare your number.
Customers’ WhatsApp conversations in one place, assignable to a team member.
Each campaign counts its successful, pending and failed sends per channel. Every failure keeps its reason, and one button retries the failures.
What the module includes
- Campaign wizard
- Message templates
- Audience segments
- Dynamic variables
- WhatsApp, SMS and email
- Drafts and preview before sending
- Reminders that stop once paid
- Internal circulars
WhatsApp first, and a calendar that matters
In this market a WhatsApp message gets read and an email often does not. SMS reaches every phone, even without internet: customers not on WhatsApp come out in the failures, to be reached by SMS. And the local commercial calendar (Tabaski, Ramadan, back-to-school, payday week) weighs more than any segmentation: the same campaign sent in the wrong week will do nothing, hence scheduled sending.
Common questions
Do I need to link a WhatsApp number?
Yes to send on WhatsApp: from settings, you link your number as a connected device, by scanning a QR code or entering a pairing code. SMS and email work without that step.
Can I see who read it?
No. Tracking shows what is sent, pending or failed, with the reason for each failure. Delivery and read status are not tracked.
How are opt-outs handled?
A customer can be excluded from campaigns from their record, and the exclusion applies across all channels, checked when each campaign launches. There is no STOP keyword or unsubscribe link: also respect WhatsApp’s own rules on unsolicited messages.
Works with
The modules talk to each other: what happens here shows up there, with nothing typed twice.