Skip to content
Akontec AI logoAKONTECAI Automation
Questions

The twenty questions clients actually ask

About ownership, accuracy, cost, language, speed and leaving. If yours is not here, register and ask it — a solutions lead will answer it personally.

  • No. We build around your existing stack and connect through APIs, webhooks, database views, email or file drops — whatever you already have. Replacing a system is a separate decision and we will not bundle it into an automation project to inflate scope.

  • You own your data, your process logic and the configured workflows built for you. Akontec retains its own reusable platform components and domain templates. This split is written into the MSA before work starts, not argued about at exit.

  • Three layers. High-risk actions never execute without a human. Supervised actions are sampled weekly by QC — 200 decisions re-checked at random. And every decision is logged with the inputs that produced it, so an error can be traced, corrected and guarded against rather than argued about.

  • As a prepaid operating balance. The provider's charge appears at cost and our operations fee of 15% appears as a separate line. Your balance, burn rate per hour, spend today and a per-charge ledger are visible in the dashboard, and you have a hard stop control. High-volume operations can switch to outcome billing instead, where you pay per resolved unit and the model cost is our problem.

  • Yes — English, Hindi and Tamil are standard, and additional language packs are a priced add-on. Voice quality varies by language and dialect; we test on your own recordings during the pilot rather than promising it in advance.

  • Fifteen days from signed scope to a first pilot agent on the Pilot package. Six weeks to a working department automation on Launch. Ten weeks for a full fleet on Operate. The clock starts at scope lock, and it depends on how fast we get system access.

  • No. Your data is processed to perform the task and is not contributed to model training. Retention is limited to the decision log and whatever your own compliance policy requires. Data residency and on-premise deployment are available on the Enterprise package.

  • Yes, and we often do. Akontec runs a delivery-partner network, so multi-party engagements are normal for us. Responsibilities are set out in a three-party table before build so nobody discovers a gap during an incident.

  • Thirty days' notice on the services agreement after the three-month minimum term. You keep your data export, the decision log and the configuration documentation. There is no exit fee and no hostage clause.

  • An hour for the discovery call, a named process owner, read access to the systems involved, and a sample of real work — a hundred tickets, orders or documents is usually enough to size the job properly.

  • A workflow moves work between systems along a defined path. An agent makes a judgement — which reply, which price, which classification. Most engagements use both: the workflow carries the volume, the agent handles the decisions, and the exception queue catches what neither should decide alone.

  • Yes. Every agent has a pause control in the dashboard, and consumption has a separate hard stop. Pausing an agent stops it immediately and routes its queue to the human review desk rather than dropping the work.

  • It depends entirely on the task, and any figure quoted before we have tested on your data would be a guess. We set a measured accuracy benchmark during the supervised pilot, sample 200 decisions a week against it, and demote any agent that falls below it to draft-only.

  • Because a hidden price usually means the number depends on how much the buyer looks like they can pay. Publishing lets you size a business case before speaking to anyone and starts the conversation at scope rather than price discovery.

  • The build is a one-time fee. The run and management plan has a three-month minimum term, then thirty days' notice on either side. There is no lock-in beyond that and no exit fee.

  • We design fallbacks, retries and degraded modes, and we monitor them. Work queues rather than disappears, and the exception desk picks up what cannot wait. What we cannot do is guarantee a third party's uptime, and we will not pretend otherwise.

  • Yes, on the Enterprise package, and as a priced add-on from ₹2,50,000 on others. It is the right answer for regulated data or a strict residency requirement, and it costs more in both build and running than a shared environment.

  • That is what the Pilot package is for — one agent, one workflow, two integrations, thirty days of supervised running. Additional agents are ₹45,000 each and additional integrations ₹15,000, added at any time by a signed change note.

  • No. Volume moves off the team, which usually means the same people handle more work or move to work that needs judgement. Where a role genuinely goes, we say so during discovery rather than after signature.

  • A free discovery call of about an hour. If AI is the wrong answer for your process we will tell you in that hour rather than in month three, and you are not committed to anything until Schedule A is signed.

Send us one process. We’ll tell you what it costs to automate it.

Register in two minutes. A solutions lead comes back to you with a fit check and the package we would recommend — no obligation until Schedule A is signed.