Call intelligence for teams that sell on the phone.

A call tracking dashboard is one screen that holds every call your team made, what was said on it, and what came out of it. Not a phone bill and not a pile of recordings: the call, the written transcript, the customer's details, what they asked for, what they objected to, and whether it became a lead. Auratel builds one from the calls your telecallers are already making on the handsets they already have.

Yes. Every call is transcribed and split by speaker, so you read it instead of listening to it. A twelve-minute call takes about forty seconds to read, and the details that matter, what the customer wanted, the quantity, the rate discussed, the objection, and what was promised, are pulled out and shown above the transcript as fields.

Samsung, Xiaomi, Redmi, POCO, Realme, Oppo, Vivo and OnePlus handsets all write call recordings to a folder Auratel can read. Pixel, Motorola and Nokia use the Google Dialer, which keeps recordings in private app storage that Android blocks every other app from reading, so those handsets cannot be used. That is confirmed on hardware, not guessed, and the full matrix is published on our phone compatibility page.

Yes, including the half-and-half sentences people actually speak on a sales call. Tamil, Hindi, Telugu and English are handled, and a sentence that starts in Tamil and finishes in English is transcribed as it was spoken rather than forced into one language. The fields pulled out of the call are the same either way.

Yes. Every call carries the telecaller who made it, and every lead carries the call it came from, so the dashboard reports conversion by person rather than call volume by person. Because the calls are written down, you can also read what the people who convert actually say, which is the part a call log can never give you.

Yes. A qualified call becomes a lead in your CRM with the fields already filled in, across eleven live connectors including LeadSquared, HubSpot, Freshsales and Pipedrive, plus plain webhooks, Zapier, Make and n8n for anything else. You map your own field names. If you do not run a CRM, Auratel has its own lead board and nothing else is needed.

Only the people in your organisation you give access to. Isolation is enforced inside Postgres by row-level security, on a database role that has no permission to bypass it, rather than by application code that has to remember to filter. A bug in a query cannot return another company's rows, and every access to your data is written to an audit log you can read.

Your telecaller does, out loud, at the start of the call, and waits for an answer. One sentence is enough: that the call is recorded, why, and is that alright. Auratel takes no part in obtaining it. There is no spoken notice in the app, no field that stores the customer's yes or no, and no way for the software to refuse a call. What the console can tell you is whether your telecaller disclosed the recording, per call and as a percentage per person, so you can supervise your own floor. That is a model's reading of the transcript rather than proof, and it says what your telecaller said, never what your customer agreed to. Under the DPDP Act the business making the call is the Data Fiduciary, so obtaining consent, and any consequence of not obtaining it, rests with you and not with us.

Auratel is built to meet India's Digital Personal Data Protection Act, 2023, and the division of duties it sets out: you are the Data Fiduciary and Auratel is the Data Processor, processing your recordings on your instructions and for nothing else. On our side that means the database runs on our own servers in Mumbai, isolation is enforced by Postgres row-level security on a role that cannot bypass it, recordings are deleted when your retention window runs out, erasing a call cascades through the transcript, fields, lead and CRM record and returns a signed receipt, and access is written to an audit log. Consent is the part that stays with you, because it happens on a call we are not party to.

As long as your organisation's retention setting says and no longer. It defaults to 90 days, it is yours to change, and a scheduled job deletes the audio, the transcript and everything derived from it when the clock runs out. You can also erase a single call: the recording, the transcript, the extracted fields, the lead and the CRM delivery record all go, and you get a signed receipt in your audit log.