The questions you would ask on the call.

No, and any document telling you otherwise is one you should not sign. Income is earned against work delivered and verified on the board, priced on a published unit card, and it varies with allocated volume, your quality score and the USD rate on settlement day.

What we commit to in writing is allocation: billable volume within 45 days of go-live, or the setup fee is credited back pro-rata against the shortfall. That commits us to giving you work. It does not commit us to a number on your bank statement.

After. Every income figure on this site — ₹57,000 at ramp, ₹1,24,000 at standard, ₹2,06,000 at extended — already has the licence, VPS, AI consumption, telephony and compliance cost taken out. The gross payout, the USD unit card and the full cost breakdown are all published on the meter so you can check the arithmetic yourself.

Nothing, most nights. The crew works the queue and everything it cannot decide is waiting in your review lane when your supervisor starts their ordinary day.

The exception is a safety flag. Safety AI classifies it, collates the trip record and both parties' history, and calls your out-of-hours rota. A named person answers within sixty seconds and decides everything from there. Expect a handful of these a month, and expect most of them to turn out to be nothing — the classifier is deliberately over-sensitive, because there is no acceptable rate of missed flags.

Yes. If you cannot sustain the safety rota, allocation is withdrawn without a remediation window and your running cost continues. If the review lane is not cleared, the score falls and allocation reduces. If the rupee strengthens sharply against the dollar, your income falls without anything on the desk changing. The setup fee is capital at risk in the ordinary commercial sense — it is not a deposit and it is not protected.

You do, between statement date and settlement. The unit card is denominated in USD and every INR figure on this site converts at a ₹95 planning basis. If the rate moves against you between the statement being issued and the money landing, that difference is yours. It cuts both ways, and over a twelve-month term it has historically been a few per cent in either direction — but you should model it rather than assume it away.

Because the failure mode is not a bad customer experience, it is a person in danger. Safety AI is bound to no reply tool and no closure tool — it physically cannot answer an incident, and there is no configuration setting that would let it. It triages, collates and hands over. That limit is in the action handler, not in a prompt, so it cannot be argued past by a persuasive message or a clever instruction.

Akontec. The operator contract, pricing and commercial relationship stay with Akontec throughout. Your company delivers the support and is paid for it. This is stated in the brief, in the agreement and here, so it cannot become a dispute later.

No. It sits alongside it, consuming no floor space and no headcount beyond one supervisor and a light rota. Most partners run it as a second line while conventional campaigns continue unchanged — and use it as the AI capability they can show existing clients.

One experienced team leader on ordinary hours, plus two or three people rotating the out-of-hours safety phone. A full-time supervisor from agent 16 onward. That is the whole human requirement — no shift roster, no dialler, no floor.

That is the operator's disclosure policy, not ours, and it differs by market and by channel. What is fixed is that every message a rider or driver receives has been released by a named person in your desk, and that the crew never claims to be a human being. Where an operator requires explicit AI disclosure, it is encoded in the spec at station one.

The crew consumes model capacity as it works, so cost moves with volume. It is a prepaid balance, visible on the board at all times with the burn rate and a per-charge ledger on screen. At ten agents it runs around ₹24,000 a month at standard band. You top it up on the board and can stop the crew at any moment.

Yes, and you should. A fifteen-minute ride-along on a live desk shows the queue moving, the review lane filling, and Safety AI raising a flag and then refusing to touch it. Bring your operations head.

Ten is the minimum viable crew for 24/7 cover across six streams. Below that, streams go uncovered at exactly the hours this run exists to cover. If capital is the constraint, ask about the structured pilot for early partners when you book.

Rule changes are versioned updates to the spec, pushed to your crew and re-benched before they take effect. There is a lag between an operator changing something and the spec catching up — during that window the affected ticket type reverts to draft-only and lands in your lane.

Yes, and most desks do at standard band and above — often across different markets. Fare structures, policy sets, city knowledge and rider data are kept strictly separated, enforced at the desk level rather than by convention, so one operator's rules can never surface in another's answer.

No. It is a business services engagement. The setup fee purchases infrastructure, licensing, training and onboarding — deliverables listed in the agreement schedule. Income is consideration for services delivered. Nothing here is a security, deposit, chit or collective investment scheme, no funds are pooled, and no return is assured.

Initial term 12 months, then 60 days' written notice either side. Allocation is wound down on an agreed schedule so no operator is left without a desk overnight. Final income settles against the last verified month, desk data is exported to you and then purged, and the licence closes on the exit date.

You invoice Akontec monthly in arrears against the statement, issued alongside the scorecard. Your running charges are billed separately. GST applies at prevailing rates, and the foreign inward remittance arrives to your company account.