Questions owners ask
What about crew data and privacy?
We scope to the minimum data each workflow needs, usually site names, service types, contract dates and customer contact details. Crew personal or HR data isn't needed for these workflows. We ask for access scoped to what the build requires, and we document which tools and accounts are touched. During discovery we tell you which third-party services would process data, so you can check that against your own contracts and policies. Our privacy policy is at audit.relaycairn.com/privacy.html.
What does the AI draft, and what does a human send?
The AI drafts follow-up emails, acknowledgement replies, crew-lead task notes and renewal outreach, and it flags stalled quotes and overdue closures. A person on your team reviews and sends customer-facing messages. Approval gates are part of the build, and nothing is sent to a customer on its own unless you explicitly choose that for a specific low-risk step.
How does seasonality affect timing of a build?
We plan around your calendar. Pre-renewal snow outreach is best built and tested before the season, and spring bid follow-up before bid volume peaks. We'd rather schedule short review sessions than pull crew leads out during your busiest weeks. The schedule is set in the written scope after discovery, and we'll tell you honestly if the timing you want isn't realistic.
Do you work with LMN, Aspire, Jobber or QuickBooks?
These are the kinds of tools we build around, but we don't assume a given connection exists. In discovery we check what your specific plan and setup can connect to or export, and the scope states exactly how each workflow gets its data.
Do I need to change software?
No. The aim is to add a follow-up and recovery layer on top of your current tools, not to replace your field-service or accounting platform.