Muse WorkflowPlaybooksPlan a workflow
← All playbooks
Property tasks / Practitioner report

Prepare contractor calls and estimate requests

Turn a repair description into a consistent brief you can send to several providers.

MuseIntermediateOriginal editorial guide

What you’ll produce

A scope brief, call script, provider shortlist, and quote-comparison template.

Inputs & connections

  • A clear repair description and approved photos
  • Location, access constraints, and preferred schedule

Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.

Your starting prompt

Replace the bracketed fields. This is our suggested prompt, not a quote from the source.

Prepare an estimate-request pack for [repair] at [general location]. Summarize the supplied scope without diagnosing beyond the evidence. List clarification questions, information each provider should quote, and an appointment script. Research candidate businesses with official source links. Do not call, send photos, disclose a full address, accept an estimate, or book a visit without my specific approval.
Open Muse ↗

How to run it

  1. 01

    Clarify what is known, what is uncertain, and which photos can be shared.

  2. 02

    Prepare one scope brief to make provider responses comparable.

  3. 03

    Verify provider details and review the call script or draft message.

  4. 04

    Use approved communication manually, or a calling feature only if available and authorized.

KEEP A PERSON IN THE LOOP

Review before you act

The owner checks scope, provider credentials, address disclosure, access arrangements, and the quote details.

Limitations & success checks

  • The source uses a beta calling capability that may not be available in your account.
  • An AI-prepared brief is not a professional diagnosis or proof a contractor is qualified.

Measure: Complete comparable responses and clarification rounds required.

Sources & attribution

The sources below support the reported example or a tool capability. They do not validate our prompt or prove the outcome in your environment.

Practitioner reportContractor calls with Muse ↗

September 14, 2026. Reports beta calling and follow-up email. Calling access is not assumed; this guide also works as a preparation-only workflow.

Creator / publisher: Zach Solomon

Official documentationIntroducing Muse ↗

Official introduction of the personal agent. Connector access, account availability, and action permissions still need to be configured.

Creator / publisher: Meta

Editorial review: 2026-10-11. How we label evidence.

FROM A USE CASE TO A WORKING SYSTEM

Have a workflow worth building?

Ferociter plans and builds AI workflows for hospitality and commercial real estate teams.

Talk through your project ↗