Nobody chose this
A real gap. A post no workflow covers, or a comment that never got dispatched. This is the number worth acting on.
Instagram + WhatsApp → replies
Somebody comments on your Reel. Within seconds they have a private DM, a public reply under their comment, and a place on your contact list. And when nothing is sent, the record says which control refused, and why.
examples, not clients

@riya.bakes · on your Reelprice kitna hai? 😍
● SENT · DM + public reply

WhatsApp · new numberDemo
● SENT · lead question

Instagram DM · late nightare you open tomorrow?
● SENT · keyword reply

@growfast.bot · on your Post🔥🔥 check my page for followers
● REFUSED · spam filter

@lena.styles · on your ReelLINK
● SENT · DM + public reply

@karan.fit · after “stop”PRICE
● REFUSED · opted out

@sofia.m · on your Postdo you have peonies today?
● SENT · DM

Instagram DM · late nightaaj khule ho?
● SENT · keyword reply
meta error 368 · spam behaviour
Measured on 17 October 2026, from the live record. Re-measured every time the site is published, with the date attached.
is my account safe?
our promise
If Instagram ever restricts your account, or warns it about automation, while HeyJaanu is running, we switch your auto-replies off the same day, show you everything that was sent, and help you with Instagram’s review. That month is not charged.
Nobody can promise Instagram will never restrict an account, so we do not. This is what we promise instead. The details are on security and safety.
Real numbers from our first client
The first three weeks ran from 7 September 2026 to 28 September 2026. Every one of these was a reply to somebody who had commented. Test messages are not counted.
the path a comment takes
A workflow is data, not a script. Nothing in it executes code.
Before go-live, a real comment runs through the real engine with the sending capability structurally absent — not disabled by a flag somebody could flip.
27 named endings
This one tells you why one wasn’t — by name, against the comment that caused it, in something you can search and count.
3 endings mean something went out. 4 are failures. 2 are rehearsals. 2 mean no workflow matched. The remaining 16 are deliberate refusals.
Decisions made on your behalf, which you are entitled to read.
The message, the message with a failed public reply, and the case where only internal actions were due.
Including the one nobody else names: a send whose result is unknown.
Nothing was chosen for this comment, or another workflow won.
Dry runs. They can never send, and they are recorded anyway.
UNKNOWN_OUTCOME deserves its own sentence. It is a send whose result nobody knows, and it is never retried automatically — because retrying a message that may already have arrived is exactly how a person ends up DM’d twice. It goes to a human instead.
the half nobody shows
A comment that matches no workflow writes no execution row — deliberately, or the database fills with tens of thousands of rows for posts nobody automated. The cost is that the misses appear nowhere at all. There is a screen for exactly those, and it splits them three ways.
A real gap. A post no workflow covers, or a comment that never got dispatched. This is the number worth acting on.
An emoji-only comment, or a reply under another comment. A decision, not a bug.
It arrived ten seconds ago. Counting it as a miss makes the number climb every time traffic does, which is alarming in the one moment it should be reassuring.
the guard
An automation that sends everything it can is an automation that gets the account restricted. These limits live in the engine itself, not in a setting somebody can forget to switch on.
| Situation | Control | What happens | The record says |
|---|---|---|---|
| The same person comments three times in an hour | per-person cap | The first one gets the DM. The other two do not. | SKIPPED_USER_COOLDOWN |
| A Reel goes viral — four hundred comments in ten minutes | account ceiling, then deferral | The overflow waits. Nobody is dropped. | SKIPPED_RATE_CAP |
| Someone replied "stop" last week | opt-out wall | They will not hear from you again. | SKIPPED_OPTED_OUT |
| Instagram starts rejecting sends | circuit breaker | It stops trying instead of hammering the door. | SKIPPED_CIRCUIT_OPEN |
| It is day one and every workflow is built | send mode | Nothing can go out yet. | nothing is sent, and the reason is recorded |
| Somebody comments on a nine-day-old post | platform window | There is no way to answer them. | SKIPPED_WINDOW_EXPIRED |
One DM per person per day, which is Meta’s actual rule, plus a separate budget for public replies so a comment’s two halves never compete for the same allowance.
Per post per hour, per account per hour, per account per day, set against your account’s real volume rather than a default.
A cap postpones a send within Instagram’s seven-day window, it does not discard it. When a post goes viral the overflow is retried later, so nobody is silently skipped for commenting at the wrong minute.
Somebody says stop and the record cannot be deleted by the application. Not a preference — a wall in the database.
Four scopes — everything, one client, one account, one workflow — and it still works when the console cannot be reached.
If Instagram starts rejecting sends the engine stops trying rather than earning a longer penalty. Error 368 opens it instantly, with a 24-hour hold.
Meta’s own usage headers are read continuously, and sending pauses before the limit rather than after it.
DISABLED by default, then TEST with an allowlist and a tiny cap, then LIVE — enforced inside the guard, so nothing can send on day one even if every workflow is finished.
Shipped, and it records what it suppressed instead of quietly dropping it.
Every DM carries one, and no setting in the product can take it out of a DM.
Caps are set against your account’s real volume rather than printed here. A figure on a website that does not match what your account gets is worse than no figure at all.
looked after
A comment is saved before anything is done with it, so a crash or a restart delays a reply rather than dropping it.
Work is shared out fairly between accounts, so one viral post does not hold up everybody else.
Each comment can produce one private reply, and the record refuses a second one.
Every client’s records are kept apart inside the database itself, not by a filter somebody has to remember.
Instagram access is stored encrypted, and the keys can be rotated.
Not only taken: restored into a spare database and checked, including that the encrypted access still opens.
Every change our side makes is logged, refusals included, in a log the application itself cannot edit.
including us
These are not gaps here. They are closed on Instagram’s side, for every product on the market — and anybody selling them to you is either scraping or guessing.
| Claim you will hear elsewhere | The truth |
|---|---|
| Only DM people who follow you | At the moment of sending, whether somebody follows you is not readable — Meta consent-gates the field. It can be checked afterwards, which is a different promise. |
| Broadcast DMs to everyone | There is no such API. A message is a reply to somebody who contacted you first, inside a window that expires. |
| Unlimited DMs per person | One private reply per comment, ever. Not a policy — a platform constraint. |
| We’ll reply to old comments forever | The window is seven days from the comment. After that nobody can reply, at any price. |
| Send a PDF or an image in the DM | A private reply carries text and a link, not an attachment. |
| We’ll automate your private account | A private account produces no comment webhook at all. |
| Scrape their followers | Off the table. Official APIs only — which is also the reason the account stays yours. |
This list is also a schedule in the services agreement, signed at the start, so nobody can later say they were promised a follow-gate.
not built yet
Nothing below is available today. Each item carries its status, so nothing here can be mistaken for a feature.
The best-performing reply wording chosen automatically, and a wait step that holds across restarts.
Authorising Instagram is already yours to do and no token reaches us by hand. What is not built is the removal of the step in the middle: we add your account as a tester on our Meta app, and you accept that in the Instagram app. Taking that away is what would need App Review — see below.
Story replies, DM keywords, content only for followers, email capture and one follow-up are built and switched off. Meta has verified our business; we are applying for the permission these need, and they stay off until Meta approves it.
run for you, not sold to you
You can create a workspace yourself in a minute. What is not self-serve is one manual step: Instagram has to grant this installation access to your account, we send that invitation by hand, and you accept it in the Instagram app. Usually the same day. It needs no App Review and no Business Verification. We would rather say so here than after an invoice.
Create a workspace · Or have us set it up and run it
Workflow configurations, copy, and any keyword sets created for you are assigned to you on payment — worldwide, for the full term.
We act as Data Processor under India’s DPDP Act 2023, and delete commenter data on exit. Opt-out records are kept, because deleting those is how somebody who said stop starts hearing from you again.
Go-live is conditional on platform approvals. Timelines extend day for day, and a refusal is not a breach.
GST, TDS under 194J, MSMED terms and e-stamping, handled.
pricing
Comparing this to a subscription compares a retainer to a tool licence. The honest comparison is their subscription plus the hours you or your agency spend inside it, against one retainer where the hours are ours.
| Setup | One-time. Half on signature, half at go-live. |
|---|---|
| Managed operation | Monthly, by active workflows and account volume. |
| Tiering | By workflows and posts covered — never by contact count. Contact pricing punishes you for going viral, which is the exact moment you should be happiest. |
| Overage | None. Caps postpone a send within Instagram’s seven-day window, they do not drop it, so there is nothing to bill for. |
| First month | On a monthly plan, if it is not working for you within 30 days of go-live, tell us and we refund the setup fee and the first month’s fee in full. |
Three plans, each a one-time setup and a monthly fee, and an Agency plan priced per client account, are on the pricing page.
who is behind HeyJaanu
HeyJaanu is run by Shivangi Yadav, from Agra, Uttar Pradesh. Every account is set up and watched by a person, and you can always write to us directly.
Every comment gets an answer. Or a reason.
Tell us the account. We look at it and at your last few posts before replying, and if Instagram’s rules make the thing you want impossible, you hear that in the first reply rather than after the setup fee.
Request a proposal