DeploymentsJuly 30, 2026

What two weeks of MetisPro actually looks like.

People ask us "so what happens in the pilot?" often enough that it deserved a straight answer. Here's what a typical two-week MetisPro pilot looks like, in five stages.

The five stages.

Days 1–2

Discovery.

We spend an hour with your team learning your business. How calls come in today. Who answers them. What the top five reasons for a call are. What escalates. What waits for morning. Which systems you use (calendar, CRM, PMS). What "good" sounds like.

Days 2–4

Design & build.

We design the agent — greeting, tone, top-5 conversation flows, escalation rules, integrations. You review a draft. We iterate. Meanwhile, we provision the phone number (or configure forwarding from your existing line), wire the integrations, and stage the deployment.

Day 5

Go-live.

Agent goes live on the pilot line. We monitor closely for the first 24 hours. Any surprise in a real call gets addressed same-day. This is the day where 90% of the "wait, we didn't think about that" moments happen. That's why it's day 5, not day 1.

Days 6–10

Live operation & first review.

Agent runs live. We hold the week-one review call on day 10 with actual transcripts and metrics: total calls handled, calls answered, escalations triggered, appointments booked (or leads captured), average call time. This is where the ROI story starts becoming real numbers.

Days 11–14

Iteration & decision.

We tune based on week-one feedback. New flows added. Escalation rules refined. Any missed calls or bad transfers investigated. Week-two review on day 14 with the full performance report. From there, you decide: extend, scale to production, or archive. No auto-conversion.

What we usually discover in the first review call.

Every business has 2–3 conversation flows they didn't know they needed until they saw the transcripts. Sometimes it's a specific product question that comes up more than expected. Sometimes it's a routing rule that needs to send after-hours differently on weekends. Sometimes it's a callback pattern where the agent should offer to have a human call back, not just take a message.

The first review call is where the deployment goes from "an agent" to "your agent." That's why we don't skip it.

Where the interesting conversation starts.

Week three is where customers usually say something like "okay, this is the north-star deployment — now what does the multi-line, multi-department version look like?" That conversation is the production engagement, and it's the one we're building the pilot to earn.

Ready to run the pilot? Book a demo, or see all three engagement models.