Behind our 48-hour go-live promise

Step 1: Launch Profile — you tell us how your phone actually works

Everything starts with a structured brief we call the Launch Profile. You don’t write prompts or touch software — you tell us how your business handles calls today and how you want them handled going forward:

• ›Services you offer, and the pricing or ranges you’re comfortable quoting on the phone.
• ›Hours, locations, and the exceptions — holidays, half days, the Tuesday the office closes early.
• ›Booking rules — appointment types, durations, which provider or crew takes what, and the buffers your calendar actually needs.
• ›Escalation rules — which calls should go straight to a human, and to whom, at what hours.
• ›The systems we should write into: your booking platform, CRM, or POS.

Step 2: Agent Build — the brief becomes a working agent

Our team turns that brief into conversation flows, a library of approved answers, and routing logic. The agent answers only from the facts you gave us — it doesn’t guess at your prices or improvise your policies. If a caller asks something outside the approved material, the flow routes to a human rather than making something up.

This is also where integrations get wired: booking written straight into Google Calendar or your scheduler, leads into HubSpot or Salesforce, orders into Toast, jobs into ServiceTitan — whatever your stack is, the goal is that nobody on your team re-keys anything.

Step 3: Voice Testing — nothing goes live untested

Before a single real customer hears the agent, we run real-scenario test calls against it: the booking that goes smoothly, the caller who rambles and changes their mind, the question with no approved answer, the upset caller who needs a person immediately.

We tune the wording, the pacing, and the escalation triggers until the agent handles your scenarios the way you would. This step is the unglamorous one, and it’s the one that separates an agent callers are happy to talk to from one they hang up on. Nothing goes live untested — that’s a rule, not a slogan.

Step 4: Go Live — and what switches on with it

We connect your phone flow — typically call forwarding from your existing number on day one, so nothing about your number changes for callers. From the first live call, the agent answers in under two seconds, books and captures into your systems, and transfers to your team with context when a call needs judgment.

Go-live also turns on your visibility: call summaries, full transcripts, and review tools, so you can read exactly what the agent said and did on every call. In the first week or two, that’s where the remaining tuning comes from — real calls always surface a wording tweak or a new FAQ to approve.

Why 48 hours is possible (it’s not magic)

Two reasons, and neither is a shortcut:

• ›Industry-tuned starting points. We’ve built agents for 20 verticals — restaurants, home services, dental, legal, mortgage, and more — so we don’t start from a blank page. The booking flows, common questions, and escalation patterns for your industry are already drafted; your Launch Profile customizes them rather than creating them.
• ›A team that does this every day. The thousand small decisions — how to phrase a price range, when to offer the next available slot versus asking for a preference, what counts as an escalation — are decisions we’ve already made many times. With DIY, every one of those is a decision you make alone, then test alone.

What honestly makes it take longer

I’d rather tell you this up front than hit 48 hours on a technicality:

• ›Complex or custom integrations. Standard connectors are fast. A legacy system, a custom API, or unusual write-back rules can add days — we’ll tell you before we start, not after.
• ›Number porting. If you want to move your number to us entirely (rather than forward it), the porting timeline is set by the carriers, not by us — industry estimates commonly put it at a week or more, sometimes longer. That’s exactly why we go live on forwarding first and let the port complete in the background.
• ›Approval cycles on your side. If your scripts need sign-off from three partners and a franchisor, the calendar reflects that. The 48-hour clock assumes someone can answer our questions and approve the test calls.
• ›Multi-location rollouts. One location in 48 hours is normal; twelve locations with different hours and menus is a staged rollout, and we’ll map it with you.

Frequently asked questions

Keep reading

• How MapleVoice works →
• Integrations we connect to →
• The AI receptionist playbook →