A loop is an automated process — something Caddi runs for you. Loopy is Caddi's assistant: you talk to it to build, change, and troubleshoot loops. Loop Studio is where those conversations happen, along with testing, running, and reviewing your loops.

No. You describe what you want in plain English and show Caddi how you work today. Loopy handles everything technical — there's nothing to code or configure.

Caddi connects to 70+ tools your team already uses — email, calendars, document management (iManage, NetDocuments), CRM (Salesforce, Clio, Wealthbox), e-signature, and more. See Tool-by-tool capability for what Caddi can do in each, and the full list at trycaddi.com/integrations.

Yes. Caddi is built privacy-first with SOC 2 controls, engineered for regulated firms. Full details, reports, and documentation are in the Trust Center; see also our Privacy Policy.

Caddi uses AI to understand your process and build the loop. The loop then follows a defined workflow. Some loops may include AI-powered steps whose outputs vary based on the input, but they operate within the decisions, rules, and paths you define. Loopy does not independently change the workflow or make unrestricted decisions on your client data.

You don't build flowcharts or write prompts — you show Caddi how you work and describe the outcome, and it builds a deterministic automation. Detailed comparisons: trycaddi.com/compare.

Simple loops take minutes. A loop with recordings and a few scenarios typically comes together in one sitting. The more clearly you describe the outcome and rules, the faster it goes — see the best practices in Building Your First Loop in Loop Studio.

No. Many loops can be built from conversation alone. When showing is easier than explaining, you can share your screen and walk Loopy through the process. You can also provide PDFs, screenshots, or business rules. If Loopy needs a recording, Loop Studio gives you a checklist of exactly what to demonstrate.

Good candidates are repetitive, rule-based, and have a clear finished result — intake, doc filing, email triage, time & billing, cross-system sync, report generation. See Making your process automatable for small changes that unlock automation, and the workflow library at trycaddi.com/use-cases.

Before building, Loopy checks whether the process you described or showed can be automated. If something is blocking it—usually a missing integration or an unsupported step—it explains why and what to do next. You can connect the missing tool, adjust the process, try again, or ask the Caddi team for help.

Yes. Loopy adapts to how you talk. If you're technical, be direct — name the system, the field, or the API behavior you know exists, and it will skip the beginner framing and work at your level.

Check the chat first: builds sometimes wait on an approval from you, so reply (even just "approve") and it will continue. If Loopy keeps retrying the same fix without progress, stop and escalate — repeated failed attempts are also flagged to the Caddi team automatically.

Not yet — today loops run manually or on a schedule, which keeps every run auditable and covers most needs (a frequent schedule usually gets you close to real-time). Event-based triggers are on the roadmap; if a schedule genuinely can't solve your case, tell us — real use cases drive prioritization.

Yes. From the loop page, select Edit Loop to open Loop Studio, or open Studio directly and describe the change. Loopy creates a test version while your live loop continues running unchanged. Once you have tested the update, select Make it Live.

No. Changes only take effect when you select Make it Live after a successful test. Until then, the live version keeps running as-is.

Once your loops are migrated (by July 31), yes — all editing happens in Loop Studio.

No — run history is visible only to the person who ran the loop. Caddi never shares credentials or data across users who don't have access to it, and run outputs can contain sensitive client information. If a teammate needs to review a run, they can ask the person who ran it.

Yes, loop ownership can be transferred. Note that run history doesn't transfer with it — history stays scoped to whoever ran each run.

Tell Loopy in plain English — "run this every weekday at 8 AM." It confirms the schedule, including timezone, before anything is set.

Caddi explains every run in plain language and quietly fixes routine problems on its own. If something needs you, you'll see it in the run summary — describe the issue to Loopy via Fix an error and it will investigate.

A completed run isn't always a correct one — a "successful" run may simply have found nothing to process. Check what the run actually touched in the summary, then use Ask about a run — Loopy can tell you which records it used, why something was skipped, and what was passed between steps. If the loop misunderstood a rule, describe the fix in chat.

The diagram maps your process onto the technical operations each tool requires, so you'll sometimes see steps that weren't part of how you'd describe the work — like "refresh" steps that re-fetch the latest data, or a step that looks up an ID before downloading a file. That's how the underlying tool's API works, not a misreading of your process. These extra steps are also why loops are so dependable once built: every operation is explicit and runs the same way every time.

Click any step in the diagram and Loopy will explain what it does and why it's there. If a step's name still doesn't make sense for your process, tell Loopy — that feedback improves the loop's documentation.

A Caddi report goes out by email on the first of each month with successful runs and estimated time savings per loop.

Start with Loopy in Loop Studio — it resolves most loop questions on the spot. If it can't, escalate from the same chat and a person from the Caddi team picks it up.

Yes — Loopy now lives in Loop Studio. Use Studio chat for all loop requests; it has full context on your loops and runs.

Check status.trycaddi.com for real-time platform status and incident history.