Service Policy · Claping

Your automation
works.
What next?

We build the solution. We deliver it ready to run. And if you want, we keep watching it so it never stops.

Understand the policy ↓ See what’s included

scroll

The context

Automations are not static

They are like machines that depend on external parts. When a part changes, the machine needs adjustment.

🔌

APIs change

WhatsApp, Meta, Gmail, and any connected platform constantly updates its rules. An API change can break your flow without warning.

⚙️

Flows need maintenance

An automation that works perfectly today may behave differently tomorrow. Flows need active supervision to keep running correctly.

👥

Your team needs time to adapt

Integrating a new system into daily operations takes time. During that phase, specialized technical support on hand is critical.

📈

Your investment should be protected

Building an automation has a real cost. Without maintenance, that effort can become unusable because of a problem with a simple fix.

🏠

You build a house

The architect designs it and delivers it ready to live in.

🔧

But the house needs maintenance

Plumbing, electricity, paint. No one expects a house to maintain itself.

🛡️

The Policy is that maintenance

For your automation: we monitor it and fix it if something fails.

How to think about it

It is maintenance for your automation

When Claping delivers an automation, it is like receiving the keys to a complex, working system. But like any system connected to the digital world, it needs someone to look after it.

The Service Policy is that agreement: we take responsibility for keeping the automations we built for you running, month after month, without you having to worry.

What is covered

What the Policy does for you

Six concrete actions Claping performs actively during the service term.

Continuous monitoring

We actively watch your automations. If something starts to fail, we detect it before it impacts your operation.

Execution validation

We confirm that each documented flow and process runs correctly, within the defined times and conditions.

Fixes for external changes

If WhatsApp, Meta, or another connected platform changes its API and breaks your flow, we fix it. That is not your problem — it is ours.

Corrective maintenance

For any unexpected behavior within the delivered scope, we step in to restore correct operation.

Stability adjustments

We make small adjustments to keep flows efficient as the digital environment evolves. At no extra cost.

Specialized technical support

Direct access to Claping’s technical team to answer questions, review behavior, or handle one-off situations.

Minimum commitment

How we estimate your minimum commitment period

We estimate it based on how many workflows your operation has.

The more workflows you have, the longer the minimum support period required.

We count workflows

We identify how many real flows support your operation.

We measure complexity

We assess connections, validations, and critical points.

We define the commitment

The commitment grows with the size of your operation.

We tailor it to your case

We do not use a fixed term — we quote based on your real structure.

Scope

What is and is not covered

The Policy is clear and honest. It covers exactly what is documented in your quote.

✓ Covered INCLUDED

Monitoring of delivered automations
Error fixes due to changes in connected APIs
Execution validation of documented flows
Corrective maintenance within the agreed scope
Minor stability adjustments
Specialized technical support from the Claping team

✕ Not covered OUT OF SCOPE

New automations or additional features
Processes not documented in the original quote
Tools or platforms outside the agreed scope
Changes requested by the client outside the project
Third-party integrations not included initially

Frequently asked questions

What we hear most often

Is the Policy required to work with Claping?▾

No. The Service Policy is completely optional. When Claping delivers an automation, it runs on its own. The Policy is for companies that prefer to delegate maintenance instead of managing it in-house.

What happens when the minimum commitment period ends?▾

When the minimum commitment period estimated for your operation is complete, you decide whether to continue the Policy or end it. If you continue, the service stays active. If not, your automations remain yours and keep working within the delivered scope.

What is covered if WhatsApp changes its policies?▾

Exactly that: if WhatsApp, Meta, or any other platform connected in your project updates its API and that affects your flows, Claping makes the necessary fixes at no extra cost. That is one of the main benefits of the Policy.

Can I request new features while the Policy is active?▾

New features or additional automations are not included in the Policy. They are quoted separately as a new project. The Policy covers only what was already delivered and documented.

How long does Claping take to respond if something fails?▾

Claping’s technical team handles failure reports with priority during service hours. Specific response and resolution times are defined in the Policy contract according to the plan purchased.