Skip to main content
A lead arrives at 7:12pm. You mean to answer after dinner. By 9am they’re already talking to somebody else. The valuable work isn’t “write an email.” It’s checking for the lead, reading the inquiry, checking your calendar, preparing the right response, and stopping once a person has replied. That’s one AI employee with a clear job.
Writes follow your tool permissions. Keep messages, CRM updates, bookings, and submissions on Ask while you test. Runner stages each write as an Action Card. Browser bookings and submissions add a final confirmation before they’re submitted.

​
Recurring jobs around a transaction

Each Runner works independently. Runners can read the same source apps, but they don’t pass work or results to one another automatically.
Don’t give one AI employee the whole transaction. Start with the lead that needs a reply.

​
Start with: lead response

A user-created Runner becomes active as soon as it’s created. Review its schedule and permissions, then click Run now. A Runner that fires twice a day uses more of your plan. Start once a day if a second check isn’t worth the cost. Turn on Carry unresolved Action Cards into new runs so a pending reply can appear at the next check instead of being drafted twice. The card still expires 24 hours after it was staged. Run it with a few test inquiries first. Read every reply. Fast and wrong isn’t better than slow.

​
Save the job rules

Use a real estate Project for background such as service area, property types, lead owners, and source locations. Put these in the Runner’s saved prompt:
  • Working hours and routing rules.
  • Approved voice and response templates.
  • The minimum gap between follow-ups.
  • Fair housing, brokerage, and legal boundaries.
  • Actions that always need you or your broker.
Keep live lead status in the CRM and conversation status in email. Each run reads those sources again. It doesn’t automatically remember the prior run’s output. Start every send and CRM write on Ask. Keep offer, contract, booking, and submission decisions behind a person.

​
Other jobs to schedule

​
Lead follow-up

Run every weekday morning. Find open leads with no reply or next step after the gap you set. Read the actual thread before drafting anything. Stop when the source says the person replied, opted out, or the lead closed.

​
Showing prep

Run each morning. For today’s showings, gather the client thread, calendar details, and property documents you provided. List missing instructions instead of filling the gaps with guesses.

​
Seller update

Run every weekday at 5pm. If Calendar shows no showing that day, stop. Otherwise, draft a short update from confirmed activity, feedback, and open questions. Don’t invent buyer interest or market signals.

​
Weekly pipeline review

Run Friday afternoon. Pull current CRM status, recent client threads, and next week’s dates into one list. Flag missing owners and next steps. Don’t rank people by vague labels such as “hot” unless your CRM contains an explicit rule.

​
Speed matters. So does trust.

The first win is simple: new leads get checked on schedule, the reply uses real context, and nothing sends before you’re ready. Then you add the next Runner.

​
What’s next?

Connect your apps

Link Gmail, Calendar, and the CRM you use.

Which AI employee should you add next?

Find the next job closest to revenue or cost.

Tool permissions

Keep messages and submissions behind review.