Work Order Import
Turn emailed work orders into Simpro jobs or Fergus jobs and enquiries.
Getting started
Records
- Read the Dashboard to see what each emailed work order became The Work Order Import Dashboard: inbox folders, the record list, the Results and Email tabs, what each message means and what to do with a failed record.
- Check how many emails were imported, skipped or failed The Work Order Import Reports page: pick a period, filter by inbox or platform, and see what the import did with each email and which errors repeat.
Inboxes
Parsers
Account
Account settings
- Choose the Simpro credential Work Order Import uses Pick the one Simpro credential every Simpro inbox and parser in Work Order Import uses, test it, and see what the import does when it is missing.
- Choose the Fergus credential Work Order Import uses Pick the one Fergus credential every Fergus inbox and parser in Work Order Import uses, test it, and see what happens when you clear or swap it.
- Choose the Simpro custom fields parsers can fill Tick the Simpro job custom fields a Work Order Import parser may map to, and what happens when Simpro refuses a value or you untick a field a parser uses.
Inbox settings
- Create an inbox and choose its email address, platform and parser Create a Work Order Import inbox: choose Simpro or Fergus, set the email alias work orders are sent to, pick a parser, and see when the address appears.
- Set the company, customer and defaults for new Simpro jobs and quotes Simpro Defaults for a Work Order Import inbox: company, customer, job type, status, stage, salesperson, manager, tags and a service template.
- Set the customer, job type and notes for new Fergus jobs Fergus Defaults for a Work Order Import inbox: the customer, job type, first phase title, quote validity and job notes used for every new Fergus job.
- Map text in a work order's address to an existing site Map text found in a work order's address or site name to an existing Simpro or Fergus site, and set how the address of a new site is written.
- Map the response time on a work order to a Simpro response time Map response time text on a work order, such as P1 or 4 hours, to a Simpro response time on new jobs, and what the Generate Due Date rule does with it.
- Change an inbox's defaults when the order number, name or description matches Add conditions to a Work Order Import inbox that override its defaults, such as status, customer or job type, when the order number or name matches.
- Choose which emails an inbox processes and how duplicates, files and sites are handled Inbox Rules for Work Order Import: accepted subjects and senders, the duplicate check, attachments, site handling, dates and notification emails.
Parser settings
- Create a document parser and choose what it reads and where it imports to Set a document parser's name, whether it reads PDFs or emails, whether it imports to Simpro or Fergus, and which object it creates. Three settings lock on save.
- Teach a PDF parser where each field sits in a work order Build a PDF parser from a sample work order: mark fields, data points and repeating rows, add guard rules so other PDFs are skipped, use suggestions, test it.
- Read work orders from the body of an email with an email parser Build an email parser from a sample .eml file: text rules that read labelled values, PDFs handed to a PDF parser, guard rules, suggested rules and a test.
- Clean up what a PDF parser reads with field filters Remove text, add text before or after, or strip numbers or spaces from the value a PDF parser reads for a field, and find out when a filter is skipped.
- Turn a due date written as words into a real date with field mapping Add conditions so a PDF parser turns a due date such as Urgent or Next day into a date a set number of days after the date issued.
- Build the job description and notes from a template Use a template with field placeholders to write the job description or notes from several parsed values, and set up template reference fields for repeating rows.
- See which parsed values a Fergus parser can write to Fergus Where each value a Fergus parser reads is written in Fergus, and which values Fergus has no field for, so they are read but never saved.