What Happens in the First 30 Days of a Managed Enquiry Workflow

Most businesses that enquire about a managed service ask some version of the same question before signing up: "What actually happens?" They want to know what the setup process involves, what it feels like when it is running, and whether they will know it is working. The question is reasonable. The lack of a clear answer from most providers is not.

This article is a concrete, week-by-week account of what the first 30 days with a managed enquiry workflow look like in practice. No abstractions — just what happens, in order.

In short: The first 30 days break into three phases: setup (days 1–7), calibration (days 8–21), and first results (days 22–30). By day 30, the workflow is running, you have seen the first qualified leads, and you have enough data to decide whether to expand.

Days 1–3: knowledge base and setup

The first thing that happens is a structured intake session — usually a 45-minute call. The goal is to extract everything the workflow needs to know to represent your business accurately: the services you offer, the areas you cover, how pricing works (or whether you price at consultation), what the next step looks like for a new enquiry, and what categories of message should always come to a human rather than being handled by the workflow.

This produces the draft knowledge base: the approved information the workflow draws from when responding. You review it. You correct anything that is off. You add anything that is missing. Most knowledge bases go through one round of revisions before sign-off — the first draft is usually 80–90% right, and the session surfaces the edge cases.

By day three, the knowledge base is approved and the workflow is built. Nothing has gone live yet.

Days 4–7: pre-launch testing

Before any real enquiries are handled, the workflow is tested internally. Several realistic enquiry scenarios are submitted — a standard new client enquiry, a pricing question, an out-of-hours contact, and at least one that should trigger human review. The responses are reviewed against the knowledge base and refined where needed.

This is the stage that separates a managed service from a self-serve tool. The testing is done by the team running the workflow, not by you. If anything produces an answer that does not match your business accurately, it is caught here, before a real enquirer sees it.

By day seven, the workflow is tested, approved, and live across the agreed channels — website form, email, direct message, or whichever combination is relevant to your business.

Days 8–14: first live responses

The first week of live operation is the most instructive. Real enquiries arrive and receive real responses. You receive a copy of every response alongside the enquirer's message, so you can see exactly what the workflow is saying on your behalf.

In most cases, the responses are accurate and appropriate from the start. Occasionally something in the first live week reveals a gap in the knowledge base — a question type that was not anticipated, a service detail that needs more precision, a scenario that the testing did not cover. These are updated within 24 hours of being flagged.

You will also start to see the timing data: when enquiries actually arrive, which is often different from when the business assumed they arrived. Most businesses discover that a significant proportion of their contacts come in outside 9am–5pm — sometimes more than half.

Days 15–21: calibration

The second and third weeks are quieter from your perspective. The workflow is handling enquiries, the responses are going out, and qualified leads are being passed to you in structured form. The team running the workflow is reviewing the edge cases — anything that went to human review, any feedback from the knowledge base that suggests a refinement.

By day 21, the workflow has handled enough real enquiries to have a clear picture of the common query types, the response patterns, and where the knowledge base is strongest. If any recurring question is not being handled quite right, it gets addressed in this window.

This is also when the first follow-up sequences start running. Enquiries from week one that have not yet converted receive a well-timed check-in — polite, relevant, and sent without anyone having to remember.

Days 22–30: first results

By the end of the first 30 days, you have data you did not have before: total enquiries captured, response times (including the ones that arrived at midnight and were answered within minutes), leads qualified and passed to the team, and the first pipeline of follow-ups in progress.

Most businesses at this stage report the same experience: the team is spending less time managing the inbox, the leads arriving for human attention are warmer and better-qualified, and the out-of-hours window — previously a black hole — is producing contacts that would simply have been missed.

At day 30, the standard next step is a review. You see the data, you discuss what worked and what could be refined, and you decide whether to expand the workflow to additional channels or add a second workflow for a different process — onboarding, follow-up, or maintenance.

What the 30-day pilot is actually for

The pilot period is not a trial to convince you the product works. It is a calibration period to ensure the workflow is accurately configured for your specific business before any long-term commitment is made. The service is month-to-month: if after 30 days the data does not show a clear return, you stop. If it does — which it usually does — you continue and expand.

The guarantee is concrete: if the workflow is not live within seven business days of your sign-off, the setup fee is refunded in full.

Frequently asked questions

How much time does the setup require from me?

The main time commitment is the initial intake session — typically 45 minutes. After that, a single review of the draft knowledge base (usually 20–30 minutes). Once live, the workflow runs without requiring your involvement unless you want to make a change or provide feedback.

What do I need to have ready before starting?

A clear description of the services you offer and the areas you cover. Your pricing approach (published, range, or consultation-only). Your preferred process for a new client — what should happen after an enquiry arrives. Any categories of enquiry that should always come to a human. Everything else can be worked out in the intake session.

Will the workflow sound like my business or like a generic AI?

The knowledge base is written in your business's voice and approved by you before going live. The tone, the specific details, the way your services are described — all of this comes from you. What the workflow provides is the consistency to apply that voice at 10pm on a Sunday as reliably as at 11am on a Tuesday.

What happens at the end of the 30-day pilot?

You receive a summary of the 30-day data — enquiry volume, response times, qualified leads passed to your team, and any notable patterns. You then decide whether to continue. There is no auto-renewal and no pressure — the data either makes the case or it does not.