FAQ for Be AI Assist

Be AI Assist helps busy local businesses stop losing work from missed calls and slow follow-up.

Depending on your package, the system can:

• send an instant missed-call text-back,
• capture basic job details by SMS or voice,
• schedule callbacks or appointments,
• send confirmations and reminders,
• give simple estimate ranges where suitable, and
• escalate urgent jobs for immediate attention.

The main fit is busy local service businesses that miss calls because they are on-site, driving, already with a customer, or stretched on admin.

• Plumbers
• Electricians
• Gas / heating engineers
• Roofers
• Drainage firms
• Locksmiths

It can also suit estate agents, lettings teams, and other service businesses with similar missed-call problems.

No. The aim is to reduce the simple, repetitive work that causes leads to go cold.

It catches missed calls, handles the first few steps, and moves the enquiry forward where possible. You or your team still handle the jobs that need real judgment, site knowledge, or a human relationship.

We keep the offer simple:

• Missed Call Rescue — instant text-back, basic 2-way SMS, callback capture, escalation alerts, weekly summary.
• Lead Capture & Booking — everything above plus booking flows, callback slot scheduling, confirmations, reminders, and lead logging.
• AI Reception Upgrade — everything above plus AI voice receptionist, voice lead capture, voice booking, transcripts, and stronger front-line handling.

The setup fee covers the work needed to tailor the system to your business rather than just switching on something generic.

• message and call flow setup,
• FAQ and response design,
• booking / callback logic,
• emergency routing rules,
• testing and go-live checks.

That depends on the package and the commercial deal you agree with us.

For early-stage or simpler setups, we aim to keep things commercially straightforward and low-friction. If a longer commitment makes sense because of custom work, integrations, or discounted pricing, that is discussed clearly before anything is signed.

Yes — where your service and workflow suit it.

For example, the system can:

• offer available callback windows,
• book survey visits,
• confirm boiler service slots,
• schedule inspections,
• send confirmations and reminders.

The more standard your booking rules are, the more automation we can safely put in place.

Yes, for suitable jobs.

A good example is giving a guide range for a common request like extra sockets, a routine service, or a standard callout type.

We do not recommend pretending every job can be priced automatically. Where a final quote depends on access, materials, risk, or site inspection, the system should make that clear and book the right next step instead.

Many do, especially when they want a quick response and they are already used to messaging businesses.

Not every customer will text back, but an instant reply still beats silence or voicemail. The goal is to recover the customers who are happy to continue that way and stop some enquiries going elsewhere.

Urgent jobs should not be treated like routine bookings.

For emergencies, the system can:

• identify the problem as urgent,
• mark it as high priority,
• alert your team or owner immediately,
• tell the customer to expect a callback ASAP.

That keeps the workflow sensible and safer than trying to push serious problems into a normal calendar slot.

This depends on your trade, but common examples include:

• burst pipes or active flooding,
• burning smells or sparking electrics,
• gas smells or safety concerns,
• water pouring through a roof,
• serious access or security issues.

We agree the emergency rules with you before launch so the system matches how your business handles urgent work.

For a straightforward setup, we usually aim for a practical go-live inside a sensible onboarding window rather than dragging things out.

The exact timing depends on:

• how many workflows you want,
• whether booking logic is simple or complex,
• how quickly business details and FAQs are provided,
• whether there are integrations or not.

Usually:

• your business type and service area,
• common call types,
• basic FAQs,
• what counts as urgent,
• callback or booking rules,
• who should get escalations.

If there is a CRM, calendar, or other system involved, we also need the details required to connect it safely.

Not always. The exact phone setup depends on how your current system works and how you want missed calls handled.

In many cases, the solution can be set up around your existing business number so the customer experience stays simple.

That is normal. Businesses change, services change, and workflows change.

Ongoing tweaks might include:

• new services,
• new callout areas,
• different booking times,
• updated pricing ranges,
• new escalation contacts.

The aim is not to leave you stuck with a rigid setup that no longer matches how you work.

We treat that as an operational issue, not something for you to just “work around”.

Common examples include:

• incorrect reply wording,
• wrong escalation behaviour,
• delayed messages,
• booking logic not behaving as expected.

Part of the service is testing, refining, and tightening these workflows so the system becomes more dependable over time.