insight

Your own people, over the last 30 days. Tools are the searches and lookups their questions ran, so a question with none was answered without reading your mail.

This is the instruction your brief is written from, and you can edit it directly. Say what it should lead with, what to leave out, which sections matter most to your fleet, and the tone. Reset puts the Dualog default back. Preview before saving, so nobody finds out at 06:00 what changed.

Insight is not tied to any one mail system. A source is a place it reads from: Dualog's own store, an IMAP server, a Maildir, a folder of documents. Everything downstream, the search, the ship pages, the brief, never learns where a message came from. Credentials are encrypted and cannot be read back out, and nothing saves until the connection has been tested.

Mail matching an active filter is never indexed, so it cannot appear in answers. Use it for traffic that carries no meaning: device telemetry, delivery-failure notices, automated feeds. Patterns use * and ?; anchor them (aft.*) rather than wrapping in stars, or they catch more than you meant. Check what a pattern would catch before saving it.

A stop is a pattern on the question. A question that trips it gets the refusal text below instead of an answer, and the attempt is logged with the user. Dualog ships a few defaults for personal data about crew; you can retire them or add your own. Patterns are regular expressions, case-insensitive. Try a question before you save.

Tell Insight who each mail domain is: your own offices, the ships, owners, charterers, class, suppliers, agents. The brief and the answers use this to sort mail by who wrote it. "Suggest roles" fills in what Insight can already tell; it never overwrites what you have set.

These prompts reach every customer instance. Braces are filled in by the user when they run it: {vessel}, {days}, {period}, {port}, {sender}. Retire a prompt rather than deleting it once people have saved it.

Prompts users typed rather than took from the library, across every customer. A question that keeps being written by hand belongs in the catalogue. Rewrite it generically (swap the vessel for {vessel}) before adding it — these bodies are customer content.