Frequently Asked Questions

Butler is an AI task assistant built to carry supported work through to an outcome, not merely add another item to a to-do list. It researches, uses connected tools, records what happened, and asks for approval at defined authority boundaries.

Research and comparisons, Phone calls, Email, Calendar, Supported web tasks, Reminders and recurring tasks.

No. Websites, vendors, account permissions, payment walls, and third-party services can block a task. Butler is designed to report verified outcomes, identify what blocked completion, and use another available channel rather than fabricate success.

Butler can call real businesses, identify itself as an AI assistant, record the outcome, and provide a transcript or recording when the provider returns one.

Butler treats the call transcript and meaningful talk time as evidence. A provider label such as “answered by human” cannot, by itself, prove that a conversation happened.

Butler can draft and send email. Draft-only requests cannot send, and any send approval must show the recipient, subject, and full body.

Butler can read Google Calendar, check availability, and create events, including all-day and multi-day events on a named calendar such as your family calendar. Forward any email with dates in it to butler@trybutler.xyz and Butler adds every event it finds. Guest invitations and deliberate double-booking require explicit approval.

Yes. Forward the email from the address on your Butler account to butler@trybutler.xyz. Butler reads it, pulls out every event, deadline, or appointment (a school week and a one-hour info call in the same email become two events), keeps join links and addresses in the event notes, and adds them to your Google Calendar. Type a note above the forwarded message, like "add to the family calendar", and Butler uses that calendar. If Google is not connected yet, Butler asks you to connect it once and then finishes the job.

No. Reading the calendar and adding a conflict-free personal block are lower-authority actions. Sending guest invitations or knowingly creating an overlapping event requires an explicit approval recorded through the user-reply flow.

Butler can work through supported website flows, but site behavior varies. It stops for payment, login, CAPTCHA, or final checkout when user control is required, and it does not claim a booking or purchase without confirmation evidence.

Yes. Butler uses AI and third-party services, so errors remain possible. The product reduces risk with deterministic action guards, an execution ledger, idempotency for mutations, evidence checks, and explicit approvals for higher-authority actions.

It should not. Personal identity fields must come from the user’s request or verified profile data. Ungrounded names, phone numbers, and labeled form values are rejected before the action executes.

Current plans and included credits are shown on Butler’s pricing page and in the app. Those live surfaces are the source of truth because plan limits can change.