LMN

LMN keeps your estimates and your contracts; Zenvox keeps the request and the call. The receptionist recognises a contract customer from the first call and builds the estimate request.

7 days, 20 answered calls, no card

Where your request lands

The request is written into Zenvox: customer, address, type of work, stated area and workable times. LMN keeps the truth of the estimate, the contract and its milestones. Through the connection, Zenvox reads the customer, the estimate and the contract to attach the call to the right file; it writes nothing into LMN.

LMN follows a specific chain: the estimate export toward accounting, invoices built from the contract, and a configurable status change at export. A status change at export is no proof the customer accepted, and Zenvox does not read it as one.

LMN prices from hours and materials and turns a signed contract into invoices; the season is short in Canada, and an estimate lost in spring is lost for the year.

Read, create, update, cancel

Acceptance is observed where the customer gave it, not at an export. The four actions follow from that distinction.

ActionWhat that means
ReadShe finds a customer, estimate or contract in LMN, and recognises a contract customer from the call itself.
CreateThe estimate request is created inside Zenvox during the call: project type, site scale, address, target season. The estimator picks it up in LMN.
UpdateEstimate status belongs to your sales chain. Zenvox moves nothing there, and does not infer acceptance from a successful export.
CancelCancelling a contract or a billing milestone touches a signed commitment. A person does that, inside the software.

What is included, what needs an add-on

Come spring, a landscaper answers from an excavator seat or not at all. Taking every call, telling a large build apart from a maintenance enquiry, noting scale and address, and alerting right away on a big job: that is your base, and that is what fills the book ahead of competitors.

Add-ons that work with your software

Assisted estimates

The file built during the call, then follow-up until the answer is clear. On landscape builds, the estimate leaves in spring and the decision lands weeks later: without follow-up, it fades.

Contracts and recurring service

Seasonal maintenance, spring openings, fall closings and renewals: a contract customer is identified from the records you authorise.

Authorisation, and where truth sits

Reading is authorised from your account. What follows says who holds truth on what.

  • Your account stays yours; Zenvox asks for no credentials
  • LMN holds the truth on pricing, contracts and billing milestones
  • Estimate acceptance is observed where the customer gave it, not at a successful export
  • Zenvox holds the truth on the call: what was asked, by whom, at what hour, with the recording

Tax, site, estimate and invoice live in LMN, and payment methods are those of your LMN account.

A Tuesday in late April, peak season. The owner is on a site, machine running.

CustomerI would like my driveway redone in pavers, and a retaining wall along one side of the house.

ReceptionistI will take your name and a callback number first. Do you have an idea of the area, in feet or metres, even roughly?

ReceptionistIs that work for this season, or are you planning ahead for next year? I am noting the address with the postal code, and the owner calls you back to set an estimate visit.

The owner receives a full request while working: project type, scale, target season, address. He calls back that evening and books the visit. No price was floated over the phone, since paver work is priced on site.

If no connection exists

Without a connection, the receptionist works in Zenvox, and your season loses nothing.

  • The request is created in Zenvox, with the project scale and the target season
  • The estimator re-enters it in LMN once, instead of calling back to obtain it
  • Estimate follow-up goes out without anybody thinking about it, and stops at the answer
  • Every base capability works without this connection

Questions about this connection

Does a successful export mean the customer accepted?

No. A status change at export is no proof the customer accepted: acceptance is observed where the customer gave it. Zenvox does not infer acceptance from a successful export.

Is there a connection to LMN?

Yes, for reading: Zenvox finds the customer, the estimate and the contract to attach the call to the right file. The estimate request is created inside Zenvox during the call, and the estimator picks it up in LMN.

What changes during the season?

Come spring, a landscaper answers from an excavator seat or not at all. Every call is taken, a large build is told apart from a maintenance enquiry, scale and address are noted, and a big job raises an alert straight away.

Does the estimator have to re-enter everything?

He re-enters it once in LMN, instead of calling the customer back to obtain it. LMN holds the truth on pricing, contracts and billing milestones; Zenvox holds the call, with its hour and its recording.

What about chasing the estimate?

It leaves without anybody thinking about it and stops at an answer. On landscape builds the estimate goes out in spring while the decision lands weeks later: the Assisted estimates add-on holds that follow-up, connected or not.

Where to next

See the trade concerned, or the full software list.

LMN

LMN keeps your estimates and your contracts; Zenvox keeps the request and the call. The receptionist recognises a contract customer from the first call and builds the estimate request.

Start your free trial7 days, 20 answered calls, no card