By Bedrock Automations Team. Updated .
Buying from an AI agency is new for most owners, and the pitches sound alike. These questions separate a build you can rely on from a demo that falls apart. You do not need to understand every technical detail. You do need to know what the system will do, who is responsible and what happens when something goes wrong.
Ask the same questions of every provider and keep the answers together. Request a demonstration where possible and written terms where an answer affects ownership, costs or responsibilities. A confident sales conversation is useful, but it is not a substitute for a scope your team can check.
Start with the demo and the handoff
1. Can I hear a demo built for my business before I pay?
Why it matters: a polished generic conversation does not show whether an agent understands your services, your booking rules or the language your customers use. Ask to hear ordinary calls and awkward ones. Try a caller who changes their mind, interrupts or asks for a service you do not offer. Use made-up customer details in the demonstration, not private records.
A good answer sounds like: 'We will demonstrate your main call paths using the rules you give us, and you can test what happens outside those rules.' Ask which parts are actually connected and which are being simulated. A simulated booking can be useful, provided nobody presents it as proof that the live calendar connection already works.
2. What happens when the AI can't handle a call or question?
Why it matters: every system needs a boundary. A caller may ask for a person, describe an urgent situation or say something the agent cannot understand. The answer should cover transfer, escalation and the fallback when your team is unavailable. A message sent to an inbox is not the same as a confirmed handoff.
A good answer sounds like: 'These situations go to your team through this route. If nobody answers, this is the callback process and the record your team receives.' Have the agency demonstrate a failed transfer. When comparing an AI receptionist, pay as much attention to the exception path as the greeting.
Know who supports it and what you own
3. Who builds it, and who supports it after launch?
Why it matters: the person selling the system may not be the person building or maintaining it. Your hours, staff, services and booking rules will change. Ask who makes those changes, how you report a problem and what support covers. Find out who checks a reported failure and how your team knows it has been resolved.
A good answer sounds like: 'This role owns the build, this role handles ongoing support, and this is how you request changes or report an outage.' Ask for the process in writing, including what requires an extra project. Do not assume every future change is included just because the initial pitch says the service is managed.
4. Who owns my data, my phone numbers and the setup if we part ways?
Why it matters: exporting customer records, keeping a phone number and transferring an automation setup are separate issues. A provider may answer one and leave the others unclear. Ask whose account holds each asset, what can be exported and what assistance you receive when leaving. Your existing business number should not become an unexplained dependency.
A good answer sounds like: 'The agreement identifies ownership for each asset, the export format and the steps for moving away.' Request an example export using fictional data. Ask which parts of the setup are transferable and which depend on the provider's tools. Do not accept a broad ownership promise in place of specific exit instructions.
Check data protection and real connections
5. How is my customers' data protected?
Why it matters: call records and customer details may pass through more than one provider. Ask for written data protection terms, encryption details, access controls and retention rules. Find out who the AI providers are, what information they receive and how they use it. Ask what happens if a record needs to be deleted or an incident needs investigation.
A good answer sounds like: 'Here are the written terms, the providers involved, the access rules and the retention process.' If you handle health information, ask your qualified compliance adviser whether a business associate agreement is required and whether the full provider chain can support your obligations. This is general information, not legal advice; have your attorney or appropriate adviser review the arrangement.
6. What does it connect to, and how?
Why it matters: a native connection, a workaround and a manual task can produce a similar-looking demo while creating different maintenance needs. Ask how the system connects to the phone system, calendar and CRM you already use. Have the provider explain what is read, what is written and what happens when the connection fails.
A good answer sounds like: 'This action uses a direct connection, this one uses an intermediate workflow and this part still requires staff.' Ask how duplicate records and conflicting appointments are handled. For custom AI agents, define the allowed actions clearly so a broad promise to automate does not become permission to change anything in your business tools.
Get complete costs and clear compliance responsibilities
7. What's the all-in cost?
Why it matters: the headline monthly amount may not describe every charge. Ask about setup, monthly service, usage such as per-minute charges, phone numbers and overages. Find out what triggers extra costs and whether tools billed by other providers are included. Request a breakdown without relying on a low-usage demonstration as the spending model.
A good answer sounds like: 'These items are included, these vary with usage and these require approval before additional work begins.' Ask the agency to explain the bill under your expected workload and a busier period, clearly labeled as hypothetical scenarios. You are checking the charging rules, not asking for a promised return on investment.
8. How do you handle compliance?
Why it matters: call recording consent, outbound contact and AI disclosure are not details to settle after launch. Some states require everyone on a recorded call to agree. Outbound calls and texts require review of consent and opt-outs, and the rules depend on the activity and circumstances. This is general information, not legal advice. Ask your attorney and the relevant authority which requirements apply.
A good answer sounds like: 'We document the approved disclosure and consent process, preserve contact preferences and define who reviews the rules.' Ask what happens when someone declines recording, requests a human or opts out of contact. The agency should explain its implementation role without promising that a standard script makes every use compliant.
Agree on reporting and the exit before signing
9. How will we measure whether it's working, and what reports do I get?
Why it matters: an answered call is not necessarily a booked job. Decide which outcomes matter to your business and how they will be checked against real records. Ask to see the report format, how exceptions appear and who reviews missed handoffs. Keep spam, duplicate inquiries and existing-customer questions separate from new opportunities.
A good answer sounds like: 'We agree on the baseline, define these outcomes and review this report with you.' Start with your own call and booking records. The Missed Call Calculator helps frame a leak estimate, but it is not proof that an agency will recover that amount. Ask how reports connect activity to confirmed outcomes without counting the same caller twice.
10. What's the contract length, and how do I cancel?
Why it matters: support, billing and exit obligations continue after the demonstration. Read the contract for renewal, notice periods, cancellation steps and any remaining charges. Ask what happens to open appointments, call routing and data exports when service ends. A smooth exit matters even if you expect a long working relationship.
A good answer sounds like: 'The agreement spells out the term, notice process, final charges and transition responsibilities.' Have your attorney review terms you do not understand. Do not rely on a verbal promise that cancellation is easy when the written process says something different. Keep a copy of the agreed scope alongside the contract.
Red flags to take seriously
- Guaranteed results without a review of your own records, operations and constraints.
- No custom demo, or a refusal to let you test a difficult conversation.
- Vague handoff answers that do not name a receiving person or explain the unavailable-team fallback.
- Long lock-ins pushed before you understand the scope and transition process.
- Refusing to put data ownership, protection and export terms in writing.
- Testimonials you cannot verify or claims presented without permission to check them.
A provider does not need an instant answer to every question. It does need to distinguish what it knows from what it must check. 'We will confirm that connection before you commit' is more useful than a promise that everything works with everything. Watch whether uncertainty becomes a documented action or disappears from the conversation.
If you are still comparing approaches, read AI receptionists versus answering services and hiring. The right choice depends on the calls you receive and the work your team needs help with, not on which pitch uses the most impressive terminology.
How we answer these
Bedrock Automations offers a custom demo before you commit through the Live Demo step. Urgent calls can hand off to your team. Every client signs a Data Protection Agreement. You own your data and can export it anytime, and there is one monthly bill for all tools.
Use the questions above to examine those points against the work you need. Bring your services, booking rules and the calls your team finds hardest to handle. A useful conversation starts with your operating requirements, then checks whether the demonstrated workflow fits them.
