Professional services
Expert hands for the work you'd rather not do alone
Migrations, AI rollouts, integrations, and training — delivered by the team that builds Airclou. Scoped first, quoted in writing, and finished when your team runs it without us.
Fixed written quotes · No retainers · The people who build the product
When to bring us in
Airclou never requires consultants. Sometimes you want them anyway.
The product is built to be self-serve, and most teams go live without us. Services are for the moments where a second pair of hands is cheaper than a month of your own team's attention.
Most teams never need us
Setup, routing, SLAs, and rules are configuration, not a project. If the docs and standard support get you live, that is the outcome we prefer — services are an option, never a toll booth.
You work with the builders
No outsourced delivery bench, no certified-partner middle layer. The engineer on your engagement works on the product itself — and what they learn from your rollout feeds back into it.
Scoped before anything is owed
Every engagement starts with a scope call and ends that call with a fixed, written quote. No day rates, no open-ended retainers, and no work — or invoice — before you sign.
What we take on
Six kinds of engagement
Each is a defined outcome, not a menu of hours. Tell us which one sounds like your situation, and the scope call makes it concrete.
Migration & setup
Moving from Zendesk, Intercom, or Freshdesk without losing history. We map tickets, contacts, saved replies, and macros into Airclou's rules — and you approve the cutover.
AI agent rollout
Putting the AI agent to work with approval gates from day one: which tickets it touches, what it may do alone, and what always waits for a person. Autonomy is earned, not assumed.
Integrations & API work
Connecting Airclou to your billing, order, or internal systems — custom AI-agent actions, webhooks, and API builds — so tickets carry real account context instead of guesswork.
Workflow & routing design
Queues, teams, SLAs, business hours, and plain-language automation rules designed around how your support actually flows — not a template forced onto it.
Knowledge & training
Turning what your senior people know into a knowledgebase the AI can cite and Playbook SOPs the team can follow — then training everyone on the result.
Optimization reviews
A post-launch look at what the numbers say: where replies stall, which gates are ready to open further, and which automations would pay for themselves next.
How it runs
Five steps, and you hold the gate
Every engagement follows the same shape the product does: visible work, explicit approvals, and nothing irreversible without your sign-off.
Scope call
What you're moving, what must not break, and what done looks like.
Written quote
Fixed price, timeline, and scope — nothing starts until you sign.
Build
Migration, configuration, and integrations — in a workspace you can watch.
Go live
The cutover runs when you say so, with a rollback path agreed first.
You approveHandover
Training, documentation, and a team that runs it without us.
Common questions
What teams ask before the scope call
Do we need professional services to use Airclou?
No. Airclou is built to be self-serve — most teams set it up, migrate, and go live on their own with the docs and standard support. Services exist for teams that would rather hand the heavy lifting to us: a large migration, an AI rollout they want supervised, or integration work their own engineers should not have to own.
How is an engagement priced?
Every engagement is scoped first and quoted in writing as a fixed price for a defined outcome. There are no open-ended retainers, no day rates that drift, and nothing is owed until the quote is signed. If the scope changes mid-engagement, the quote is revised in writing before the new work starts.
Who actually does the work?
The team that builds Airclou. We do not resell engagements to a delivery bench or certify third parties to work under our name — the person configuring your workspace or writing your integration is an Airclou engineer. If an agency you already trust runs your rollout instead, that is our partner program, and we support it.
How long does a migration take?
Most helpdesk migrations — tickets, contacts, saved replies, automation rules — land within two to four weeks from signed quote to gated go-live, depending on volume and how much workflow redesign you want along the way. The scope call ends with a written timeline, and you approve go-live explicitly; nothing switches over behind your back.
What happens after handover?
The engagement ends with your team running the workspace, not depending on us. You keep standard product support like every customer, and the documentation we write during the engagement stays yours. If you later want another pair of hands — a new channel, a deeper AI rollout — that is a new scoped quote, not a subscription you forgot to cancel.
Start with a scope call
Tell us what you're moving
A migration, an AI rollout, an integration your team shouldn't have to own — describe it in a few sentences and we'll come back with questions, then a fixed written quote. A person reads every message.
Scoped first · Quoted in writing · Nothing owed until you sign