Return-Path: <gdale@neopolitan.com>
Received: from [65.87.16.98] (account gdale@neopolitan.com HELO [10.0.0.149])
  by mx1.neopolitan.us (CommuniGate Pro SMTP 4.2.10)
  with ESMTP-TLS id 38225731; Wed, 21 Oct 2009 19:22:20 -0700
Message-ID: <4ADFC1D8.2070500@neopolitan.com>
Date: Wed, 21 Oct 2009 19:22:16 -0700
From: Geoff Dale <gdale@neopolitan.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: frobles@neopolitan.com
CC: "accounting@neopolitan.com" <accounting@neopolitan.com>
Subject: Re: WBS San Antonio Order [Fwd: TrustFax Notification for 8666663358
 - 171608 10/20/2009]
References: <4ADE4582.6080005@neopolitan.com> <4ADFA906.9070904@neopolitan.com>
In-Reply-To: <4ADFA906.9070904@neopolitan.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Frank R. Robles wrote:
> Thanks. I've had this one. What I need is the actual MSA. The Master 
> Service Agreement that this service order references. Do you not have 
> it? It contains several key terms governs the transfer of the agreements.

Ah sorry, there doesn't seem to be one. Not in the file and I don't 
think I've ever seen. If it shows up with my signature on it I would be 
most surprised.

Initial business with WBSconnect was in a rush after Sago lost transit.

I never saw that initial paperwork. Subsequent business has all assumed 
there was a standard MSA, signed.

Maybe none of this is legal.

- G


