# You said yes. Here is exactly what happens before you go live.

URL: https://callhush.com/getting-started
Last updated: 2026-10-28

A dated, sourced timeline for what happens after you say yes: kickoff call, script approval, number provisioning, the carrier warmup every new line needs, the opt-in-form check, platform qualification, and the webinar cycle that runs as the pilot itself.

**Getting started is a fixed sequence of steps, not a project.** A kickoff call, script approval, a number provisioned in your name, a mandatory carrier warmup on that number, a check of your opt-in form's wording, one question about which webinar platform you run: and then your very first webinar cycle runs as the pilot itself.

Most of the calendar time belongs to a carrier's own clock, not to us or to you. The honest answer to “how long” is closer to a month. The honest answer to “how much of my time” is a handful of decisions, spread across that month, not a project plan.

## How much of my time does this actually take?

Not a project plan with a Slack channel and a weekly stand-up. Almost everything below is ours to run: provisioning the number, pacing its warmup, wiring the script into the thread. What is genuinely yours is a short list of decisions, and each one is a single sitting, not an open-ended task:

- **One call.** The kickoff, where we confirm your registrant volume, your webinar cadence, and who has the authority to sign off on wording.
- **One script sign-off.** You read the exact language your registrants will see, line by line, and approve it in writing.
- **One form review.** You (or whoever can edit your registration page) make the wording change we flag, once.
- **One fact.** Which webinar platform you run, so we know what is technically possible before we build anything around it.

> **What we are not asking you to do:** Learn a new dashboard, write a script from scratch, manage a number, or watch a warmup ramp day by day. None of that is your calendar's problem: it is ours.

## What actually decides how long this takes?

Not our build speed. Three numbers govern the calendar, and only one of them is ours to set:

- **~21 days**: Typical carrier warmup a brand-new number needs before it can carry a full launch without reading as automated traffic (industry vendor warmup schedules; CallHush research note)
- **6**: Specific things your opt-in form has to say before anything can send: not pre-checked, clearly disclosed, seller named, artificial voice named, among them
- **1**: Webinar cycle: the length of the pilot itself, priced on the kickoff call

The 21 days is the one nobody controls, including us. A number that has never sent anything cannot text a thousand people the same message on day one without looking exactly like the automated, non-consumer traffic carriers are built to catch. So it starts small, a handful of genuinely varied, reply-seeking messages a day, using the script you've already approved, and ramps in stages before it can carry a real launch. Everything else on this page happens inside that window, not after it.

## What do we need from you before anything can send?

Four inputs, and none of them is a technical task. The opt-in form review is the one worth taking seriously rather than rubber-stamping: it is the single artifact everything else in this relationship rests on, not a formality:

- **Script sign-off.** Every line, in writing, before the number sends anything. Full wording is on [what it says](https://callhush.com/what-it-says).
- **Opt-in form access.** Whoever can edit your registration page makes the wording change we flag, itemised in full on [what your opt-in form must say](https://callhush.com/compliance/what-your-opt-in-form-must-say).
- **Which platform you run.** Compared in full on [does this work on my webinar platform](https://callhush.com/platforms).
- **Rough registrant volume per cycle.** So the number is sized correctly and the warmup clock finishes in time for a real launch, not a small test.

The form review matters because consent, once captured correctly, has to keep working long after the kickoff call is forgotten:

- **10 business days**: SLA to honour a revocation once the system is live, regardless of the consent already on file
- **8am–9pm**: Calling-hours window enforced in the registrant's own local time: a mechanic consent does not override
- **Per client**: How consent is captured and retained: never pooled across clients, never reused for a different seller

## What happens, step by step, from kickoff to your first live cycle?

1. **Day 0: the kickoff call**: We confirm your registrant volume, your webinar cadence, and who has the authority to sign off on wording. The script and the registration form both need one named owner before anything else moves.
2. **Script approval, before the number sends anything**: You see the exact language, line by line, including the opening line that says it is an assistant. Nothing about the micro-commitment gets approved in the abstract: it is approved as the literal words your registrants will read. Full wording is on What It Says.
3. **Number provisioning, one per client**: We provision a number in your name specifically. It is never shared or pooled across clients: the same rule that governs your opt-in language governs the number itself: one seller, one line, no reuse.
4. **The carrier warmup clock starts (about 21 days)**: The number can't start warming on placeholder text: it needs your approved script's actual, varied language, because a warmup ramps by sending genuinely conversational copy, not filler. This is the one step that runs on a clock nobody controls, and it's why the honest answer to 'how long' is weeks, not days.
5. **The opt-in-form check, running alongside the warmup**: While the number warms, we check your registration page's consent wording against the six things it actually has to say. Full checklist on What Your Opt-In Form Must Say.
6. **Platform qualification, one question that changes what's on the table**: Which webinar tool you run decides what's technically possible before we build anything around it. We ask this on the kickoff call so nobody discovers a platform limit after paying for it. Full comparison on Does This Work On My Webinar Platform.
7. **Your first cycle runs as the pilot itself**: Once the number has cleared its warmup and the form is fixed, the first webinar you run with us is not a soft launch. It is the pilot: your registrant list split 50/50, one cycle, priced on the kickoff call. Full mechanics on The Pilot.

What follows is the same readout described on [the pilot](https://callhush.com/pilot) page: one document, whichever way the numbers land. Nothing above closes the leak between registration and the sale by itself; it exists so that when the cycle runs, it runs on a warmed number, an approved script and a compliant form, not on hope.

## What do people assume about this timeline: and what's actually true?

*This timeline, assumption versus reality*

|  | What people assume | What's actually true |
| --- | --- | --- |
| What sets the timeline | Our build queue | A new number's own carrier warmup: about three weeks, starting the day it's provisioned |
| Can an existing number skip it | Yes, if it's already yours | Only if it was already carrying real, varied, two-way traffic before we touched it: idle isn't the same as seasoned |
| Your time cost | A multi-week project with milestones and check-ins | A handful of decisions, one call, one script sign-off, one form review, spread across weeks you're not tracking daily |
| What can happen in parallel | Nothing: everything queues behind the number | Script approval, the opt-in-form check and the platform question all happen inside the same three weeks the number is warming, not after it |

> **Skipping the clock is not a shortcut we offer:** We will not launch a client's full registrant list through an unwarmed number to hit an earlier date. A filtered or banned number mid-launch costs everyone more time than the three weeks it was trying to save.

Three pages fill in what this one deliberately keeps brief. The exact wording your registrants will read is on [what it says](https://callhush.com/what-it-says), the statistical case for why the first cycle is split 50/50 is on [the pilot](https://callhush.com/pilot), and the six things your registration form has to say before any of this can send are on [what your opt-in form must say](https://callhush.com/compliance/what-your-opt-in-form-must-say). If you already run webinars and want to know what's technically possible on your specific platform before booking a kickoff call, start with [does this work on my webinar platform](https://callhush.com/platforms). When you're ready, [book the kickoff call](https://ainora.lt/contact?from=callhush).

## Frequently asked questions

### Can the pilot start before the number finishes warming up?

No. Sending a full registrant list through a number that has not earned three weeks of real, varied traffic first is the exact pattern carriers are built to catch, and a filtered or banned number mid-launch is a worse outcome than a later start date. We would rather push the date than gamble the number.

### I already have a business texting number: can we skip the warmup?

Only if it has already been sending genuinely varied, two-way traffic at something close to that volume before we touch it. A number that has been sitting idle, or that has only ever carried one-way blast reminders, has not earned anything a carrier would recognise as consumer-like behaviour. It starts the clock the same as a brand-new one.

### What exactly do you need from me, personally?

Three sign-offs and one fact: approval of the exact script, word for word, including the line where it says it is an assistant; approval of the wording change we flag on your opt-in form; confirmation of which webinar platform you run; and roughly how many people register per cycle, so the number gets sized correctly. Provisioning, warmup pacing and the technical wiring are ours.

### Does the timeline get longer if I run more than one webinar a month?

The warmup clock moves for time, not for volume. Once a number has cleared its three weeks it carries every subsequent cycle without waiting again, so the wait happens once, at the start of the relationship, not before every cycle after it.

### What if my webinar platform does not support everything?

Then you hear that in the kickoff call, not after signing anything. A live mid-session drop-off signal exists as a genuine real-time event on very few platforms and does not exist at all on most of the popular evergreen tools: that is a platform limit, not a service tier, and it is exactly why platform qualification is one of the first questions we ask. Full comparison on Does This Work On My Webinar Platform.

### When do we agree on price?

On the kickoff call, before anything above gets scheduled. CallHush is priced individually after a call, and a pilot on your own list comes first. No figure is published on this page or anywhere else on this site (see How Pricing Works), and you get the actual number the moment you ask, not after we have heard your ad spend.

### Is the first cycle really the pilot, or is there a separate setup month first?

Really the pilot. There is no dummy cycle that does not count. The first webinar your registrants get texts and calls for is split 50/50 and measured exactly as described on The Pilot. Everything above happens first only so that cycle runs on a warmed number and a compliant form, not on hope.

---

CallHush is operated by AINORA, MB (Vilnius, Lithuania). Book a call: https://ainora.lt/contact?from=callhush