Handle tree service calls with a workflow your team can review.

Current Reece product assurances

• Keep your business number: Use your provider's forwarding instructions for all calls or missed calls only.
• Cover configured calls 24/7: Answers configured business calls 24/7, including after-hours and overflow calls.
• Review call results: The web dashboard keeps call recordings, transcripts, AI summaries, caller details, and outcomes together.
• Test without a card: 7 days and 60 call minutes are included.

Representative call—not a customer recording

Caller: I am calling about tree removal estimate.

Reece: I can collect the details your tree service team uses for the next step.

Boundary: Reece records the request and applies the approved rule; the business confirms professional judgments and commitments.

Separate tree service calls before asking a long questionnaire

Tree removal estimate, Pruning inquiry, Storm-related observation, Stump or debris request are different caller jobs. A useful receptionist identifies the job first, then asks only the questions that change the callback or routing decision. That keeps a routine inquiry from following the same path as a time-sensitive or existing-customer request.

• Tree removal estimate
• Pruning inquiry
• Storm-related observation
• Stump or debris request

Create a concise, reviewable intake record

The approved field set should cover property location, caller-described tree condition, nearby structures or utilities, storm and access context. Each answer belongs in a call record that a team member can review alongside the recording, transcript, summary, caller details, and outcome. Avoid collecting sensitive or speculative information that the team will not use.

• property location
• caller-described tree condition
• nearby structures or utilities
• storm and access context

Use the tree-call risk-boundary and intake map

The central planning tool on this page is a tree-call risk-boundary and intake map. Write the allowed questions, stop conditions, destination, fallback, and owner of the next action in plain language. Then test the map with a straightforward request, an incomplete answer, a changed detail, an unsupported question, and a destination that does not answer.

Keep promises with the people who can authorize them

No arborist assessment, safety clearance, emergency response, or crew promise. Reece may repeat a current, business-approved fact when the caller and request fit the rule. When the facts do not fit, the truthful action is to acknowledge the limit, capture the request, and send it to the configured destination rather than infer an answer.

Product boundary: No arborist assessment, safety clearance, emergency response, or crew promise.

Define the next step and its evidence

Apply the tree company's approved escalation boundary and let qualified staff assess risk, access, and service. A request, captured preference, fallback link, or transfer attempt is not the same as a completed appointment or accepted job. Name the outcome accurately in the call record so the receiving employee knows what happened and what remains open.

Design after-hours and no-answer behavior

Outside normal hours, decide which tree service requests should be recorded for the next work period, which should attempt an approved destination, and when automation must stop. If a transfer destination or provider does not complete the action, use a documented fallback; never imply that a person, crew, appointment, or response has been secured when it has not.

Run evidence-led acceptance calls

Test at least six calls: a common tree removal estimate, a different service path, a caller who corrects an answer, an unsupported request, an after-hours call, and a failed next step. Review the recording, transcript, summary, captured fields, routing outcome, and staff follow-up. Revise the flow before relying on it.

Translate approved knowledge into caller-safe answers

Tree removal estimate, Pruning inquiry, Storm-related observation, Stump or debris request are different caller jobs. A useful receptionist identifies the job first, then asks only the. Use that source material to write short approved answers, but preserve conditions, exclusions, dates, and ownership. Website import can propose knowledge for review; it does not make every sentence current or safe to say on a call. Mark facts that change often—hours, service areas, prices, availability, provider connections, and transfer destinations—and assign an accountable employee to approve them. When two sources conflict, keep the item inactive until a person resolves it. When a caller asks beyond the reviewed source, Reece should acknowledge the limit and take the approved conservative action instead of filling the gap from general knowledge.

Label every outcome by evidence, not by intention

The approved field set should cover property location, caller-described tree condition, nearby structures or utilities, storm and access context. Each answer belongs in a call record that a. Define outcome states as answered, routed, deferred, stopped, or awaiting review. A requested appointment is not a booked event, a configured transfer is not a connected call, and a captured phone number is not a qualified lead. For each state, specify what appears in the recording, transcript, summary, caller fields, action result, and employee queue. This vocabulary should be shared by the call flow, dashboard review, analytics event, and operating playbook. Consistent labels let a reviewer distinguish product behavior from staff follow-up and prevent an attempted action from becoming an unsupported completion claim in reporting or customer-facing copy.

How Reece handles the call

1. Forward the calls you choose. Keep the number customers already know, then use your phone provider's instructions to forward all calls or missed calls only to Reece.
2. Reece answers with approved knowledge. Reece answers the configured call and uses business knowledge the owner has reviewed before it becomes active.
3. The caller explains what they need. Reece answers approved FAQs and gathers the caller, request, and intake details needed for a clear next step.
4. A supported handoff happens. Eligible Scale and Growth setups can use configured direct or warm transfers. Otherwise, Reece records details or an appointment request for staff follow-up.
5. Your team reviews the result. The recording, transcript, summary, caller details, and outcome stay together in the responsive web dashboard.

Your team stays in control. Reece handles approved call intake and configured routing. Your team still owns diagnosis, safety decisions, pricing, dispatch, appointment confirmation, and any follow-up that needs a person.

Start free 7-day trial

Know the handoff before you forward a call

Can I keep my current number?

Plans include 1, 3, or 10 Reece phone numbers. Businesses can keep an existing number and forward selected calls to Reece.

Can Reece take missed calls only?

Yes. Choose missed-call forwarding when staff should have the first chance to answer, or forward all calls when Reece should answer first. Your provider controls forwarding behavior.

What if the caller needs a person?

Scale and Growth support owner-configured direct and warm transfers. Reece does not include a staffed human fallback, so the team must define the follow-up path for calls that are not transferred.

Does an appointment request mean booked?

Reece can capture appointment requests, preferred times, caller details, and approved intake answers for staff follow-up. The current production UI does not offer customer-configurable calendar connections or direct provider-backed booking, so Reece does not report an appointment as confirmed.

Setup is guided, but completion time varies with business rules, transfer routing, testing, and carrier forwarding. Call results are available in the web dashboard. Production email delivery and SMS notifications are not currently offered.

Privacy and sensitive calls. Review the current Privacy Policy and Terms before forwarding calls that may include sensitive information. Reece does not claim HIPAA compliance; medical, legal, emergency, financial, and other consequential calls may require a qualified person. Privacy Policy · Terms

Questions, answered