How an email is read, layer by layer

How an email is read, layer by layer A workflow diagram generated by Archify. 01 / The layers, for an enquiry 02 / The stage, worked out in code EX / Tags, and what comes later Stored email · rows and files · The layers, for an enquiry Stored email rows and files Name the stage · from text and file names · The layers, for an enquiry Name the stage from text and file names Read the files · convert and clean · The layers, for an enquiry Read the files convert and clean Find the lines · one per tag · The layers, for an enquiry Find the lines one per tag Read each line · stated or missing · The layers, for an enquiry Read each line stated or missing Suggest products · from the catalogue · The layers, for an enquiry Suggest products from the catalogue Check the thread · earlier mail, oldest first · The stage, worked out in code Check the thread earlier mail, oldest first Moves forward · new stage recorded · The stage, worked out in code Moves forward new stage recorded Revision tag · no new stage, unlinked · Tags, and what comes later Revision tag no new stage, unlinked Link a revision · to its quotation · Tags, and what comes later Link a revision to its quotation Match to the offer · orders and changes · Tags, and what comes later Match to the offer orders and changes Our quotation · built and sent · Tags, and what comes later Our quotation built and sent moves it on does not a stage message enquiry, or unsure order arrives Legend Code step Revision Stored data Model step Later

New, and from the POC

  • • New: name the stage, read the files, the revision tag
  • • POC layers 1 to 3: find lines, read each, suggest

Stage and revision

  • • Enquiry, offer, order, sales order: the deal only moves forward
  • • No new stage is a revision; thanks and chasers are only tagged

Safe by default

  • • Unsure or down: treat it as an enquiry
  • • Every layer saves its answer; reading again replaces it