YOUNG/Client area
Already a client

Your operation is live.
Here is how we stay with it.

An AI running relationship in production is not a delivered project — it is an operation with a team behind it. This page says who to talk to, what we watch, and what happens when something breaks.

Three ways in

Who to talk to, depending on what you need.

01

Day-to-day with your squad

Adjustments, new cadences, copy changes and journey tuning go straight to the project lead and the specialists already on your operation. No ticket queue between you and the people who built it.

02

Something is wrong in production

Wrong answers, a channel down, an integration failing or a journey behaving unexpectedly: this is the path that jumps the queue, and it is the one we measure ourselves by.

03

Evolve the operation

New audiences, new journeys, another industry, another system to connect. This one usually starts as a conversation, not as a request.

What we watch, without being asked

Monitoring is part of the operation, not an extra.

  • ●Volume and response time per channel
  • ●Resolution rate and escalation rate
  • ●Sampled reading of real conversations
  • ●Integration health and event failures
  • ●Journey indicators against the agreed goal
When something breaks

Fix the cause, then tell you what happened.

Detection→Containment→Cause→Fix→Report

Because behaviour is traceable to a versioned playbook, an incident is corrected at the rule that produced it — for every client running that playbook, not only for the one who reported it.

What does not exist yet

No portal, no status page, no published SLA.

Support today runs through the squad on your project and through the commercial contact, not through a self-service portal. Response commitments are defined in each contract, and we would rather say that than publish a number we have not agreed with you. A status page and a client portal are the natural next step — when they exist, they appear here.

Already a client and need something?

Tell us the company, the operation and what is happening. It goes to the squad on your project, not to a generic inbox.