01Acceptance of these terms
Welcome to Lambda Service Desk. These terms of service form a legal agreement between you and Lambda Services Limited Liability Company, a company established in the United States at 334 N Colonnade Rd, Saratoga Springs - 84045-4550, United States (US). The developer that designs and runs the systems behind this desk goes by the name LambdaServe. By visiting this website, by calling the office, or by asking for a proposal, you agree to be bound by the terms presented here.
Lambda is used below to mean Lambda Services Limited Liability Company, and the words we, us, and our refer to that same company. The words you, your, and the customer describe the person or the firm that uses the website or buys the service. Everyone who visits the site is bound by the terms that apply to ordinary use of the pages, and every client is bound by the terms that apply to a service agreement.
We ask you to read this entire document before you begin to work with us. A polite note in an email or a quick promise on the telephone does not replace these written terms. Where you and Lambda sign a separate statement of work, that signed document and this document are read together as one agreement. If one part of the two documents conflicts, the signed statement of work governs for the specific job that it covers.
02About Lambda Services Limited Liability Company
Lambda Services Limited Liability Company runs a professional service desk and offers integrated support systems design to small firms and to property managers. Our work sits in the industry of computer systems design and related services, which includes computer integrated systems design and the professional, scientific, and technical trades that help a small business run its buildings and its office technology in one connected rhythm.
We answer calls, run a ticket queue, coordinate technicians and specialist vendors, look after contracts and insurance records, track the assets that a business owns, administer accounts and building access, and plan preventive maintenance so that small problems do not become large failures. We have built the discipline of a serious help desk and we bring that discipline to firms that never had the staff time to build it alone.
The everyday office line for the desk is +12798994629 and the everyday email address is direct@lambdaserve.lol. Letters can be sent to the address shown above. These contact routes are used throughout this agreement as the ordinary way to reach the desk and to give notice under the terms below.
03The LambdaServe developer behind this site
The website you are reading and the support platform that keeps the help desk working are designed and maintained under the developer name LambdaServe. LambdaServe is not a separate legal owner of your data. LambdaServe is the development name that the Company uses to describe the engineering and the design craft behind the desk.
Every tool, template, dispatch logbook layout, and reporting format produced by LambdaServe, and every method used to run the queue, belongs to Lambda Services Limited Liability Company unless a writing says otherwise. A customer who works with the desk may use those tools for its own operation while it is a client, but does not take ownership of them merely by paying a monthly fee.
Where this agreement talks about the platform or about tooling, it means the systems designed under the LambdaServe developer name and owned by Lambda Services Limited Liability Company. The developer name is published openly so that managers always know who built what they depend on.
04What the service desk offers
The Company operates a managed service desk. From the outside, a service desk looks like a fast and friendly way to get help. From the inside, a service desk is a set of repeated steps that ensure each request is caught, labelled, owned, worked, and closed in the same way every time. That consistency is what the customer is really buying.
The desk also reaches beyond the telephone. We design the integrated support system that connects the queue, the maintenance calendar, the vendor register, the asset ledger, and the access records into one operating framework. Our goal is that a small firm can prove its standards, plan its spending, and answer confidently about what is happening in its buildings.
Each customer receives a named desk analyst as a steady point of contact, plus the wider team that answers when that analyst is away. The number of covered hours and the expected response speed are written in the statement of work so that both sides understand the level of service from the first day.
05The six open lines of service
The recurring service is most easily described as six lines of work that sit open on the desk at all times. They are Service Desk and Ticket Triage, OnSite Dispatch Coordination, Vendor and Contract Management, Asset Tracking and Refresh Cycles, Access and Account Administration, and Preventive Maintenance Scheduling.
Service desk and ticket triage is the intake line. Every request arrives in one queue, is answered by a person, is given a category, and is moved toward an owner. OnSite dispatch coordination plans and tracks the physical visits that resolve the problems that cannot be fixed from the office. Vendor and contract management keeps the third party agreements, certificates, and renewal dates in one known place.
Asset tracking and refresh cycles records the location and the history of each item a business owns so that replacements are planned on real data. Access and account administration keeps the accounts and the keys of a firm tidy and safe from the day a person joins until the day that person leaves. Preventive maintenance scheduling plans the regular work that keeps filters, coils, valves, and systems healthy before they break. The services page of this site lists each line in more detail.
06Statement of work and scope
The exact work that Lambda will perform for a customer is defined in a statement of work, a proposal, or an order form that states the scope, the hours, the sites, and the regular tasks. That document is sent to you in writing before recurring work begins, and it forms part of the agreement once both sides accept it.
The statement of work will name the expected volume of tickets, the covered days and hours, the sites that are included, and the reporting you can expect. If a later request falls clearly outside that scope, Lambda will say so plainly and will either agree a fair additional charge in writing before the work begins or will decline the task honestly.
Lambda does not claim to be a licensed electrical, plumbing, mechanical, or low voltage contractor. Where regulated work is needed, Lambda coordinates a properly licensed specialist, confirms the licence before that crew is sent to the site, and keeps that record for the customer.
07Fees, estimates, and deposits
Prices are always confirmed in writing before a recurring engagement starts. A fixed monthly retainer covers the agreed desk hours, the open queue, and the standard reporting. Work that goes beyond the written scope, such as extra dispatches or unusual vendor oversight, is billed by time and materials at the rate stated in the proposal and is started only after you approve an estimate.
Where Lambda buys parts or books a third party service on your behalf, you may be asked to advance the funds or to reimburse them on the invoice. All prices are stated in United States dollars. A deposit may be required before large or custom work begins, and the deposit amount is shown on the proposal so there are no surprises later.
Quotes for a fixed job are held open for the number of days written on the quote. If materials prices change sharply before the work starts, Lambda may restate the quote for your approval before committing to the purchase.
08Payment and late charges
Lambda invoices on the date written in the agreement. Payment is due within thirty days of the invoice date unless a different term is printed on the invoice. The customer is responsible for any reasonable late fee that is shown in the proposal and for the costs reasonably incurred to collect an amount that stays overdue.
An invoice is sent to the email address or to the mailing address that the customer told Lambda to use. It is the customer duty to tell the desk if that address changes. A question about a single line on an invoice does not pause the rest of the account, but Lambda will always take a genuine question seriously and will correct an honest error without delay.
Managed plans that are prepaid are carried forward for use within a sensible period. Where a prepaid balance has not been used because Lambda could not schedule the work, that balance is refunded on request. A prepaid balance that expires unused because of the customer own planning is governed by the reuse and expiry policy shown on the statement of work.
09Start and renewal of an agreement
A binding relationship starts when the customer accepts a written proposal or statement of work and Lambda confirms that it will begin. An enquiry sent through the website form, or a conversation held on the telephone, does not by itself create a duty for Lambda to provide service.
If the customer asks Lambda to start a task and Lambda physically starts that task with the customer knowledge, then a contract exists for the work described and accepted at that time. The written scope and the rates discussed before that moment form part of that contract.
Lambda may decline to work with any customer for a sound business reason, which could include a record of unpaid invoices, a request that would break the law, or a request that would put our staff or a vendor crew in danger. A decline is always explained honestly to the customer.
10Changes to fees and to scope
The tools and the reporting behind the desk improve over time as LambdaServe ships small updates. Routine improvements that make the same service better do not change the customer price or the promised level of service, and they require no new signature.
Fees for a fixed monthly plan are steady for the initial term written in the agreement. After that term the plan may be adjusted on at least thirty days of written notice. A customer is free to decline a proposed fee change and may stop the service at the end of the current billing term instead of paying a higher rate.
When a request falls outside the written scope, Lambda will agree the additional fee in writing before doing the extra work. Lambda may also ask to adjust the scope document so that recurring services match what was actually agreed, since an honest written record keeps both sides safe.
11Customer duties and point of contact
The customer agrees to give Lambda current and truthful information about the sites, systems, people, and contracts that will be supported. This includes a working point of contact, real access details for the buildings, a handover of any vendor agreements in force, and a fair account of the age and state of the equipment that Lambda will look after.
The customer must keep the desk informed when its point of contact changes, when a building is sold, or when an access code or a lock changes. Anyone who gives Lambda an instruction on site must hold the authority to make that decision for the customer.
The customer also agrees to respect the rules of its own buildings and to warn Lambda and any vendor about risks that it knows of, such as a recent flood, an unstable doorway, a heavy item high on a shelf, hazardous material, or an animal that guards the site.
12Site access, safety, and permits
To run the service, Lambda and its vendors need reasonable access to the site at the agreed time, in a space that is safe to stand in, with light, power, and water wherever the job depends on them. The customer grants that access for the tasks in the scope and for the short follow up visits needed to finish the job.
The customer is responsible for landowner approval and for any local permission that applies to its own property. When a job on a regulated system requires a permit, the properly licensed trade obtains the permit as part of the licensed scope, and the permit fee is a reasonable cost of that job.
If Lambda arrives and the site is locked, unsafe, or not prepared as agreed, the visit is rescheduled. When a visit is missed more than once through no fault of Lambda, a reasonable rescheduling fee shown in the proposal may be charged so that the desk time is treated fairly.
13Vendors and subcontractors
A large part of what Lambda delivers is coordination. Lambda works with independent contractors, licensed trades, and specialist firms. Each of those third parties remains responsible for its own people, its own safety, its own licence, and its own rules, unless a writing says that Lambda employs that crew.
Lambda selects vendors with care. We check that a trade holds the licence and the insurance its craft needs, we help write a clear scope, we hand the crew a real arrival window, and we track the work to a clean close out. Lambda is not the employer of a third party crew and does not stand behind the individual errors of that crew except where the law says it must.
Vendor invoices for approved work pass through to the customer at the rates Lambda agreed or at the vendor published rate, with no hidden uplift. Every vendor charge is shown on the customer invoice so the customer can always see what was spent on its behalf.
14Assets, parts, and materials
Tools, test instruments, and small computers that Lambda brings to a site belong to Lambda. The customer should return any Lambda tool that is left behind, and Lambda will collect those tools as soon as it is told that they were left.
Parts and materials bought for a specific job belong to the customer once they are installed and paid for. When Lambda buys an asset on the customer behalf, that asset belongs to the customer from the day of payment. Lambda keeps a simple receipt record for each purchase so the trail stays clear.
Advice about refresh cycles, such as a recommendation to replace aging computers or worn pumps, is advice unless a separate writing commits Lambda to deliver specific new assets. Renewal planning built from the asset register helps the customer budget, but it does not claim that a working item will fail on a fixed date.
15Dispatch and maintenance scheduling
For a customer on a managed plan, the coordination of planned work is part of the monthly service. Lambda keeps a rolling calendar of regular tasks such as filter changes, coil cleaning, backflow tests, and seasonal checks agreed with the customer, and it schedules those tasks well before they fall due.
A planned visit is given a written confirmation with a sensible arrival window. The customer is asked to make the site ready for that visit. If a customer cancels a planned visit with less than forty eight hours of notice, a reasonable rebooking charge shown in the proposal may apply.
A scheduled maintenance visit does not fix a fault that was already there but unknown to Lambda. If the visit uncovers a failing part, Lambda reports that finding in writing and gives an estimate for the repair, and no paid repair work starts without the customer approval.
16Inspection and acceptance of completed work
At the close of a dispatch, a repair, or a maintenance visit, Lambda gives the customer a short close out note that says what was done. Where it is useful, a photograph or a simple record is included so the customer can verify the work from a distance.
The customer is invited to inspect the finished job and to raise any concern. If no concern is raised within seven days of the close out note, the job is treated as accepted in the ordinary way, without removing a warranty that applies to a part or to the craft of a responsible vendor.
Lambda enters every completed job into its dispatch logbook. The customer can ask for a copy of its own history at any time while the service runs, and Lambda provides that copy in a readable format at no charge during the relationship.
17Warranty and corrections
Lambda stands behind the scheduling and the coordination that it controls. If a fault in a completed job is caused by a scheduling mistake of our desk, by a wrong dispatch, or by Lambda passing on an incorrect instruction, the correction is made at no charge to the customer.
Whatever applies to parts and installations supplied by third parties is governed by the maker warranty and by the responsible trade. Lambda helps the customer use a valid parts warranty by coordinating with that trade and by keeping the purchase and install date clearly on the record.
No warranty covers harm from misuse, from someone changing the equipment without permission, from the customer failing to maintain the item as the maker instructed, or from normal wear over time. A change a customer makes to a site or a system without telling Lambda may also remove Lambda responsibility for work that then collides with that change.
18Limitation of liability
The value of what Lambda can owe is written to match the size of the desk it runs. To the fullest extent that the law allows, Lambda total responsibility for any claim that comes out of the services or out of this agreement is limited to the total of the fees that the customer paid to Lambda in the twelve months before the claim arose.
Neither party is responsible to the other for lost profit, lost revenue, lost data, lost savings, or other indirect harm that follows from a failure under this agreement, even if that party was told that such harm could happen. These limits survive the end of the agreement.
Nothing in this section removes a right that a consumer holds under a statute that cannot be waived by contract. Where such a right exists, the limits in this section apply only to the extent that the law allows them to apply.
19Indemnification between the parties
Each party answers for its own careless act or its own deliberate wrongdoing. The customer agrees to protect Lambda against claims that follow from site information the customer held that was wrong, from instructions the customer gave that contradicted the written scope, or from changes that the customer people made without telling Lambda.
Lambda agrees to answer for claims that follow from Lambda own carelessness in dispatching or in coordinating a vendor. An indemnity given by Lambda is limited to the amount that the Lambda insurance or the law says Lambda must carry, which keeps the promise true to the real capacity of the business.
An indemnity never asks one party to answer for the deliberate fault of the other. Any claim is handled by first notifying the other party promptly and by allowing that party to defend the matter through its own insurer.
20Insurance and certificates
Lambda carries commercial insurance that is reasonable for an office coordination and service desk business, including liability cover appropriate to the size of the operation. A customer may request a current certificate as a reasonable step before the service begins.
Every licensed trade and specialist vendor that Lambda coordinates is asked to hold the licence and the insurance that its own craft requires. Lambda checks certificates in a sensible way when a working relationship starts and again when a certificate renewal falls due.
Site owner property insurance and site liability cover for the owner own building risks are still the responsibility of the site owner. Lambda does not act as the agent of any customer insurance, and Lambda only holds the contact details it is given about a customer policy.
21Confidential information
Both sides may see the operating records of the other. Customer records, which include site maps, access codes, vendor terms, asset lists, and business plans, are held as confidential and are used only to run the customer service. They are not shown outside Lambda unless that is needed to deliver the service or is required by law.
Lambda records, which include the order of its queue, the way it dispatches work, its logbook format, and the computing tooling built under the LambdaServe developer name, are confidential. A customer may use the tooling while it is a client but may not copy, take apart, or resell it without permission.
The duty of confidentiality has no fixed ending date. It stays in force for as long as the information has value and is not generally known, and it stops only when the information enters the public domain through no fault of the party that held it.
22Records, logbook, and your data
Lambda keeps a record of each ticket, dispatch, and maintenance visit. That record, sometimes called the dispatch logbook, protects both parties whenever a question arises about what was promised and what was done.
While the service runs, a customer may ask for its own records in a readable form at no charge. After the service ends, Lambda holds operational records for the periods and in the ways described in the Privacy Policy published on this site.
Login details and access codes are treated with care. Lambda holds them only where a customer asks Lambda to store them, keeps them protected, and removes them promptly when the customer asks or when the agreement ends.
23Intellectual property and tooling
The written scopes, the logbook format, the reporting templates, and the software that LambdaServe designs belong to Lambda Services Limited Liability Company. The customer keeps the business data that it provides and the reports that relate only to its own operation, to the degree that the law lets a business own such material.
No part of this agreement gives a copyright, a trademark, or a trade secret from one side to the other, apart from the limited rights needed to run the agreed service. A customer may not use the Lambda name or mark so that an outsider thinks that the customer owns Lambda or is Lambda.
When Lambda builds a bespoke integrated support design for a customer under a defined design project, the delivered design belongs to the customer once it is paid in full, unless the statement of work for that project assigns the result differently.
24Termination and suspension
A customer on a fixed monthly plan may stop at the end of the initial term by giving at least thirty days of written notice before the renewal date. A customer on a time and materials project may stop that project with written notice and settles for the work completed and the materials committed up to the stop date.
Lambda may pause the service with notice to the customer if the customer does not pay an invoice that is well past due, breaks a material term, or places Lambda people or a vendor crew in danger. If the cause is not put right within a reasonable time, the pause may become an end to the service.
When the service ends, Lambda closes the open tickets, returns any customer records that were handed over, and issues a final invoice for the work performed. Each side returns the confidential records of the other or confirms that those records have been destroyed. A notice that you intend to stop should be sent to direct@lambdaserve.lol so that the desk can process it without delay.
25Circumstances beyond our control
Neither side is at risk for a delay that comes from a cause outside its own control. That includes a storm, a flood, a fire, a power loss, a break in telephone service, a public health emergency, or a labour problem at a utility that serves the site.
An affected party does not lose the right to rely on such a cause by failing to say so at once, but it must give notice as soon as it is practical after it learns of the cause. Once the cause ends, the party returns to the promised work with all reasonable speed.
If a cause outside a party control continues for more than ninety days, either side may end the affected part of the agreement by written notice, with no further duty beyond paying for the work that was honestly completed before the cause began.
26Governing law and disputes
Both sides will try to settle a disagreement by talking first, between the customer point of contact and the service desk manager. If that discussion does not resolve the matter within a reasonable time, the parties may agree to use a neutral mediator before any court action.
These terms and any claim that comes from them are governed by the law of the State of Utah, United States, without applying its conflict of law rules. A court action that is not settled by agreement will be brought in the state or the federal court that serves Utah County, Utah, and the parties agree to that court for such a case.
Where a consumer statute allows a customer to bring a case in the customer own location, nothing in this section takes that right away. This clause runs only to the extent that the law permits.
27Notices and how to reach us
Notices for Lambda may be sent by email to direct@lambdaserve.lol or by letter to Lambda Services Limited Liability Company, 334 N Colonnade Rd, Saratoga Springs - 84045-4550, United States (US). Messages that only run the daily service, such as a visit confirmation or a reminder that a certificate is about to lapse, may also be given by the help desk over the telephone at +12798994629.
A notice sent by email on a normal working day is treated as received that day, and on the next working day if it is sent later in the day or on a closed day. A letter is treated as received when it is delivered, or on the fifth postal working day after posting if delivery cannot be shown.
Either side may change its notice address by telling the other in the way this section describes. Notes that are part of running a ticket, such as an email that answers a question from a tenant, do not have to follow the formal notice rules in this section.
28Surviving clauses and the full agreement
These terms, along with any signed statement of work and the published Privacy Policy, are the whole agreement about the services that they cover. They replace every earlier talk, note, or proposal about the same subject that has not been written into this agreement.
If a court finds that one clause is not enforceable, that clause is narrowed to the smallest extent needed to make the rest lawful, and every other clause keeps its full force. A decision to overlook one breach is not a choice to overlook any later breach.
No person outside this agreement may claim a benefit from it, and neither side may give its rights away without the consent of the other except where that consent is not withheld unreasonably. These closing clauses give the whole document a clear order and a fair place to begin.
29Contact details for these terms
Questions about these terms, about an invoice, or about the boundary of a scope can be raised with the desk at direct@lambdaserve.lol or by telephone at +12798994629. Legal notice may be mailed to Lambda Services Limited Liability Company, 334 N Colonnade Rd, Saratoga Springs - 84045-4550, United States (US).
If you ask about a clause, Lambda answers in plain language and works toward a fair reading. Where a true edge case calls for a changed term, Lambda will discuss the change in writing before you commit so that there is never a hidden surprise.
Lambda hopes that every working relationship runs cleanly and never needs a lawyer to read a single sentence aloud. When a question does appear, the help desk and the contact details in this section are the fastest path to a straight answer.