Live in weeks, not quarters

Most dealership teams expect new software to drag on. Weeks turn into months, people lose track of what is needed, and go-live keeps slipping for reasons nobody can quite pin down.

That is usually not because setup is hard. The real delay is often WhatsApp approval, plus a few decisions that need to come from the dealership before anything can be switched on.

The good news is that the path is straightforward when everyone knows what happens next. From kick-off call to first message sent, success depends less on heavy technical work and more on getting the right details lined up at the right time.

What happens at kick-off

The kick-off call is where the project stops being a plan and starts becoming a working setup. This is where the dealership group and onboarding team agree the scope, the locations involved, the number to use, and what success looks like for launch.

It is also where expectations get set properly. If there is going to be any waiting, it is usually around Meta and WhatsApp approval rather than the platform build itself, so it helps to be clear about that from day one.

A good kick-off covers the basics first. Which sites are going live, who needs access, what inbox rules matter, what integrations are in scope, and which use cases need to work first, such as service enquiries, sales leads, aftersales updates or missed call follow-up.

This is also the point where dealership owners can make the project move faster by nominating one clear internal lead. When decisions sit with too many people, small questions can add days that have nothing to do with the setup.

What the dealership needs to provide

Most of the information needed is simple, but it does need to be accurate. A trading name, business details for verification, the phone number plan, user lists, and any preferences around routing, opening hours and templates all matter.

If the group wants to use an existing number, that needs checking early. If a new shared WhatsApp business number is being set up, that tends to be more straightforward, but either way the decision should happen near the start rather than halfway through.

Access matters too. If there is a DMS integration in scope, the right contacts need to be involved so credentials, permissions and testing can happen without back and forth later.

The dealership should also think about message tone before launch. Short, clear replies, sensible handover rules, opening hours, and what should happen out of hours all shape the first customer experience more than most teams expect.

None of this is especially heavy. Time goes when details are incomplete, approvals are sitting in someone else's inbox, or internal teams are still deciding how they want enquiries handled once messages start coming in.

Where the waiting time really is

This is the part that surprises people. Platform setup, user creation, inbox configuration and workflow planning can move quickly, but WhatsApp approval follows Meta's process and timeline, not the dealership's preferred go-live date.

That does not mean the project stalls. It means the smart approach is to use that waiting time well, so training, routing rules, templates, automations and internal sign-off are all ready before approval lands.

Business verification and number approval can be simple when the details match exactly. They can also slow down if company information is inconsistent across documents, if the wrong number path is chosen, or if approvals are started late.

That is why realistic onboarding conversations matter. Telling a dealership everything will be live almost immediately sounds good at the start, but it creates the wrong expectation if the one external step still has to happen.

Go-live is usually limited by approval, not by setup. The more prepared the dealership is before that point, the faster the first message can go out once approval comes through.

In practice, the best projects treat approval as a track running alongside setup, not after it. While one process is in motion, the rest of the onboarding can keep moving so launch does not depend on a last-minute scramble.

From setup to first working journeys

Once the foundations are in place, onboarding moves into practical configuration. Users are added, permissions are set, inbox views are organised, and the first customer journeys are mapped around how the group actually works.

This is where the dealership decides what needs to happen automatically and what should stay with the team. An initial reply can go out instantly, a lead can be routed to the right site, and certain enquiries can be booked or tagged without manual effort.

It is also where edge cases should be discussed. How should missed calls be handled, who gets messages for each franchise or site, what happens when a customer replies after hours, and when should a conversation move from automation to a person?

If there is a DMS connection, testing matters here. Contact records, booking flows and message visibility need checking so teams can trust what they are seeing once live conversations begin.

This stage does not need to become complicated. The best launches start with the journeys that matter most, get those right, and leave room to expand later once the team has real usage and real conversations to learn from.

That is one reason Fuzey projects can move quickly once the inputs are there. The work is usually about shaping a clear operating model, not building something from scratch for every site.

Training, testing and go-live

Before the first customer message is sent, the dealership team needs a short period of hands-on training. Not pages of theory, just enough to know where messages land, how to reply, how handovers work, and what good response standards look like.

Testing should mirror real life as closely as possible. Send messages in, trigger automations, check opening hours behaviour, confirm routing, and make sure users can do the simple things quickly without asking for help.

This is also the right moment to sense check ownership. If a customer asks about a booking, a part exchange or a service update, everyone should know who picks that up and how quickly, because go-live exposes gaps in process very quickly.

When approval is complete and testing is signed off, the first message can go out. For some groups that is a soft launch with a smaller set of locations or journeys first, and for others it is a wider release once the core setup has been proven.

A sensible go-live is not about turning on every possible feature on day one. It is about making sure customers get clear responses, the team feels confident, and the group has a strong base to build on.

How to keep the timeline short

If a dealership wants to be live in weeks rather than quarters, the biggest help is preparation. Decide early on the number strategy, gather the business details needed for approval, nominate an internal owner, and bring any integration contacts in before they become blockers.

It also helps to keep the first phase focused. Start with the use cases that will be used immediately, agree the routing and tone, and avoid turning onboarding into a long internal debate about every future possibility.

Most projects do not slow down because the setup is too technical. They slow down because decisions arrive late, ownership is spread too thinly, or external approval has not been accounted for in the plan.

That is why the most productive onboarding experience feels calm rather than rushed. Everyone knows what the dealership needs to provide, what the platform team is doing, and which part of the timeline sits outside either side's direct control.

By the time the first message is sent, the work should feel unsurprising. The team knows the inbox, the journeys make sense, and the only real wait should have been the one that usually is, WhatsApp approval.

For dealer groups that want to get started without turning onboarding into a long project, that clarity matters as much as the technology itself. Fuzey works best when launch is treated as a practical rollout with clear inputs, clear ownership and a realistic view of where time is actually spent.