Never Miss a Message: How Sign OS Logs Job Correspondence Automatically

Every sign job is really a conversation: the enquiry, the artwork back-and-forth, the "can we move it a week," the approval, the delivery question. That conversation is scattered across two inboxes, someone's phone, and a memory of a call that happened on a Friday. When a dispute or a query lands months later, reconstructing it is archaeology.

Sign OS gathers a job's correspondence onto one timeline — most of it automatically. Here's what gets captured, and what still takes a human ten seconds.

Emails, captured without forwarding them one by one

Connect a mailbox and Sign OS captures job email automatically, through whichever route fits how your team works:

• ✓Outlook and Gmail sync. Connect the mailbox once and relevant messages are pulled in — no manual forwarding.
• ✓Email companions. An Outlook add-in and a Gmail add-on let staff tag a message to a job or quote from inside the inbox they already live in, without switching apps.
• ✓Inbound addresses. Each shop gets inbound aliases — mail sent to a job's address (or with the job number in the subject) is routed to the right job on its own, and any attachments are saved straight into the job's files.

Captured emails are grouped into conversation threads and shown on the job's Correspondence tab with sender, direction (inbound or outbound), timestamp and full body. You can filter by sender or by direction, see who tagged each message and when, and deep-link back to open the original in Outlook or Gmail. Attachments ride along into the job's files instead of being buried in someone's mailbox.

Every document you send is logged on its own

When you send a quote, invoice or purchase order out of Sign OS, the send itself is recorded automatically — who it went to, which document, whether it succeeded or failed, and when. So "did the quote actually go out?" stops being a guess. If a send fails, that's on the record too, not silently swallowed.

Calls and meetings, in ten seconds

Not every conversation is an email. The Log correspondence action lets anyone record a phone call or a meeting against the job — channel, subject, a note — and it lands on the same timeline, interleaved with the captured emails in date order. It's the one manual step, and it's deliberately small: the aim is that the phone call your estimator took at 4pm is on the job by 4:01, not lost by Monday.

Kept as long as you need, and no longer

Because it's structured data rather than a pile of forwarded mail, correspondence obeys a retention policy you set: how many days to keep tagged emails, and when to purge message bodies while keeping the metadata. You decide the balance between having the history and holding personal data, and Sign OS enforces it automatically.

What's automatic, and what isn't

Being straight about it, because the headline word is "automatically":

Automatic today — capturing emails from connected Outlook and Gmail mailboxes; routing inbound mail (and its attachments) to the right job; threading conversations; logging every document you send with its delivery status; enforcing retention.

Still a human step — logging phone calls and meetings (a quick manual note). And replies still happen in your own email client; Sign OS captures and organises the conversation, it isn't a place you compose email from. Deeper email actions and attachment capture are on our public roadmap, and we keep an honest status board rather than overclaiming.

The net effect is the one that matters: months later, when someone asks what was agreed, you open the job and the conversation is there — the emails that flowed, the documents that went out, and the calls that got noted — on a single timeline instead of scattered across three inboxes and a memory.

Sign OS is built and operated in Australia — Outlook and Gmail companions, configurable retention, and a free 7-day trial with no card required.