How email job matching works
The real rule for matching incoming emails to jobs — the job number in the subject line.
When you connect Gmail or Outlook, VanMan watches your inbox and files matching emails onto the right job's Messages tab. The whole thing hinges on one detail in the subject line.
The matching rule
VanMan looks in the subject line for the job's job number — an eight-character code like a3f9c2b1. This is the same value that shows as {{JobNumber}} in your templates, and it is the first eight characters of the job's ID.
It is not "Job #1234", "VM-1234", or any numbering format you choose. Those never match. The code is eight hexadecimal characters (0–9 and a–f), and it is the only thing the matcher recognises.
So a subject that matches looks like Booking confirmed — a3f9c2b1, and it matches because of the a3f9c2b1, not the words around it. A reply keeping that code in its Re: subject stays matched.
Because your outgoing VanMan emails put {{JobNumber}} in the subject automatically, replies from customers usually carry the code back without anyone thinking about it.
Booking references match too
If no job matches, VanMan tries a booking reference — the BK-XXXX-XXXX code on a booking request. This lets a customer's reply attach to their enquiry before it becomes a job, so the thread carries over on conversion.
What it watches, and what it doesn't
Only your inbox is watched — incoming email. Emails you send from Gmail or Outlook directly are not scanned. The only outbound emails recorded on a job are ones you send through VanMan's own reply feature.
So "scans your incoming and outgoing email" is only half right: incoming inbox mail is matched; your Sent folder is not.
Matching happens in near real time — Gmail and Outlook push new inbox mail to VanMan as it arrives.
No match
If the subject carries no recognisable job number and no booking reference, the email is skipped — nothing is stored, and it simply stays in your inbox. VanMan does not guess by sender or content.
It's a shared inbox
The connection is one shared mailbox for the whole business, not a per-user connection. You connect a central inbox — your bookings@ or office@ address — and everyone works from what it captures. There is no "each team member connects their own email".
Tutorial: make sure replies land on the job
You want customer replies to file themselves automatically.
Connect the central inbox customers actually reply to — bookings@ or office@ — not a personal one. It is a shared, business-wide connection, so pick the address your customer emails go through. See connecting Gmail.
Your message templates already put {{JobNumber}} in the subject line. Leave it there. That eight-character code is the entire matching mechanism — strip it out and replies stop filing themselves.
Do not add "Job #1234" style references expecting them to match — they will not. The only thing the matcher reads is the {{JobNumber}} code. Your own numbering scheme is invisible to it.
After a customer replies, open the job and its Messages tab. The reply should be there. If it is not, look at the subject line of what they sent — a reply that dropped the Re: and the code has nothing for VanMan to match on.
A customer who starts a fresh email with no job number in the subject will not match — it stays in the inbox, unfiled. That is not a fault; there was nothing to match. For those, forward or handle them by hand.
If you reply from Gmail directly rather than through VanMan, that reply is not captured onto the job — only inbound mail is watched. Reply from VanMan's Messages tab to keep the thread on the job. See replying to emails.