Campaigns Tools:
Ask about any broadcast you have sent, how it performed, who it reached, and why it did what it did.
"How did last week's Diwali broadcast do?"
"Which campaign had the best ROI this month?"
"Compare my last three WhatsApp broadcasts."
"Why did that campaign reach fewer people than I expected?"
"What template and audience did this campaign use?"
"Am I running campaigns well?"
Performance comes back as three funnels - deliverability (sent, delivered, failed, suppressed, bounce rate and the reasons behind failures), engagement (read, replied, link clicks, opt-outs) and sales (orders, revenue, ROI, cost, add-to-carts, abandoned checkouts). Only the metrics that mean something on that channel are shown.
The last question returns a score out of 100 grading your last 30 days of broadcasts across sixteen practices drip sends, retries, smart retry, frequency capping, fallbacks, quiet hours, personalisation, best-time windows, sender warm-up, segment use and more with the biggest gaps ranked first, so you know what to fix next.
Tool | What it does |
| Every broadcast you have sent, newest first, each with who it went to and how it did, sent, delivered, read, clicked, orders, revenue, ROI. Filter by channel, date, status or segment, or sort by best ROI, read rate or revenue. |
| One campaign in depth, or up to five side by side: the deliverability, engagement and sales funnels, including the reasons messages failed. |
| How a campaign was set up, when it was scheduled and by whom, which segments were included and excluded, the template and its fallback, the sender number or email domain, and any retry rounds. |
| A score out of 100 for how well your store runs campaigns, graded over your last 30 days of broadcasts, with the weakest practices ranked first and a recommended action for each. |
Your audience
Ask what segments you have, how many people are in them, and how many you can actually reach.
"What segments do I have?"
"Find my retention segment."
"How big is my repeat buyers segment, and how many can I reach on WhatsApp?"
"How was this segment built?"
"Why can't I message these customers?"
Reachability is reported per channel, with opted-out counts separated from available ones so a large segment that is small on email is visible as exactly that.
For the last question, give up to 100 phone numbers or email addresses. Each comes back as suppressed or not, and a suppressed one carries the channel, the date and the reason opted out, hard bounce, too many soft bounces, marked as spam, or a specific WhatsApp delivery error. This covers the automatic suppression list only; a customer who looks clear here could still be on a suppression list you uploaded yourself.
Tool | What it does |
| All your segments, Bik's smart RFM segments, ready-made library ones, your own filter or uploaded ones, Shopify-synced ones and suppression lists, each with its size and reachable count per channel. Searchable by name. |
| One segment explained: who built it and when, the filter rules or upload behind it, and total, reachable, available and opted-out counts per channel. |
| How big a segment is and how much of it you can actually reach, split per channel into available and opted-out. |
| Checks up to 100 phone numbers or email addresses and tells you which are suppressed, on which channel, since when, and for what reason. |
Journeys and automations
Ask how your automated journeys are performing, where customers fall out of them, and what you are missing.
"Which journeys made me the most money last quarter?"
"Is my abandoned cart journey doing better than last month?"
"Where do people drop out of my COD confirmation flow?"
"Why won't this journey publish?"
"What journeys should I add?"
"What ready-made journeys can I use?"
"Who changed this journey, and when?"
Drop-off is answered block by block, the way the Funnel view counts it: how many customers reached each step, and what happened there delivered but never read, a button nobody pressed. That tells you where the flow leaks and why.
"What journeys should I add?" returns your journey score with specific recommendations the journey that is missing, the feature that is missing inside an existing one, and what each is worth ordered by the points you would gain.
Tool | What it does |
| All your journeys with their channel, whether each is live or in test mode, and optionally revenue and how many customers entered, so your best and worst performers sort themselves out. |
| Full numbers for one journey or all of them over a date range: entries, sent, delivered, read, clicked, orders, revenue, cost and ROI, with an optional comparison against the period before. |
| The block-by-block funnel, how many customers reached each step and what happened there, so you can see where the journey leaks and why. |
| Your journey score with ranked recommendations: journeys worth adding, features missing from the ones you have, and the points each is worth. |
| The errors and warnings on each block of a journey, exactly as the builder shows them, explaining why it will not publish. |
| Bik's ready-made journeys, abandoned cart, order tracking, COD confirmation and more, that are available to your store. |
| Who saved each version of a journey, when, from where and with what note; and what changed between any two versions. |
Templates
Ask what you can send, what happened to a template in review, and how one is doing.
"Which templates can I send right now?"
"Do I already have a sale template, or do I need a new one?"
"Why was my Diwali template rejected?"
"How did that template perform?"
"Has my template's quality rating dropped?"
A rejection comes back with Meta's stated reason and its recommendation. Quality is shown as previous versus current rating, which is the change that precedes a number being throttled or paused. Performance covers the last 30 days, sent, delivered, read, clicks and cost, for WhatsApp templates Meta reports on; when it is unavailable, you are told why rather than shown a zero.
Tool | What it does |
| Your approved WhatsApp templates, the ones you can send right now, with each one's category, body text, and how many variables and buttons it has. |
| Finds your templates across every channel by name or content, with filters for channel, type, status and where the template came from. |
| One template in full: the rejection reason and Meta's recommendation, previous versus current quality rating, the content, its variables, and 30-day performance. |
Spend, credits and invoices
Ask where your money went and what is left.
"How long will my balance last?"
"Why did my WhatsApp spend jump last week?"
"What was this debit on the 14th?"
"Have I used up my free email credits?"
"Send me last month's invoice."
The overview leads with anything that needs attention, a zero or negative balance, under a week of runway at your current burn, a free quota nearly used up. A spend spike is answered by naming the two or three campaigns or journeys that drove it, not by handing you a ledger. Invoices come with their line items, each tax component listed separately, and a link to the hosted PDF.
Tool | What it does |
| Wallet balance, how many days it will last at your current burn, your plan and billing period, free credit allocations and usage per channel, led by anything that needs attention. |
| Your wallet ledger, newest first, saying what each row is: a recharge, a gift, an expiry, a daily usage debit or a broadcast settlement. Filter by date, channel, or credit versus debit. |
| Where one channel's spend came from over a date range, with the biggest contributors named, per campaign or journey for WhatsApp and email. |
| Your invoices, newest first, with number, status, due date, total and whether a PDF is available. |
| One invoice in full: line items, each tax component separately, payments made, credits applied, the balance still due, and a link to the PDF. |
Deliverability and channel setup
Two different questions sit here, and it is worth knowing which one you are asking.
Is my sender healthy? quality rating, daily conversation limits and how much of one you have used, throughput, a 30-day quality timeline, and for email the read, bounce and unsubscribe rates of your last three broadcasts against their thresholds, plus each sending domain's Postmaster reputation.
Is my channel set up correctly? whether it is connected at all, the provider, each number's status, DNS records on your sending domains, Postmaster permissions. Problems come back as a list of issues, each with the fix.
"Why is my delivery rate low?"
"Is my WhatsApp number's quality rating okay?"
"Is my email domain set up correctly?"
"What frequency caps and quiet hours am I running?"
That last one returns your account-level sending controls: how many messages a customer can receive in a given window per channel, the extra cap that applies while an email domain's reputation is poor, your quiet-hours window, and how many WhatsApp delivery errors it takes before a customer is suppressed.
Tool | What it does |
| Sender health: each WhatsApp number's quality rating, daily conversation limit and how much of it is used, throughput and a 30-day quality timeline; for email, your last three broadcasts' read, bounce and unsubscribe rates against their thresholds, plus each sending domain's reputation. |
| Whether each channel is connected and configured correctly provider, number status, DNS on your sending domains, Postmaster permissions with a fix given for every problem found. |
| Your account-level sending controls: frequency caps per channel, the extra cap that applies while an email domain's reputation is poor, your quiet-hours window, and how many delivery errors it takes to suppress a customer. |
Good to know
Nothing is sent or changed. Every one of these is a lookup. Campaigns, journeys, templates and credits are untouched.
These are live figures, not estimates. Revenue carries an attribution rule, and it will be quoted alongside the number so you know how an order was credited.
Some totals won't tie to the rupee. Credits come from your wallet and message volume from delivery events, so a usage breakdown can differ slightly from your wallet balance. Usage also stops at the last fully billed date.
Date ranges default to the last 30 days unless you give one. Journey drop-off looks back at most 90 days.
If an answer looks wrong, say so. It can be reported straight to the BIK team along with the question that produced it through this portal: https://dashboard.bik.ai/bik-labs?screen=support-portal