Auron on your phone
What the Auron app is for, how it splits work with the web console, and where to find each part of it.
Auron on your phone is built for the time you spend away from a desk. You open the record for the person or account you are about to deal with, start a voice call with an AI agent or a text chat, dictate a note afterwards, check what your automations did, and read back what Auron made of all of it.
The web console stays the place where agents, automation templates, entity types and organization settings are configured. The app uses those settings and creates the sessions, notes, posts and approval decisions that feed them. If a screen tells you to go to the browser, that is why. The full split is in What you do in the web console.
A typical run
You are on your way to a meeting. You open Auron, find the account in Jump back in on Home, and read the last two sessions on its record. You tap Call, pick the agent, and put the phone in your pocket while the agent listens and takes the transcript. Afterwards you switch the agent to Recap to get the action items read back, end the call, and dictate a voice note with the things you did not want to say out loud in the room.
By the time you are back in the car, the session has signals attached to it, the summary is in the feed, and the automation that fires when a meeting ends has drafted the follow-up and is waiting for you to approve the email. You approve it from the notification.
Nothing in that sequence needs the web console.
Where things are
Getting started
Which devices the app runs on, signing in with your domain, keeping more than one deployment on the same phone, and switching organizations.
Concepts
The words the rest of these docs use, and a map of the four tabs, the top bar and the menu.
Everyday screens
Home, the organization feed, Ask Auron, browsing records, who can see a record, your history, and how favorites are ranked.
Sessions
Voice calls and chats with an agent: agent modes, transcripts, attachments, the signals detected inside a session, and everything it produces.
Automations
The automations tab, what each one is configured for, running one on demand, reading its runs, and answering the approvals they pause on.
Voice notes
Recording with no agent present and no signal required, then asking for a transcript and summary when you are ready.
Research reports
Long-form reports about one record over a period, with a two-step setup you can save as a template.
Account and setup
Notifications, connected services, your profile, API keys, light and dark appearance, and the permissions the app asks your phone for.
Reference
What each role can do, when the app refreshes itself, what it keeps on the phone, and what stays in the web console.
What the app will not do
It is a companion to the console, not a replacement for it. You cannot create an agent, author an automation template, define an entity type, grant someone access to a record, manage members or read analytics dashboards from the phone. You can use all of those things once someone has set them up, and you can ask for an automation you cannot build yourself.