FAQ
Answers before you automate.
The short version: we design, build, and run automation systems that plug into the tools you already use. Below are the questions teams usually ask before they let us touch their calendar, CRM, or client messaging.
How the systems work
Do you replace our booking system or CRM? ⌄
No. We sit on top of what you already use. We connect to your calendar, PMS, or CRM and trigger reminders, routing, and follow-ups from there so your team doesn’t have to learn a new system or move data around.
What kind of results should we realistically expect? ⌄
Industry data shows teams typically see 20–40% fewer no-shows once SMS reminders and follow-ups are running vs manual or email-only reminders. Exact numbers depend on your baseline, audience and how aggressive you want the flows to be.
How “AI” is the AI Receptionist? ⌄
It’s not a chatbot bolted to your website. We build a constrained agent that answers FAQs, routes messages and calls, books appointments, and hands off to humans when needed. It’s trained on your policies and knowledge base, not the whole internet.
Will this create more work for our team? ⌄
The goal is the opposite. We design flows so your team deals with exceptions only edge cases, escalations or high-value conversations not routine reminders, confirmations, and follow-ups.
Implementation, pricing & support
How long does setup usually take? ⌄
Most teams go from “nothing live” to production systems in 7–14 days. The timeline is mainly driven by how quickly we can get access to your tools, agree the reminder / routing logic, and run a short test phase.
How do you price projects? ⌄
We price on complexity, volume, and ownership. Simpler, single-location reminder systems are at the lower end; multi-location setups with advanced routing, custom campaigns, and ongoing optimisation sit higher. You’ll always see a clear monthly range before we start.
Who owns the data and phone numbers? ⌄
You do. Numbers, message logs, and reporting stay in your Twilio account, CRM, or data warehouse. We work inside your stack so you’re not locked into a mystery platform.
What support do we get after launch? ⌄
We don’t disappear after go-live. Greyfall monitors deliverability and key metrics, ships tweaks when you change policies or offers, and suggests improvements based on reply and show-up rates. You tell us the outcome you want; we keep tuning the system to get there.
Still have questions?
Send us your current workflow and one or two bottlenecks. We’ll reply with a Loom walkthrough—not a hard pitch— showing what we’d automate first and what it should realistically move.