Nilyo
Sign inGet started →
Persistent agent notifications

Let your persistent agent reach you on WhatsApp

An agent that works while you are away needs a way to reach you, and email is where alerts go to be ignored. WhatsApp is read — which is why the discipline about what it sends matters more than the plumbing.

Your own number, not a bot

The alert arrives in the conversation you already have with yourself or with a colleague, under your name. No brand number, no template approval, no reply window — and nothing for anyone to install or accept before the first message works.

Only what deserves an interruption

The temptation is to notify on everything, and the result is muted within a week. A good filter is specific: a message from a named account, a keyword that matters, a task the agent could not finish. If it fires ten times a day, tighten it rather than getting used to it.

Say what happened, not that something happened

An alert that says check your LinkedIn is worse than no alert. Read the context first and put it in the message: who wrote, what they said, what the agent did or could not do. The test is whether you can decide without opening anything else.

Do not create a loop

Two rules. The agent must never treat its own alerts as inbound messages to react to — filter on who sent, strictly. And it must not alert about a conversation it is also answering, or you get a notification for each step of its own work. Loops here are quiet and expensive: twenty messages before anyone notices.

“Tell me on WhatsApp when a client replies about the invoice.”
“Message me if you could not finish a task.”

Replies are unlimited, new chats are not

Sending to a conversation that already exists is unrestricted, which is the case for alerting yourself or a regular colleague. Brand new conversations are capped at twenty a day per account and spaced fifteen seconds apart — worth knowing if the agent alerts a rotating on-call list.

Answer from the same place

The useful ending is not the alert, it is what you do next. Because the accounts are reachable from your assistant, you can read the thread and answer from the same conversation, without opening the app the alert was about.

Common questions

Does it need WhatsApp Business?

No. The number you already use is paired by QR code; templates and the Business Cloud API belong to the brand-number route.

Can it alert a colleague?

Yes, resolved by name from your conversations. If several contacts match, nothing is sent and you are asked which.

How do I stop an alert loop?

Filter strictly on who sent the message, so the agent never reacts to its own alerts, and do not alert about a conversation it is also handling.

Is there a limit?

Replies in existing conversations are unrestricted. Brand new conversations are capped at twenty a day per account and spaced.

How WhatsApp works with Nilyo

Connection. Scan a QR code shown in the conversation (WhatsApp › Linked devices), or type a pairing code on your phone. The line stays linked like any other device.

What your agent can do. Contacts and chats, message history, text, media and native voice notes, reactions, groups, checking whether a number is on WhatsApp.

Pacing and safety. 20 new conversations per day with 15 seconds between them; existing chats are not limited beyond serialization.

  • “Send a WhatsApp to Julien” resolves the person among your recent chats and contacts; two matches mean the agent asks.
  • Disconnecting from the phone marks the account for reconnection; the same account is re-linked with a new QR, never duplicated.

All WhatsApp guides

Related guides

Give Nilyo to your agent.

Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.

© 2026 Nilyo.