Leskly

The Leskly Assistant · Built on Claude by Anthropic

Your office manager’s
best first draft.

Leskly’s assistant handles the work between a customer’s message and a finished job. Claude reads the request, uses Leskly’s tools to look up the customer, the property, your prices, the forecast, and your crews, and proposes the estimate, the visit, and the messages. Your rules decide what sends on its own and what waits for you.

Turn on JavaScript to see the assistant at work. Each step is described below.

How a request runs

Read. Look up.
Propose. Check. Record.

The assistant works through the same records and rules as your team. It can only do what a person in your company could do in Leskly.

  1. 1

    Read the request

    A customer email, a forecast change, a crew running late, or a question from the owner. Claude works out who it’s about and what needs to happen.

  2. 2

    Look up what it needs

    Claude calls Leskly tools instead of guessing: the customer and their history, the property and its lawn area, your service prices, the forecast, crew capacity, and the route.

  3. 3

    Propose concrete actions

    The output is structured work, not just text: an estimate with line items from your catalog, a visit on a specific crew and time, and the customer and crew messages that go with it.

  4. 4

    Check your rules

    Each action is checked against the rules you set. Weather moves within a few days might run on their own; new estimates, large changes, and invoices wait for approval.

  5. 5

    Act and record

    Approved actions run through the same validated changes as a person’s edits. Every tool call, draft, and action is in the activity trail, so you can see why something happened.

Tools

What the assistant
can reach.

Tools are typed functions over your Leskly data. Lookups run freely; anything that changes your schedule or reaches a customer goes through your rules.

ToolWhat it doesRules
find_customerMatch an email or phone number to a customer, with visit and payment historyLookup
get_propertyProperty details: lawn and bed areas, access notes, gate codesLookup
get_service_pricesYour service catalog, rates, and per-area pricingLookup
check_forecastHourly forecast for your service areaLookup
find_crew_slotOpen crew time that fits a duration, a time window, and the routeLookup
query_visitsVisits by date, crew, status, or billing stateLookup
plan_routeReorder a crew’s stops to cut driving timeLookup
draft_estimateCreate an estimate with line items from your catalogDraft
schedule_visitBook, move, or hold a visit on a crew’s dayYour rules
draft_invoicesTurn completed visits, time, and materials into invoice draftsDraft
send_messageEmail or text a customer, or post to a crew’s channelYour rules

Models and data

Claude, used
with care.

Leskly uses Claude models through the Anthropic API, matched to the job.

Models

The right model for each step.

A fast Claude model sorts and matches incoming email. A more capable one builds estimates, replans days, and writes customer replies.

Anthropic API · tool use
Data

Only what the task needs.

Each request sends Claude the records it needs and nothing else. Anthropic does not train its models on data sent through its commercial API.

No training on your data
Control

You set the limits.

Choose what runs automatically, set price and schedule limits, and keep quiet hours for customer messages. Every action is recorded, and schedule and record changes can be reversed.

Rules & activity trail

See it with your own work

Bring us an email
from last week.

We’ll walk through how Leskly would handle it, from the first lookup to the booked visit, and set up the rules that fit your business.

Book a walkthrough