{"id":"d7230bdf-33bd-40a1-a8aa-1629a1ce0725","slug":"worker-inbound-message-triage","category_slug":"workers","order_index":115,"published":true,"created_at":"2026-10-26T11:29:25.538Z","related_slugs":"[\"workers-communication-channels\",\"worker-managers-management\",\"workers-on-delos\"]","title_fr":"Pourquoi mon worker n'a pas répondu à un email ou un message WhatsApp ?","title_en":"Why did my worker not reply to an email or WhatsApp message?","content_en":"<p>A worker receives many messages that need no action: newsletters, automatic notifications, group chatter. To avoid making the worker run (and use credits) for nothing, Delos <strong>sorts incoming emails and WhatsApp messages before the worker starts</strong>.</p>\n<h2>How the sorting works</h2>\n<ol>\n<li>A message from <strong>its manager</strong> is always handled by the worker.</li>\n<li>A first filter discards only obvious noise.</li>\n<li>A second check reads the worker's role, missions, instructions and rules, then decides whether the message calls for a reply or an action.</li>\n<li>When in doubt, the worker handles the message.</li>\n</ol>\n<p>If the sorting cannot decide, or hits an error, the message is handled normally.</p>\n<h2>What happens when a message is ignored?</h2>\n<ul>\n<li>For an email or a one-to-one WhatsApp message: a conversation is created and marked as dismissed, with a summary starting with \"Ignored\" and the reason.</li>\n<li>For a WhatsApp group discussion: the message is simply set aside.</li>\n</ul>\n<p>The sorting is rolled out gradually: depending on the organization, it may first run in observation only, ignoring nothing.</p>\n<h2>Your worker did not reply: what to check?</h2>\n<table>\n<thead><tr><th>Question</th><th>Lead</th></tr></thead>\n<tbody>\n<tr><td>Does the message come from its manager?</td><td>It is then always handled. Check instead that the channel is properly connected.</td></tr>\n<tr><td>Is it a newsletter, a notification or a group message?</td><td>The sorting may have discarded it. This is the expected behavior.</td></tr>\n<tr><td>Was the message addressed to a colleague, with the worker in copy?</td><td>It may be judged as requiring no action from the worker.</td></tr>\n<tr><td>Should the worker handle this type of message?</td><td>Say so in its missions, instructions and rules: the sorting relies on them.</td></tr>\n</tbody>\n</table>\n<h2>Slack: lend the manager's account to a worker</h2>\n<p>In the worker's <strong>Slack</strong> tab, you can choose how it connects: with <strong>its own bot</strong> or with <strong>its manager's Slack account</strong> (one or the other). When the manager's account is lent, a warning is shown: the worker's messages then appear under the manager's identity.</p>\n<h2>Frequently asked questions</h2>\n<h3>Can the sorting ignore an important message?</h3>\n<p>It is designed to handle the message when in doubt, but an error remains possible on borderline cases. If an expected message got no reply, prompt the worker from Ping.</p>\n<h3>How do I prevent a type of message from being ignored?</h3>\n<p>Describe it in the worker's missions or instructions (for example: \"handle emails of this type\").</p>\n<h2>Looking for something else?</h2>\n<ul>\n<li><a href=\"/en/articles/workers-communication-channels\">A worker's communication channels</a></li>\n<li><a href=\"/en/articles/rules-for-workers\">Set a worker's rules</a></li>\n<li><a href=\"/en/articles/create-workers\">Create a worker</a></li>\n</ul>","tags_fr":null,"tags_en":null,"intro_fr":"Le tri des messages entrants écarte le bruit évident avant de lancer un worker ; les emails ignorés sont classés avec une raison, mais ceux du manager sont traités.","intro_en":"Incoming-message triage filters obvious noise before launching a worker; ignored emails are filed with a reason, while messages from the manager are processed.","prerequisites_fr":null,"prerequisites_en":null}